Re: [Nut-upsuser] stopping ups services resets my network
I will give more details on the symptomes asap. It will take some time because the issue occures only after a few days. I had another report of malfunctioning with nut today but it is a different issue. I'll create another thread later. (cpu load and performance issue after several weeks). The UPS model is MGE evolution S 1250. Nut-2.4.1 (home made rpm) Red Hat 4.7 I'll comme back to you soon. Antoine -Message d'origine- De : Arnaud Quette [mailto:aquette@gmail.com] Envoyé : mercredi 28 octobre 2009 10:24 À : Charles Lepple Cc : Antoine Gatineau; nut-upsuser@lists.alioth.debian.org Objet : Re: [Nut-upsuser] stopping ups services resets my network 2009/10/27 Charles Lepple : > > On Oct 27, 2009, at 11:56 AM, Arnaud Quette wrote: > >> 2009/10/27 Antoine Gatineau: >>> >>> Hello, >> >> salut Antoine, >> >>> I'm back again on this issue. >>> I have contacted Red Hat support but they won't do anything to help >>> since it is not an official Red Hat package. Unless I prove the >>> conflict come from RH. >>> >>> So I am trying to figure out what is going on. >>> >>> Adding -D will not add any more log at the services stop. >>> >>> When I look at the sources, I couldn't find the piece of code that >>> release properly the usb UPS device. There is just a normal SIGTERM >>> handling. Is this normal? >> >> not at all, everything is clean here ;-) what you're looking for is >> drivers/usbhid-ups.c->upsdrv_cleanup() >> the comm_driver->close() will more specifically call, in your case, >> the libusb.c backend, and so the usb_close() function. >> >>> I also noticed that there are debug logs but I don't know how to >>> activate them... Can somebody tell me how to do it? >> >> I'm not sure for RHEL, but you should look around /etc/syslog.conf, >> man syslog.conf and /var/log/debug >> > Arnaud, Hey Charles, > Antoine may be referring to the debug information from the drivers but > I don't think we have narrowed it down to something that can be > resolved with those logs. possible. imo, Antoine was talking about the few "upslogx(LOG_DEBUG...", but it's quite possible that he was refering to the upsdebugx(). Antoine: if you're refering to the latter, you should launch the driver in debug mode, ie: $ /path/to/usbhid-ups -D -a cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] stopping ups services resets my network
2009/10/27 Charles Lepple : > > On Oct 27, 2009, at 11:56 AM, Arnaud Quette wrote: > >> 2009/10/27 Antoine Gatineau: >>> >>> Hello, >> >> salut Antoine, >> >>> I'm back again on this issue. >>> I have contacted Red Hat support but they won't do anything to help since >>> it >>> is not an official Red Hat package. Unless I prove the conflict come from >>> RH. >>> >>> So I am trying to figure out what is going on. >>> >>> Adding -D will not add any more log at the services stop. >>> >>> When I look at the sources, I couldn't find the piece of code that >>> release >>> properly the usb UPS device. There is just a normal SIGTERM handling. Is >>> this normal? >> >> not at all, everything is clean here ;-) >> what you're looking for is drivers/usbhid-ups.c->upsdrv_cleanup() >> the comm_driver->close() will more specifically call, in your case, >> the libusb.c backend, and so the usb_close() function. >> >>> I also noticed that there are debug logs but I don't know how to activate >>> them... Can somebody tell me how to do it? >> >> I'm not sure for RHEL, but you should look around /etc/syslog.conf, >> man syslog.conf and /var/log/debug >> > Arnaud, Hey Charles, > Antoine may be referring to the debug information from the drivers but I > don't think we have narrowed it down to something that can be resolved with > those logs. possible. imo, Antoine was talking about the few "upslogx(LOG_DEBUG...", but it's quite possible that he was refering to the upsdebugx(). Antoine: if you're refering to the latter, you should launch the driver in debug mode, ie: $ /path/to/usbhid-ups -D -a cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] stopping ups services resets my network
On Oct 27, 2009, at 11:56 AM, Arnaud Quette wrote: 2009/10/27 Antoine Gatineau: Hello, salut Antoine, I'm back again on this issue. I have contacted Red Hat support but they won't do anything to help since it is not an official Red Hat package. Unless I prove the conflict come from RH. So I am trying to figure out what is going on. Adding -D will not add any more log at the services stop. When I look at the sources, I couldn't find the piece of code that release properly the usb UPS device. There is just a normal SIGTERM handling. Is this normal? not at all, everything is clean here ;-) what you're looking for is drivers/usbhid-ups.c->upsdrv_cleanup() the comm_driver->close() will more specifically call, in your case, the libusb.c backend, and so the usb_close() function. I also noticed that there are debug logs but I don't know how to activate them... Can somebody tell me how to do it? I'm not sure for RHEL, but you should look around /etc/syslog.conf, man syslog.conf and /var/log/debug Arnaud, Antoine may be referring to the debug information from the drivers but I don't think we have narrowed it down to something that can be resolved with those logs. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] stopping ups services resets my network
2009/10/27 Antoine Gatineau: > Hello, salut Antoine, > I'm back again on this issue. > I have contacted Red Hat support but they won't do anything to help since it > is not an official Red Hat package. Unless I prove the conflict come from > RH. > > So I am trying to figure out what is going on. > > Adding -D will not add any more log at the services stop. > > When I look at the sources, I couldn't find the piece of code that release > properly the usb UPS device. There is just a normal SIGTERM handling. Is > this normal? not at all, everything is clean here ;-) what you're looking for is drivers/usbhid-ups.c->upsdrv_cleanup() the comm_driver->close() will more specifically call, in your case, the libusb.c backend, and so the usb_close() function. > I also noticed that there are debug logs but I don't know how to activate > them... Can somebody tell me how to do it? I'm not sure for RHEL, but you should look around /etc/syslog.conf, man syslog.conf and /var/log/debug > Do you have any advice on how to debug this? I have not seen anything > particuliar about IRQs and there is no message in syslog when stopping ups. > > The fact is that I don't know at all what is blocking my network card and > even less why... :( Charles has a point in his later mail: what if NUT is not running? cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] stopping ups services resets my network
Also, is this the same UPS that had EMI issues in the past? What brand and model is it? On Oct 27, 2009, at 6:36 AM, "Antoine Gatineau" > wrote: Hello, I'm back again on this issue. I have contacted Red Hat support but they won't do anything to help since it is not an official Red Hat package. Unless I prove the conflict come from RH. So I am trying to figure out what is going on. Adding -D will not add any more log at the services stop. When I look at the sources, I couldn't find the piece of code that release properly the usb UPS device. There is just a normal SIGTERM handling. Is this normal? I also noticed that there are debug logs but I don't know how to activate them... Can somebody tell me how to do it? Do you have any advice on how to debug this? I have not seen anything particuliar about IRQs and there is no message in syslog when stopping ups. The fact is that I don't know at all what is blocking my network card and even less why... :( Thanks, Antoine -Message d'origine- De : Charles Lepple [mailto:clep...@gmail.com] Envoyé : vendredi 2 octobre 2009 01:05 À : Antoine Gatineau Cc : nut-upsuser@lists.alioth.debian.org Objet : Re: [Nut-upsuser] stopping ups services resets my network On Mon, Sep 28, 2009 at 6:40 AM, Antoine Gatineau wrote: Hello, I have this issue: ups is working fine for a time but when I stop the services or if I unplug the ups device (over usb) I get the following in /var/log/messages I am running nut-2.4.1 on RHEL4. Sep 28 14:44:57 mabolas upsd[24151]: Signal 15: exiting Sep 28 14:45:06 mabolas upsmon[24156]: Signal 15: exiting Sep 28 15:04:10 mabolas sshd(pam_unix)[29190]: session closed for user root Sep 28 15:04:36 mabolas kernel: NETDEV WATCHDOG: eth0: transmit timed out Sep 28 15:04:36 mabolas kernel: tg3: eth0: transmit timed out, resetting Sep 28 15:04:36 mabolas kernel: tg3: DEBUG: MAC_TX_STATUS[0008] MAC_RX_STATUS[] Sep 28 15:04:36 mabolas kernel: tg3: DEBUG: RDMAC_STATUS[] WDMAC_STATUS[] Sep 28 15:04:36 mabolas kernel: tg3: eth0: Link is down. Sep 28 15:04:38 mabolas kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex. Sep 28 15:04:38 mabolas kernel: tg3: eth0: Flow control is off for TX and off for RX. This sounds like a bug in the tg3 driver in that kernel version. Have you checked the RedHat bugzilla to see if anyone else sees this? Depending on how the motherboard is laid out, moving the UPS to a different USB port might avoid this problem. It could have something to do with interrupt handling (for example, the tg3 driver expects an interrupt that is stolen by the USB controller). -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] stopping ups services resets my network
You said this also happens when you unplug the USB cable for the UPS- what if NUT is not running when you unplug USB? On Oct 27, 2009, at 6:36 AM, "Antoine Gatineau" > wrote: Hello, I'm back again on this issue. I have contacted Red Hat support but they won't do anything to help since it is not an official Red Hat package. Unless I prove the conflict come from RH. So I am trying to figure out what is going on. Adding -D will not add any more log at the services stop. When I look at the sources, I couldn't find the piece of code that release properly the usb UPS device. There is just a normal SIGTERM handling. Is this normal? I also noticed that there are debug logs but I don't know how to activate them... Can somebody tell me how to do it? Do you have any advice on how to debug this? I have not seen anything particuliar about IRQs and there is no message in syslog when stopping ups. The fact is that I don't know at all what is blocking my network card and even less why... :( Thanks, Antoine -Message d'origine- De : Charles Lepple [mailto:clep...@gmail.com] Envoyé : vendredi 2 octobre 2009 01:05 À : Antoine Gatineau Cc : nut-upsuser@lists.alioth.debian.org Objet : Re: [Nut-upsuser] stopping ups services resets my network On Mon, Sep 28, 2009 at 6:40 AM, Antoine Gatineau wrote: Hello, I have this issue: ups is working fine for a time but when I stop the services or if I unplug the ups device (over usb) I get the following in /var/log/messages I am running nut-2.4.1 on RHEL4. Sep 28 14:44:57 mabolas upsd[24151]: Signal 15: exiting Sep 28 14:45:06 mabolas upsmon[24156]: Signal 15: exiting Sep 28 15:04:10 mabolas sshd(pam_unix)[29190]: session closed for user root Sep 28 15:04:36 mabolas kernel: NETDEV WATCHDOG: eth0: transmit timed out Sep 28 15:04:36 mabolas kernel: tg3: eth0: transmit timed out, resetting Sep 28 15:04:36 mabolas kernel: tg3: DEBUG: MAC_TX_STATUS[0008] MAC_RX_STATUS[] Sep 28 15:04:36 mabolas kernel: tg3: DEBUG: RDMAC_STATUS[] WDMAC_STATUS[] Sep 28 15:04:36 mabolas kernel: tg3: eth0: Link is down. Sep 28 15:04:38 mabolas kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex. Sep 28 15:04:38 mabolas kernel: tg3: eth0: Flow control is off for TX and off for RX. This sounds like a bug in the tg3 driver in that kernel version. Have you checked the RedHat bugzilla to see if anyone else sees this? Depending on how the motherboard is laid out, moving the UPS to a different USB port might avoid this problem. It could have something to do with interrupt handling (for example, the tg3 driver expects an interrupt that is stolen by the USB controller). -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] stopping ups services resets my network
Hello, I'm back again on this issue. I have contacted Red Hat support but they won't do anything to help since it is not an official Red Hat package. Unless I prove the conflict come from RH. So I am trying to figure out what is going on. Adding -D will not add any more log at the services stop. When I look at the sources, I couldn't find the piece of code that release properly the usb UPS device. There is just a normal SIGTERM handling. Is this normal? I also noticed that there are debug logs but I don't know how to activate them... Can somebody tell me how to do it? Do you have any advice on how to debug this? I have not seen anything particuliar about IRQs and there is no message in syslog when stopping ups. The fact is that I don't know at all what is blocking my network card and even less why... :( Thanks, Antoine -Message d'origine- De : Charles Lepple [mailto:clep...@gmail.com] Envoyé : vendredi 2 octobre 2009 01:05 À : Antoine Gatineau Cc : nut-upsuser@lists.alioth.debian.org Objet : Re: [Nut-upsuser] stopping ups services resets my network On Mon, Sep 28, 2009 at 6:40 AM, Antoine Gatineau wrote: > Hello, > > > I have this issue: ups is working fine for a time but when I stop the > services or if I unplug the ups device (over usb) I get the following > in /var/log/messages > > I am running nut-2.4.1 on RHEL4. > > Sep 28 14:44:57 mabolas upsd[24151]: Signal 15: exiting Sep 28 > 14:45:06 mabolas upsmon[24156]: Signal 15: exiting Sep 28 15:04:10 > mabolas sshd(pam_unix)[29190]: session closed for user root Sep 28 > 15:04:36 mabolas kernel: NETDEV WATCHDOG: eth0: transmit timed out Sep > 28 15:04:36 mabolas kernel: tg3: eth0: transmit timed out, resetting > Sep 28 15:04:36 mabolas kernel: tg3: DEBUG: MAC_TX_STATUS[0008] > MAC_RX_STATUS[] Sep 28 15:04:36 mabolas kernel: tg3: DEBUG: > RDMAC_STATUS[] WDMAC_STATUS[] Sep 28 15:04:36 mabolas > kernel: tg3: eth0: Link is down. > Sep 28 15:04:38 mabolas kernel: tg3: eth0: Link is up at 1000 Mbps, > full duplex. > Sep 28 15:04:38 mabolas kernel: tg3: eth0: Flow control is off for TX > and off for RX. This sounds like a bug in the tg3 driver in that kernel version. Have you checked the RedHat bugzilla to see if anyone else sees this? Depending on how the motherboard is laid out, moving the UPS to a different USB port might avoid this problem. It could have something to do with interrupt handling (for example, the tg3 driver expects an interrupt that is stolen by the USB controller). -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] stopping ups services resets my network
On Mon, Sep 28, 2009 at 6:40 AM, Antoine Gatineau wrote: > Hello, > > > I have this issue: ups is working fine for a time but when I stop the > services or if I unplug the ups device (over usb) I get the following in > /var/log/messages > > I am running nut-2.4.1 on RHEL4. > > Sep 28 14:44:57 mabolas upsd[24151]: Signal 15: exiting > Sep 28 14:45:06 mabolas upsmon[24156]: Signal 15: exiting > Sep 28 15:04:10 mabolas sshd(pam_unix)[29190]: session closed for user root > Sep 28 15:04:36 mabolas kernel: NETDEV WATCHDOG: eth0: transmit timed out > Sep 28 15:04:36 mabolas kernel: tg3: eth0: transmit timed out, resetting > Sep 28 15:04:36 mabolas kernel: tg3: DEBUG: MAC_TX_STATUS[0008] > MAC_RX_STATUS[] > Sep 28 15:04:36 mabolas kernel: tg3: DEBUG: RDMAC_STATUS[] > WDMAC_STATUS[] > Sep 28 15:04:36 mabolas kernel: tg3: eth0: Link is down. > Sep 28 15:04:38 mabolas kernel: tg3: eth0: Link is up at 1000 Mbps, full > duplex. > Sep 28 15:04:38 mabolas kernel: tg3: eth0: Flow control is off for TX and > off for RX. This sounds like a bug in the tg3 driver in that kernel version. Have you checked the RedHat bugzilla to see if anyone else sees this? Depending on how the motherboard is laid out, moving the UPS to a different USB port might avoid this problem. It could have something to do with interrupt handling (for example, the tg3 driver expects an interrupt that is stolen by the USB controller). -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] stopping ups services resets my network
Hi, So anybody heard about this issue? I've been trying to troubleshoot but nothing wierd in the debug output or in syslog... Antoine -Message d'origine- De : Antoine Gatineau [mailto:antoine.gatin...@alcatel-lucent.com] Envoyé : lundi 28 septembre 2009 12:40 À : nut-upsuser@lists.alioth.debian.org Cc : antoine.gatin...@alcatel-lucent.com Objet : [Nut-upsuser] stopping ups services resets my network Hello, I have this issue: ups is working fine for a time but when I stop the services or if I unplug the ups device (over usb) I get the following in /var/log/messages I am running nut-2.4.1 on RHEL4. Sep 28 14:44:57 mabolas upsd[24151]: Signal 15: exiting Sep 28 14:45:06 mabolas upsmon[24156]: Signal 15: exiting Sep 28 15:04:10 mabolas sshd(pam_unix)[29190]: session closed for user root Sep 28 15:04:36 mabolas kernel: NETDEV WATCHDOG: eth0: transmit timed out Sep 28 15:04:36 mabolas kernel: tg3: eth0: transmit timed out, resetting Sep 28 15:04:36 mabolas kernel: tg3: DEBUG: MAC_TX_STATUS[0008] MAC_RX_STATUS[] Sep 28 15:04:36 mabolas kernel: tg3: DEBUG: RDMAC_STATUS[] WDMAC_STATUS[] Sep 28 15:04:36 mabolas kernel: tg3: eth0: Link is down. Sep 28 15:04:38 mabolas kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex. Sep 28 15:04:38 mabolas kernel: tg3: eth0: Flow control is off for TX and off for RX. As soon I kill usbhid-ups, I lost my ssh connexion. Logs say ssh is lost after 15m but in fact I couldn't type anything just after the ups stop. The network is resetted 15 minutes later. It appears this error occures only when nut has run for some days (4 days in this case). When stopping ups after few hours, nothing happens. I also have noticed some wierd behaviours on other applications that might be related. I'm not so sure it is the same so I will make a seperate thread when I have more debug info on that. Can you help me fix this? Regards, Antoine ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] stopping ups services resets my network
Hello, I have this issue: ups is working fine for a time but when I stop the services or if I unplug the ups device (over usb) I get the following in /var/log/messages I am running nut-2.4.1 on RHEL4. Sep 28 14:44:57 mabolas upsd[24151]: Signal 15: exiting Sep 28 14:45:06 mabolas upsmon[24156]: Signal 15: exiting Sep 28 15:04:10 mabolas sshd(pam_unix)[29190]: session closed for user root Sep 28 15:04:36 mabolas kernel: NETDEV WATCHDOG: eth0: transmit timed out Sep 28 15:04:36 mabolas kernel: tg3: eth0: transmit timed out, resetting Sep 28 15:04:36 mabolas kernel: tg3: DEBUG: MAC_TX_STATUS[0008] MAC_RX_STATUS[] Sep 28 15:04:36 mabolas kernel: tg3: DEBUG: RDMAC_STATUS[] WDMAC_STATUS[] Sep 28 15:04:36 mabolas kernel: tg3: eth0: Link is down. Sep 28 15:04:38 mabolas kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex. Sep 28 15:04:38 mabolas kernel: tg3: eth0: Flow control is off for TX and off for RX. As soon I kill usbhid-ups, I lost my ssh connexion. Logs say ssh is lost after 15m but in fact I couldn't type anything just after the ups stop. The network is resetted 15 minutes later. It appears this error occures only when nut has run for some days (4 days in this case). When stopping ups after few hours, nothing happens. I also have noticed some wierd behaviours on other applications that might be related. I'm not so sure it is the same so I will make a seperate thread when I have more debug info on that. Can you help me fix this? Regards, Antoine ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
