syslog flooded

[wayne0206]

Appliance 21600
Gaia R77.10 with Jumbo 167
VRRP cluster
Blades: Firewall, IPSec VPN, IPS, Anti-Bot

one of the cluster member is constantly flooded with these messages in syslog regardless whether it's the primary or backup. PID 6228 is confd.

what could be causing this and how should I approach to resolve it? thanks in advance.

Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/in13_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/in16_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/in11_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/in15_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/in10_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/in5_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/in6_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/in7_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/in8_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/in9_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/in14_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/in12_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/in13_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/in16_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/in11_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/in15_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/fan6_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/fan5_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/fan8_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/fan7_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/fan10_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/fan9_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/fan2_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/fan1_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/fan4_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/fan3_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/temp6_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/temp7_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/temp1_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read
Dec 23 13:05:57 FW01 xpand[6228]: cannot open sysfs file /sys/class/hwmon/hwmon0/device/temp2_input ; skipping it
Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read

[wyndfx]

Dec 23 13:05:57 FW01 xpand[6228]: The value of sensor could not be read

Seems to be a known issue with hotfixes available throguh support:

"The value of sensor could not be read" error in /var/log/messages file and SNMP Traps about hardware sensors are sent repeatedly"
https://supportcenter.checkpoint.com...ionid=sk101898

I'd assume that the second message is somehow related, but a hotfix would be a good start.

[wayne0206]

Seems to be a known issue with hotfixes available throguh support:

"The value of sensor could not be read" error in /var/log/messages file and SNMP Traps about hardware sensors are sent repeatedly"
https://supportcenter.checkpoint.com...ionid=sk101898

I'd assume that the second message is somehow related, but a hotfix would be a good start.

I am aware of the bug mentioned in sk101898. this is a different issue. as I dig a bit deeper, I notice the gateway is missing a folder "hwmon0" in /etc/class/hwmon. this cluster pair was built identical and i am not sure how this happen. trying to find out whether i can copy this directory from the other cluster member.

[jflemingeds]

I am aware of the bug mentioned in sk101898. this is a different issue. as I dig a bit deeper, I notice the gateway is missing a folder "hwmon0" in /etc/class/hwmon. this cluster pair was built identical and i am not sure how this happen. trying to find out whether i can copy this directory from the other cluster member.

so /sys/class is a special filesystem. Everything in there is dynamically created by the kernel. I think to figure out what the problem is you should be trying to figure out what those files hold on the working one. Then you can figure out what hardware isn't being monitored correctly and for what reason.

[jflemingeds]

I am aware of the bug mentioned in sk101898. this is a different issue. as I dig a bit deeper, I notice the gateway is missing a folder "hwmon0" in /etc/class/hwmon. this cluster pair was built identical and i am not sure how this happen. trying to find out whether i can copy this directory from the other cluster member.

Can you compare the output of


lsmod

on both members? I think that is where the drive for hardware monitoring is coming from. should be a hwmon loaded on both.

[wayne0206]

please see attachment


[Expert@FW01:0]# ls –lR /sys/class/hwmon/
ls: –lR: No such file or directory
/sys/class/hwmon/:


[Expert@FW02:0]# ls –lR /sys/class/hwmon/
ls: –lR: No such file or directory
/sys/class/hwmon/:
hwmon0

[jflemingeds]

please see attachment


[Expert@FW01:0]# ls –lR /sys/class/hwmon/
ls: –lR: No such file or directory
/sys/class/hwmon/:


[Expert@FW02:0]# ls –lR /sys/class/hwmon/
ls: –lR: No such file or directory
/sys/class/hwmon/:
hwmon0

Something with your ls command seems odd. i'm not sure why its saying no such file or directory. Could be you have the unicode super long dash and ls isn't understanding thats a "-". I'm guessing you did a copy/paste. do it by hand this time.

Also if you want to compare the lsmod output sort it before doing the compare.

lsmod | sort

that way the output is more uniform and can be diffed correctly.

Happy holidays!

[wayne0206]

Something with your ls command seems odd. i'm not sure why its saying no such file or directory. Could be you have the unicode super long dash and ls isn't understanding thats a "-". I'm guessing you did a copy/paste. do it by hand this time.

Also if you want to compare the lsmod output sort it before doing the compare.

lsmod | sort

that way the output is more uniform and can be diffed correctly.

Happy holidays!

;) here it is again.


[Expert@FW01:0]# ls -lR /sys/class/hwmon/
/sys/class/hwmon/:
total 0
[Expert@FW01:0]#




[Expert@FW02:0]# ls -lR /sys/class/hwmon/
/sys/class/hwmon/:
total 0
drwxr-xr-x 2 admin root 0 Dec 24 12:35 hwmon0

/sys/class/hwmon/hwmon0:
total 0
lrwxrwxrwx 1 admin root 0 Dec 20 00:26 device -> ../../../devices/pci0000:00/0000:00:1f.3/i2c-0/0-002e
lrwxrwxrwx 1 admin root 0 Dec 24 12:35 subsystem -> ../../../class/hwmon
--w------- 1 admin root 4096 Dec 24 12:35 uevent

[jflemingeds]

The only difference i'm really seeing is it looks like you have a driver do a scsi cdrom loaded. Seems a little strange but i don't see how that would effect anything.

Anything interesting in dmesg? You may also want to attach something to the console so that you can capture all logged output during a boot up and then poke around in there.

Just wondering.. was that all the output? I see the scroll bar. Just making sure there wasn't anything else we're not seeing.

[wayne0206]

thanks for your help. checkpoint is RMA my gateway.