similar to: Network UPS Tools version 2.7.1 released

Charles, I need so major help with getting development build working and need some assistance. Here are the issues that we are running into: Number 1 change - 2.7.2 no longer has the HAL scripts that 2.6.5 has. I am working on if HAL is actually required on CentOS6.6 with the 2.7.2 code or if they have another way around it. This is code diving which is taking some time. Number 2 change -

Hello, My name is Eric Cobb and I am a Product Specialist with Tripp Lite. We have tested your latest NUT distributions against our HID USB compatible UPS systems and would like to know what is needed and/or who is needed to contact in order to updated the listing of compatible Tripp Lite UPS systems in your HCL list? Best Regards, Eric K. Cobb Product Management Specialist [Tripp Lite] 1111

On Oct 15, 2013, at 3:40 PM, Eric Cobb wrote: > My name is Eric Cobb and I am a Product Specialist with Tripp Lite. We have tested your latest NUT distributions against our HID USB compatible UPS systems and would like to know what is needed and/or who is needed to contact in order to updated the listing of compatible Tripp Lite UPS systems in your HCL list? Hi Eric, From end users of NUT,

Hello, I am trying to get a SMART500RT1U working on CentOS and just receiving the following message when attempting to start the driver: Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.6.5) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: Tripp Lite /TRIPP LITE SMART500RT1U Unknown input voltage range: 0x02 Unknown number of

On Mar 23, 2015, at 7:57 PM, Eric Cobb <Eric_Cobb at tripplite.com> wrote: > Number 1 change - 2.7.2 no longer has the HAL scripts that 2.6.5 has. I am working on if HAL is actually required on CentOS6.6 with the 2.7.2 code or if they have another way around it. This is code diving which is taking some time. HAL support in NUT was bit-rotting, so it was removed. It isn't

On Mar 6, 2015, at 12:51 PM, Eric Cobb <Eric_Cobb at tripplite.com> wrote: > Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.6.5) > Warning: This is an experimental driver. > Some features may not function correctly. > > Detected a UPS: Tripp Lite /TRIPP LITE SMART500RT1U > Unknown input voltage range: 0x02 > Unknown number of switchable load banks:

Charles, Thanks again for your help. We were able to have a 2.7.2.6 build complied into a working RPM for CENTOS 6.6. There is one more issue that needs to be addressed: The init script no longer works so a new script needs to be written to enable and disable the ups functionality, however it is communicating with the UPS properly. The question I have at this point is, is there a way I can

On March 6, 2015, at 6:17pm, Charles Leppe ,cleppe at gmail.com> wrote: If this is the same protocol 3005 that we saw in mid-2014 (USB ID: 09AE:0001), then support will be part of the upcoming NUT 2.7.3 release. You wouldn't happen to know anyone who would be able to publish the specs of that protocol, would you? ;-) That would help remove the "experimental driver" warning.

Hey 2015-04-09 1:46 GMT+02:00 Charles Lepple <clepple at gmail.com>: > On Apr 8, 2015, at 2:04 PM, Eric Cobb <Eric_Cobb at tripplite.com> wrote: > > Charles and list, > > If I leave the driver alone it does not eventually start. It continues to > report that it is unable to connect. I have to perform a upsdrvctl stop ; > upsdrvctl start (I actually just perform

Ok, so I have made some progress that seems to suggest the initial “fix” I stumbled upon isn’t required. I haven’t yet worked backwards to figure out reasons why our customers have had similar complaints or solve the problem on the CentOS VM yet, but that is on the todo list. I am hoping it ends up just being not enabling the service on startup, but I can’t say that explains away all the symptoms

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

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

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

# 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 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

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