Intermittent network issues with Freebsd 6.2
Hi All, I am having intermittent network issues with our IBM X236 dual xeon server. Server comes with two bge network cards. At random intervals internal lan drops out. And then few minutes later it comes back online. So far I can only find some interface errors on netstat -i. Can anyone help me to resolve this issue. Please refer to attached files and below outputs for more information. /etc/sysctl.conf kern.ipc.maxsockbuf=8388608 kern.ipc.somaxconn=2048 net.inet.tcp.sendspace=3217968 net.inet.tcp.recvspace=3217968 net.inet.tcp.rfc1323=1 #net.inet.tcp.rfc3042=0 net.inet.ip.portrange.hilast=65535 net.inet.ip.portrange.hifirst=49152 net.inet.ip.portrange.last=65535 net.inet.ip.portrange.first=1024 net.inet.tcp.inflight.enable=0 /boot/loader.conf kern.ipc.nmbclusters=32768 vmstat -i interrupt total rate irq52: ips075446 17 irq30: ahd0 81 0 irq31: ahd1 15 0 irq1: atkbd0 69 0 irq3: sio174 0 irq4: sio067 0 irq6: fdc090 0 irq14: ata0 47 0 irq16: bge0 bge1+1395326315 irq19: uhci1 15 0 irq23: ehci0 1 0 cpu0: timer 8845847 1998 cpu3: timer1 0 cpu1: timer2 0 cpu2: timer 8830658 1995 Total 19147739 4326 netstat -i NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll bge0 1500 00:11:25:e9:7f:58 392325 880 449420 0 0 bge0 1500 192.168.1 lan 342652 - 4175 - - bge1 1500 00:11:25:e9:7f:59 369744 1648 363688 0 0 Regards Dimuthu Parussalla Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-STABLE #0: Tue Feb 6 18:13:39 EST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BSG WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant WARNING: MPSAFE network stack disabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.80GHz (3800.16-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf43 Stepping = 3 Features=0xbfebfbff Features2=0x659d> AMD Features=0x2000 Logical CPUs per core: 2 real memory = 2147266560 (2047 MB) avail memory = 2096476160 (1999 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic2 irqs 48-71 on motherboard ioapic1 irqs 24-47 on motherboard ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x588-0x58b on acpi0 cpu0: on acpi0 acpi_perf0: on cpu0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: on acpi0 pci0: on pcib0 pci0: at device 0.1 (no driver attached) pcib1: at device 2.0 on pci0 pci2: on pcib1 pcib2: at device 0.0 on pci2 pci3: on pcib2 ahd0: port 0x4000-0x40ff,0x4100-0x41ff mem 0xcfffe000-0xcfff irq 30 at device 7.0 on pci3 ahd0: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs ahd1: port 0x4200-0x42ff,0x4300-0x43ff mem 0xcfffc000-0xcfffdfff irq 31 at device 7.1 on pci3 ahd1: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs pcib3: mem 0xcdfff000-0xcdff at device 0.2 on pci2 pci4: on pcib3 pcib4: at device 1.0 on pci4 pci5: on pcib4 ips0: mem 0xcd00-0xcd000fff irq 52 at device 8.0 on pci5 pcib5: at device 4.0 on pci0 pci7: on pcib5 bge0: mem 0xc8bf-0xc8bf irq 16 at device 0.0 on p
RE: Intermittent network issues with Freebsd 6.2
Hi Glen, I did that already and it works for few days and dropping out. now I have change network cards to Intel (em). Hopefully this will solve the issue. Cheers, Dimuthu -Original Message- From: Glen Van Lehn [mailto:[EMAIL PROTECTED] Sent: Thursday, 15 February 2007 9:01 AM To: [EMAIL PROTECTED]; freebsd-stable@freebsd.org Subject: Re: Intermittent network issues with Freebsd 6.2 >>> "Dimuthu Parussalla" <[EMAIL PROTECTED]> 02/11/07 3:54 PM >>> Hi All, I am having intermittent network issues with our IBM X236 dual xeon server. Server comes with two bge network cards. At random intervals internal lan drops out. And then few minutes later it comes back online. So far I can only find some interface errors on netstat -i. Can anyone help me to resolve this issue. Please refer to attached files and below outputs for more information. /etc/sysctl.conf kern.ipc.maxsockbuf=8388608 kern.ipc.somaxconn=2048 net.inet.tcp.sendspace=3217968 net.inet.tcp.recvspace=3217968 net.inet.tcp.rfc1323=1 #net.inet.tcp.rfc3042=0 net.inet.ip.portrange.hilast=65535 net.inet.ip.portrange.hifirst=49152 net.inet.ip.portrange.last=65535 net.inet.ip.portrange.first=1024 net.inet.tcp.inflight.enable=0 /boot/loader.conf kern.ipc.nmbclusters=32768 vmstat -i interrupt total rate irq52: ips075446 17 irq30: ahd0 81 0 irq31: ahd1 15 0 irq1: atkbd0 69 0 irq3: sio174 0 irq4: sio067 0 irq6: fdc090 0 irq14: ata0 47 0 irq16: bge0 bge1+1395326315 irq19: uhci1 15 0 irq23: ehci0 1 0 cpu0: timer 8845847 1998 cpu3: timer1 0 cpu1: timer2 0 cpu2: timer 8830658 1995 Total 19147739 4326 netstat -i NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll bge0 1500 00:11:25:e9:7f:58 392325 880 449420 0 0 bge0 1500 192.168.1 lan 342652 - 4175 - - bge1 1500 00:11:25:e9:7f:59 369744 1648 363688 0 0 Regards Dimuthu Parussalla == Do you have access to the network switch that your server connects to? The stats on the port may show CRC errors or the log may show carrier off/on transitions indicating that 'Auto-negotiation' isn't stable. I've seen this a lot with 100FDx connections and a few times with GbE. Sometimes it helps to change the port speed/duplex settings from 'Auto' to [or vice versa ;].My preference has been to use 'Auto' if it works, and, if it doesn't, to nail down the server settings, then see whether nailing the switch port setting or leaving the switch port in 'Auto' is best. ymmv, glen van lehn city college san francisco ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Intermittent network issues with Freebsd 6.2
Hi All, I've just noticed when this incident happens Ierrs starting to increase and then interface in not pingable. Refer to output below. Also how do I set the interface in rc.conf to use 1000baseTX. Without using to autoselect? NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll bge01500 00:0e:0c:d0:73:3c 620587 2875 812683 0 0 bge01500 192.168.1 lan 538034 - 7723 - - bge11500 00:0e:0c:9f:f4:5e 848966 14257 775021 0 0 Regards Dimuthu -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dimuthu Parussalla Sent: Thursday, 15 February 2007 12:17 PM To: 'Glen Van Lehn'; freebsd-stable@freebsd.org Subject: RE: Intermittent network issues with Freebsd 6.2 Hi Glen, I did that already and it works for few days and dropping out. now I have change network cards to Intel (em). Hopefully this will solve the issue. Cheers, Dimuthu -Original Message- From: Glen Van Lehn [mailto:[EMAIL PROTECTED] Sent: Thursday, 15 February 2007 9:01 AM To: [EMAIL PROTECTED]; freebsd-stable@freebsd.org Subject: Re: Intermittent network issues with Freebsd 6.2 >>> "Dimuthu Parussalla" <[EMAIL PROTECTED]> 02/11/07 3:54 PM >>> Hi All, I am having intermittent network issues with our IBM X236 dual xeon server. Server comes with two bge network cards. At random intervals internal lan drops out. And then few minutes later it comes back online. So far I can only find some interface errors on netstat -i. Can anyone help me to resolve this issue. Please refer to attached files and below outputs for more information. /etc/sysctl.conf kern.ipc.maxsockbuf=8388608 kern.ipc.somaxconn=2048 net.inet.tcp.sendspace=3217968 net.inet.tcp.recvspace=3217968 net.inet.tcp.rfc1323=1 #net.inet.tcp.rfc3042=0 net.inet.ip.portrange.hilast=65535 net.inet.ip.portrange.hifirst=49152 net.inet.ip.portrange.last=65535 net.inet.ip.portrange.first=1024 net.inet.tcp.inflight.enable=0 /boot/loader.conf kern.ipc.nmbclusters=32768 vmstat -i interrupt total rate irq52: ips075446 17 irq30: ahd0 81 0 irq31: ahd1 15 0 irq1: atkbd0 69 0 irq3: sio174 0 irq4: sio067 0 irq6: fdc090 0 irq14: ata0 47 0 irq16: bge0 bge1+1395326315 irq19: uhci1 15 0 irq23: ehci0 1 0 cpu0: timer 8845847 1998 cpu3: timer1 0 cpu1: timer2 0 cpu2: timer 8830658 1995 Total 19147739 4326 netstat -i NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll bge0 1500 00:11:25:e9:7f:58 392325 880 449420 0 0 bge0 1500 192.168.1 lan 342652 - 4175 - - bge1 1500 00:11:25:e9:7f:59 369744 1648 363688 0 0 Regards Dimuthu Parussalla == Do you have access to the network switch that your server connects to? The stats on the port may show CRC errors or the log may show carrier off/on transitions indicating that 'Auto-negotiation' isn't stable. I've seen this a lot with 100FDx connections and a few times with GbE. Sometimes it helps to change the port speed/duplex settings from 'Auto' to [or vice versa ;].My preference has been to use 'Auto' if it works, and, if it doesn't, to nail down the server settings, then see whether nailing the switch port setting or leaving the switch port in 'Auto' is best. ymmv, glen van lehn city college san francisco ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Intermittent network issues with Freebsd 6.2
Hi, Dmesg output related to bge as follows. miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:11:25:e9:7f:58 bge0: [GIANT-LOCKED] pcib6: at device 5.0 on pci0 pci8: on pcib6 bge1: mem 0xc6ff-0xc6ff irq 16 at device 0.0 on pci8 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:11:25:e9:7f:59 bge1: [GIANT-LOCKED] -Original Message- From: Jeremy Chadwick [mailto:[EMAIL PROTECTED] Sent: Thursday, 15 February 2007 3:36 PM To: Dimuthu Parussalla Cc: 'Glen Van Lehn'; freebsd-stable@freebsd.org Subject: Re: Intermittent network issues with Freebsd 6.2 On Thu, Feb 15, 2007 at 03:09:08PM +1100, Dimuthu Parussalla wrote: > Hi All, > > I've just noticed when this incident happens Ierrs starting to increase and > then interface in not pingable. Refer to output below. > > Also how do I set the interface in rc.conf to use 1000baseTX. Without using > to autoselect? You can do the following: ifconfig_bge0="inet xxx netmask yyy media 1000baseTX mediaopt full-duplex" ifconfig_bge1="inet xxx netmask yyy media 1000baseTX mediaopt full-duplex" See the bge(4) manpage for additional details. Also, which particular Broadcom chip are you using? dmesg(8) should show this, or pciconf -l -v. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networkinghttp://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Slow network performance
Hi All, Apart from random dropout from the network. Our IBM X236 server suffers slow network performance. I've changed the server from CISCO switch to a netgear switch on a test platform. Also tried 1000m full-duplex setup with no auto negotionation on both ends. Still after few days (3-4) server drops the connection. And while its working I get 90KBps upload/download with ftp transfers. I have treid changing BGE network cards to EM (intel 100/1000) still the same result. Any idea's to nail this problem? /etc/sysctl.conf kern.ipc.maxsockbuf=8388608 kern.ipc.somaxconn=2048 net.inet.tcp.sendspace=3217968 net.inet.tcp.recvspace=3217968 net.inet.tcp.rfc1323=1 #net.inet.tcp.rfc3042=0 net.inet.ip.portrange.hilast=65535 net.inet.ip.portrange.hifirst=49152 net.inet.ip.portrange.last=65535 net.inet.ip.portrange.first=1024 net.inet.tcp.inflight.enable=0 /boot/loader.conf kern.ipc.nmbclusters=32768 Interfaces: em0: flags=8843 mtu 1500 options=b inet 192.168.1.12 netmask 0xff00 broadcast 192.168.1.255 ether 00:0e:0c:d0:73:3c media: Ethernet 1000baseTX status: active em1: flags=8843 mtu 1500 options=b inet 6x.xx.xx.xx netmask 0xffc0 broadcast xxx.xxx.xxx.255 ether 00:0e:0c:9f:f4:5e media: Ethernet 100baseTX status: active Regards Dimuthu Parussalla # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.7.2.2 2006/05/01 00:15:12 scottl Exp $ machine i386 cpu I686_CPU ident BSG maxusers512 # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols #optionsSCHED_ULE # ULE scheduler options SCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread preemption options INET# InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFS_ROOT# NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework options GEOM_GPT# GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT# Print register bitfields in debug options SMP # SMP Support # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~215k to driver. options ADAPTIVE_GIANT # Giant mutex is adaptive. device apic# I/O APIC options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=100 options IPFIREWALL_FORWARD options IPFIREWALL_DEFAULT_TO_ACCEPT options IPDIVERT options IPFILTER options IPFILTER_LOG #optionsIPFILTER_DEFAULT_TO_ACCEPT options IPSEC options IPSEC_ESP options IPSEC_DEBUG #options IPTUNNEL #options NCP options NETATALK options DUMMYNET #options TCP_RESTRICT_RST options QUOTA options BRIDGE # Bus support. #device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # AT
RE: Slow network performance
Hi Sten, I have ruled out the faulty cable. Also no errors reporting on the managed switch. Doing a test with a reduced parameters to 32k. -Original Message- From: Sten Daniel Soersdal [mailto:[EMAIL PROTECTED] Sent: Saturday, 17 February 2007 2:33 AM To: Dimuthu Parussalla BWEADM non-std-pwd Cc: Vinny Abello; freebsd-stable@freebsd.org Subject: Re: Slow network performance Dimuthu Parussalla BWEADM non-std-pwd wrote: > This is exactly what I did. > Managed Switch A (2950G) > 1) both switch and bge/em card set for auto negeotiation > 2) Both switch and bge/em set for 1000mb full-duplex. > > Managed Switch B (Netgeat GSM7224) > 1) both switch and bge/em card set for auto negeotiation > 2) Both switch and bge/em set for 1000mb full-duplex. > > I am seriously running out of options. > Thanks What have you done to rule out if it's a faulty cable or noise on the cable? What kind of cable is it? net.inet.tcp.sendspace=3217968 net.inet.tcp.recvspace=3217968 Are you sure these two should be set to the millions? Try reducing them to ~32k or so. -- Sten Daniel Soersdal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Clamav-90_2 Lockup with freebsd 6.2
Clamav-90_2 Lockup with freebsd 6.2 Still under load clamav_90_2 locks up with high cpu usage. Had to downgrade the port to 88.7_1 to get the server going. Sockstat shows lots of open sockets from clamd. I am using simscan+Qmail+Clamav. Any Ideas to solve this problem?. Regards Dimuthu Parussalla ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Clamav-90_2 Lockup with freebsd 6.2
Hi, I can confirm the same situation. My dual xeon x236 server runs very high cpu utilisation with clamav. Also tried with maxthreads to 1. Result is the same but frequency of locked process seems to be reduced. Cheers Dimi -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Martin Blapp Sent: Wednesday, 28 February 2007 4:37 AM To: Sergey N. Voronkov Cc: freebsd-stable@freebsd.org Subject: Re: Clamav-90_2 Lockup with freebsd 6.2 Hi, >> Change the threading lib. It fixed it for us. >> >> % cat /etc/libmap.conf >> [clamd] >> libc_r.so.5 libthr.so.2 >> libc_r.so.6 libthr.so.2 >> libthr.so.2 libthr.so.2 >> libpthread.so.1 libthr.so.2 >> libpthread.so.2 libthr.so.2 Even with libthr the CPU usage is still far too high ... I'm currently looking at the code. Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Intermittent network issues with Freebsd 6.2
I had to disbale both bge nics to get the server going. Now I am running with twin em0 nics. Seems to be very stable for at least 9 days. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Greg Barniskis Sent: Thursday, 1 March 2007 8:55 AM To: Vivek Khera Cc: FreeBSD Stable Subject: Re: Intermittent network issues with Freebsd 6.2 Vivek Khera wrote: > On our PE800, I had to disable the bge on BIOS and plug in an em-based > NIC card. Made a world of difference in system stability and > performance -- it is actually usable now :-) On our Dell PE2950 units, we had to do the same thing (disable and replace the Broadcom interfaces), and that was running Windows Server 2k3. The problem really seems to be flakiness of the chips or firmware, not necessarily flakiness in the drivers for FreeBSD. Maybe it's both, I don't know. My point is that Broadcom cards have had some serious problems on other platforms too, and not just recently. Other NIC brands have never given us nearly as much trouble. -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) , (608) 266-6348 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Clamav-90_2 Lockup with freebsd 6.2
Hi, I am running latest CVSUP branch today. Still having the same problem. Only way to reduce cpu usage is to increase maxthreads as others mentioned. What version it is fixed? is it not submitted through ports yet? Regards Dimi -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Renato Botelho Sent: Friday, 2 March 2007 2:56 AM To: Alexander Shikoff Cc: Marko Lerota; Chris; freebsd-stable@FreeBSD.org; Daniel Eischen; Martin Blapp; Anton Karpov Subject: Re: Clamav-90_2 Lockup with freebsd 6.2 On Thu, Mar 01, 2007 at 03:43:26PM +0200, Alexander Shikoff wrote: > Hi All, > > On Thu, Mar 01, 2007 at 08:32:55AM -0500, Daniel Eischen wrote: > > On Thu, 1 Mar 2007, Martin Blapp wrote: > > > > > > > >Hi, > > > > > >Clamd is currently broken with libpthread for some threading-reason. > > >You definitly need to use libthr (which is still CPU hungry, but > > >works better). > > > > I don't think it is a problem with libpthread. > > FYI: https://wwws.clamav.net/bugzilla/show_bug.cgi?id=307#c8 I found the problem, a bad REINPLACE_CMD was changing wrong var on configure scripts, don't respecting PTHREAD_LIBS. It's fixed now on 0.90_3. Thanks for all. -- Renato Botelho GnuPG Key: http://www.FreeBSD.org/~garga/pubkey.asc Love at first sight is one of the greatest labor-saving devices the world has ever seen. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Clamav-90_2 Lockup with freebsd 6.2
How do I tell clamd to use libthr.so ? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Martin Blapp Sent: Friday, 9 March 2007 4:08 AM To: Marko Lerota Cc: Chris; freebsd-stable@freebsd.org; Renato Botelho; Daniel Eischen; Anton Karpov; Alexander Shikoff Subject: Re: Clamav-90_2 Lockup with freebsd 6.2 Hi, > No, It's not. Today I added a new server with fresh clamav-0.90_3 > package. Sockstat again started to jump to the sky. Clamd with libpthread.so is still broken. Please use libthr.so. I'm currently investigating why libpthreads.so has problems with clamd, and it looks to me like a library bug. -- Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Clamav-90_2 Lockup with freebsd 6.2
Hi, I am not sure why. But my dual xeon with libthr on clamav-90.1 still gives very high cpu usage. Is it fixed yet? Di -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Martin Blapp Sent: Saturday, 17 March 2007 1:00 AM To: Laurent Frigault Cc: Rob MacGregor; clamav-devel@lists.clamav.net; freebsd-stable@freebsd.org Subject: Re: Clamav-90_2 Lockup with freebsd 6.2 Hi, I just fixed those issues with the port. Thanks for reporting ! Martin Blapp, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- ImproWare AG, UNIXSP & ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Clamav 0.90.1
Hi All, Anyone tried new clamav version (Clamav 0.90.2) with 6.2 stable?. Also any success using Clamav 0.90.1 without clamd.conf on 6.2?. Does it still need lipthread mapping? Cheers Dim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Slow network performance
This is exactly what I did.
Managed Switch A (2950G)
1) both switch and bge/em card set for auto negeotiation
2) Both switch and bge/em set for 1000mb full-duplex.
Managed Switch B (Netgeat GSM7224)
1) both switch and bge/em card set for auto negeotiation
2) Both switch and bge/em set for 1000mb full-duplex.
I am seriously running out of options.
Thanks
Vinny Abello writes:
Although I don't think this is necessarily the cause of your dropouts as
you put it, one must understand the way autonegotiation and manual speed
and duplex work between network gear.
For autonegotiation to work, BOTH devices must support autonegotiation, OR
both devices must be set to the same speed and duplex setting. If one only
supports auto and the other does not, you must NOT set the device that you
can manually configure to full duplex. The auto device will never
negotiate at full duplex and fall back to half when autonegotiation fails,
causing a duplex mismatch and horrible network performance and loss.
A very rough set of rules of thumb (YMMV):
When connecting to an unmanaged switch, use auto. If your host doesn't
support auto, set it to half-duplex.
When connecting to a managed switch, make sure the port is set to auto and
set your system to auto, otherwise force both the switch port and your
host to the same settings. This is required especially if the host doesn't
support auto negotiation and you want to run at full duplex.
When connecting to a managed switch, enable portfast or the equivalent
spanning-tree command on the switch port your host is connected to so it
forwards traffic immediately when getting link.
So to sum it up, auto only works if both sides speak auto. Auto
negotiation failure falls back to half-duplex!
Of course there are all the horror stories where auto negotiation is evil
and that different vendor's implementations don't play nice or are just
completely broken, so always set things to manual or you and your family
will suffer an untimely death... There are so many of these stories that
one would think there has to be some truth to it. In my own experience, I
have never had an issue with auto negotiation in some ten years of working
with a dozen different vendors' networking gear so I guess I'm lucky... or
I just understand how it interacts with other devices and their
capabilities. I still don't know which exactly.
Hope this helps! :)
Dimuthu Parussalla wrote:
Hi All,
Apart from random dropout from the network. Our IBM X236 server suffers
slow
network performance. I've changed the server from CISCO switch to a
netgear
switch on a test platform. Also tried 1000m full-duplex setup with no
auto
negotionation on both ends. Still after few days (3-4) server drops the
connection. And while its working I get 90KBps upload/download with ftp
transfers.
I have treid changing BGE network cards to EM (intel 100/1000) still the
same result. Any idea's to nail this problem?
/etc/sysctl.conf
kern.ipc.maxsockbuf=8388608
kern.ipc.somaxconn=2048
net.inet.tcp.sendspace=3217968
net.inet.tcp.recvspace=3217968
net.inet.tcp.rfc1323=1
#net.inet.tcp.rfc3042=0
net.inet.ip.portrange.hilast=65535
net.inet.ip.portrange.hifirst=49152
net.inet.ip.portrange.last=65535
net.inet.ip.portrange.first=1024
net.inet.tcp.inflight.enable=0
/boot/loader.conf
kern.ipc.nmbclusters=32768
Interfaces:
em0: flags=8843 mtu 1500
options=b
inet 192.168.1.12 netmask 0xff00 broadcast 192.168.1.255
ether 00:0e:0c:d0:73:3c
media: Ethernet 1000baseTX
status: active
em1: flags=8843 mtu 1500
options=b
inet 6x.xx.xx.xx netmask 0xffc0 broadcast xxx.xxx.xxx.255
ether 00:0e:0c:9f:f4:5e
media: Ethernet 100baseTX
status: active
Regards
Dimuthu Parussalla
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
