Hi there -- I reconfigured the network cards on the server in question so that one is disabled, and the other is set to autonegotiate. Additionally, I updated the BIOS for the motherboard and the NIC on the server. Even with these new configurations, the problem where the server lost its connection to the network still occurred.
I manually ran the script that is the scheduled cron job, and I was able to track when the network connection was lost. The disconnect occurred about five minutes into the anti-virus scan. Attached to this e-mail is the script that is run as well as the output summary text file. Just as a recap, the server in question is running openSuSE 11.1 which was updated from the openSuSE 10.3 version. The version of ClamAV is the 0.94.2 release that was compiled and installed from source. One thought came to mind: Would the removal of the source version of ClamAV and then having it replaced by the one that comes bundled with openSuSE be a solution to this issue? -----Original Message----- From: clamav-users-boun...@lists.clamav.net [mailto:clamav-users-boun...@lists.clamav.net] On Behalf Of Chuck Swiger Sent: Wednesday, January 07, 2009 1:05 PM To: ClamAV users ML Subject: Re: [Clamav-users] opensuse11.1 loses network connection duringa cronjob that utilizes freshclam and clamscan On Jan 7, 2009, at 8:03 AM, Kaplan, Andrew H. wrote: > One of our servers had opensuse 11.1 installed as an upgrade from > opensuse 10.3 > on Monday of this week, and has lost its network connection twice in > as many days. The network cards on > the server, of which one is currently in use and the other is up > with the same ip address but not currently > connected to the network, are the NetXtreme BCM5722 gigabit ethernet > PCI express model. The cards are > configured to run at 100Mbps Full Duplex with Autonegotiation turned > off. Losing your net connection is unlikely to have anything to do with ClamAV. Barring unusual circumstances (setting up a bridge or some kind of link aggregation or trunking like Cisco's FEC or CARP), you should not configure two NICs with the the same IP. Barring unusual circumstances, such as connecting to a defective switch, you should never need to disable ethernet autonegotiation. This said, there are some other reasons which might cause the link to fail; some platforms have an integrated remote management platform layered on top of a normal NIC, which can interfere with ARP and normal operation of the interface-- usually a BIOS firmware update or adjusting the BIOS to disable the management stuff helps. Regards, -- -Chuck _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.
/home/ahk/clamav-0.94.2/test/.split/split.clam.arjaa: Input/Output error /sys/devices/platform/vesafb.0/graphics/fb0/bl_curve: Input/Output error /sys/devices/pci0000:00/0000:00:04.0/0000:05:00.0/resource0: Input/Output error /sys/devices/pci0000:00/0000:00:04.0/0000:05:00.0/resource1: Input/Output error /sys/devices/pci0000:00/0000:00:04.0/0000:05:00.0/resource3: Input/Output error /sys/devices/pci0000:00/0000:00:04.0/0000:05:00.0/rom: Input/Output error /sys/devices/pci0000:00/0000:00:04.0/0000:05:00.0/host0/port-0:0/end_device-0:0/sas_device/end_device-0:0/enclosure_identifier: Input/Output error /sys/devices/pci0000:00/0000:00:04.0/0000:05:00.0/host0/port-0:0/end_device-0:0/sas_device/end_device-0:0/bay_identifier: Input/Output error /sys/devices/pci0000:00/0000:00:04.0/0000:05:00.0/host0/port-0:1/end_device-0:1/sas_device/end_device-0:1/enclosure_identifier: Input/Output error /sys/devices/pci0000:00/0000:00:04.0/0000:05:00.0/host0/port-0:1/end_device-0:1/sas_device/end_device-0:1/bay_identifier: Input/Output error /sys/devices/pci0000:00/0000:00:06.0/0000:07:00.0/vpd: Input/Output error /sys/devices/pci0000:00/0000:00:06.0/0000:07:00.0/resource0: Input/Output error /sys/devices/pci0000:00/0000:00:06.0/0000:07:00.0/resource2: Input/Output error /sys/devices/pci0000:00/0000:00:06.0/0000:07:00.0/resource3: Input/Output error /sys/devices/pci0000:00/0000:00:06.0/0000:07:00.0/rom: Input/Output error /sys/devices/pci0000:00/0000:00:1c.4/0000:01:00.0/vpd: Input/Output error /sys/devices/pci0000:00/0000:00:1c.4/0000:01:00.0/resource0: Input/Output error /sys/devices/pci0000:00/0000:00:1c.5/0000:02:00.0/resource0: Input/Output error /sys/devices/pci0000:00/0000:00:1c.5/0000:02:00.0/net/eth1/carrier: Input/Output error /sys/devices/pci0000:00/0000:00:1c.5/0000:02:00.0/net/eth1/dormant: Input/Output error /sys/devices/pci0000:00/0000:00:1d.0/resource4: Input/Output error /sys/devices/pci0000:00/0000:00:1d.1/resource4: Input/Output error /sys/devices/pci0000:00/0000:00:1d.2/resource4: Input/Output error /sys/devices/pci0000:00/0000:00:1d.7/resource0: Input/Output error /sys/devices/pci0000:00/0000:00:1e.0/0000:0a:07.0/resource1: Input/Output error /sys/devices/pci0000:00/0000:00:1e.0/0000:0a:07.0/resource2: Input/Output error /sys/devices/pci0000:00/0000:00:1e.0/0000:0a:07.0/rom: Input/Output error /sys/devices/pci0000:00/0000:00:1f.2/resource0: Input/Output error /sys/devices/pci0000:00/0000:00:1f.2/resource2: Input/Output error /sys/devices/pci0000:00/0000:00:1f.2/resource4: Input/Output error /sys/devices/pci0000:00/0000:00:1f.2/resource5: Input/Output error /sys/devices/pci0000:00/0000:00:1f.5/resource0: Input/Output error /sys/devices/pci0000:00/0000:00:1f.5/resource2: Input/Output error /sys/devices/pci0000:00/0000:00:1f.5/resource4: Input/Output error /sys/devices/pci0000:00/0000:00:1f.5/resource5: Input/Output error
_______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
