Errors starting snmpd after upgrade from 11.2 to 11.3

English Install/Boot/Login
1

Hi,

after upgrading from openSuse 11.2 to 11.3 some of my servers showing these errors after starting snmpd:

Starting snmpdError: Line 278: Parse error in chip name
Error: Line 283: Label statement before first chip statement
Error: Line 284: Label statement before first chip statement
Error: Line 285: Label statement before first chip statement
Error: Line 286: Label statement before first chip statement
Error: Line 287: Label statement before first chip statement
Error: Line 288: Label statement before first chip statement
Error: Line 289: Label statement before first chip statement
Error: Line 322: Compute statement before first chip statement
Error: Line 323: Compute statement before first chip statement
Error: Line 324: Compute statement before first chip statement
Error: Line 325: Compute statement before first chip statement
Error: Line 1073: Parse error in chip name
Error: Line 1094: Parse error in chip name
Error: Line 1104: Parse error in chip name
Error: Line 1114: Parse error in chip name
Error: Line 1124: Parse error in chip name

It happens on the x64 and i586 plattforms. all hardware are hp proliant servers. any idea?

Additionally some of the serves with 11.3 are freezing after 1 oder 2 day with no errors in the log. then i can not log in (console and ssh) but ping is o.k. any ideas for that behavior?

bye
Daniel

2

firewalldo wrote:

> It happens on the x64 and i586 plattforms. all hardware are hp
> proliant servers. any idea?
>
> Additionally some of the serves with 11.3 are freezing after 1 oder 2
> day with no errors in the log. then i can not log in (console and ssh)
> but ping is o.k. any ideas for that behavior?

I’ve just yesterday logged a bug report for exactly the same problem
(also on a proliant server).

http://bugzilla.novell.com/show_bug.cgi?id=626253

Wrt snmp, check to see which snmp libary version you’ve got - 11.3 comes
with 2.0, but the HP PSP pack still requires 1.5.

–
Per Jessen, Zürich (18.4°C)
http://en.opensuse.org/User:pjessen

3

i’ve got libsnmp20 on all servers, but the problem is not on all servers (with same hardware). very strange!

btw, freezing of systems has stopped since friday…

bye
Daniel

4

I can ssh from konsole or terminal
fish from konq or dolphin

but not sftp in konsole, terminal, K or D

My report:
https://bugzilla.novell.com/show_bug.cgi?id=627323

5

Hi,

I noticed the same problem, after doing a live update of 11.2 to 11.3

  1. I found the following after upgrade there were two files in etc
    /etc/sensors.conf
    /etc/sensors3.conf

and check showed two different version of libsensors??
rpm -qf /etc/sensors.conf
libsensors3-2.10.6-46.2.x86_64
rpm -qf /etc/sensors3.conf
libsensors4-3.1.2-7.1.x86_64

  1. tried the following:
    2.1) zypper remove libsensors3
    2.2) zypper remove libsensors4 <<<<did remove lots of things, for me were irrelevant as it is a server
    2.3) but that removed net-snmp and perl-SNMP too :cry:
  2. installed …
    zypper install net-snmp perl-SNMP
  3. restarted snmpd no more erros… :wink:

Hope that helps!!

Regards,

BP

6

Thanks for your suggestions, I fixed it on my system by removing just libsensors3 - turns out it was a leftover package from 11.2

I think I’ll do a more general search for 11.2 packages. :wink:

John.

7

I hit the problem with a clean install of OpenSUSE 11.4 and an older /etc/sensors.conf.

Seems to be a problem with /usr/sbin/snmpd trying to parse /etc/sensors.conf. If there are any chip names with two dashes in the name, e.g. ‘chip “lm78-j-*”’, then snmpd spits out the “Parse error in chip name” error followed by “Label statement before first chip statement” (because it didn’t parse the chip statement line) followed by the other errors.

Removing /etc/sensors.conf fixes the problem with snmpd, and since OpenSUSE 11.4 ships with /etc/sensors3.conf, which is used by sensors before /etc/sensors.conf, removing /etc/sensors.conf doensn’t hurt the operation of sensors.

8

FWIW, removing chip names with two dashes from /etc/sensors.conf also fixes the problem, which means that an even better fix would be to fix snmpd so it can parse chip names containing two dashes.