errors after upgrading procps [SOLVED]

ozar · 2005-06-30 15:58:44

System was running fine but after upgrading to the procps 3.2.5-2 package yesterday, I get about 9 error messages at system boot like the following:

error: "net.ipv4.conf.lo accept_source_route" is an unknown key

Other error messages appear regarding eth0 and kernel.sysrq

The system seems to be working fine, but I can't find these errors in the logs. Maybe I'm just missing them.

Anyone know what's causing this, or how to fix it?

Thanks in advance...

wdemoss · 2005-06-30 16:04:45

You are most likly using hotplug to load the necassary modules that the module parameters apply to. Since sysctl gets run before the daemons, this happens. The erros do not hurt anything. If you want to make the error messages go away add the modules to the MODULES array in /etc/rc.conf.

HTH,
wdemoss

rasat · 2005-06-30 16:30:28

I am not running hotplug and have the same errors. Was wandering what's the cause.

CyberTron · 2005-06-30 16:55:59

I too experienced these errors...not running hotplug (actually almost no modules at all)

lucke · 2005-06-30 17:19:49

Judd has added "default arch" sysctl.conf file to procps package. If you don't want to get those errors, just remove /etc/sysctl.conf or comment out offending lines in it (I guess all of them should work on stock arch kernel - in my case sysrq doesn't work, because I don't have it compiled in the kernel).

ozar · 2005-06-30 17:27:18

lucke wrote:

Judd has added "default arch" sysctl.conf file to procps package. If you don't want to get those errors, just remove /etc/sysctl.conf or comment out offending lines in it (I guess all of them should work on stock arch kernel - in my case sysrq doesn't work, because I don't have it compiled in the kernel).

I changed the name on the sysctl.conf file then rebooted and all seems to be working fine. Thanks for the tip, lucke! 8)

apeiro · 2005-06-30 20:06:20

Ah, sorry guys. Those errors are harmless, but i'll get em out of the way. It's because the sysctl variables are being loaded before your eth0 modules, so any eth0 variables are invalid at that point.

I'll move the sysctl stuff to rc.multi. That should shut them up.

apeiro · 2005-06-30 20:09:24

Errr, correcting myself.

The eth0 modules are loaded, but the interface itself hasn't been brought up yet. So sysctl complains.

pedantically yours,

- J

CyberTron · 2005-06-30 21:48:59

Ah, that clears things up

thanks J.

ozar · 2005-06-30 23:23:32

apeiro wrote:

Ah, sorry guys. Those errors are harmless, but i'll get em out of the way. It's because the sysctl variables are being loaded before your eth0 modules, so any eth0 variables are invalid at that point.
I'll move the sysctl stuff to rc.multi. That should shut them up.

Okay, thanks for the info, Judd. 8)

sweiss · 2005-07-01 09:03:54

Would this default configuration does something which does not happen without it?

I mean, I'm no networking expert, and I use Windows ICS to get my internet connection working. Should it harm anything?

tomk · 2005-07-01 09:40:58

apeiro wrote:

It's because the sysctl variables are being loaded before your eth0 modules

apeiro wrote:

The eth0 modules are loaded, but the interface itself hasn't been brought up yet.

I think there will be instances of both - e.g. my desktop's network module is loaded from rc.conf, my laptop's from hotplug.

Dreameen · 2005-07-02 09:58:03

sweiss wrote:

Would this default configuration does something which does not happen without it?
I mean, I'm no networking expert, and I use Windows ICS to get my internet connection working. Should it harm anything?

Yes it could break your internet connection. I was chatting on irc yesterday and 2 folks were unable to browse the net because of these entries in /etc/sysctl.conf. I told them to rename the file and wait for the next upgrade of procps, which hopefully will fix things up.

deft · 2005-07-06 11:11:16

Just a heads up really - I've just updated to procps 3.2.5-3 - all of the boot-up error messsages have disappeared execpt for this one:

error: "kernel.sysrq" is an unknown key

Just thought 'd mention it. Thanks for the work on clearing the rest of it up though guys.

dtw · 2005-07-06 11:13:05

don't worry about that - that's just means it is not enabled in your kernel AFAIK nothing serious

deft · 2005-07-06 11:15:32

Cheers Dib

deft · 2005-07-09 02:51:41

Interestingly, after just updating the kernel to 2.6.12.2-1 , this error message:

error: "kernel.sysrq" is an unknown key

has disappeared from the bootup messages - everything seems fine now.

Thanks all

ozar · 2005-07-09 03:27:23

deft wrote:

Interestingly, after just updating the kernel to 2.6.12.2-1 , this error message:
error: "kernel.sysrq" is an unknown key
has disappeared from the bootup messages - everything seems fine now.
Thanks all

Yeah, the kernel upgrade cleared that problem for me too, but now I have some new messages at system boot to deal with (posted about them in the kernel forum). These upgrades are giving me fits lately...

mdk · 2005-09-04 18:11:21

Well, it's a bit off topic but... -- why is the magic sysreq key removed from the kernel 2.6.13? I mean - it's there (source, makefile, etc.) but you can't enable it explicitly in the menuconfig->kernel hacking (it's simply not there).

I'd like to use the sysreq key as a final resort against the nvidia lock-up bug, which drives me totally nuts recently.

mdk · 2005-09-04 18:29:55

Oooppsss... shame on me. It IS there. I somehow... just missed it.

Arch Linux

#1 2005-06-30 15:58:44

errors after upgrading procps [SOLVED]

#2 2005-06-30 16:04:45

Re: errors after upgrading procps [SOLVED]

#3 2005-06-30 16:30:28

Re: errors after upgrading procps [SOLVED]

#4 2005-06-30 16:55:59

Re: errors after upgrading procps [SOLVED]

#5 2005-06-30 17:19:49

Re: errors after upgrading procps [SOLVED]

#6 2005-06-30 17:27:18

Re: errors after upgrading procps [SOLVED]

#7 2005-06-30 20:06:20

Re: errors after upgrading procps [SOLVED]

#8 2005-06-30 20:09:24

Re: errors after upgrading procps [SOLVED]

#9 2005-06-30 21:48:59

Re: errors after upgrading procps [SOLVED]

#10 2005-06-30 23:23:32

Re: errors after upgrading procps [SOLVED]

#11 2005-07-01 09:03:54

Re: errors after upgrading procps [SOLVED]

#12 2005-07-01 09:40:58

Re: errors after upgrading procps [SOLVED]

#13 2005-07-02 09:58:03

Re: errors after upgrading procps [SOLVED]

#14 2005-07-06 11:11:16

Re: errors after upgrading procps [SOLVED]

#15 2005-07-06 11:13:05

Re: errors after upgrading procps [SOLVED]

#16 2005-07-06 11:15:32

Re: errors after upgrading procps [SOLVED]

#17 2005-07-09 02:51:41

Re: errors after upgrading procps [SOLVED]

#18 2005-07-09 03:27:23

Re: errors after upgrading procps [SOLVED]

#19 2005-09-04 18:11:21

Re: errors after upgrading procps [SOLVED]

#20 2005-09-04 18:29:55

Re: errors after upgrading procps [SOLVED]

Board footer