Hi, I'm trying to set up my ups [Powermate 3105] so far :
1/ It's recognised as 'Vendor=0592 Prodid=0002'
2/ Kernel message : 'reddwarf kernel: usb 2-1: new low speed USB device using uhci_hcd and address 2'
I installed 'CheckUPS' from Powermate.com.au
Read posts at marc.theaimsgroup, didn't appear to help (serial connections as against usb)
Have problems in understanding which port or pipe to use.
similar problem in uderstanding how you start it running and the config files for me are murder to work through.
I realy need someone to help me install/run Nut/CheckUPS
Thanks david
On Sat, 24 Sep 2005, david walcroft wrote:
Hi, I'm trying to set up my ups [Powermate 3105] so far :
1/ It's recognised as 'Vendor=0592 Prodid=0002'
2/ Kernel message : 'reddwarf kernel: usb 2-1: new low speed USB device using uhci_hcd and address 2'
I installed 'CheckUPS' from Powermate.com.au
Read posts at marc.theaimsgroup, didn't appear to help (serial connections as against usb)
Have problems in understanding which port or pipe to use.
similar problem in uderstanding how you start it running and the config files for me are murder to work through.
I realy need someone to help me install/run Nut/CheckUPS
Thanks david
ALthough there's no documentation refrerring to it, you need to configure nut in FC using /etc/sysconfig/ups. Things that you can set there need to be set there. Other things are configured using the files in /etc/ups.
Also, there's a bug against the kernel (can't get to Bugzilla to check the number just now due to flakey net connection) regarding the hidups driver and unhandled interrupts that may cause you problems (unless it's fixed in the latest updates-testing kernel).
Matthew Saltzman wrote:
On Sat, 24 Sep 2005, david walcroft wrote:
Hi, I'm trying to set up my ups [Powermate 3105] so far :
1/ It's recognised as 'Vendor=0592 Prodid=0002'
2/ Kernel message : 'reddwarf kernel: usb 2-1: new low speed USB device using uhci_hcd and address 2'
I installed 'CheckUPS' from Powermate.com.au
Read posts at marc.theaimsgroup, didn't appear to help (serial connections as against usb)
Have problems in understanding which port or pipe to use.
similar problem in uderstanding how you start it running and the config files for me are murder to work through.
I realy need someone to help me install/run Nut/CheckUPS
Thanks david
ALthough there's no documentation refrerring to it, you need to configure nut in FC using /etc/sysconfig/ups. Things that you can set there need to be set there. Other things are configured using the files in /etc/ups.
Also, there's a bug against the kernel (can't get to Bugzilla to check the number just now due to flakey net connection) regarding the hidups driver and unhandled interrupts that may cause you problems (unless it's fixed in the latest updates-testing kernel).
Matthew, Progress so far,read Bugzilla Bug 164051 and 160700 Very helpful upgraded to nut 2.0.2.1 and able start nut with the result :
[david@reddwarf ~]$ sudo service ups restart Stopping UPS monitor: [FAILED] Stopping upsd: [FAILED] Shutting down Powermate-3105: [FAILED] Starting Powermate-3105: /etc/init.d/functions: line 148: /sbin/Powermate-3105: No such file or directory [FAILED] Starting upsd: Network UPS Tools upsd 2.0.2 Can't chdir to /var/run/nut: No such file or directory [FAILED] Starting UPS monitor (master): Network UPS Tools upsmon 2.0.1 UPS: genericups@reddwarf (master) (power value 1) Using power down flag file /etc/killpower
[ OK ] But not able to tell if nut is doing anything.
Thanks david
david walcroft kirjoitti viestissään (lähetysaika lauantai, 24. syyskuuta 2005 11:13):
Very helpful upgraded to nut 2.0.2.1 and able start nut with the result :
[david@reddwarf ~]$ sudo service ups restart Stopping UPS monitor: [FAILED] Stopping upsd: [FAILED] Shutting down Powermate-3105: [FAILED] Starting Powermate-3105: /etc/init.d/functions: line 148: /sbin/Powermate-3105: No such file or directory
[FAILED] Starting upsd: Network UPS Tools upsd 2.0.2
Nut is _not_ starting, you haven't configured it correctly. Nut doesn't have a driver called "Powermate-3105". You must be confusing the driver name with the name of your UPS.
Markku Kolkka wrote:
david walcroft kirjoitti viestissään (lähetysaika lauantai, 24. syyskuuta 2005 11:13):
Very helpful upgraded to nut 2.0.2.1 and able start nut with the result :
[david@reddwarf ~]$ sudo service ups restart Stopping UPS monitor: [FAILED] Stopping upsd: [FAILED] Shutting down Powermate-3105: [FAILED] Starting Powermate-3105: /etc/init.d/functions: line 148: /sbin/Powermate-3105: No such file or directory
[FAILED] Starting upsd: Network UPS Tools upsd 2.0.2
Nut is _not_ starting, you haven't configured it correctly. Nut doesn't have a driver called "Powermate-3105". You must be confusing the driver name with the name of your UPS.
Yes Markku,I know I haven't configured it properly thats where my problem lies,theres some seven configs to get through and I'm a little confused in doing it.
Thanks david
On Sat, 24 Sep 2005, david walcroft wrote:
Matthew Saltzman wrote:
On Sat, 24 Sep 2005, david walcroft wrote:
Hi, I'm trying to set up my ups [Powermate 3105] so far :
1/ It's recognised as 'Vendor=0592 Prodid=0002'
2/ Kernel message : 'reddwarf kernel: usb 2-1: new low speed USB device using uhci_hcd and address 2'
I installed 'CheckUPS' from Powermate.com.au
Read posts at marc.theaimsgroup, didn't appear to help (serial connections as against usb)
Have problems in understanding which port or pipe to use.
similar problem in uderstanding how you start it running and the config files for me are murder to work through.
I realy need someone to help me install/run Nut/CheckUPS
Thanks david
ALthough there's no documentation refrerring to it, you need to configure nut in FC using /etc/sysconfig/ups. Things that you can set there need to be set there. Other things are configured using the files in /etc/ups.
Also, there's a bug against the kernel (can't get to Bugzilla to check the number just now due to flakey net connection) regarding the hidups driver and unhandled interrupts that may cause you problems (unless it's fixed in the latest updates-testing kernel).
Matthew, Progress so far,read Bugzilla Bug 164051 and 160700 Very helpful upgraded to nut 2.0.2.1 and able start nut with the result :
[david@reddwarf ~]$ sudo service ups restart Stopping UPS monitor: [FAILED] Stopping upsd: [FAILED] Shutting down Powermate-3105: [FAILED] Starting Powermate-3105: /etc/init.d/functions: line 148: /sbin/Powermate-3105: No such file or directory [FAILED] Starting upsd: Network UPS Tools upsd 2.0.2 Can't chdir to /var/run/nut: No such file or directory [FAILED] Starting UPS monitor (master): Network UPS Tools upsmon 2.0.1 UPS: genericups@reddwarf (master) (power value 1) Using power down flag file /etc/killpower
[ OK ]But not able to tell if nut is doing anything.
What's in /etc/sysconfig/ups?
Matthew Saltzman wrote:
On Sat, 24 Sep 2005, david walcroft wrote:
Matthew Saltzman wrote:
On Sat, 24 Sep 2005, david walcroft wrote:
Hi, I'm trying to set up my ups [Powermate 3105] so far :
1/ It's recognised as 'Vendor=0592 Prodid=0002'
2/ Kernel message : 'reddwarf kernel: usb 2-1: new low speed USB device using uhci_hcd and address 2'
I installed 'CheckUPS' from Powermate.com.au
Read posts at marc.theaimsgroup, didn't appear to help (serial connections as against usb)
Have problems in understanding which port or pipe to use.
similar problem in uderstanding how you start it running and the config files for me are murder to work through.
I realy need someone to help me install/run Nut/CheckUPS
Thanks david
ALthough there's no documentation refrerring to it, you need to configure nut in FC using /etc/sysconfig/ups. Things that you can set there need to be set there. Other things are configured using the files in /etc/ups.
Also, there's a bug against the kernel (can't get to Bugzilla to check the number just now due to flakey net connection) regarding the hidups driver and unhandled interrupts that may cause you problems (unless it's fixed in the latest updates-testing kernel).
Matthew, Progress so far,read Bugzilla Bug 164051 and 160700 Very helpful upgraded to nut 2.0.2.1 and able start nut with the result :
[david@reddwarf ~]$ sudo service ups restart Stopping UPS monitor: [FAILED] Stopping upsd: [FAILED] Shutting down Powermate-3105: [FAILED] Starting Powermate-3105: /etc/init.d/functions: line 148: /sbin/Powermate-3105: No such file or directory [FAILED] Starting upsd: Network UPS Tools upsd 2.0.2 Can't chdir to /var/run/nut: No such file or directory [FAILED] Starting UPS monitor (master): Network UPS Tools upsmon 2.0.1 UPS: genericups@reddwarf (master) (power value 1) Using power down flag file /etc/killpower
[ OK ]But not able to tell if nut is doing anything.
What's in /etc/sysconfig/ups?
Information requested in the attachment.
david
# If the UPS is locally attached set it to "yes" SERVER=yes # Model of the UPS (filename to call for it, without path) # Example - one of # apcsmart - APC SMartUPS and similar # fentonups - Fenton UPS # optiups # bestups # genericups # ups-trust425+625 # upsdrvctl # You MUST change this, or set SERVER to "no" # To support multiple drivers, set MODEL=upsdrvctl MODEL=Powermate-3105 # UPS device - needed if UPS is locally attached DEVICE=/dev/ttyS0 # Any options to pass to $MODEL # ex. for my TrippLite UPS, use # OPTIONS="-t 5" OPTIONS= # Any options to pass to upsd UPSD_OPTIONS= # # [End]
david walcroft kirjoitti viestissään (lähetysaika sunnuntai, 25. syyskuuta 2005 00:37):
# If the UPS is locally attached set it to "yes" SERVER=yes # Model of the UPS (filename to call for it, without path) # Example - one of # apcsmart - APC SMartUPS and similar # fentonups - Fenton UPS # optiups # bestups # genericups # ups-trust425+625 # upsdrvctl # You MUST change this, or set SERVER to "no" # To support multiple drivers, set MODEL=upsdrvctl MODEL=Powermate-3105
The "MODEL" parameter does _not_ mean the actual model of your ups, you must set it to the nut driver used for your UPS (or "upsdrvctl").
# UPS device - needed if UPS is locally attached DEVICE=/dev/ttyS0
Wasn't your UPS connected through USB, not the serial port?
Markku Kolkka wrote:
david walcroft kirjoitti viestissään (lähetysaika sunnuntai, 25. syyskuuta 2005 00:37):
# If the UPS is locally attached set it to "yes" SERVER=yes # Model of the UPS (filename to call for it, without path) # Example - one of # apcsmart - APC SMartUPS and similar # fentonups - Fenton UPS # optiups # bestups # genericups # ups-trust425+625 # upsdrvctl # You MUST change this, or set SERVER to "no" # To support multiple drivers, set MODEL=upsdrvctl MODEL=Powermate-3105
The "MODEL" parameter does _not_ mean the actual model of your ups, you must set it to the nut driver used for your UPS (or "upsdrvctl").
# UPS device - needed if UPS is locally attached DEVICE=/dev/ttyS0
Wasn't your UPS connected through USB, not the serial port?
Ok, I'll set up with MODEL=genericups, but I'm not sure what USB uses for connections <socket> <port> and how to determine the same for a config file.
Thanks for all you help Markku.
david
david walcroft wrote:
Markku Kolkka wrote:
david walcroft kirjoitti viestissään (lähetysaika sunnuntai, 25. syyskuuta 2005 00:37):
# If the UPS is locally attached set it to "yes" SERVER=yes # Model of the UPS (filename to call for it, without path) # Example - one of # apcsmart - APC SMartUPS and similar # fentonups - Fenton UPS # optiups # bestups # genericups # ups-trust425+625 # upsdrvctl # You MUST change this, or set SERVER to "no" # To support multiple drivers, set MODEL=upsdrvctl MODEL=Powermate-3105
The "MODEL" parameter does _not_ mean the actual model of your ups, you must set it to the nut driver used for your UPS (or "upsdrvctl").
# UPS device - needed if UPS is locally attached DEVICE=/dev/ttyS0
Wasn't your UPS connected through USB, not the serial port?
Ok, I'll set up with MODEL=genericups, but I'm not sure what USB uses for connections <socket> <port> and how to determine the same for a config file.
Thanks for all you help Markku. david
For what it's worth this is at restart in s-c-services:
ups failed. The error was: Stopping UPS monitor: [FAILED] Stopping upsd: [FAILED] Shutting down genericups: [FAILED] Starting genericups: Network UPS Tools - Generic UPS driver 1.30 (2.0.2) [FAILED] Starting upsd: Network UPS Tools upsd 2.0.2 [FAILED] Starting UPS monitor (master): [ OK ]
david
david walcroft wrote:
david walcroft wrote:
Ok, I'll set up with MODEL=genericups, but I'm not sure what USB uses for connections <socket> <port> and how to determine the same for a config file.
Thanks for all you help Markku. david
For what it's worth this is at restart in s-c-services:
ups failed. The error was: Stopping UPS monitor: [FAILED] Stopping upsd: [FAILED] Shutting down genericups: [FAILED] Starting genericups: Network UPS Tools - Generic UPS driver 1.30 (2.0.2) [FAILED] Starting upsd: Network UPS Tools upsd 2.0.2 [FAILED] Starting UPS monitor (master): [ OK ]
david
Further activity,this as far as I have ventured and now I really don't understand what is going on:
ups failed. The error was: Stopping UPS monitor: [FAILED] Stopping upsd: [FAILED] Shutting down genericups: [FAILED] Starting genericups: Network UPS Tools - Generic UPS driver 1.30 (2.0.2) [FAILED] Starting upsd: Network UPS Tools upsd 2.0.2 [FAILED] Starting UPS monitor (master): Network UPS Tools upsmon 2.0.1
Fatal error: insufficient power configured!
Sum of power values........: 0 Minimum value (MINSUPPLIES): 1
Edit your upsmon.conf and change the values. [FAILED]
With (MINSUPLLIES): 1, upsmon.conf states <powervalue> is an integer - the number of power supplies that this UPS # feeds on this system. Most computers only have one power supply, so this # is normally set to 1. You need a pretty big or special box to have any # other value here. # # You can also set this to 0 for a system that doesn't supply any power, # but you still want to monitor. Use this when you want to hear about # changes for a given UPS without shutting down when it goes critical, # unless <powervalue> is 0. # # <username> and <password> must match an entry in that system's # upsd.users. If your username is "monmaster" and your password is # "blah", the upsd.users would look like this: # # [monmaster] # password = blah # allowfrom = (whatever applies to this host) # upsmon master (or slave) # # "master" means this system will shutdown last, allowing the slaves # time to shutdown first. # # "slave" means this system shuts down immediately when power goes critical. # # Examples: # # MONITOR myups@bigserver 1 monmaster blah master # MONITOR su700@server.example.com 1 upsmon secretpass slave MONITOR "genericups usptype=7"@reddwarf 0 david 4skin46 master
If I can state "0" why do I get an error.
Thanks david
david walcroft wrote:
david walcroft wrote:
david walcroft wrote:
Ok, I'll set up with MODEL=genericups, but I'm not sure what USB uses for connections <socket> <port> and how to determine the same for a config file.
Thanks for all you help Markku. david
For what it's worth this is at restart in s-c-services:
ups failed. The error was: Stopping UPS monitor: [FAILED] Stopping upsd: [FAILED] Shutting down genericups: [FAILED] Starting genericups: Network UPS Tools - Generic UPS driver 1.30 (2.0.2) [FAILED] Starting upsd: Network UPS Tools upsd 2.0.2 [FAILED] Starting UPS monitor (master): [ OK ]
davidFurther activity,this as far as I have ventured and now I really don't understand what is going on:
ups failed. The error was: Stopping UPS monitor: [FAILED] Stopping upsd: [FAILED] Shutting down genericups: [FAILED] Starting genericups: Network UPS Tools - Generic UPS driver 1.30 (2.0.2) [FAILED] Starting upsd: Network UPS Tools upsd 2.0.2 [FAILED] Starting UPS monitor (master): Network UPS Tools upsmon 2.0.1
Fatal error: insufficient power configured!
Sum of power values........: 0 Minimum value (MINSUPPLIES): 1
Edit your upsmon.conf and change the values. [FAILED]
With (MINSUPLLIES): 1, upsmon.conf states <powervalue> is an integer - the number of power supplies that this UPS # feeds on this system. Most computers only have one power supply, so this # is normally set to 1. You need a pretty big or special box to have any # other value here. # # You can also set this to 0 for a system that doesn't supply any power, # but you still want to monitor. Use this when you want to hear about # changes for a given UPS without shutting down when it goes critical, # unless <powervalue> is 0. # # <username> and <password> must match an entry in that system's # upsd.users. If your username is "monmaster" and your password is # "blah", the upsd.users would look like this: # # [monmaster] # password = blah # allowfrom = (whatever applies to this host) # upsmon master (or slave) # # "master" means this system will shutdown last, allowing the slaves # time to shutdown first. # # "slave" means this system shuts down immediately when power goes critical. # # Examples: # # MONITOR myups@bigserver 1 monmaster blah master # MONITOR su700@server.example.com 1 upsmon secretpass slave MONITOR "genericups usptype=7"@reddwarf 0 david 4skin46 master
If I can state "0" why do I get an error.
Thanks david
Just tried starting 'genericups'
[david@reddwarf ~]$ sudo genericups -x upstype=7 /dev/usb/ups
Network UPS Tools - Generic UPS driver 1.30 (2.0.2) UPS type: CyberPower Power99 ioctl TIOCMSET: Invalid argument
In 'network UPS Tools driver.list' I selcted "Powerware 3110" "DTR cable power" "genericups upstype=7" as being most likly to run my 3105 ( strange but 3105 supercedes 3110)
One day I'll get this to work :-)
thanks david
On Saturday 24 September 2005 18:43, david walcroft wrote:
Markku Kolkka wrote:
david walcroft kirjoitti viestissään (lähetysaika sunnuntai, 25.
syyskuuta 2005 00:37):
# If the UPS is locally attached set it to "yes" SERVER=yes # Model of the UPS (filename to call for it, without path) # Example - one of # apcsmart - APC SMartUPS and similar # fentonups - Fenton UPS # optiups # bestups # genericups # ups-trust425+625 # upsdrvctl # You MUST change this, or set SERVER to "no" # To support multiple drivers, set MODEL=upsdrvctl MODEL=Powermate-3105
The "MODEL" parameter does _not_ mean the actual model of your ups, you must set it to the nut driver used for your UPS (or "upsdrvctl").
# UPS device - needed if UPS is locally attached DEVICE=/dev/ttyS0
Wasn't your UPS connected through USB, not the serial port?
Ok, I'll set up with MODEL=genericups, but I'm not sure what USB uses for connections <socket> <port> and how to determine the same for a config file.
Thanks for all you help Markku.
david
-- To find out where udev is putting your ups, as root run "tail /var/log/message" after plugging the ups into the usb socket, the entry you want will probably contain /dev/ttyUSB1..4. But be warned, it may not always be loaded as the same usb device depending on other usb devices being plugged or unplugged.
You will probably have to write a rule for your ups. Take a look at the man page for udev and examine the existing rules in /etc/udev/rules/d to get the idea. It would be a good idea to create a "file" under /dev, sav /dev/ups, and put a symlink pointing to it in the rule.
Hope this helps, Tom
- Tom Taylor Linux user #263467 Federal Way, WA Iraq war: 1,914 and counting
Thomas Taylor wrote:
On Saturday 24 September 2005 18:43, david walcroft wrote:
Markku Kolkka wrote:
david walcroft kirjoitti viestissään (lähetysaika sunnuntai, 25.
syyskuuta 2005 00:37):
# If the UPS is locally attached set it to "yes" SERVER=yes # Model of the UPS (filename to call for it, without path) # Example - one of # apcsmart - APC SMartUPS and similar # fentonups - Fenton UPS # optiups # bestups # genericups # ups-trust425+625 # upsdrvctl # You MUST change this, or set SERVER to "no" # To support multiple drivers, set MODEL=upsdrvctl MODEL=Powermate-3105
The "MODEL" parameter does _not_ mean the actual model of your ups, you must set it to the nut driver used for your UPS (or "upsdrvctl").
# UPS device - needed if UPS is locally attached DEVICE=/dev/ttyS0
Wasn't your UPS connected through USB, not the serial port?
Ok, I'll set up with MODEL=genericups, but I'm not sure what USB uses for connections <socket> <port> and how to determine the same for a config file.
Thanks for all you help Markku.
david-- To find out where udev is putting your ups, as root run "tail /var/log/message" after plugging the ups into the usb socket, the entry you want will probably contain /dev/ttyUSB1..4. But be warned, it may not always be loaded as the same usb device depending on other usb devices being plugged or unplugged.
You will probably have to write a rule for your ups. Take a look at the man page for udev and examine the existing rules in /etc/udev/rules/d to get the idea. It would be a good idea to create a "file" under /dev, sav /dev/ups, and put a symlink pointing to it in the rule.
Hope this helps, Tom
Tom Taylor Linux user #263467 Federal Way, WA Iraq war: 1,914 and counting
Thanks Tom, I've run 'Tail /var/log/messages' several times before - same result
"Sep 25 17:19:24 reddwarf kernel: usb 3-2: USB disconnect, address 2
Sep 25 17:19:34 reddwarf kernel: usb 3-2: new low speed USB device using uhci_hcd and address 5"
I have never seen so many config files for one programme !!
david
david walcroft kirjoitti viestissään (lähetysaika sunnuntai, 25. syyskuuta 2005 10:25):
I have never seen so many config files for one programme !!
Nut isn't one program, it's at least three: the UPS driver, the server (upsd) and the monitor client (upsmon). Each is configured separately.
Markku Kolkka wrote:
david walcroft kirjoitti viestissään (lähetysaika sunnuntai, 25. syyskuuta 2005 10:25):
I have never seen so many config files for one programme !!
Nut isn't one program, it's at least three: the UPS driver, the server (upsd) and the monitor client (upsmon). Each is configured separately.
So I'm finding out but my config problems remain,can someone post copies of working configs?,it would help me a great deal.
david
Quoting Markku Kolkka markkuk@tuubi.net:
david walcroft kirjoitti viestissään (lähetysaika sunnuntai, 25. syyskuuta 2005 10:25):
I have never seen so many config files for one programme !!
Nut isn't one program, it's at least three: the UPS driver, the server (upsd) and the monitor client (upsmon). Each is configured separately.
Not to mention the udev-->USB? that likely needs configuring as well.
If it makes you feel better, David, I have an older UPS that worked fine with NUT on Mandrake 9, but if I connect it to a WinXP machine, the UPS turns off briefly during startup. The vendor's FAQ says I need a firmware update. Be thankful if you get off with nothing worse than a half-dozen config file edits (and that you don't have to reboot after each edit!).
On Sun, 25 Sep 2005, david walcroft wrote:
Thomas Taylor wrote:
On Saturday 24 September 2005 18:43, david walcroft wrote:
Markku Kolkka wrote:
david walcroft kirjoitti viestissään (lähetysaika sunnuntai, 25.
syyskuuta 2005 00:37):
# If the UPS is locally attached set it to "yes" SERVER=yes # Model of the UPS (filename to call for it, without path) # Example - one of # apcsmart - APC SMartUPS and similar # fentonups - Fenton UPS # optiups # bestups # genericups # ups-trust425+625 # upsdrvctl # You MUST change this, or set SERVER to "no" # To support multiple drivers, set MODEL=upsdrvctl MODEL=Powermate-3105
The "MODEL" parameter does _not_ mean the actual model of your ups, you must set it to the nut driver used for your UPS (or "upsdrvctl").
# UPS device - needed if UPS is locally attached DEVICE=/dev/ttyS0
Wasn't your UPS connected through USB, not the serial port?
Ok, I'll set up with MODEL=genericups, but I'm not sure what USB uses for connections <socket> <port> and how to determine the same for a config file.
All the drivers listed as examples in /etc/sysconfig/ups are for devices connected by serial cable.
If your UPS is connected via USB, use MODEL=hidups. (If that doesn't work, try MODEL=newhidups. The only other USB-enabled driver is energizerups, but that's brand specific.) The DEVICE will be something like /dev/hiddevX (where X is a digit. The device will be created at startup, so you should not need an entry is /etc/udev/rules.d.
On boot, I see:
Sep 10 12:43:20 yankee kernel: hiddev96: USB HID v1.10 Device [APC Back-UPS ES 650 FW:818.w1.D USB FW:w1] on usb-0000:00:04.2-2
The device created is:
# ls -l /dev/hiddev0 crw-rw---- 1 root root 180, 96 Sep 17 12:52 /dev/hiddev0
My /etc/sysconfig/ups has
MODEL=hidups DEVICE=/dev/hiddev0
Thanks for all you help Markku.
david-- To find out where udev is putting your ups, as root run "tail /var/log/message" after plugging the ups into the usb socket, the entry you want will probably contain /dev/ttyUSB1..4. But be warned, it may not always be loaded as the same usb device depending on other usb devices being plugged or unplugged.
You will probably have to write a rule for your ups. Take a look at the man page for udev and examine the existing rules in /etc/udev/rules/d to get the idea. It would be a good idea to create a "file" under /dev, sav /dev/ups, and put a symlink pointing to it in the rule. Hope this helps, Tom
Tom Taylor Linux user #263467 Federal Way, WA Iraq war: 1,914 and counting
Thanks Tom, I've run 'Tail /var/log/messages' several times before - same result
"Sep 25 17:19:24 reddwarf kernel: usb 3-2: USB disconnect, address 2
Sep 25 17:19:34 reddwarf kernel: usb 3-2: new low speed USB device using uhci_hcd and address 5"
I have never seen so many config files for one programme !!
david
Matthew Saltzman wrote:
All the drivers listed as examples in /etc/sysconfig/ups are for devices connected by serial cable.
If your UPS is connected via USB, use MODEL=hidups. (If that doesn't work, try MODEL=newhidups. The only other USB-enabled driver is energizerups, but that's brand specific.) The DEVICE will be something like /dev/hiddevX (where X is a digit. The device will be created at startup, so you should not need an entry is /etc/udev/rules.d.
On boot, I see:
Sep 10 12:43:20 yankee kernel: hiddev96: USB HID v1.10 Device [APC Back-UPS ES 650 FW:818.w1.D USB FW:w1] on usb-0000:00:04.2-2
The device created is:
# ls -l /dev/hiddev0 crw-rw---- 1 root root 180, 96 Sep 17 12:52 /dev/hiddev0
My /etc/sysconfig/ups has
MODEL=hidups DEVICE=/dev/hiddev0
Changed my "MODEL=[new]hidups" and booted both with no result,no /dev/hiddev* is generated and syslog has errors:
Sep 25 21:50:55 reddwarf upsmon[2105]: Set username on [david@reddwarf] failed: Server disconnected
Sep 25 21:51:05 reddwarf upsmon[2105]: Poll UPS [david@reddwarf] failed - Write error: Bad file descriptor
david
On Sun, 25 Sep 2005, david walcroft wrote:
Matthew Saltzman wrote:
All the drivers listed as examples in /etc/sysconfig/ups are for devices connected by serial cable.
If your UPS is connected via USB, use MODEL=hidups. (If that doesn't work, try MODEL=newhidups. The only other USB-enabled driver is energizerups, but that's brand specific.) The DEVICE will be something like /dev/hiddevX (where X is a digit. The device will be created at startup, so you should not need an entry is /etc/udev/rules.d.
I use MODEL=upsdrvctl and then set the ups specific stuff in /etc/ups/ups.conf I have it working on several systems using serial port ups's just fine. One of these systems has 4 ups's attached to it. The problem is that they are attached to the machine via serial ports. I am still fighting the one that is attached via usb.
On boot, I see:
Sep 10 12:43:20 yankee kernel: hiddev96: USB HID v1.10 Device [APC Back-UPS ES 650 FW:818.w1.D USB FW:w1] on usb-0000:00:04.2-2
The device created is:
# ls -l /dev/hiddev0 crw-rw---- 1 root root 180, 96 Sep 17 12:52 /dev/hiddev0
My /etc/sysconfig/ups has
MODEL=hidups DEVICE=/dev/hiddev0
Changed my "MODEL=[new]hidups" and booted both with no result,no /dev/hiddev* is generated and syslog has errors:
Sep 25 21:50:55 reddwarf upsmon[2105]: Set username on [david@reddwarf] failed: Server disconnected
Sep 25 21:51:05 reddwarf upsmon[2105]: Poll UPS [david@reddwarf] failed
- Write error: Bad file descriptor
See if you can talk directly to the ups. Try "/sbin/newhidups -u root -D -a PS1" where PS1 is the name of the ups you configured in /etc/ups.conf. It should return a bunch of stuff about your ups. It took me awhile to get that to work but I think that is the first step. If the driver cannot talk to the ups then nut will never work :-)
The above works for me, however I still cannot get nut to start. I get the following in the logs: Sep 25 12:17:45 porky upsdrvctl: Network UPS Tools: New USB/HID UPS driver 0.23 (2.0.2) Sep 25 12:17:45 porky upsdrvctl: Sep 25 12:17:45 porky upsdrvctl: Network UPS Tools - UPS driver controller 2.0.2 Sep 25 12:17:45 porky upsdrvctl: No USB/HID UPS found Sep 25 12:17:45 porky upsdrvctl: Driver failed to start (exit status=1) Sep 25 12:17:45 porky ups: upsdrvctl startup failed Sep 25 12:17:45 porky upsd[23661]: Can't connect to UPS [PS1] (newhidups-hiddev0): No such file or directory Sep 25 12:17:45 porky upsd: Can't connect to UPS [PS1] (newhidups-hiddev0): No such file or directory Sep 25 12:17:45 porky upsd: Network UPS Tools upsd 2.0.2
At this point I suspect that there is something missing from the driver but I am not sure. :-(
Regards,
Tom Diehl tdiehl@rogueind.com Spamtrap address mtd123@rogueind.com
On Sun, 25 Sep 2005, david walcroft wrote:
Matthew Saltzman wrote:
All the drivers listed as examples in /etc/sysconfig/ups are for devices connected by serial cable.
If your UPS is connected via USB, use MODEL=hidups. (If that doesn't work, try MODEL=newhidups. The only other USB-enabled driver is energizerups, but that's brand specific.) The DEVICE will be something like /dev/hiddevX (where X is a digit. The device will be created at startup, so you should not need an entry is /etc/udev/rules.d.
On boot, I see:
Sep 10 12:43:20 yankee kernel: hiddev96: USB HID v1.10 Device [APC Back-UPS ES 650 FW:818.w1.D USB FW:w1] on usb-0000:00:04.2-2
The device created is:
# ls -l /dev/hiddev0 crw-rw---- 1 root root 180, 96 Sep 17 12:52 /dev/hiddev0
My /etc/sysconfig/ups has
MODEL=hidups DEVICE=/dev/hiddev0
Changed my "MODEL=[new]hidups" and booted both with no result,no /dev/hiddev* is generated and syslog has errors:
Sep 25 21:50:55 reddwarf upsmon[2105]: Set username on [david@reddwarf] failed: Server disconnected
Sep 25 21:51:05 reddwarf upsmon[2105]: Poll UPS [david@reddwarf] failed - Write error: Bad file descriptor
Not sure what to suggest next. Is the UPS cable plugged in? Is the USB module (in my case, uhci-hcd) loaded?
david
On Saturday 24 September 2005 18:43, david walcroft wrote:
Markku Kolkka wrote:
david walcroft kirjoitti viestissään (lähetysaika sunnuntai, 25.
syyskuuta 2005 00:37):
# If the UPS is locally attached set it to "yes" SERVER=yes # Model of the UPS (filename to call for it, without path) # Example - one of # apcsmart - APC SMartUPS and similar # fentonups - Fenton UPS # optiups # bestups # genericups # ups-trust425+625 # upsdrvctl # You MUST change this, or set SERVER to "no" # To support multiple drivers, set MODEL=upsdrvctl MODEL=Powermate-3105
The "MODEL" parameter does _not_ mean the actual model of your ups, you must set it to the nut driver used for your UPS (or "upsdrvctl").
# UPS device - needed if UPS is locally attached DEVICE=/dev/ttyS0
Wasn't your UPS connected through USB, not the serial port?
Ok, I'll set up with MODEL=genericups, but I'm not sure what USB uses for connections <socket> <port> and how to determine the same for a config file.
Thanks for all you help Markku.
david
-- To find out where udev is putting your ups, as root run "tail /var/log/message" after plugging the ups into the usb socket, the entry you want will probably contain /dev/ttyUSB1..4. But be warned, it may not always be loaded as the same usb device depending on other usb devices being plugged or unplugged.
You will probably have to write a rule for your ups. Take a look at the man page for udev and examine the existing rules in /etc/udev/rules.d to get the idea. It would be a good idea to create a "file" under /dev, sav /dev/ups, and put a symlink pointing to it in the rule.
Hope this helps, Tom
Oops: Looks like I made a mistake on the rules location the first time I sent this. It's corrected above.
- Tom Taylor Linux user #263467 Federal Way, WA Iraq war: 1,914 and counting
Thomas Taylor wrote:
On Saturday 24 September 2005 18:43, david walcroft wrote:
Markku Kolkka wrote:
david walcroft kirjoitti viestissään (lähetysaika sunnuntai, 25.
syyskuuta 2005 00:37):
# If the UPS is locally attached set it to "yes" SERVER=yes # Model of the UPS (filename to call for it, without path) # Example - one of # apcsmart - APC SMartUPS and similar # fentonups - Fenton UPS # optiups # bestups # genericups # ups-trust425+625 # upsdrvctl # You MUST change this, or set SERVER to "no" # To support multiple drivers, set MODEL=upsdrvctl MODEL=Powermate-3105
The "MODEL" parameter does _not_ mean the actual model of your ups, you must set it to the nut driver used for your UPS (or "upsdrvctl").
# UPS device - needed if UPS is locally attached DEVICE=/dev/ttyS0
Wasn't your UPS connected through USB, not the serial port?
Ok, I'll set up with MODEL=genericups, but I'm not sure what USB uses for connections <socket> <port> and how to determine the same for a config file.
Thanks for all you help Markku.
david-- To find out where udev is putting your ups, as root run "tail /var/log/message" after plugging the ups into the usb socket, the entry you want will probably contain /dev/ttyUSB1..4. But be warned, it may not always be loaded as the same usb device depending on other usb devices being plugged or unplugged.
You will probably have to write a rule for your ups. Take a look at the man page for udev and examine the existing rules in /etc/udev/rules.d to get the idea. It would be a good idea to create a "file" under /dev, sav /dev/ups, and put a symlink pointing to it in the rule.
Hope this helps, Tom
Oops: Looks like I made a mistake on the rules location the first time I sent this. It's corrected above.
Tom Taylor Linux user #263467 Federal Way, WA Iraq war: 1,914 and counting
State of play:
Sep 26 15:35:05 reddwarf upsd[4089]: /var/run/nut is world readable Sep 26 15:35:05 reddwarf upsd[4089]: /etc/ups/upsd.conf is world readable Sep 26 15:35:05 reddwarf upsd[4089]: Can't connect to UPS [powermate3105] (upsdrvctl-hiddev0): No such file or directory Sep 26 15:35:10 reddwarf upsd[4105]: Startup successful Sep 26 15:35:10 reddwarf upsd[4105]: writepid: fopen /var/run/nut/upsd.pid: Permission denied Sep 26 15:35:10 reddwarf upsmon[4108]: Startup successful Sep 26 15:35:10 reddwarf upsd[4105]: Rejecting TCP connection from 127.0.0.1 Sep 26 15:35:10 reddwarf upsmon[4109]: Set username on [david@reddwarf] failed: Server disconnected Sep 26 15:35:20 reddwarf upsmon[4109]: Poll UPS [david@reddwarf] failed - Write error: Bad file descriptor Sep 26 15:35:20 reddwarf upsmon[4109]: Communications with UPS david@reddwarf lost Sep 26 15:35:20 reddwarf wall[4160]: wall: user nut broadcasted 1 lines (45 chars) Sep 26 15:35:30 reddwarf upsd[4105]: Rejecting TCP connection from 127.0.0.1 Sep 26 15:35:30 reddwarf upsmon[4109]: Set username on [david@reddwarf] failed: Server disconnected Sep 26 15:35:40 reddwarf upsmon[4109]: Poll UPS [david@reddwarf] failed - Write error: Bad file descriptor
Does this help any......
david
david walcroft kirjoitti viestissään (lähetysaika maanantai, 26. syyskuuta 2005 08:39):
Sep 26 15:35:05 reddwarf upsd[4089]: /var/run/nut is world readable Sep 26 15:35:05 reddwarf upsd[4089]: /etc/ups/upsd.conf is world readable
chmod those files to 600 or 640.
Sep 26 15:35:05 reddwarf upsd[4089]: Can't connect to UPS [powermate3105] (upsdrvctl-hiddev0): No such file or directory Sep 26 15:35:10
Your UPS driver isn't configured correctly and doesn't start.
reddwarf upsd[4105]: Startup successful Sep 26 15:35:10 reddwarf upsd[4105]: writepid: fopen /var/run/nut/upsd.pid: Permission denied
Check the ownership and protection of /var/run/nut/ and the files in it.
Sep 26 15:35:10 reddwarf upsmon[4108]: Startup successful Sep 26 15:35:10 reddwarf upsd[4105]: Rejecting TCP connection from 127.0.0.1
Change the access controls in upsd.conf to allow connections from localhost.
Markku Kolkka wrote:
david walcroft kirjoitti viestissään (lähetysaika maanantai, 26. syyskuuta 2005 08:39):
Sep 26 15:35:05 reddwarf upsd[4089]: /var/run/nut is world readable Sep 26 15:35:05 reddwarf upsd[4089]: /etc/ups/upsd.conf is world readable
chmod those files to 600 or 640.
Sep 26 15:35:05 reddwarf upsd[4089]: Can't connect to UPS [powermate3105] (upsdrvctl-hiddev0): No such file or directory Sep 26 15:35:10
Your UPS driver isn't configured correctly and doesn't start.
reddwarf upsd[4105]: Startup successful Sep 26 15:35:10 reddwarf upsd[4105]: writepid: fopen /var/run/nut/upsd.pid: Permission denied
Check the ownership and protection of /var/run/nut/ and the files in it.
Sep 26 15:35:10 reddwarf upsmon[4108]: Startup successful Sep 26 15:35:10 reddwarf upsd[4105]: Rejecting TCP connection from 127.0.0.1
Change the access controls in upsd.conf to allow connections from localhost.
Markku, you have been a great help but 'nut'is becoming to complicated and confusing for me (Bi-Polar, Depression, etc) to get configured,its actully depressing me working on it.It looks as if my powermate will finish up as a power filter and not a ups. It says little for Linux where one service (ups) takes 3> programmes,7> confifig files to get up and running, the M$ jibe about Linux is built by geeks for geeks has a gem of truth!!
david
On Tue, 2005-09-27 at 10:47 +1000, david walcroft wrote:
Markku Kolkka wrote:
david walcroft kirjoitti viestissään (lähetysaika maanantai, 26. syyskuuta 2005 08:39):
Sep 26 15:35:05 reddwarf upsd[4089]: /var/run/nut is world readable Sep 26 15:35:05 reddwarf upsd[4089]: /etc/ups/upsd.conf is world readable
chmod those files to 600 or 640.
Sep 26 15:35:05 reddwarf upsd[4089]: Can't connect to UPS [powermate3105] (upsdrvctl-hiddev0): No such file or directory Sep 26 15:35:10
Your UPS driver isn't configured correctly and doesn't start.
reddwarf upsd[4105]: Startup successful Sep 26 15:35:10 reddwarf upsd[4105]: writepid: fopen /var/run/nut/upsd.pid: Permission denied
Check the ownership and protection of /var/run/nut/ and the files in it.
Sep 26 15:35:10 reddwarf upsmon[4108]: Startup successful Sep 26 15:35:10 reddwarf upsd[4105]: Rejecting TCP connection from 127.0.0.1
Change the access controls in upsd.conf to allow connections from localhost.
Markku, you have been a great help but 'nut'is becoming to complicated and confusing for me (Bi-Polar, Depression, etc) to get configured,its actully depressing me working on it.It looks as if my powermate will finish up as a power filter and not a ups. It says little for Linux where one service (ups) takes 3> programmes,7> confifig files to get up and running, the M$ jibe about Linux is built by geeks for geeks has a gem of truth!!
---- another way of looking at the same thing might be - let the buyer beware. There are UPS systems such as APC that have software and would work out of the box and there are 3rd party programs such as APCUPSD which are terrific and easy enough. Of course, you would have to check on these things before you purchase.
also, there is the notion that the net gain is zero. You gave up and thus no one learned anything at all from your efforts or from the efforts given on the list to help you get it working. If you were to persevere instead of giving up, document what you did for the next person who follows in your footstep, Linux would probably benefit and the driver db in the 'nut' project could probably include your hardware. Alas, you surrendered.
Craig
Craig White wrote:
On Tue, 2005-09-27 at 10:47 +1000, david walcroft wrote:
Markku Kolkka wrote:
david walcroft kirjoitti viestissään (lähetysaika maanantai, 26. syyskuuta 2005 08:39):
Sep 26 15:35:05 reddwarf upsd[4089]: /var/run/nut is world readable Sep 26 15:35:05 reddwarf upsd[4089]: /etc/ups/upsd.conf is world readable
chmod those files to 600 or 640.
Sep 26 15:35:05 reddwarf upsd[4089]: Can't connect to UPS [powermate3105] (upsdrvctl-hiddev0): No such file or directory Sep 26 15:35:10
Your UPS driver isn't configured correctly and doesn't start.
reddwarf upsd[4105]: Startup successful Sep 26 15:35:10 reddwarf upsd[4105]: writepid: fopen /var/run/nut/upsd.pid: Permission denied
Check the ownership and protection of /var/run/nut/ and the files in it.
Sep 26 15:35:10 reddwarf upsmon[4108]: Startup successful Sep 26 15:35:10 reddwarf upsd[4105]: Rejecting TCP connection
from 127.0.0.1
Change the access controls in upsd.conf to allow connections from localhost.
Markku, you have been a great help but 'nut'is becoming to complicated and confusing for me (Bi-Polar, Depression, etc) to get configured,its actully depressing me working on it.It looks as if my powermate will finish up as a power filter and not a ups. It says little for Linux where one service (ups) takes 3> programmes,7> confifig files to get up and running, the M$ jibe about Linux is built by geeks for geeks has a gem of truth!!
another way of looking at the same thing might be - let the buyer beware. There are UPS systems such as APC that have software and would work out of the box and there are 3rd party programs such as APCUPSD which are terrific and easy enough. Of course, you would have to check on these things before you purchase.
also, there is the notion that the net gain is zero. You gave up and thus no one learned anything at all from your efforts or from the efforts given on the list to help you get it working. If you were to persevere instead of giving up, document what you did for the next person who follows in your footstep, Linux would probably benefit and the driver db in the 'nut' project could probably include your hardware. Alas, you surrendered.
Craig
I wish I had a simple choice between carry on or stop, depression says stop!!
david
Quoting david walcroft david_walcroft@yahoo.com.au:
Markku Kolkka wrote: Markku, [...] you have been a great help but 'nut'is becoming to complicated and confusing for me (Bi-Polar, Depression, etc) to get configured,its actully depressing me working on it.It looks as if my powermate will finish up as a power filter and not a ups. It says little for Linux where one service (ups) takes 3> programmes,7> confifig files to get up and running, the M$ jibe about Linux is built by geeks for geeks has a gem of truth!!
The grass is not always greener on the M$ side of the fence!
When I connect my UPS to Windows XP Pro SP2 and reboot, the UPS gets shut down during the startup process, so the system just cycles endlessly starting, losing power, and restarting. On another XP Pro system down the hall with a different UPS, some process (trojan trying to rack up phone bills to a 1-900 p0rn number?) is attempting to use the serial port, so the UPS software won't run.
When something seems complicated and confusing, it probably means you are lacking the appropriate background. The design of NUT with the 3 componments comes straight out of basic university courses in OS fundamentals. You should consider reading one of the standard texts, such as Andrew Tanenbaums's "Operating Systems. Design and Implementation". To read this book you may need to learn a bit of the "C" programming language, which is handy for anyone who is serious about using linux.
Sure this is a serious investment of time and energy, but when you have finished, things that seem complicated and confusing now will seem normal. Be warned, however, that any good feelings you may have had about M$ will probably disappear.
david walcroft kirjoitti viestissään (lähetysaika tiistai, 27. syyskuuta 2005 03:47):
It says little for Linux where one service (ups) takes 3> programmes,7> confifig files to get up and running,
Nut is not part of Linux, it runs on BSD, Solaris, Apple OSX, AIX or any other POSIX/Unix style OS. Its properties have nothing to do with Linux.
On Sun, 25 Sep 2005, david walcroft wrote:
Matthew Saltzman wrote:
What's in /etc/sysconfig/ups?
Information requested in the attachment.
david
Reproduced here.
# If the UPS is locally attached set it to "yes" SERVER=yes # Model of the UPS (filename to call for it, without path) # Example - one of # apcsmart - APC SMartUPS and similar # fentonups - Fenton UPS # optiups # bestups # genericups # ups-trust425+625 # upsdrvctl # You MUST change this, or set SERVER to "no" # To support multiple drivers, set MODEL=upsdrvctl MODEL=Powermate-3105
This parameter can't be just anything--it needs to be the name of the nut driver that handles your UPS. I don't see Powermate listed in the README in /usr/share/nut-*/ and I don't see it in the compatibility list at http://www.networkupstools.org/compat/. So you need to figure out if the protocol used by your Powermate is compatible with any of the listed devices. If so, use that driver. If not, try MODEL=genericups and see if that gets you anywhere.
# UPS device - needed if UPS is locally attached DEVICE=/dev/ttyS0 # Any options to pass to $MODEL # ex. for my TrippLite UPS, use # OPTIONS="-t 5" OPTIONS= # Any options to pass to upsd UPSD_OPTIONS= # # [End]
Still plugging away.got it down to this:
[root@reddwarf ups]# service ups restart Stopping UPS monitor: [ OK ] Stopping upsd: [FAILED] Shutting down upsdrvctl: Network UPS Tools - UPS driver controller 2.0.2 Stopping UPS: powermate3105 Can't open /var/run/nut/genericups-ttyUSB0.pid: No such file or directory
Starting upsdrvctl: Network UPS Tools - UPS driver controller 2.0.2 Network UPS Tools - Generic UPS driver 1.30 (2.0.2) Can't chdir to /var/run/nut: Permission denied Driver failed to start (exit status=1) [FAILED] Starting upsd: Network UPS Tools upsd 2.0.2 Can't chdir to /var/run/nut: Permission denied [FAILED] Starting UPS monitor (master): Network UPS Tools upsmon 2.0.1 UPS: reddwarf@localhost (slave) (power value 1) Using power down flag file /etc/killpower [ OK ]
[david@reddwarf ups]$ ls -l total 80 -rwxr-x--- 1 nut nut 1121 Oct 1 17:25 hosts.conf -rwxr-x--- 1 nut nut 3772 Oct 1 17:55 ups.conf -rwxr-x--- 1 nut nut 1369 Oct 1 18:17 upsd.conf -rwxr-x--- 1 nut nut 2190 Oct 1 12:53 upsd.users -rw------- 1 nut nut 11304 Oct 1 12:37 upsmon.conf -rwxr-x--- 1 nut nut 3871 Oct 1 12:42 upssched.conf -rwxr-x--- 1 nut nut 1420 Mar 11 2005 upsset.conf -rw-rw---- 1 root root 1773 Mar 11 2005 upsstats.html -rw-rw---- 1 root root 1867 Mar 11 2005 upsstats-single.html [david@reddwarf ups]$ service ups start Starting upsdrvctl: Network UPS Tools - UPS driver controller 2.0.2 Can't open /etc/ups/ups.conf: Can't open /etc/ups/ups.conf: Permission denied [FAILED] Starting upsd: Network UPS Tools upsd 2.0.2 Can't chdir to /var/run/nut: Permission denied [FAILED] Starting UPS monitor (master):
Oct 1 18:28:20 reddwarf upsmon[19155]: UPS reddwarf@localhost is unavailable Oct 1 18:28:20 reddwarf wall[21215]: wall: user nutmon broadcasted 1 lines (39 chars) Oct 1 18:28:25 reddwarf upsmon[19155]: UPS [reddwarf@localhost]: connect failed: Connection failure: Connection refused
[david@reddwarf ups]$ service ups stop rm: cannot remove `/var/run/upsmon.pid': Permission denied [FAILED]
Stopping upsd: [FAILED] Shutting down upsdrvctl: Network UPS Tools - UPS driver controller 2.0.2 Can't open /etc/ups/ups.conf: Can't open /etc/ups/ups.conf: Permission denied rm: cannot remove `/var/run/upsmon.pid': Permission denied [FAILED]
Stopping upsd: [FAILED] Shutting down upsdrvctl: Network UPS Tools - UPS driver controller 2.0.2 Can't open /etc/ups/ups.conf: Can't open /etc/ups/ups.conf: Permission denied
[david@reddwarf ups]$ ls -l /var/run/upsmon.pid -rw-r--r-- 1 root root 6 Oct 1 18:18 /var/run/upsmon.pid
I'm a bit puzzled over permmision refusals and unavailability of localhost. Could I ask for some help please or I'll never get Nut configured.
Thanks david
On Sat, 1 Oct 2005, david walcroft wrote:
Still plugging away.got it down to this:
Can't open /var/run/nut/genericups-ttyUSB0.pid: No such file or directory
Does /var/run/nut exist??
Can't chdir to /var/run/nut: Permission denied Driver failed to start (exit status=1) [FAILED] Can't chdir to /var/run/nut: Permission denied
It does not look like it, either that or it is not owned by the nut user.
[david@reddwarf ups]$ ls -l total 80 -rwxr-x--- 1 nut nut 1121 Oct 1 17:25 hosts.conf -rwxr-x--- 1 nut nut 3772 Oct 1 17:55 ups.conf -rwxr-x--- 1 nut nut 1369 Oct 1 18:17 upsd.conf -rwxr-x--- 1 nut nut 2190 Oct 1 12:53 upsd.users -rw------- 1 nut nut 11304 Oct 1 12:37 upsmon.conf -rwxr-x--- 1 nut nut 3871 Oct 1 12:42 upssched.conf -rwxr-x--- 1 nut nut 1420 Mar 11 2005 upsset.conf -rw-rw---- 1 root root 1773 Mar 11 2005 upsstats.html -rw-rw---- 1 root root 1867 Mar 11 2005 upsstats-single.html Can't open /etc/ups/ups.conf: Can't open /etc/ups/ups.conf: Permission denied
You do not show the permissions for /etc/ups.
Can't chdir to /var/run/nut: Permission denied
Fix the permissions on /var/run/nut or create it.
[david@reddwarf ups]$ ls -l /var/run/upsmon.pid -rw-r--r-- 1 root root 6 Oct 1 18:18 /var/run/upsmon.pid
Remember nut drops privs after starting. The nut user must be able to write there. The above will not work. Suggest moving this to /var/run/nut and make sure the dir is owned by the nut user.
I'm a bit puzzled over permmision refusals and unavailability of localhost. Could I ask for some help please or I'll never get Nut configured.
My suggestions above will fix some of the permissions problems but most likely will not fix all of your problems. I would suggest that you fix as much as you can and see what problems are left.
Are you using the nut rpm? If so it should have created the proper directories and permissions.
Mine looks like this:
(foghorn pts7) # ll -d /var/run/nut drwxr-x--- 2 nut nut 4096 Sep 17 22:46 /var/run/nut (foghorn pts7) # ll /var/run/nut total 24 srw-rw---- 1 nut nut 0 Sep 17 22:45 apcsmart-ttyQ01e1 -rw-r--r-- 1 nut nut 5 Sep 17 22:45 apcsmart-ttyQ01e1.pid srw-rw---- 1 nut nut 0 Sep 17 22:45 apcsmart-ttyQ01e2 -rw-r--r-- 1 nut nut 5 Sep 17 22:45 apcsmart-ttyQ01e2.pid srw-rw---- 1 nut nut 0 Sep 17 22:45 apcsmart-ttyQ01e3 -rw-r--r-- 1 nut nut 5 Sep 17 22:45 apcsmart-ttyQ01e3.pid srw-rw---- 1 nut nut 0 Sep 17 22:46 apcsmart-ttyQ01e4 -rw-r--r-- 1 nut nut 5 Sep 17 22:46 apcsmart-ttyQ01e4.pid -rw-r--r-- 1 nut nut 5 Sep 17 22:46 upsd.pid -rw-r--r-- 1 root root 5 Sep 17 22:46 upsmon.pid (foghorn pts7) #
Notice that with the exception of upsmon.pid everything is owned by nut. You will get different file names then above unless you happen to be monitoring 4 apc ups's connected via Equinox Ethernet Serial ports. :-)
Hope this helps,
Tom Diehl tdiehl@rogueind.com Spamtrap address mtd123@rogueind.com
Tom Diehl wrote: <------------------------------- SNIP --------------------------------------->
My suggestions above will fix some of the permissions problems but most likely will not fix all of your problems. I would suggest that you fix as much as you can and see what problems are left.
Are you using the nut rpm? If so it should have created the proper directories and permissions.
Mine looks like this:
(foghorn pts7) # ll -d /var/run/nut drwxr-x--- 2 nut nut 4096 Sep 17 22:46 /var/run/nut (foghorn pts7) # ll /var/run/nut total 24 srw-rw---- 1 nut nut 0 Sep 17 22:45 apcsmart-ttyQ01e1 -rw-r--r-- 1 nut nut 5 Sep 17 22:45 apcsmart-ttyQ01e1.pid srw-rw---- 1 nut nut 0 Sep 17 22:45 apcsmart-ttyQ01e2 -rw-r--r-- 1 nut nut 5 Sep 17 22:45 apcsmart-ttyQ01e2.pid srw-rw---- 1 nut nut 0 Sep 17 22:45 apcsmart-ttyQ01e3 -rw-r--r-- 1 nut nut 5 Sep 17 22:45 apcsmart-ttyQ01e3.pid srw-rw---- 1 nut nut 0 Sep 17 22:46 apcsmart-ttyQ01e4 -rw-r--r-- 1 nut nut 5 Sep 17 22:46 apcsmart-ttyQ01e4.pid -rw-r--r-- 1 nut nut 5 Sep 17 22:46 upsd.pid -rw-r--r-- 1 root root 5 Sep 17 22:46 upsmon.pid (foghorn pts7) #
Notice that with the exception of upsmon.pid everything is owned by nut. You will get different file names then above unless you happen to be monitoring 4 apc ups's connected via Equinox Ethernet Serial ports. :-)
Hope this helps,
Tom Diehl tdiehl@rogueind.com Spamtrap address mtd123@rogueind.com
Thanks for helping Tom, This as far as got this morning,seems that usb comms is the last stumbling [fumbling :-)] block. Error messages :
[root@reddwarf sysconfig]# service ups start Starting genericups -x upstype=11 -x CP = usb: Network UPS Tools - Generic UPS driver 1.30 (2.0.2) UPS type: Powerware 3115
Unable to open =: No such file or directory
Things to try:
- Check 'port=' in ups.conf
- Check owner/permissions of all parts of path
Fatal error: unusable configuration [FAILED] Starting upsd: Network UPS Tools upsd 2.0.2 Can't connect to UPS [powermate3105] (genericups -x upstype = 11 -x CP = usb-ttyUSB0): No such file or directory Synchronizing........ giving up [ OK ] Starting UPS monitor (master): Network UPS Tools upsmon 2.0.1 UPS: reddwarf@localhost (slave) (power value 1) Using power down flag file /etc/killpower
[ OK ] [root@reddwarf sysconfig]# su - david [david@reddwarf ~]$ sudo service ups restart Stopping UPS monitor: [ OK ] Stopping upsd: [ OK ] Shutting down genericups -x upstype=11 -x CP = usb: [FAILED] Starting genericups -x upstype=11 -x CP = usb: Network UPS Tools - Generic UPS driver 1.30 (2.0.2) UPS type: Powerware 3115
Unable to open =: No such file or directory
Things to try: ---- || ----- - Check 'port=' in ups.conf
- Check owner/permissions of all parts of path
Fatal error: ***unusable configuration*** [FAILED] Starting upsd: Network UPS Tools upsd 2.0.2 Can't connect to UPS [powermate3105] (genericups -x upstype = 11 -x CP = usb-ttyUSB0): No such file or directory Synchronizing........ giving up [ OK ] Starting UPS monitor (master): Network UPS Tools upsmon 2.0.1 UPS: reddwarf@localhost (slave) (power value 1) Using power down flag file /etc/killpower [ OK ] [david@reddwarf ~]$ sudo service ups stop Stopping UPS monitor: [ OK ] Stopping upsd: [ OK ] Shutting down genericups -x upstype=11 -x CP = usb: [FAILED] [david@reddwarf ~]$
Broadcast message from nutmon (Sun Oct 2 14:21:04 2005):
UPS reddwarf@localhost is unavailable Broadcast message from nutmon (Sun Oct 2 14:22:20 2005): Broadcast UPS reddwarf@localhost is unavailable
[david@reddwarf ~]$ ls -l /etc/sysconfig/ups -rwxr-x--- 1 nut nut 648 Oct 2 14:19 /etc/sysconfig/ups
david
david walcroft wrote:
Tom Diehl wrote:
Additional info from Kernel messages
[david@reddwarf ~]$ sudo tail -f /var/log/messages Oct 2 14:22:30 reddwarf wall[10471]: wall: user nutmon broadcasted 1 lines (39 chars) Oct 2 14:22:35 reddwarf upsd[10413]: Rejecting TCP connection from 127.0.0.1 Oct 2 14:22:35 reddwarf upsmon[10416]: Set username on [reddwarf@localhost] failed: Server disconnected Oct 2 14:22:40 reddwarf upsmon[10416]: Poll UPS [reddwarf@localhost] failed - Write error: Bad file descriptor Oct 2 14:22:45 reddwarf upsd[10413]: Rejecting TCP connection from 127.0.0.1 Oct 2 14:22:45 reddwarf upsmon[10416]: Set username on [reddwarf@localhost] failed: Server disconnected Oct 2 14:22:50 reddwarf upsmon[10416]: Poll UPS [reddwarf@localhost] failed - Write error: Bad file descriptor Oct 2 14:22:52 reddwarf upsmon[10416]: Signal 15: exiting Oct 2 14:22:52 reddwarf upsmon[10415]: upsmon parent: read: Success Oct 2 14:22:52 reddwarf upsd[10413]: Signal 15: exiting Oct 2 14:46:19 reddwarf upsd[15051]: Can't connect to UPS [powermate3105] (genericups -x upstype = 11 -x CP = usb-ttyUSB0): No such file or directory Oct 2 14:46:24 reddwarf upsd[15067]: Startup successful Oct 2 14:46:24 reddwarf upsmon[15069]: Startup successful Oct 2 14:46:24 reddwarf upsd[15067]: Rejecting TCP connection from 127.0.0.1 Oct 2 14:46:24 reddwarf upsmon[15070]: Set username on [reddwarf@localhost] failed: Server disconnected Oct 2 14:46:29 reddwarf upsmon[15070]: Poll UPS [reddwarf@localhost] failed - Write error: Bad file descriptor Oct 2 14:46:29 reddwarf upsmon[15070]: UPS is not talking Oct 2 14:46:29 reddwarf wall[15090]: wall: user nutmon broadcasted 1 lines (20 chars) Oct 2 14:46:34 reddwarf upsd[15067]: Rejecting TCP connection from 127.0.0.1 Oct 2 14:46:34 reddwarf upsmon[15070]: Set username on [reddwarf@localhost] failed: Server disconnected Oct 2 14:46:39 reddwarf upsmon[15070]: Poll UPS [reddwarf@localhost] failed - Write error: Bad file descriptor Oct 2 14:46:39 reddwarf upsmon[15070]: UPS reddwarf@localhost is unavailable Oct 2 14:46:39 reddwarf wall[15127]: wall: user nutmon broadcasted 1 lines (39 chars) Oct 2 14:46:44 reddwarf upsd[15067]: Rejecting TCP connection from 127.0.0.1 Oct 2 14:46:44 reddwarf upsmon[15070]: Set username on [reddwarf@localhost] failed: Server disconnected Oct 2 14:46:49 reddwarf upsmon[15070]: Poll UPS [reddwarf@localhost] failed - Write error: Bad file descriptor Oct 2 14:46:54 reddwarf upsd[15067]: Rejecting TCP connection from 127.0.0.1 Oct 2 14:46:54 reddwarf upsmon[15070]: Set username on [reddwarf@localhost] failed: Server disconnected Oct 2 14:46:55 reddwarf upsmon[15070]: Signal 15: exiting Oct 2 14:46:55 reddwarf upsmon[15069]: upsmon parent: read: Success Oct 2 14:46:55 reddwarf upsd[15067]: Signal 15: exiting
-
Craig White -
david walcroft -
George N. White III -
Markku Kolkka -
Matthew Saltzman -
Thomas Taylor -
Tom Diehl