Re: [Nut-upsuser] Best Power FE700VA?
On 03/22/2018 07:43 PM, Charles Lepple wrote: If the Slackware startup scripts call "upsdrvctl start", and the UPS is listed in ups.conf, that should start the driver at boot. Now I see that also after doing necessary things in http://networkupstools.org/docs/user-manual.chunked/index.html chapters five and six (only difference was package I'm using doesn't use /usr/local.) So, it's set do all necessary; thanks very much for help so far! However, it doesn't start unless I add to /etc/rc.d/rc.local. Is there a log to show why? I'd like to fix standard setup, then relearn setting up each UPS to be network-/HTTP-controlled. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Best Power FE700VA?
On Mar 22, 2018, at 10:22 PM, David Melik wrote: > > I assume if I just go through the setup instructions on the NUT website, > that'll make the server automatically load this driver on boot. If the Slackware startup scripts call "upsdrvctl start", and the UPS is listed in ups.conf, that should start the driver at boot. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Best Power FE700VA?
On 03/21/2018 07:07 PM, Charles Lepple wrote: On Mar 20, 2018, at 6:06 PM, David Melik wrote: Ok, around 24hrs ago I retested, but the (same) output is still on the screen without it going into background to release tty/sh... My mistake - I misinterpreted the log you posted. Without the "-D" flag, the driver should go into the background in a matter of seconds, usually. Can you run the driver under strace, and see where it gets stuck? Or did you only run it with the "-D" flag? In that case, if you are getting "Connection refused" from "upsc", you might need to start "upsd" by hand. Of course I did (-D) so (without,) works now. I assume if I just go through the setup instructions on the NUT website, that'll make the server automatically load this driver on boot. I did that before, even with some differences between default and Slackware's unofficial versions, even when having to note/change a few different things. That was with USB UPSes, so maybe it'll be different with this serial port one... forgot most the details, but it's not that hard after setting up a few USB ones. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Best Power FE700VA?
On Mar 20, 2018, at 6:06 PM, David Melik wrote: > > On 03/19/2018 04:49 AM, Charles Lepple wrote: >> The rc-style init systems typically want programs like the drivers to go >> into the background on their own (as the driver does without "-D", or when >> launched by "upsdrvctl start"). Other init systems like launchd or systemd >> will monitor the PID of the program to restart it if necessary, so they work >> best when the driver doesn't fork. > > Ok, around 24hrs ago I retested, but the (same) output is still on the screen > without it going into background to release tty/sh... My mistake - I misinterpreted the log you posted. Without the "-D" flag, the driver should go into the background in a matter of seconds, usually. Can you run the driver under strace, and see where it gets stuck? Or did you only run it with the "-D" flag? In that case, if you are getting "Connection refused" from "upsc", you might need to start "upsd" by hand. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Best Power FE700VA?
On 03/19/2018 04:49 AM, Charles Lepple wrote: The rc-style init systems typically want programs like the drivers to go into the background on their own (as the driver does without "-D", or when launched by "upsdrvctl start"). Other init systems like launchd or systemd will monitor the PID of the program to restart it if necessary, so they work best when the driver doesn't fork. Ok, around 24hrs ago I retested, but the (same) output is still on the screen without it going into background to release tty/sh... Here's output I got within the last few minutes, just wondering how to complete configuration now (if this is working)... root@darwinheim:~# Network UPS Tools - Best Ferrups/Fortress driver 0.12 (2.7.4) Warning: This is an experimental driver. Some features may not function correctly. 0.00 debug level is '1' 8.434336 UPS Time: Saturday, July 18, 2009 - 16:01:08 26.245736 Best Power Ferrups FE700 detected 26.245755 Battery voltages: 13.58 nominal, 14.90 full, 11.00 low, 10.50 empty This driver doesn't have any additional configuration options (or many debug log messages, for that matter), so the next step is to be sure that upsd has started, and run "upsc ups" to see all of the values. The rest of the configuration is split between upsd (defining roles for monitoring) and upsmon (defining how to shut down or notify you of other events). root@darwinheim:~# upsc ups Error: Connection failure: Connection refused Some things (one might use for an organization) I won't need to set up (as maybe said, it's just my server at home)... maybe would be nice to monitor from my PC. --D ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Best Power FE700VA?
On Mar 19, 2018, at 4:00 AM, David Melik wrote: > >> Then you can launch the driver with at least one "-D" flag: >> >> /usr/libexec/nut/bestfcom -a ups -D > > I thought there was a lot more to it than that, but after I ran that stuff, > the driver outputs. However, /etc/rc.d/rc.ups initialization script might > not do anything yet (only the command you gave, also when forked, or it will > continue using the tty.) The rc-style init systems typically want programs like the drivers to go into the background on their own (as the driver does without "-D", or when launched by "upsdrvctl start"). Other init systems like launchd or systemd will monitor the PID of the program to restart it if necessary, so they work best when the driver doesn't fork. > > Here's output I got within the last few minutes, just wondering how to > complete configuration now (if this is working)... > > root@darwinheim:~# Network UPS Tools - Best Ferrups/Fortress driver 0.12 > (2.7.4) > > Warning: This is an experimental driver. > > Some features may not function correctly. > >0.00 debug level is '1' > > 8.434336 UPS Time: Saturday, July 18, 2009 - 16:01:08 > > 26.245736 Best Power Ferrups FE700 detected > > 26.245755 Battery voltages: 13.58 nominal, 14.90 full, 11.00 low, 10.50 > empty This driver doesn't have any additional configuration options (or many debug log messages, for that matter), so the next step is to be sure that upsd has started, and run "upsc ups" to see all of the values. The rest of the configuration is split between upsd (defining roles for monitoring) and upsmon (defining how to shut down or notify you of other events). ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Best Power FE700VA?
On 02/20/2018 06:16 PM, Charles Lepple wrote: Do you have a pinout for that cable? Unsure, but after recent suggestions, it may be working. Already had NUT from SlackBuilds.org (SBo) installed, but reinstalled to add the group:user. I forget if it is the default, but you might need to turn off the hardware and software flow control (minicom: Ctrl-A then letter O, "Serial port setup"). I would also recommend double-checking the serial port name (sometimes motherboards swap the headers around). That said, if you have a maintenance window, it may be worth trying the bestfcom driver directly. It will set up all of the serial port parameters, and attempt to get an identification string. I'm not sure if this is the recommended place to get NUT for Slackware, but this looks promising: https://slackbuilds.org/repository/14.2/system/nut/ I don't have a maintenance window but sounded like recent suggestions were easier. Some official Slackware team members run SlackBuilds.org but its software isn't official... I call some quasi-official, and some gets added/redone for Slackware later. For testing, you only need to do the first two steps (through "usermod -a -G dialout nut") after building. Then, add a section to ups.conf that looks like this: [ups] driver = bestfcom port = /dev/ttyS0 ### replace with the actual serial port name. Then you can launch the driver with at least one "-D" flag: /usr/libexec/nut/bestfcom -a ups -D I thought there was a lot more to it than that, but after I ran that stuff, the driver outputs. However, /etc/rc.d/rc.ups initialization script might not do anything yet (only the command you gave, also when forked, or it will continue using the tty.) Here's output I got within the last few minutes, just wondering how to complete configuration now (if this is working)... root@darwinheim:~# Network UPS Tools - Best Ferrups/Fortress driver 0.12 (2.7.4) Warning: This is an experimental driver. Some features may not function correctly. 0.00 debug level is '1' 8.434336 UPS Time: Saturday, July 18, 2009 - 16:01:08 26.245736 Best Power Ferrups FE700 detected 26.245755 Battery voltages: 13.58 nominal, 14.90 full, 11.00 low, 10.50 empty :D --D ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Best Power FE700VA?
On Feb 19, 2018, at 3:44 PM, David Melik wrote: > > Minicom listed a blank modem init string, and 'f' did nothing. Do you have a pinout for that cable? I forget if it is the default, but you might need to turn off the hardware and software flow control (minicom: Ctrl-A then letter O, "Serial port setup"). I would also recommend double-checking the serial port name (sometimes motherboards swap the headers around). That said, if you have a maintenance window, it may be worth trying the bestfcom driver directly. It will set up all of the serial port parameters, and attempt to get an identification string. I'm not sure if this is the recommended place to get NUT for Slackware, but this looks promising: https://slackbuilds.org/repository/14.2/system/nut/ For testing, you only need to do the first two steps (through "usermod -a -G dialout nut") after building. Then, add a section to ups.conf that looks like this: [ups] driver = bestfcom port = /dev/ttyS0 ### replace with the actual serial port name. Then you can launch the driver with at least one "-D" flag: /usr/libexec/nut/bestfcom -a ups -D ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Best Power FE700VA?
On 02/13/2018 03:49 AM, Charles Lepple wrote: On Feb 12, 2018, at 11:53 PM, David Melik wrote: On 01/21/2018 05:53 AM, Charles Lepple wrote: If you hook up a terminal emulator to the comms port (1200 baud, 8/N/1 unless stickers and/or configuration DIP switches indicate otherwise), and type "f" , do you get a status line like one of the following? https://github.com/networkupstools/nut/blob/v2.7.4/drivers/bestfcom.c#L226-L244 Of course, I got Eaton Powerware's RS-232 cable for FE700VA/etc. but don't know what 'hook up a terminal emulator'... no Slackware GNU/Linux BASH command 'f,' or do I run (or install/compile) a certain program to enable/access that? minicom or screen should work - after you configure the serial port settings, they will show everything sent by the UPS, and you can enter the "f" command in that session. For initial setup, you can run "minicom -s" and it takes you right to the configuration screen. You will probably want to clear out some of the modem init strings if they are present - the UPS will likely not understand them. Minicom listed a blank modem init string, and 'f' did nothing. I didn't see how to do anything similar in screen. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Best Power FE700VA?
On 02/12/2018 11:53 PM, David Melik wrote: > > Of course, I got Eaton Powerware's RS-232 cable for FE700VA/etc. but > don't know what 'hook up a terminal emulator'... no Slackware > GNU/Linux BASH command 'f,' or do I run (or install/compile) a certain > program to enable/access that? The classic terminal emulator is 'cu': http://www.airs.com/ian/uucp.html RedHat and Fedora have a package for it. I rolled my own with special features to handle file transfers to mini-computers that can't turn off echo... There are other packages like minicom, kermit, etc, that support more advanced file transfer over serial lines. But the file transfer features are irrelevant to talking to a UPS. Serial communication can be quickly jury rigged in an apocalypse - unlike ethernet, USB, and other modern (and much faster) wire protocols. Keep such software archived. Note that even if computers no longer come with UARTs, you can still do serial communication with digital input/output and a timer interrupt. (I found 3 DI samples per bit time works reliably.) I have a real wyse60 CRT terminal if you are interested. :-) Once you connect to the serial port with your terminal emulator at the proper baud rate, it is like a shell prompt - except the UPS has only a few one letter commands. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Best Power FE700VA?
On Feb 12, 2018, at 11:53 PM, David Melik wrote: > > On 01/21/2018 05:53 AM, Charles Lepple wrote: >> If you hook up a terminal emulator to the comms port (1200 baud, 8/N/1 >> unless stickers and/or configuration DIP switches indicate otherwise), and >> type "f" , do you get a status line like one of the following? >> >> >> https://github.com/networkupstools/nut/blob/v2.7.4/drivers/bestfcom.c#L226-L244 > > Of course, I got Eaton Powerware's RS-232 cable for FE700VA/etc. but don't > know what 'hook up a terminal emulator'... no Slackware GNU/Linux BASH > command 'f,' or do I run (or install/compile) a certain program to > enable/access that? minicom or screen should work - after you configure the serial port settings, they will show everything sent by the UPS, and you can enter the "f" command in that session. For initial setup, you can run "minicom -s" and it takes you right to the configuration screen. You will probably want to clear out some of the modem init strings if they are present - the UPS will likely not understand them. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Best Power FE700VA?
On 01/21/2018 05:53 AM, Charles Lepple wrote: My understanding was that many of the older Best Power units were downstream of generators, and as such, full-blown power outages of both mains and generator power were not expected. That said, it might be that the "bestfcom" driver predates when we were actively collecting specific model names for the Hardware Compatibility List and the Device Dump Library. Does the manual linked below describe your model? http://unifiedpowerusa.com/wp-content/uploads/2017/04/ferrups-users-guide.pdf If you hook up a terminal emulator to the comms port (1200 baud, 8/N/1 unless stickers and/or configuration DIP switches indicate otherwise), and type "f" , do you get a status line like one of the following? https://github.com/networkupstools/nut/blob/v2.7.4/drivers/bestfcom.c#L226-L244 Of course, I got Eaton Powerware's RS-232 cable for FE700VA/etc. but don't know what 'hook up a terminal emulator'... no Slackware GNU/Linux BASH command 'f,' or do I run (or install/compile) a certain program to enable/access that? Let us know how it goes, and we can update the various compatibility lists: http://buildbot.networkupstools.org/~buildbot/docker-debian-jessie/docs/latest/stable-hcl.html#footnotes Certainly, once I figure this out... ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Best Power FE700VA?
On Jan 21, 2018, at 1:12 AM, David Melik wrote: > > I have an excellent old Best Power FE700VA but am suprised it's unlisted. I > thought Best Power ones were for critical applications, mostly for > POSIX-based (Unix, etc.) servers, so I want to run it on 64-bit Slackware > GNU/Linux. I'm wondering why, or if it may be added in the future, or if > there are any other options. My understanding was that many of the older Best Power units were downstream of generators, and as such, full-blown power outages of both mains and generator power were not expected. That said, it might be that the "bestfcom" driver predates when we were actively collecting specific model names for the Hardware Compatibility List and the Device Dump Library. Does the manual linked below describe your model? http://unifiedpowerusa.com/wp-content/uploads/2017/04/ferrups-users-guide.pdf If you hook up a terminal emulator to the comms port (1200 baud, 8/N/1 unless stickers and/or configuration DIP switches indicate otherwise), and type "f" , do you get a status line like one of the following? https://github.com/networkupstools/nut/blob/v2.7.4/drivers/bestfcom.c#L226-L244 Let us know how it goes, and we can update the various compatibility lists: http://buildbot.networkupstools.org/~buildbot/docker-debian-jessie/docs/latest/stable-hcl.html#footnotes -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
