similar to: upsc does not dig connection from other hosts

Hi, I would like to make it impossible for users to change the contents of the authorized_keys-file. I just found out about the sshd_config setting: AuthorizedKeysFile /etc/ssh/authorized_keys/%u But even in that case that file has to be owned by the user, unless I set ``StrictModes no'' which would allow other nastyness. I would like to request that that file could also be owned by

Greetings! I have successfully installed and configured nut package. All i want now is to power off ups. If i run upsmon -c fsd as root - everything goes fine, system and ups gracefully shutting down. If i unplug power cable from an ups, then system is down, but ups still on load. Any help would be appreciated. Debian Lenny x86 ups.conf [ippon] driver = megatec port = /dev/ttyS0

Hi thanks for the reply. The servers can ping each other... The router log doesn't show anything and I am the admin for the servers. The machines firewalls allow each other's ips etc. Part of the issue is possibly that I just don't know if I've set up NUT correctly for this arrangement? Like I say it works ok on LAN, but not across networks. Is there something I should be doing

Hi all, I've just upgraded my debian box from etch to lenny, and am now having Nut problems. I have read through the UPGRADING text (which helped fixed my first ups driver related problem), but have now hit another problem, which seems quite common, but non of the responses I've found on Google apply, so I'm coming to you for help. On issuing a "/etc/init.d/nut start"

Hello, I'm facing problems as I'm installing NUT to monitor a MGE Ellipse ASR600USBS on a FreeBSD 6.1 box. UPS is recognized as : ugen0: MGE UPS SYSTEMS ELLIPSE, rev 1.10/42.41, addr 2 I'm temporarily using root profile (devfs/devd scripts not modified atm). newhidups starts & runs fine (unplugging mains makes newhidups outputs lots of data when started with -DDDD flags)

Hi, this is my first nut installation, i see lot of connection failure and when i tried the configuration removing the power chord from the ups i expected tha machine will power itslef down but this has not happened. I'm using nut 2.2.2-2 from debian lenny, ups is a mustek powermust 2000 with usb cable. All config files are root:nut and 640, i've had to add nut user to nut group

Hi thanks Roger, I've amended my hosts.allow file to your suggested one - thanks for that. I'm still getting "Connection refused on the client cgi screen as well as in the shell it gives me UPS upsname at ipaddresshere is unavailable... Any ideas what I can try next to debug why it's not working. Also should the "allowfrom = clientIPaddresshere" line be in my monuser

Short description: when upsmon starts it logs this to /var/log/messages: Jul 11 12:35:55 sorcerer upsmon[23902]: Startup successful Jul 11 12:35:55 sorcerer upsmon[23902]: user monuser not found Near as I can tell upsd is running properly. Long description: Centos 5 system (x86_64), built nut 2.2.2 from stable source with ./configure --with-usb --with-user=nut --with-group-nut make

Hi All, I have an mge pulsar esv 14+ rackmount UPS connected via straight through serial cable to a USB to serial adaptor (My motherboard does not have a native RS232 port). I am running Ubuntu Server 9.04 x64, and nut 2.4.1-2ubuntu4 installed via APT. I am getting the error: Poll UPS [ups1 at localhost] failed - Driver not connected My conf files: (ups.conf) [ups1] driver=mge-utalk

Hi Everyone, I am new to UPSs and Linux.? I purchased a Belkin F6C750-AVR UPS for our church.? We are?running CENTOS 5.2. I tried the Linux Power Management Software that came with Belkin UPS with NO success. I installed the NUT software. After some experimentation I received some success with the megatec_usb Nut driver: [root at server bin]# /sbin/megatec_usb -u root -a serverups -DDDD

Hi all, I know there are some howto's about Powerware 5115 and Ubuntu, but I can't still get that thing working. Can someone give some light... 1. Powerware 5115, serial port (ttyS0) 2. Ubuntu 6.06.1 as LTSP-server As reference: http://gentoo-wiki.com/HOWTO_NUT http://keystoneit.wordpress.com/2006/09/25/network-ups-tools-nut-on-ubuntu/ --- a. I try to start driver as root. root at

Hi all, I know there are some howto's about Powerware 5115 and Ubuntu, but I can't still get that thing working. Can someone give some light... 1. Powerware 5115, serial port (ttyS0) 2. Ubuntu 6.06.1 as LTSP-server As reference: http://gentoo-wiki.com/HOWTO_NUT http://keystoneit.wordpress.com/2006/09/25/network-ups-tools-nut-on-ubuntu/ --- a. I try to start driver as root. root at

Hi all I have a simple setup: Ubuntu 9.04 server APC Back-UPS ES-700 connected with USB nut installed from packages (apt-get install nut). I guess that makes it version 2.4.1 ? The problem: When issuing: upsmon -c fsd I get a messages that the server will halt, and it does. But it won't restart again. I have set the BIOS to always power on, and this works fine when if I just cut the

Greetings, I imagine this question must have been answered previously on the list, but I can't search for the answer because the archives are gone. Executive summary: I am trying to install and configure nut 2.0.1 on Fedora Core. I have a SmartUPS Pro plugged into a USB port. Upsmon is logging "UPS myups@localhost is unavailable" to syslog and via wall when it starts up and

Here are the results from the output of upsc under different conditions from my Debian Test system with NUT 2.7.2 : Normal: ups.status: OL No wall power: ups.status: OB Runtime calibration (started from AP9630 web interface): ups.status: OB CAL So at this stage there is a difference! I then connected to my QNAP and set the UPS settings on the web interface to "Shutdown server if power

Problems getting reading from UPS with nut 2.0.2 Debian Sid I know that the server starts running and accepts incoming connections, it can verify the username and password but refutes that the UPS lives at localhost, what am I doing wrong ? I have read and reread both the official documentation and various guides around the net I am unsure where to go now. If the UPS itself is at fault (not

This command fails % ssh tarzan KnownHostsCommand-ORDER /usr/bin/sss_ssh_knownhosts 10.10.11.14 failed, status 1 KnownHostsCommand failed If there is an IP entry in ~/.ssh/config Host tarzan hostname 10.10.11.14 So I created a wrapper: % cat /usr/bin/sss_ssh_knownhosts.wrapper #!/bin/sh /usr/bin/sss_ssh_knownhosts "$@" || true Which works around the problem and does make ssh

hi i have a belkin ups here some setting chmod 0600 /dev/hiddev0 chown nut:root /dev/hiddev0 linux:/home/sonia # /usr/lib/ups/driver/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) No matching USB/HID UPS found Driver failed to start (exit status=1) linux:/home/sonia # /usr/lib/ups/driver/upsdrvctl -u root start

Hi, I tried to do the minimum configuration for Nut. When I stop the on-line power i get terminal message that I'm on battery power and when I plug on-line power back in I get a message that I'm back to on-line power. So things are working/communicating. What I want is: if it's been on battery power for over 5 minutes the PC will shutdown. If powers comes on-line again before the 5

Good morning all. I am on a different system with a different UPS, and I am fighting a similar problem to the one I posted about yesterday, and again making little headway. This system is running Debian Wheezy and connected to an APC BackUPS ES550. Starting things manually seems to go well, but my startup script fails, and nothing is logged anywhere. This may not be a NUT question per se, but I