similar to: upssched setup

# reboot Connection to 192.168.5.81 closed by remote host. Connection to 192.168.5.81 closed. ppo at admin:/tmp$ ssh root at 192.168.5.81 root at 192.168.5.81's password: Last login: Tue Jul 30 14:10:49 2013 from pc-ppo.kh.ektos OpenBSD 5.3 (GENERIC.MP) #58: Tue Mar 12 18:43:53 MDT 2013 # ps -aux | grep ups root 2254 0.0 0.0 324 700 p0 S+ 5:29PM 0:00.00 grep ups # ps -aux

Thanks for you reply. I have installed asciidoc with "pkg_add asciidoc" And it returns something: # asciidoc fgh asciidoc: FAILED: input file /root/nut/fgh missing # which asciidoc /usr/local/bin/asciidoc Maybe there is any way to skip building man pages. This is not the such main thing as a new devices support. I also could built the driver that I need # make riello_ser but I don't

On Jul 29, 2013, at 6:43 AM, Pavel Potcheptsov (EKTOS) wrote: > Hello list, > I have explored https://github.com/networkupstools/nut repository > and found that Riello UPS added into list of supported UPS. > But current package for most distribution it's nut-2.6.5 which > doesn't have Riello's models. > Do we need to wait next upcoming nut release to get start with

On Jul 30, 2013, at 3:28 AM, Pavel Potcheptsov (EKTOS) wrote: > another attempt: > # upsd > Network UPS Tools upsd 2.6.5 > fopen /var/db/nut/upsd.pid: No such file or directory > listening on 127.0.0.1 port 3493 > listening on ::1 port 3493 > Can't connect to UPS [senpro] (riello_ser-senpro): No such file or directory We need to determine whether upsd and the driver are

Here is what I did: # cd /root/nut/ # nut here it's checkouted repository # ./configure --with-user=_ups --with-group=_ups # cd drivers/ # make riello_ser # chgrp bin riello_ser # cp riello_ser /usr/local/bin # here I copied builder driver to folder where nut-package will store their files/drivers # pkg_add nut-2.6.5p1 # ls -la /dev/tty00 crw-rw---- 1 _ups _ups 8, 0 Jul 30

Hello list, I have explored https://github.com/networkupstools/nut repository and found that Riello UPS added into list of supported UPS. But current package for most distribution it's nut-2.6.5 which doesn't have Riello's models. Do we need to wait next upcoming nut release to get start with Riello? I tried to install from source but stuck: # git clone

On Jul 29, 2013, at 7:56 AM, Charles Lepple wrote: > On Jul 29, 2013, at 6:43 AM, Pavel Potcheptsov (EKTOS) wrote: > >> Hello list, >> I have explored https://github.com/networkupstools/nut repository >> and found that Riello UPS added into list of supported UPS. >> But current package for most distribution it's nut-2.6.5 which >> doesn't have

I'll test it. I'm a bit confused with cgi-bin. I have made a lot of hosts.conf copies and didn't understand where does upsstats trying to find hosts.conf # ps -aux | grep ups _ups 13934 0.0 0.0 484 920 ?? Ss 5:41PM 0:01.53 /usr/local/bin/riello_ser -a senpro _ups 9171 0.0 0.1 532 1168 ?? Ss 5:41PM 0:00.13 /usr/local/sbin/upsd _ups 16906 0.0 0.1

On Jul 30, 2013, at 10:39 AM, Pavel Potcheptsov (EKTOS) wrote: > Is this a trouble? Driver use path /var/state/ups/ but upsd use path /var/db/nut/upsd.pid Yes, the driver and upsd need to agree on the path to the socket. From the FreeBSD ports tree: /usr/ports/sysutils/nut/Makefile: STATEDIR?= /var/db/nut [...] CONFIGURE_ARGS= --sysconfdir=${PREFIX}/etc/nut \

another attempt: # upsd Network UPS Tools upsd 2.6.5 fopen /var/db/nut/upsd.pid: No such file or directory listening on 127.0.0.1 port 3493 listening on ::1 port 3493 Can't connect to UPS [senpro] (riello_ser-senpro): No such file or directory # ls -la /var/db/nut/ total 12 drwx------ 2 _ups wheel 512 Jul 30 10:22 . drwxr-xr-x 10 root wheel 512 Jul 29 16:41 .. -rw-r--r-- 1 _ups

Thank you very much!! I have tried configure downloaded source with # ./configure --with-user=_ups --with-group=_ups --with-statepath=/var/db/nut/ and then build driver and copy again. but this doesn't help (driver pid still in the /var/state/ups). Maybe I must add more arguments to change driver's pid location, but I did next, I changed this argument in openbsd ports: # pkg_delete nut #

On Jul 31, 2013, at 3:36 AM, Pavel Potcheptsov (EKTOS) wrote: > Does it looks good? I think so - 40.8 volts with a nominal of 36 volts is 13.6 V/cell, which agrees with the 100% charge value. Hopefully the line voltages and frequency make sense for your region. > Another question what does riello experimental driver warning mean? We add that to all new drivers. This driver was written by

Network UPS Tools version 2.7.1 has been released: http://www.networkupstools.org/ This release is an interim release, part of the testing series, and the first release after the transition from Subversion to Git. The last release (2.6.5) is almost a year old. A lot of work has been done, but a good amount remains to achieve 2.8.0 goals. Direct access: - Download:

Hi Roger, I get: Apr 27 20:50:05 unifi upsmon[1022]: UPS ups on batteryApr 27 20:50:05 unifi upssched[2688]: Timer daemon startedApr 27 20:50:06 unifi upssched[2688]: New timer: onbatt (20 seconds)Apr 27 20:50:26 unifi upssched[2688]: Event: onbattApr 27 20:50:26 unifi upssched[2688]: exec_cmd(/sbin/upssched-cmd.sh onbatt) returned 126Apr 27 20:50:41 unifi upssched[2688]: Timer queue empty,

Roger, I did and it didnt work. Hence why I was trying to run just the shell script manually. I am not sure if this works though with the timer defined in it? Cheers, James Date: Mon, 27 Apr 2015 15:03:44 +0200 From: roger at rogerprice.org To: nut-upsuser at lists.alioth.debian.org Subject: Re: [Nut-upsuser] upssched setup On Mon, 27 Apr 2015, James Hammond wrote: > I am unable to get

You are right. Before install nut-cgi I have stopped apache and started it again without chroot. I have started it again with chroot and cgi is working! This is best support for open source project I have ever seen. Good luck! On Thu, Aug 1, 2013 at 3:03 PM, Charles Lepple <clepple at gmail.com> wrote: > On Jul 31, 2013, at 11:39 AM, Pavel Potcheptsov (EKTOS) wrote: > > >

Hi, The exec is returning 126 - "Command invoked cannot execute. A permission or command not executable problem.". Are you sure that the script is executable by the user running NUT? Do you have SELinux enabled? Regards, Neil. On 27/04/15 20:55, James Hammond wrote: > Hi Roger, > > I get: > > Apr 27 20:50:05 unifi upsmon[1022]: UPS ups on battery > Apr 27

Gents, Thanks, yes definitely a permissions problem. Roger pointed me in the correct direction with the command to add logging for the script. I have the shutdown working now but need to tighten up the permissions. Not too sure where to start with assigning the correct permissions. Cheers, James > Date: Mon, 27 Apr 2015 21:25:45 +0100 > From: neil at dana.org.uk > To: nut-upsuser at

Hello, I'm using nut with my MG Ellipse on serial port. No problem since one year. Two days ago, I wanted to add a phone alert through my asterisk box when power is down. Since then, upssched doesn't make his job anymore. here is the "syslog" I get when the power cord is unplugged : > > May 9 11:39:34 serveur upsmon[6411]: UPS ellipse@localhost on battery > May 9

Hi, the last commit to upssched.c (Merge Coverity branch, r3555) broke upssched with commands that have a second argument. If a command with a second argument is used, "enc" in line 697 is not an empty buffer and snprintfcat() just appends some stuff, i.e. the following command CANCEL onbatt online becomes onlineCANCEL "onbatt" "online" and is then sent to the