Hi! I'm running NUT 2.0.4 and occasionally I get a segfault when starting newhidups and if I don't get a segfault when starting newhidups the process starts eating away at my memory. I sat down trying to genererate -DDDDD debug info, but just because of that I can't get it to do a segfault. So until I can, has things changed in the development version, that might have fixed this? Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) Detected a UPS: American Power Conversion/Back-UPS CS 500 FW:808.q7.I USB FW:q7 Using subdriver: APC/CyberPower HID 0.9
Yes, this has been fixed some time ago in the SVN version. -- Peter Magnus Johansson wrote:> > Hi! > > I'm running NUT 2.0.4 and occasionally I get a segfault when starting > newhidups and if I don't get a segfault when starting newhidups the > process starts eating away at my memory. I sat down trying to genererate > -DDDDD debug info, but just because of that I can't get it to do a > segfault. So until I can, has things changed in the development version, > that might have fixed this? > > > Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) > Detected a UPS: American Power Conversion/Back-UPS CS 500 FW:808.q7.I > USB FW:q7 > Using subdriver: APC/CyberPower HID 0.9 > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser >
Peter Selinger skrev:> Yes, this has been fixed some time ago in the SVN version. -- PeterThank you! I got the trunk and installed it, one thing that is a bit strange to me, restarting can cause newhidups to eat up a whole lot of memory or not restart at all... [root@vader trunk]# /etc/init.d/nut start Starting Network UPS Tools: upsd upsmon. [root@vader trunk]# ps -U nut u USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND nut 11665 0.0 0.0 7212 744 ? Ss 19:36 0:00 /usr/local/ups/bin/newhidups -a VaderUPS nut 11667 0.0 0.0 10892 752 ? Ss 19:36 0:00 /usr/local/ups/sbin/upsd nut 11670 0.0 0.1 10888 1028 ? S 19:36 0:00 /usr/local/ups/sbin/upsmon [root@vader trunk]# /etc/init.d/nut restart Restarting Network UPS Tools: (upsdrvctl failed) upsd upsmon. [root@vader trunk]# ps -U nut u USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND nut 11683 0.0 0.0 10896 764 ? Ss 19:37 0:00 /usr/local/ups/sbin/upsd nut 11686 0.0 0.1 10892 1056 ? S 19:37 0:00 /usr/local/ups/sbin/upsmon nut 11687 0.0 0.0 0 0 ? Z 19:37 0:00 [upsmon] <defunct> [root@vader trunk]# /etc/init.d/nut restart Restarting Network UPS Tools: (upsdrvctl failed) upsd upsmon. [root@vader trunk]# ps -U nut u USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND nut 11701 0.0 0.0 7216 748 ? Ss 19:37 0:00 /usr/local/ups/bin/newhidups -a VaderUPS nut 11703 0.0 0.0 10896 756 ? Ss 19:37 0:00 /usr/local/ups/sbin/upsd nut 11706 0.0 0.1 10888 1028 ? S 19:37 0:00 /usr/local/ups/sbin/upsmon [root@vader trunk]# /etc/init.d/nut restart Restarting Network UPS Tools: upsd upsmon. [root@vader trunk]# ps -U nut u USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND nut 11715 0.0 20.9 208544 202076 ? Ss 19:37 0:00 /usr/local/ups/bin/newhidups -a VaderUPS nut 11717 0.0 0.0 10892 752 ? Ss 19:37 0:00 /usr/local/ups/sbin/upsd nut 11720 0.0 0.1 10888 1028 ? S 19:37 0:00 /usr/local/ups/sbin/upsmon [root@vader trunk]# /usr/local/ups/bin/newhidups Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.1.0)