Re: [Nut-upsuser] APCsmart serial port problem
On Jun 4, 2007, at 5:57 PM, Doug Parsons wrote: > I currently have 14 of these units running on NUT 2.0.4 . They all use > the > 940-1524C black cable. In my configuration I do not use the cable > description or sdtype. I only have the drive, port and a description. > Unless there has been a change from .4 to .5 that requires the other > settings I would omit them. > > This is all on CentOS which is also a clone of RedHat on kernel 2.6. > > As for the ownership of the port, I believe you are running into an > issue > with udev. Udev creates the ports on boot up and thus is resetting the > ownership and group. > > Go to /etc/udev/permissions.d and find the section on dialup and serial > devices. You will find a line like: > > ttyS*:root:uucp:0660 > > try putting the line: > ttyS0:nut:uucp:0660 > in front of the other line. > This seems to help somewhat. The syntax is different, but it's easy to figure out. Here's what I get now: [EMAIL PROTECTED] bin]# ./apcsmart -DD -a myups Network UPS Tools (version 2.0.5) - APC Smart protocol driver Driver version 1.99.8, command table version 2.0 debug level is '2' Attempting firmware lookup Firmware: [665.6.D] Not found in table - trying normal method APC - Attempting to find command set APC - Parsing out command set UPS supports command [load.on] UPS supports command [test.panel.start] UPS supports command [calibrate.start] UPS supports command [calibrate.stop] UPS supports command [shutdown.stayoff] UPS supports command [shutdown.return] UPS supports command [test.failure.start] protocol_verify: 0x56 [V] unrecognized UPS supports command [test.battery.start] UPS supports command [test.battery.stop] UPS supports command [load.off] APC - About to get capabilities string ERROR: APC cannot do capabilites but said it could! APC - UPS capabilities determined Detected Smart-UPS 2200 RM [JS0704019003] on /dev/ttyS0 update_status: ser_send_char failed: Input/output error dstate_init: sock /var/state/ups/myups open on fd 5 smartmode: ser_send_char failed: Input/output error Communications with UPS lost - check cabling smartmode: ser_send_char failed: Input/output error Communications with UPS lost - check cabling smartmode: ser_send_char failed: Input/output error Communications with UPS lost - check cabling smartmode: ser_send_char failed: Input/output error Communications with UPS lost - check cabling smartmode: ser_send_char failed: Input/output error ^C ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can not find the Belkin F6H375-USB
On Monday 04 June 2007 6:07 pm, dcw wrote:
> On Sunday 03 June 2007 9:56 pm, dcw wrote:
> > On Sunday 03 June 2007 9:44 pm, you wrote:
> > > On 6/3/07, dcw <[EMAIL PROTECTED]> wrote:
> > > > On Sunday 03 June 2007 5:49 pm, you wrote:
> > > > > On 6/3/07, Charles Lepple <[EMAIL PROTECTED]> wrote:
> > > > > > Since you said this worked under 2.0.4 on Mandriva, I will
> > > > > > suggest that this product ID be added to the driver for the next
> > > > > > release. (The 2.0.4 Belkin HID driver apparently didn't check the
> > > > > > VID at all, just the PID.)
> > > >
> > > > But the 2.0.4 does not work on CentOS5 which is a clone of RHEL5.
> > > > The 2.0.5 does not work on CentOS5 either.
> > > > I added the following line to /etc/udev/rules.d/025_nut-usbups.rules
> > > > for version 2.0.5:
> > > > SYSFS{idVendor}=="050d", SYSFS{idProduct}=="0375", MODE="664",
> > > > GROUP="ups"
> > > >
> > > > This did not help.
> > >
> > > Did you unplug and replug the USB cable after adding this? (I think
> > > there might be a way to tell udev to rescan, but I don't know off the
> > > top of my head how that works.)
> >
> > I am sure I did but I did again, just to make sure.
> >
> > > What does the /proc/bus/usb node for the UPS look like (ls -l)
>
> after/usr/local/ups/bin/newhidups -x productid=0375 -u root -D auto
>
> > > you add the rule and re-plug the UPS?
> >
> > Everything is owned by root as follows:
> > [root]->l /proc/bus/usb
> > total 0
> > dr-xr-xr-x 2 root root 0 May 28 07:26 001
> > -r--r--r-- 1 root root 0 Jun 3 21:51 devices
> > [root]->l /proc/bus/usb/001
> > total 0
> > -rw-r--r-- 1 root root 43 May 28 07:26 001
> > -rw-r--r-- 1 root root 57 May 28 07:26 003
> > -rw-r--r-- 1 root root 52 Jun 3 21:51 009
> >
> > > > I assume that since it works on Mandriva 2006 and not CentOS5 that
> > > > there is a configuration error on CentOS separate from the nut
> > > > software. Would CentOS mailing list be the best place to ask about
> > > > that or stay with this thread and see if others have any input?
> > >
> > > Can't hurt to ask on the CentOS lists. Someone here might have some
> > > other suggestions, but that's all I have based on the error messages
> > > you sent before.
>
> I have not gotten anything from CentOS yet but I did continue to do some
> research. The following command finds the UPS:
> /usr/local/ups/bin/newhidups -x productid=0375 -u root -D auto
>
> Trying several different combinations of the above command line I have to
> have both:
> -x productid=0375
> and
> -u root
> for it to work.
>
> the ups.conf now looks like:
> driver = newhidups
> productid=0375
> port = auto
>
> adding the productid line did not help
>
> I added these lines /etc/udev/rules.d/nut-usbups.rules:
> # Belkin - Belkin-UBS
> SYSFS{idVendor}=="050d", SYSFS{idProduct}=="0375", MODE="660", GROUP="ups"
> Adding that line did not help either.
>
> FYI, when compiling nut, I use ./configure --with-user=ups
> and user ups is in group ups.
>
> SO, then I tried the upsdrvctl command with -root as an option and it
> appeared to work.
> Running upsd gave a permission denied error.
> What permissions and how do they need to be set for the upsd command to
> work?
After more research here is what makes it work
the ups.conf now looks like:
[ups]
driver = newhidups
productid=0375
port = auto
Inserted the following lines to /etc/udev/rules.d/nut-usbups.rules:
# Belkin - Belkin-UBS
SYSFS{idVendor}=="050d", SYSFS{idProduct}=="0375", MODE="660", GROUP="ups"
Then run:
/usr/local/ups/bin/upsdrvctl -u root start
chown ups:ups /var/state/ups/*
/usr/local/ups/sbin/upsd
/usr/local/ups/sbin/upsmon
/usr/local/ups/bin/upsc [EMAIL PROTECTED] ups.status
The upsc command displays:
0L CHRG
I assume the chown command above indicates that there is still a configuration
that is wrong somewhere.
Everything in /usr/local/ups is owned ups:ups.
Everthing in /var/state is ups:ups
After upsdrvctl is run there are files in /var/state/ups that have the
ownership changed to root:root.
Any ideas?
David
>
> David
>
> > Will post with CentOS. Will let you know what happens.
> >
> > Thanks for your help,
> >
> > David
> >
> > ___
> > Nut-upsuser mailing list
> > Nut-upsuser@lists.alioth.debian.org
> > http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
>
> --
> RD Woodyard, Inc.
>
> ---
>
> ___
> 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] Where to buy a db9 serial port probe
On Tuesday 05 June 2007 08:22, Dan Mahoney, System Admin wrote: > I apologize if this is slightly off topic, but I'm in the process of > trying to get NUT working and I've discovered the need for a serial > port probe that is native db9 - native db9 (the thought of hanging a > probe plus two db9-db25 adapters plus a cable on a UPS bothers me > greatly). I'm not looking for anything fancy, just a little gender > changer with a buncha LEDs on it. I suggest buying a multimeter, some wire and 2 D9 connectors, then you can use the multimeter to probe the wires to find what is going on. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgphk8hK0KZjW.pgp Description: PGP signature ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] APCsmart serial port problem
I currently have 14 of these units running on NUT 2.0.4 . They all use the 940-1524C black cable. In my configuration I do not use the cable description or sdtype. I only have the drive, port and a description. Unless there has been a change from .4 to .5 that requires the other settings I would omit them. This is all on CentOS which is also a clone of RedHat on kernel 2.6. As for the ownership of the port, I believe you are running into an issue with udev. Udev creates the ports on boot up and thus is resetting the ownership and group. Go to /etc/udev/permissions.d and find the section on dialup and serial devices. You will find a line like: ttyS*:root:uucp:0660 try putting the line: ttyS0:nut:uucp:0660 in front of the other line. I have not done this myself as I use virtual serial ports. This should set the owner to nut upon creation. The driver will take care of the port speed. Doug - Original Message - From: "Patrick Nolan" <[EMAIL PROTECTED]> To: "NUT user list" Sent: Monday, June 04, 2007 5:49 PM Subject: [Nut-upsuser] APCsmart serial port problem >I have a new APC Smart-UPS SUA2200RM2U. I've had no success with the > manufacturer's PowerChute software and smart signaling, so I have > decided to try NUT. The smartups driver can't make contact through > the serial port. > > Since this is rack-mounted, it comes with a 940-1524 serial cable. > As far as I can tell, this is supposed to work with smart signaling. > Here's my ups.conf: > [myups] > driver = apcsmart > port = /dev/ttyS0 > cable = 940-0095B > sdtype = 0 > > Here's a session which illustrates the problem: > > [root]# ls -l /dev/ttyS0 > crw--- 1 nut nut 4, 64 Jun 4 14:28 /dev/ttyS0 > [root]# /usr/local/nut/bin/upsdrvctl start > Network UPS Tools - UPS driver controller 2.0.5 > Network UPS Tools (version 2.0.5) - APC Smart protocol driver > Driver version 1.99.8, command table version 2.0 > smartmode: ser_send_char failed: Input/output error > Unable to detect an APC Smart protocol UPS on port /dev/ttyS0 > Check the cabling, port name or model name and try again > Driver failed to start (exit status=1) > [root]# ls -l /dev/ttyS0 > crw--w 1 root root 4, 64 Jun 4 14:28 /dev/ttyS0 > > The ownership of the serial port somehow got changed back to > root. The scripts in the hotplug* directories don't seem to > address this situation. By the way, this is kernel 2.6.18 > and Scientific Linux 5.0 (a clone of Red Hat Enterprise). > > Some of the other characteristics of the serial port are > changing too. After I try to start upsdrvctl, it looks like this: > [EMAIL PROTECTED] stty -F /dev/ttyS0 -a > speed 9600 baud; rows 0; columns 0; line = 0; > intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = ; > eol2 = ; swtch = ; > start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; > flush = ^O; min = 1; time = 0; > parenb parodd cs7 hupcl -cstopb cread -clocal -crtscts > -ignbrk -brkint -ignpar -parmrk inpck istrip -inlcr -igncr icrnl ixon > ixoff -iuclc -ixany -imaxbel > -iutf8 > opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 > vt0 ff0 > isig icanon -iexten -echo echoe echok -echonl -noflsh -xcase -tostop > -echoprt -echoctl echoke > > According to APC, the baud rate should be 2400. If I set it to 2400, > it gets reset to 9600. > > ___ > 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] APCsmart serial port problem
Thomas Kear wrote: > On Tue, 05 Jun 2007, Patrick Nolan wrote: >> [myups] >> driver = apcsmart >> port = /dev/ttyS0 >> cable = 940-0095B >> sdtype = 0 > > > I've got a Smart-UPS 700 (SU700I, about 5 years old) working with a more or > less identical upsd.conf, however because person I bought it from had > misplaced the serial cable, I have a pair of DB9-RJ45 adapters and a short > network cable. > > You might get some more helpful error messages if you try and start apcsmart > manually. > > # /lib/nut/apcsmart -D -a myups > [EMAIL PROTECTED] ./apcsmart -DD -a myups -u root Network UPS Tools (version 2.0.5) - APC Smart protocol driver Driver version 1.99.8, command table version 2.0 debug level is '2' Attempting firmware lookup Firmware: [665.6.D] Not found in table - trying normal method APC - Attempting to find command set Communications with UPS lost - check cabling Detected Smart-UPS [(null)] on /dev/ttyS0 Communications with UPS lost - check cabling dstate_init: sock /var/state/ups/myups open on fd 5 Communications with UPS lost - check cabling Communications with UPS lost - check cabling Communications with UPS lost - check cabling ^C Signal 2: exiting It looks as if it was able to find a firmware version string which isn't recognized. Then the communication is lost. I went with -u root because the ownership on ttyS0 keeps changing. I got tired of typing chown each time. If we assume that that problem can be ignored for the moment, it looks as if there really is a cable problem. APC says that the 940-1524 is the right cable for smart communication. In fact, it's the only one they shipped with the UPS. Does anyone have experience with this? I wonder if I should buy a 940-0024 to be sure I have the right cable? ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can not find the Belkin F6H375-USB
On Sunday 03 June 2007 9:56 pm, dcw wrote:
> On Sunday 03 June 2007 9:44 pm, you wrote:
> > On 6/3/07, dcw <[EMAIL PROTECTED]> wrote:
> > > On Sunday 03 June 2007 5:49 pm, you wrote:
> > > > On 6/3/07, Charles Lepple <[EMAIL PROTECTED]> wrote:
> > > > > Since you said this worked under 2.0.4 on Mandriva, I will suggest
> > > > > that this product ID be added to the driver for the next release.
> > > > > (The 2.0.4 Belkin HID driver apparently didn't check the VID at
> > > > > all, just the PID.)
> > >
> > > But the 2.0.4 does not work on CentOS5 which is a clone of RHEL5.
> > > The 2.0.5 does not work on CentOS5 either.
> > > I added the following line to /etc/udev/rules.d/025_nut-usbups.rules
> > > for version 2.0.5:
> > > SYSFS{idVendor}=="050d", SYSFS{idProduct}=="0375", MODE="664",
> > > GROUP="ups"
> > >
> > > This did not help.
> >
> > Did you unplug and replug the USB cable after adding this? (I think
> > there might be a way to tell udev to rescan, but I don't know off the
> > top of my head how that works.)
>
> I am sure I did but I did again, just to make sure.
>
> > What does the /proc/bus/usb node for the UPS look like (ls -l)
after/usr/local/ups/bin/newhidups -x productid=0375 -u root -D auto
> > you add the rule and re-plug the UPS?
>
> Everything is owned by root as follows:
> [root]->l /proc/bus/usb
> total 0
> dr-xr-xr-x 2 root root 0 May 28 07:26 001
> -r--r--r-- 1 root root 0 Jun 3 21:51 devices
> [root]->l /proc/bus/usb/001
> total 0
> -rw-r--r-- 1 root root 43 May 28 07:26 001
> -rw-r--r-- 1 root root 57 May 28 07:26 003
> -rw-r--r-- 1 root root 52 Jun 3 21:51 009
>
> > > I assume that since it works on Mandriva 2006 and not CentOS5 that
> > > there is a configuration error on CentOS separate from the nut
> > > software. Would CentOS mailing list be the best place to ask about that
> > > or stay with this thread and see if others have any input?
> >
> > Can't hurt to ask on the CentOS lists. Someone here might have some
> > other suggestions, but that's all I have based on the error messages
> > you sent before.
I have not gotten anything from CentOS yet but I did continue to do some
research. The following command finds the UPS:
/usr/local/ups/bin/newhidups -x productid=0375 -u root -D auto
Trying several different combinations of the above command line I have to
have both:
-x productid=0375
and
-u root
for it to work.
the ups.conf now looks like:
driver = newhidups
productid=0375
port = auto
adding the productid line did not help
I added these lines /etc/udev/rules.d/nut-usbups.rules:
# Belkin - Belkin-UBS
SYSFS{idVendor}=="050d", SYSFS{idProduct}=="0375", MODE="660", GROUP="ups"
Adding that line did not help either.
FYI, when compiling nut, I use ./configure --with-user=ups
and user ups is in group ups.
SO, then I tried the upsdrvctl command with -root as an option and it appeared
to work.
Running upsd gave a permission denied error.
What permissions and how do they need to be set for the upsd command to work?
David
> Will post with CentOS. Will let you know what happens.
>
> Thanks for your help,
>
> David
>
> ___
> Nut-upsuser mailing list
> Nut-upsuser@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
--
RD Woodyard, Inc.
---
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can not find the Belkin F6H375-USB
On Sunday 03 June 2007 9:56 pm, dcw wrote:
> On Sunday 03 June 2007 9:44 pm, you wrote:
> > On 6/3/07, dcw <[EMAIL PROTECTED]> wrote:
> > > On Sunday 03 June 2007 5:49 pm, you wrote:
> > > > On 6/3/07, Charles Lepple <[EMAIL PROTECTED]> wrote:
> > > > > Since you said this worked under 2.0.4 on Mandriva, I will suggest
> > > > > that this product ID be added to the driver for the next release.
> > > > > (The 2.0.4 Belkin HID driver apparently didn't check the VID at
> > > > > all, just the PID.)
> > >
> > > But the 2.0.4 does not work on CentOS5 which is a clone of RHEL5.
> > > The 2.0.5 does not work on CentOS5 either.
> > > I added the following line to /etc/udev/rules.d/025_nut-usbups.rules
> > > for version 2.0.5:
> > > SYSFS{idVendor}=="050d", SYSFS{idProduct}=="0375", MODE="664",
> > > GROUP="ups"
> > >
> > > This did not help.
> >
> > Did you unplug and replug the USB cable after adding this? (I think
> > there might be a way to tell udev to rescan, but I don't know off the
> > top of my head how that works.)
>
> I am sure I did but I did again, just to make sure.
>
> > What does the /proc/bus/usb node for the UPS look like (ls -l)
after/usr/local/ups/bin/newhidups -x productid=0375 -u root -D auto
> > you add the rule and re-plug the UPS?
>
> Everything is owned by root as follows:
> [root]->l /proc/bus/usb
> total 0
> dr-xr-xr-x 2 root root 0 May 28 07:26 001
> -r--r--r-- 1 root root 0 Jun 3 21:51 devices
> [root]->l /proc/bus/usb/001
> total 0
> -rw-r--r-- 1 root root 43 May 28 07:26 001
> -rw-r--r-- 1 root root 57 May 28 07:26 003
> -rw-r--r-- 1 root root 52 Jun 3 21:51 009
>
> > > I assume that since it works on Mandriva 2006 and not CentOS5 that
> > > there is a configuration error on CentOS separate from the nut
> > > software. Would CentOS mailing list be the best place to ask about that
> > > or stay with this thread and see if others have any input?
> >
> > Can't hurt to ask on the CentOS lists. Someone here might have some
> > other suggestions, but that's all I have based on the error messages
> > you sent before.
I have not gotten anything from CentOS yet but I did continue to do some
research. The following command finds the UPS:
/usr/local/ups/bin/newhidups -x productid=0375 -u root -D auto
Trying several different combinations of the above command line I have to have
both:
-x productid=0375
and
-u root
for it to work.
the ups.conf now looks like:
driver = newhidups
productid=0375
port = auto
adding the productid line did not help
I added these lines /etc/udev/rules.d/nut-usbups.rules:
# Belkin - Belkin-UBS
SYSFS{idVendor}=="050d", SYSFS{idProduct}=="0375", MODE="660", GROUP="ups"
Adding that line did not help either.
FYI, when compiling nut, I use ./configure --with-user=ups
and user ups is in group ups.
SO, the only command that recognizes the UPS is:
/usr/local/ups/bin/newhidups -x productid=0375 -u root -D auto
Therefore, I have a configuration error but I can not figure out where it
could be.
Does the above help indicate to you where the configuration is wrong?
David
>
> Will post with CentOS. Will let you know what happens.
>
> Thanks for your help,
>
> David
>
> ___
> Nut-upsuser mailing list
> Nut-upsuser@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
--
RD Woodyard, Inc.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Where to buy a db9 serial port probe
All I apologize if this is slightly off topic, but I'm in the process of trying to get NUT working and I've discovered the need for a serial port probe that is native db9 - native db9 (the thought of hanging a probe plus two db9-db25 adapters plus a cable on a UPS bothers me greatly). I'm not looking for anything fancy, just a little gender changer with a buncha LEDs on it. However, every search for "db9/analyzer/probe/breakout/rs232" and any combination thereof has yielded crap results except for one for $40 from BlackBox, and quite frankly that's a bit much for a piece of hardware I'll use ONCE. David Harris, serial guru shows a pic of this on a page of his: http://www.conserver.com/consoles/Tracers/DB9-tracer-bicolor.jpg But says this model is BAD because of the way the LEDs are soldered (I really do not care), but I cannot find out how to find this device at ALL. Anyone else have any clues? -Dan -- Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] APCsmart serial port problem
On Tue, 05 Jun 2007, Patrick Nolan wrote: > [myups] > driver = apcsmart > port = /dev/ttyS0 > cable = 940-0095B > sdtype = 0 I've got a Smart-UPS 700 (SU700I, about 5 years old) working with a more or less identical upsd.conf, however because person I bought it from had misplaced the serial cable, I have a pair of DB9-RJ45 adapters and a short network cable. You might get some more helpful error messages if you try and start apcsmart manually. # /lib/nut/apcsmart -D -a myups should work for your system. '-D' = verbose (try up to -DDD or -), '-a [upsname]' tells apcsmart to read upsd.conf for its config. I get this output from my UPS: # /lib/nut/apcsmart -D -a su700 Network UPS Tools (version 2.0.5) - APC Smart protocol driver Driver version 1.99.8, command table version 2.0 debug level is '1' Attempting firmware lookup APC - Attempting to find command set APC - Parsing out command set protocol_verify: 0x56 [V] unrecognized APC - About to get capabilities string Supported capability: 75 (I) - input.transfer.high Supported capability: 6c (I) - input.transfer.low Supported capability: 65 (4) - battery.charge.restart Supported capability: 6f (I) - output.voltage.nominal Supported capability: 73 (4) - input.sensitivity Supported capability: 71 (4) - battery.runtime.low Supported capability: 70 (4) - ups.delay.shutdown Supported capability: 6b (4) - battery.alarm.threshold Supported capability: 72 (4) - ups.delay.start Supported capability: 45 (4) - ups.test.interval APC - UPS capabilities determined Detected SMART-UPS 700 [GS0017000324] on /dev/ttyS0 If you can't find anything from software, it might be worth getting a multimeter out and checking the serial cable's wiring. signature.asc Description: This is a digitally signed message part. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] APCsmart serial port problem
I have a new APC Smart-UPS SUA2200RM2U. I've had no success with the manufacturer's PowerChute software and smart signaling, so I have decided to try NUT. The smartups driver can't make contact through the serial port. Since this is rack-mounted, it comes with a 940-1524 serial cable. As far as I can tell, this is supposed to work with smart signaling. Here's my ups.conf: [myups] driver = apcsmart port = /dev/ttyS0 cable = 940-0095B sdtype = 0 Here's a session which illustrates the problem: [root]# ls -l /dev/ttyS0 crw--- 1 nut nut 4, 64 Jun 4 14:28 /dev/ttyS0 [root]# /usr/local/nut/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools (version 2.0.5) - APC Smart protocol driver Driver version 1.99.8, command table version 2.0 smartmode: ser_send_char failed: Input/output error Unable to detect an APC Smart protocol UPS on port /dev/ttyS0 Check the cabling, port name or model name and try again Driver failed to start (exit status=1) [root]# ls -l /dev/ttyS0 crw--w 1 root root 4, 64 Jun 4 14:28 /dev/ttyS0 The ownership of the serial port somehow got changed back to root. The scripts in the hotplug* directories don't seem to address this situation. By the way, this is kernel 2.6.18 and Scientific Linux 5.0 (a clone of Red Hat Enterprise). Some of the other characteristics of the serial port are changing too. After I try to start upsdrvctl, it looks like this: [EMAIL PROTECTED] stty -F /dev/ttyS0 -a speed 9600 baud; rows 0; columns 0; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = ; eol2 = ; swtch = ; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0; parenb parodd cs7 hupcl -cstopb cread -clocal -crtscts -ignbrk -brkint -ignpar -parmrk inpck istrip -inlcr -igncr icrnl ixon ixoff -iuclc -ixany -imaxbel -iutf8 opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 isig icanon -iexten -echo echoe echok -echonl -noflsh -xcase -tostop -echoprt -echoctl echoke According to APC, the baud rate should be 2400. If I set it to 2400, it gets reset to 9600. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] MGE evolution s1250 all values = '2'
Hi, We use gentoo on amd 64 (kernel, ldd etc on the gzip file) You can have access to the machine as root on a screen if you want, it's a devellopement server. Thank you David nutdebug.gz Description: GNU Zip compressed data Le 4 juin 07 à 13:37, Arnaud Quette a écrit : Hello David, 2007/6/2, David Charbonnier <[EMAIL PROTECTED]>: Hi, I think my problem will be easy to resolve ... I don't understand why the ups return the value 2.00 for all variables ... I've been looking for 1 hour on google and I can't find similar problem. first time I see this one! goburge ~ # /lib64/nut/newhidups -D /dev/ttyS0 Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) debug level is '1' Detected a UPS: MGE UPS SYSTEMS/Evolution Using subdriver: MGE HID 1.0 Path: UPS.BatterySystem.Battery.AudibleAlarmControl, Type: Feature, Value: 2.00 Path: UPS.BatterySystem.Battery.BatteryID, Type: Feature, Value: 2.00 Path: UPS.BatterySystem.Battery.Count, Type: Feature, Value: 2.00 Path: UPS.BatterySystem.Battery.DeepDischargeProtection, Type: Feature, Value: 2.00 Path: UPS.BatterySystem.Battery.DesignCapacity, Type: Feature, Value: 2.00 Path: UPS.BatterySystem.Battery.PresentStatus.Present, Type: Feature, Value: 2.00 Path: UPS.BatterySystem.Battery.PresentStatus.Present, Type: Input, Value: 2.00 Path: UPS.BatterySystem.Battery.Test, Type: Feature, Value: 2.00 Path: UPS.BatterySystem.Battery.TestPeriod, Type: Feature, Value: 2.00 I will need some very verbose info to see what's wrong: - export USB_DEBUG=3 - newhidups -D auto Can you also provide some more info about the context: - OS name and version - version of kernel and libusb - file /newhidups - ldd /newhidups please, send these back gzip'ed. Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http:// www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource 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] MGE evolution s1250 all values = '2'
Hello David, 2007/6/2, David Charbonnier <[EMAIL PROTECTED]>: > Hi, > > I think my problem will be easy to resolve ... I don't understand why > the ups return the value 2.00 for all variables ... I've been > looking for 1 hour on google and I can't find similar problem. first time I see this one! > goburge ~ # /lib64/nut/newhidups -D /dev/ttyS0 > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 > (2.0.5) > > debug level is '1' > Detected a UPS: MGE UPS SYSTEMS/Evolution > Using subdriver: MGE HID 1.0 > Path: UPS.BatterySystem.Battery.AudibleAlarmControl, Type: Feature, > Value: 2.00 > Path: UPS.BatterySystem.Battery.BatteryID, Type: Feature, Value: > 2.00 > Path: UPS.BatterySystem.Battery.Count, Type: Feature, Value: 2.00 > Path: UPS.BatterySystem.Battery.DeepDischargeProtection, Type: > Feature, Value: 2.00 > Path: UPS.BatterySystem.Battery.DesignCapacity, Type: Feature, Value: > 2.00 > Path: UPS.BatterySystem.Battery.PresentStatus.Present, Type: Feature, > Value: 2.00 > Path: UPS.BatterySystem.Battery.PresentStatus.Present, Type: Input, > Value: 2.00 > Path: UPS.BatterySystem.Battery.Test, Type: Feature, Value: 2.00 > Path: UPS.BatterySystem.Battery.TestPeriod, Type: Feature, Value: > 2.00 I will need some very verbose info to see what's wrong: - export USB_DEBUG=3 - newhidups -D auto Can you also provide some more info about the context: - OS name and version - version of kernel and libusb - file /newhidups - ldd /newhidups please, send these back gzip'ed. Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource 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
[Nut-upsuser] Network UPS Tools version 2.2.0-pre1 released
Network UPS Tools version 2.2.0-pre1 has been released. http://www.networkupstools.org/ Direct access: - Download: http://www.networkupstools.org/source/2.2/testing/nut-2.2.0-pre1.tar.gz - News: http://www.networkupstools.org/source/2.2/testing/new-2.2.0-pre1.txt - ChangeLog: http://www.networkupstools.org/source/2.2/testing/ChangeLog The NEWS file (new-2.2.0-pre1.txt) still has to be updated, along with some documentation update for the integration of HAL. This will get into the -pre2 release. Arnaud and the NUT team -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource 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
