Eric Masson
2006-Nov-16 15:18 UTC
[Nut-upsuser] FreeBSD 6.1, MGE Ellipse ASR600USBS, newhidups & upsd
Hello, I'm facing problems as I'm installing NUT to monitor a MGE Ellipse ASR600USBS on a FreeBSD 6.1 box. UPS is recognized as : ugen0: MGE UPS SYSTEMS ELLIPSE, rev 1.10/42.41, addr 2 I'm temporarily using root profile (devfs/devd scripts not modified atm). newhidups starts & runs fine (unplugging mains makes newhidups outputs lots of data when started with -DDDD flags) When I launch upsd, it barfs vith : emss@box:~> /usr/local/sbin/upsd -u root Password: Network UPS Tools upsd 2.0.4 Connected to UPS [mge]: newhidups-auto Synchronizing........ giving up I've tried to stop and relaunch it many times but output is always the same. Relevant config files are : # Network UPS Tools: example ups.conf user = root [mge] driver = newhidups port = auto desc = "MGE Ellipse ASR600USBS" # Network UPS Tools: example upsd configuration file ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACCEPT localhost REJECT all MAXAGE 30 # Network UPS Tools: Example upsd.users [admin] password = xxxx allowfrom = localhost actions = SET instcmds = ALL [monuser] password = yyyy allowfrom = localhost upsmon master # Network UPS Tools: example upsmon configuration RUN_AS_USER root MONITOR mge@localhost 1 monuser monuser master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -p now" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 Any idea, anyone ? Regards
Eric Masson
2006-Nov-16 15:53 UTC
[Nut-upsuser] Re: FreeBSD 6.1, MGE Ellipse ASR600USBS, newhidups & upsd
Eric Masson a ?crit : Hello,> I've tried to stop and relaunch it many times but output is always the > same.I've just received a mail from Pedro C?rte Real telling me that waiting before launching upsd could solve the problem. I've tried, but no luck. newhidups was launched 2 hours ago, and I tried to launch upsd 15 minutes ago. upsd output is : emss@box:~> sudo upsd -DDDD -u root Network UPS Tools upsd 2.0.4 Connected to UPS [mge]: newhidups-auto Synchronizing........ giving up Pinging UPS [mge] Data for UPS [mge] is stale - check driver Pinging UPS [mge] Pinging UPS [mge] Pinging UPS [mge] Pinging UPS [mge] ... Seems that it should be necessary to increase synchronizing time at upsd startup. What value would be reasonable for INITIAL_WAIT_MAX ?
Pedro CĂ´rte-Real
2006-Nov-16 16:29 UTC
[Nut-upsuser] FreeBSD 6.1, MGE Ellipse ASR600USBS, newhidups & upsd
On 11/16/06, Eric Masson <emss@free.fr> wrote:> When I launch upsd, it barfs vith : > emss@box:~> /usr/local/sbin/upsd -u root > Password: > Network UPS Tools upsd 2.0.4 > Connected to UPS [mge]: newhidups-auto > Synchronizing........ giving upThis looks like the same problem I was having. If you wait a little bit it should then work. Pedro.
Peter Selinger
2006-Nov-16 21:03 UTC
[Nut-upsuser] FreeBSD 6.1, MGE Ellipse ASR600USBS, newhidups & upsd
Your problem may be related to the way upsd and upsdrvctl interact. There are several ways to start the driver: (1) newhidups [options] auto (2) newhidups [options] -a myprofile (3) upsdrvctl start myprofile where "myprofile" is the name of a profile defined in ups.conf. Except for testing purposes, it is not recommended to start the driver directly, so you should always use method (3). The problem is that upsd needs some files in /var/state/ups to be able to locate the driver; if you start the driver by method (1), these files will be incorrectly named. -- Peter Eric Masson wrote:> > Hello, > > I'm facing problems as I'm installing NUT to monitor a MGE Ellipse > ASR600USBS on a FreeBSD 6.1 box. > > UPS is recognized as : > ugen0: MGE UPS SYSTEMS ELLIPSE, rev 1.10/42.41, addr 2 > > I'm temporarily using root profile (devfs/devd scripts not modified atm). > > newhidups starts & runs fine (unplugging mains makes newhidups outputs > lots of data when started with -DDDD flags) > > When I launch upsd, it barfs vith : > emss@box:~> /usr/local/sbin/upsd -u root > Password: > Network UPS Tools upsd 2.0.4 > Connected to UPS [mge]: newhidups-auto > Synchronizing........ giving up > > I've tried to stop and relaunch it many times but output is always the same. > > Relevant config files are : > > # Network UPS Tools: example ups.conf > user = root > [mge] > driver = newhidups > port = auto > desc = "MGE Ellipse ASR600USBS" > > # Network UPS Tools: example upsd configuration file > ACL all 0.0.0.0/0 > ACL localhost 127.0.0.1/32 > > ACCEPT localhost > REJECT all > > MAXAGE 30 > > # Network UPS Tools: Example upsd.users > [admin] > password = xxxx > allowfrom = localhost > actions = SET > instcmds = ALL > > [monuser] > password = yyyy > allowfrom = localhost > upsmon master > > # Network UPS Tools: example upsmon configuration > RUN_AS_USER root > MONITOR mge@localhost 1 monuser monuser master > MINSUPPLIES 1 > SHUTDOWNCMD "/sbin/shutdown -p now" > POLLFREQ 5 > POLLFREQALERT 5 > HOSTSYNC 15 > DEADTIME 15 > POWERDOWNFLAG /etc/killpower > RBWARNTIME 43200 > NOCOMMWARNTIME 300 > FINALDELAY 5 > > Any idea, anyone ? > > Regards > > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser@lists.alioth.debian.org > lists.alioth.debian.org/mailman/listinfo/nut-upsuser >
Bruno Wolff III
2006-Nov-24 01:00 UTC
[Nut-upsuser] FreeBSD 6.1, MGE Ellipse ASR600USBS, newhidups & upsd
On Thu, Nov 16, 2006 at 14:30:04 +0000, Pedro C?rte-Real <pedro@pedrocr.net> wrote:> On 11/16/06, Eric Masson <emss@free.fr> wrote: > >When I launch upsd, it barfs vith : > >emss@box:~> /usr/local/sbin/upsd -u root > >Password: > >Network UPS Tools upsd 2.0.4 > >Connected to UPS [mge]: newhidups-auto > >Synchronizing........ giving up > > This looks like the same problem I was having. If you wait a little > bit it should then work.It went away for me when I switched to using the 2.1 code in SVN. I was using an MGE Nova 1100 w/USB. I still see occasional loss of connections, but things seem to work a lot better in 2.1.
Arjen de Korte
2006-Nov-24 17:11 UTC
[Nut-upsuser] FreeBSD 6.1, MGE Ellipse ASR600USBS, newhidups & upsd
> I still see occasional loss of connections, but things seem to work a lot > better in 2.1.I have noticed that too. The UPSes I monitor (via serial interface) lose connection every couple of days (random) and reconnect almost immediately. I suspect that this is due to a glitch in the PING/PONG between upsd and driver. Currently, the server is not really robust in this aspect, since right after retrying to PING a driver (if it failed to respond the first time), it will be declared stale (without allowing it time to reply). This needs to be changed, so that there is time to retry at least once allowing enough time for processing it without declaring the driver stale. Best regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57
Udo van den Heuvel
2006-Nov-24 17:26 UTC
[Nut-upsuser] FreeBSD 6.1, MGE Ellipse ASR600USBS, newhidups & upsd
Arjen de Korte wrote:>> I still see occasional loss of connections, but things seem to work a lot >> better in 2.1. > > I have noticed that too. The UPSes I monitor (via serial interface) lose > connection every couple of days (random) and reconnect almost immediately.Could this be the reason for the same issue, occurring when there is USB activity on my VIA Epia box? Making the pollijg intervals larger did not yet help.