Hi guys,
This adds up to the other posts related to the 6.300 update.
Since the update was applied to 2 devices (1 ASL and 1 ASG 220), we're seeing different things happening.
First of all, the Root partition usage is exceeding 75 % , which causes our ACC to report this. And quite frankly, it's something to worry about.
Secondly, even thought a manual update seems to finnish well (but says that no IPS / virus (Authentium and ClamAV), and Spam update are available) , we are seeing through Syslog these msgs :
check Failed increment sp_servers counter 1-3
check Failed increment sp_servers counter 2-3
check Failed increment sp_servers counter 3-3
DEBUG : LOGEVENT Name=sp_servers
triggerAction: 'cmd'
actionCmd(+): '/usr/bin/sp_updater'
child returned status: exit='0' signal='0'
These are brand new msgs since the 6.300 update.
And while I'm at it, I would like to add a last observation (not related to the last up2date), but I just want to know if any one have notice this :
I keep seeing these packets labeled as ICMP FLOOD (Type 3 Code 3 in majority with a few Type 11 Code 0) steadily (and of course beeing dropped) :
80.237.220.201 (Astaro Up2Date)
212.126.210.201 (TIMENET-NETZ3 in Karlsruhe)
216.167.31.83 (NTT America, Inc.)
134.222.227.14 (EUNET-BACKBONE)
They can go in "rafale mode" 8-9 times each every hour (when the system tries to update itself) or so ...
This has been going on since version 6.0 came up.
ICMP is completely disabled, but this should not interfere with the communications related to the up2date process.
Feel free to share any feedback.
Regards,
This thread was automatically locked due to age.