Bug 153952

When does this happen exactly (installation sys, installed system, recue-system), which networking method did you choose (NetworkManager or traditional), add information about your network devices (ifconfig), all files in /etc/sysconfig/network an if this was set up with YaST or during the installation the y2logs in /var/log/YaST2.

Created attachment 70717 [details]
Current y2log

Created attachment 70718 [details]
additional y2log

Created attachment 70719 [details]
SuSE config

Michael I installed from a DVD to a brand new 80GB disc. System is 866MHZ, Intel PIII. 512 MB 2 80GB disc (hda XP, hdb Suse 10.0). Not sure which files you want from /etc/sysconfig/network, there are 7 files and 4 sub directories.

The first error about the network started recently. The one about subdoomains has been here since installation.Error occurs each time I boot my system. With apparmor disabled, I think the message goes away. I need it disabled, so Adobe Reader can open PDF files. I have not had time to look at this.

Linux linux 2.6.13-15.8-default #1 Tue Feb 7 11:07:24 UTC 2006 i686 i686 i386 GNU/Linux, kde 3.4.2 level b.

ifconfig:
eth0      Link encap:Ethernet  HWaddr 00:09:5B:0A:20:A3
          inet addr:192.168.2.35  Bcast:255.255.255.255  Mask:255.255.255.0
          inet6 addr: fe80::209:5bff:fe0a:20a3/64 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3452 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3346 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1837756 (1.7 Mb)  TX bytes:1849902 (1.7 Mb)
          Interrupt:5 Base address:0x4000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:69 errors:0 dropped:0 overruns:0 frame:0
          TX packets:69 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4379 (4.2 Kb)  TX bytes:4379 (4.2 Kb)
Not sure about netmanager, what ever the default for installation was used. I have a belkin router hooked to a fiber network (100MB). network card is Netgear FA311/FA312 (FA311 with WoL HW) DHCP

If i can provide any other info or run any tests let me know.
Thanks for your help.

> Not sure which files you want from /etc/sysconfig/network, there are 7
> files and 4 sub directories.

Attach the directory as tarball.
Forget the question about the networking method, in 10.0 there was no NetworkManager ;)

Attach the _whole_ /var/log/YaST2 directory, too. Thanks.

Created attachment 71055 [details]
YaST2_Logs

Sorry I took so long to get this to you. I was out of town yesterday. Also i'm just learning how to use tar, etc.

Here's the YaST2 log files. Some how I lost -6 and -7 but they were older. Also I notice these are owned by root and I had to log on as root to create this. If I need to change the owner and recreate it let me know, I have copies of them.

Before I reassign this I need some more information:

From comment #0
> donecat: /var/run/sysconfig/network: No such file or directory

How ecactly did you configure your network cards? During the installation with YaST, etc. Did the error happen instantly, did you change something? I have to figure out whether this is a problem with YaST or another component.

Network card was configured automatically during installation from DVD purchased from Novell. I have not changed anything in the network that I'm aware of. I have enabled and disabled apparmour, right now its enabled. This meeans Adobe Reader will not open pdf documents. Says permission denined. Only profile I have found for Adobe in apparmor is /usr/X11R6/bin/aeroread. At least thats the only one that shows up under apparmor/edit profiles in YaST.

Network card info from YaST:
Netgear FA311 / FA312 (FA311 with WoL HW)
Device Name: eth-id-00:09:5b:0a:20:a3

Anything else I canprovide you?
Thanks again for your continued help.
IP address assigned using DHCP
Started automatically at boot

Let's start with the assumption that something was wrong during the network configuration in YaST. Martin: Please have a look at this. If this is not a YaST problem, assign it back to us.

The network configuration had already rotated out of the logs.
Russ, please attach the result of 
tar cvfz ~/sysconfig.tgz /etc/sysconfig/network /etc/sysconfig/hardware

Anyway, comment 0 suggests it is a sysconfig problem.

First of all, please file a seperate bug report for the AppArmor problem.

To the network problem:
Initial omment looks very curious. Normally renetwork start writes the current time in seconds into /var/run/sysconfig/network. It does that before processing the code around line 467. And you write that /var/run/sysconfig/network exists and would contain a number higer then this in the rcnetwork error message. This looks like rcnetwork would run twice.

In comment 5 you wrote:
  "The first error about the network started recently."
That looks like you changed something (by accident)

Can you reproduce the problem with running
  rcnetwork stop
  rcnetwork start -o boot

Forget the requested tarball from comment 11. Please instead attach this:
 - tar cvfz ~/sysconfig.tgz /etc/sysconfig
 - tar cvfz ~/init.d.tgz /etc/init.d

I try the restart of the network later today and also send the Comment #12 info. with comments on the restart. Should be able to do it tonight.

I will also submit a new bug report on AppArmor. Thanks for your help. I don't think I changed anything but I have been have printer problem with CUPS and may have changed something somewhere when working on that.

Created attachment 72320 [details]
init.d info requested

heres my init.d info. below is result of rcnetwork commands. Not the above error message is not appearing now but my setting up of the network interface fails each time, then when I log on as user it is working with no problems. See below aslo.

Setting up network interfaces:
    lo        
    lo        IP address: 127.0.0.1/8   
doneWaiting for mandatory devices:  eth-id-00:09:5b:0a:20:a3 __NSC__
19 18 16 14 <notice>pidofproc: dhcpcd 3820
10 9 7 6 4 3 2 0 
    eth0                                interface could not be set up
failedSetting up service network  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .failed
done

Starting resource managerdone
<notice>pidofproc: dhcpcd 5573
Starting hpiod:                                            [  OK  ]

Starting hpssd:                                            [  OK  ]

Note: You may have to restart the cupsd.
Setting up network interfaces:
    lo        
    lo        IP address: 127.0.0.1/8   
done    eth0      device: National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller
    eth0      configuration: eth-id-00:09:5b:0a:20:a3
    eth0      (DHCP) . IP/Netmask: 192.168.2.35 / 255.255.255.0 
doneSetting up service network  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .done

l # rcnetwork stop
Shutting down network interfaces:
    eth0      device: National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller
    eth0      configuration: eth-id-00:09:5b:0a:20:a3                done
Shutting down service network  .  .  .  .  .  .  .  .  .  .  .  .  . done.

# rcnetwork start -o boot
Setting up network interfaces:
    lo
    lo        IP address: 127.0.0.1/8                                done
    eth0      device: National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller
    eth0      configuration: eth-id-00:09:5b:0a:20:a3
    eth0      (DHCP) . IP/Netmask: 192.168.2.35 / 255.255.255.0      done
Setting up service network  .  .  .  .  .  .  .  .  .  .  .  .  .  . done.

Still not sure how to submit multiple attachments so I'll send the sysconfig separate.

Thanks again for all your help!!

Created attachment 72322 [details]
sysconfig info.

Let me know if you need anything else. 

Thanks
Russ

Hello again, i was very busy with 10.1 in the last weeks.

You have start and stop links to service network in /etc/init.d/boot.d:
/etc/init.d/boot.d/K15network
/etc/init.d/boot.d/S10network
Remove them; they are wrong. 

Did you add these links there?

Does it work then?
If no, please set /etc/sysconfig/network/config:DEBUG=yes, reboot and attach /var/log/boot.msg

Created attachment 78310 [details]
boot message log - Debug off

Additional forgot to answer your question about adding entries to boot.d. NO I did not add them that I know of.

Not sure how I missed the comments I added to item 17. I reinstalled SUSE 10.0 two weeks ago after major printing problem. The error message mentioned above disappeared after that. Also on the log, item 17. there is an error message about not being able to start network card. But every thing on the internet works fine as soon as I log in.

Then everything works. It just takes a little bit longer as expected. rcnetwork waits a certain time for mandatory network devices, but not longer then   
  /etc/sysconfig/network/config:WAIT_FOR_INTERFACES
You may increase this value.

It would be nice to know where the links in boot.d came from. If this happens again, you may reopen this bug. For now i resolve it as invalid. There is no bug to isolate atm.