Re: [Nut-upsuser] FreeBSD 6.1, MGE Ellipse ASR600USBS, newhidups upsd

2006-11-24 Thread Arnaud Quette
2006/11/16, Bruno Wolff III [EMAIL PROTECTED]: On Thu, Nov 16, 2006 at 14:30:04 +, Pedro Côrte-Real [EMAIL PROTECTED] wrote: On 11/16/06, Eric Masson [EMAIL PROTECTED] wrote: When I launch upsd, it barfs vith : [EMAIL PROTECTED]:~ /usr/local/sbin/upsd -u root Password: Network UPS

Re: [Nut-upsuser] FreeBSD 6.1, MGE Ellipse ASR600USBS, newhidups upsd

2006-11-24 Thread Udo van den Heuvel
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

Re: [Nut-upsuser] FreeBSD 6.1, MGE Ellipse ASR600USBS, newhidups upsd

2006-11-23 Thread Bruno Wolff III
On Thu, Nov 16, 2006 at 14:30:04 +, Pedro Côrte-Real [EMAIL PROTECTED] wrote: On 11/16/06, Eric Masson [EMAIL PROTECTED] wrote: When I launch upsd, it barfs vith : [EMAIL PROTECTED]:~ /usr/local/sbin/upsd -u root Password: Network UPS Tools upsd 2.0.4 Connected to UPS [mge]:

[Nut-upsuser] FreeBSD 6.1, MGE Ellipse ASR600USBS, newhidups upsd

2006-11-16 Thread Eric Masson
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

Re: [Nut-upsuser] FreeBSD 6.1, MGE Ellipse ASR600USBS, newhidups upsd

2006-11-16 Thread Pedro Côrte-Real
On 11/16/06, Eric Masson [EMAIL PROTECTED] wrote: When I launch upsd, it barfs vith : [EMAIL PROTECTED]:~ /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

Re: [Nut-upsuser] FreeBSD 6.1, MGE Ellipse ASR600USBS, newhidups upsd

2006-11-16 Thread Peter Selinger
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