thr3ads.net - Nut upsuser - [Nut-upsuser] About your driver NUTDRV_ATCL

If this information is useful, please help other people find it:
Share via:

Steve Ballantyne

2014-Jul-24 18:20 UTC

[Nut-upsuser] RV: About your driver NUTDRV_ATCL_USB(8) for install

I think I may be of some help in this matter.  Since I am running a
bunch of Raspberry Pi's with NUT and it took a lot of hacking to make
it possible.  You could probably copy and paste this right into a
shell script and just run it ...

# Do an rpi-update FIRST to prevent USB strangeness

#some depencies from repo
sudo apt-get -y install m4 libtool libudev-dev automake

#fixing autoconf for later
sudo ln -s /usr/share/autoconf/Autom4te /usr/local/share/autoreconf/Autom4te
sudo ln -s /usr/bin/autom4te /usr/local/bin/autom4te
sudo ln -s /usr/bin/autoconf /usr/local/bin/autoconf
sudo ln -s /usr/bin/autoheader /usr/local/bin/autoheader

#installing nut dependencies
mkdir nut-depends
cd ./nut-depends

# acscripts from source
wget
http://sourceforge.net/projects/acscripts.berlios/files/acscripts-0.0.1.13.tar.bz2
tar xf acscripts-0.0.1.13.tar.bz2
sudo mkdir /usr/lib/scripts
sudo mv acscripts-0.0.1.13 /usr/lib/scripts/acscripts

#autoreconf from source
wget
http://sourceforge.net/projects/autoreconf/files/0.0.0.1/autoreconf-0.0.0.1.tar.bz2
tar xf autoreconf-0.0.0.1.tar.bz2
cd autoreconf-0.0.0.1
./configure && sudo make install
cd ..

#libusb and libusb-compat from source
wget
"http://downloads.sourceforge.net/project/libusb/libusb-1.0/libusb-1.0.18/libusb-1.0.18.tar.bz2?r=http%3A%2F%2Fwww.libusb.org%2F&ts=1404210716&use_mirror=softlayer-ams"
-O libusb-1.0.18.tar.bz2

tar -xjf libusb-1.0.18.tar.bz2
cd libusb-1.0.18
./configure && sudo make install
cd ..
wget
"http://downloads.sourceforge.net/project/libusb/libusb-compat-0.1/libusb-compat-0.1.4/libusb-compat-0.1.4.tar.bz2?r=http%3A%2F%2Fwww.libusb.org%2F&ts=1404210428&use_mirror=softlayer-ams"
-O libusb-compat-0.1.4.tar.bz2

tar -xjf libusb-compat-0.1.4.tar.bz2
cd libusb-compat-0.1.4
./configure && sudo make install
cd ..

#get back to home root
cd ..

#download nut from dev repo
git clone git://github.com/networkupstools/nut.git
cd nut

# Run autogen
./autogen.sh

#create some groups and directories and mod some persmissions
sudo groupadd nut
sudo usermod -a -G nut pi
sudo usermod -a -G nut root
sudo mkdir /var/run/nut
sudo chown root:nut /var/run/nut
sudo mkdir -p /var/state/ups
sudo chown root:nut /var/state/ups
sudo chmod 0770 /var/state/ups

#now we ./configure and make it
./configure --without-doc --with-drivers=tripplite_usb,upsdrvctl

#still tries to build docs, even though I said NO to docs
cp Makefile Makefile.orig
sed -i 's/include common clients conf data tools docs drivers/include
common clients conf data tools drivers/' Makefile

make
sudo make install
Steve Ballantyne
Network Engineer
MCSE/MCDST; Novell CLA; LPIC-1; CTT+; A+; Network+; Linux+; Server+;
I-Net+; Security+; SonicWALL CSSA



On Thu, Jul 24, 2014 at 12:07 PM,  <pererivers at yahoo.es>
wrote:> Dear Charles,
>
> Thanks for your quick reply, but I can't install nut_2.7.2 in my
raspberry.
>
> 1) I create a [nut] directory and use wget to download three files:
> [nut_2.7.2-1.dsc] [nut_2.7.2.orig.tar.gz] [nut_2.7.2-1.debian.tar.xz] 2)I
> unpack:
> dpkg-source -x nut_2.7.2-1.dsc
> 3) I use command
>   root at pi1:/nut/nut-2.7.2# debuild -us -uc .
> ..
> And I have the following error code:
> ---------------------------------------------
> root at pi1:/nut/nut-2.7.2# debuild -us -uc -d  dpkg-buildpackage
-rfakeroot -d
> -us -uc
> dpkg-buildpackage: aviso: est? usando una orden para convertirse en
> administrador (?gain-root-command?), a pesar de que ya es el administrador
> dpkg-buildpackage: paquete fuente nut
> dpkg-buildpackage: versi?n de las fuentes 2.7.2-1
> dpkg-buildpackage: fuentes modificadas por Laurent Bigonville
> <bigon at debian.org>  dpkg-source --before-build nut-2.7.2
> dpkg-buildpackage: arquitectura del sistema armhf  fakeroot debian/rules
> clean
> debian/rules:3: /usr/share/cdbs/1/rules/debhelper.mk: No existe el fichero
o
> el directorio
> debian/rules:4: /usr/share/cdbs/1/class/autotools.mk: No existe el fichero
o
> el directorio
> debian/rules:5: /usr/share/cdbs/1/class/python-module.mk: No existe el
> fichero o el directorio
> debian/rules:7: /usr/share/cdbs/1/rules/autoreconf.mk: No existe el fichero
> o el directorio
> debian/rules:15: /usr/share/cdbs/1/rules/utils.mk: No existe el fichero o
el
> directorio
> make: *** No hay ninguna regla para construir el objetivo
> `/usr/share/cdbs/1/rules/utils.mk'.  Alto.
> dpkg-buildpackage: fallo: fakeroot debian/rules clean devolvi? un estado de
> salida de error 2
> debuild: fatal error at line 1357:
> dpkg-buildpackage -rfakeroot -d -us -uc failed root at pi1:/nut/nut-2.7.2#
> ----------------------------------------------------------
>
> Any idea? what am I doing wrong.
> I don't have installed 'apt-src' command to install
dependencies.
>
> Best regards,
> Pere Rius
>
>
>
> -----Mensaje original-----
> De: Charles Lepple [mailto:clepple at gmail.com] Enviado el: jueves, 17 de
> julio de 2014 14:41
> Para: pere at riusnebot.com
> CC: NUT List
> Asunto: Re: About your driver NUTDRV_ATCL_USB(8) for install
>
> On Jul 13, 2014, at 9:46 AM, pere at riusnebot.com wrote:
>
>> Dear Charles Lepple,
>> Sorry for my email intrusion.
>
> for next time:
>
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
>
>> I have an UPS called Ovislink 1000VA and it use a UPSMART2000R (with
?ATCL
> FOR UPS?).
>> I?m a beginner Linux user and I ?will install your new driver
> <nutdrv_atcl_usb > to work with networkupstools.org, but  I can?t.
>>
>> We have a raspberry pi with debian, and  I only installed a ?nut? with
> version:
>>
>> ii  nut            2.6.4-2.3+de all          network UPS tools -
> metapackage
>> ii  nut-client     2.6.4-2.3+de armhf        network UPS tools -
clients
>> ii  nut-server     2.6.4-2.3+de armhf        network UPS tools - core
> system
>>
>> ? But it not contain your NUTDRV_ATCL_USB to put in my ups.conf file
>> configuration
>>
>> Could you help me how we can use your new driver ATCL FOR UPS? I don?t
> know how install unstable 2.7.2-1 version in RaspBerry that I think that
> contents this new driver.
>
> There are a few options, depending on whether you prefer packages, or if
you
> need to install this quickly.
>
> One way might be to request a backport. I have no experience with this
> particular group, but you could try requesting here:
> http://sourceforge.net/p/raspbian-backports/suggestions/
>
> Another way is to download the Debian source files for 2.7.2-1 from
> https://packages.debian.org/sid/nut (three links under "Download
Source
> Package" in the right sidebar) and use 'debuild -us -uc' from
the devscripts
> package.
>
> Since I needed to build from the latest code, I used 'apt-src' to
install
> the build dependencies. Note that this will require a fair amount of free
> space on your SD card (I am using a 4GB card with Raspbian). In
> /etc/apt/sources.list, copy the first line, and change 'deb' to
'deb-src'
> like so:
>
> deb http://mirrordirector.raspbian.org/raspbian/ wheezy main contrib
> non-free rpi deb-src http://mirrordirector.raspbian.org/raspbian/ wheezy
> main contrib non-free rpi
>
> Then run 'sudo apt-src install nut'. This downloads the packages
needed to
> build NUT 2.6.4, but then you would want to grab the newer NUT 2.7.2
> package. You may also want to remove the nut* .deb binary packages to avoid
> confusion.
>
> Unpack nut-2.7.2.tar.gz, and follow the installation instructions here:
> http://www.networkupstools.org/docs/user-manual.chunked/ar01s05.html
>
> If you need help, please subscribe to the nut-upsuser list and describe the
> problem there.
>
> --
> Charles Lepple
> clepple at gmail
>
>
>
>
> ---
> Aquest correu electr?nic est? lliure de virus perqu? la protecci? de
l'avast! Antivirus est? habilitada.
> http://www.avast.com
>
>
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Charles Lepple

2014-Jul-25 03:02 UTC

head link

[Nut-upsuser] About your driver NUTDRV_ATCL_USB(8) for install

On Jul 24, 2014, at 2:20 PM, Steve Ballantyne <steve.ballantyne at
gmail.com> wrote:
> #now we ./configure and make it
> ./configure --without-doc --with-drivers=tripplite_usb,upsdrvctl
Pere: if you do build manually from source, you'll want to replace
tripplite_usb with nutdrv_atcl_usb here. (I would still recommend trying to get
apt-src to work.)
> #still tries to build docs, even though I said NO to docs
> cp Makefile Makefile.orig
> sed -i 's/include common clients conf data tools docs drivers/include
> common clients conf data tools drivers/' Makefile
Shouldn't be necessary for a tarball install (docs are already included).

I would also recommend using libusb-0.1.12 (build against libusb-dev in Debian).
We haven't done as much testing with libusb-1.0 and libusb-compat.

-- 
Charles Lepple
clepple at gmail

PERE (yahoo.es)

2015-Feb-09 11:48 UTC

head link

[Nut-upsuser] RV: About your driver NUTDRV_ATCL_USB(8) for install

Dear Steve,
Thanks.
Until today I could not install the nut in my raspberry. All installation good,
but with my ups " Ovislink Chrome 1000VA" and
"nutdrv_atcl_usb" driver, it inform me the following error details.
I can startup nut but nutmon don't receive anything only (lost conection).

My setup:


root at pi1:/nut# lsusb
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 006: ID 0001:0000 Fry's Electronics  <------------- my UPS


ups.conf
[ups]
         driver = nutdrv_atcl_usb
         port=auto
         vendor="ATCL FOR UPS"
         desc= "Ovislink"


Script
root at pi1:/nut# sudo /usr/local/ups/bin/nutdrv_atcl_usb -u root -a ups -DDDD

--------------------------------------------------------
Network UPS Tools - 'ATCL FOR UPS' USB driver 1.1
(2.7.2-signed-159-g4552d14)
Warning: This is an experimental driver.
Some features may not function correctly.

   0.000000     debug level is '4'
   0.011253     Searching for USB device...
   0.015400     Checking USB device [0001:0000] (001/006)
   0.022269     - VendorID     : 0001
   0.023193     - ProductID    : 0000
   0.023865     - Manufacturer : ATCL FOR UPS
   0.024616     - Product      : ATCL FOR UPS
   0.025382     - Serial Number: ATCL FOR UPS
   0.026048     - Bus          : 001
   0.027090     Matched expected vendor='ATCL FOR UPS'.
   0.028188     Can't set USB configuration: could not set config 1: Device
or resource busy
   0.029246     detached kernel driver from USB device...
   0.030559     USB device [0001:0000] opened
   0.866216     read: (8 bytes) => 03 00 00 00 00 00 00 00
   0.866413     reply[0] = 0x03 -> OL
   0.867461     dstate_init: sock /var/state/ups/nutdrv_atcl_usb-ups open on fd
5
   1.914346     read: (8 bytes) => 03 00 00 00 00 00 00 00
   1.915850     reply[0] = 0x03 -> OL
   5.872047     status interrupt read: error submitting URB: Device or resource
busy
   5.872261     Communications with UPS lost: Query to UPS failed
  10.874345     Checking USB device [0001:0000] (001/006)
  10.882134     - VendorID     : 0001
  10.883544     - ProductID    : 0000
  10.884823     - Manufacturer : ATCL FOR UPS
  10.886326     - Product      : ATCL FOR UPS
  10.886903     - Serial Number: ATCL FOR UPS
  10.887851     - Bus          : 001
  10.888155     Matched expected vendor='ATCL FOR UPS'.
  10.888834     Can't set USB configuration: could not set config 1: Device
or resource busy
  10.891625     detached kernel driver from USB device...
  10.892958     USB device [0001:0000] opened
  11.351356     read: (8 bytes) => 03 00 00 00 00 00 00 00
  11.351560     Communications with UPS re-established
  11.351703     reply[0] = 0x03 -> OL
  15.877029     status interrupt read: error submitting URB: Device or resource
busy
  15.877214     Communications with UPS lost: Query to UPS failed
  20.878831     Checking USB device [0001:0000] (001/006)
  20.886566     - VendorID     : 0001
  20.888713     - ProductID    : 0000
  20.890007     - Manufacturer : ATCL FOR UPS
  20.890830     - Product      : ATCL FOR UPS
  20.891162     - Serial Number: ATCL FOR UPS
  20.891345     - Bus          : 001
  20.891517     Matched expected vendor='ATCL FOR UPS'.
  20.892619     Can't set USB configuration: could not set config 1: Device
or resource busy
  20.893105     detached kernel driver from USB device...

---------------------------------------------

with the following command  root at pi1:/nut# sudo /usr/local/ups/sbin/upsc ups
at localhost I don't receive anything (only time out).

Somebody know if my "Ovislink Chrome" ups can work with
NUTDRV_ATCL_USB drivers? I tray with usbhid-ups, blazer_usb without luck.

Best regards,
Pere Rius





-----Mensaje original-----
De: Steve Ballantyne [mailto:steve.ballantyne at gmail.com] 
Enviado el: jueves, 24 de julio de 2014 20:21
Para: pererivers at yahoo.es
CC: NUT List
Asunto: Re: [Nut-upsuser] RV: About your driver NUTDRV_ATCL_USB(8) for install

I think I may be of some help in this matter.  Since I am running a bunch of
Raspberry Pi's with NUT and it took a lot of hacking to make it possible. 
You could probably copy and paste this right into a shell script and just run it
...

# Do an rpi-update FIRST to prevent USB strangeness

#some depencies from repo
sudo apt-get -y install m4 libtool libudev-dev automake

#fixing autoconf for later
sudo ln -s /usr/share/autoconf/Autom4te /usr/local/share/autoreconf/Autom4te
sudo ln -s /usr/bin/autom4te /usr/local/bin/autom4te sudo ln -s
/usr/bin/autoconf /usr/local/bin/autoconf sudo ln -s /usr/bin/autoheader
/usr/local/bin/autoheader

#installing nut dependencies
mkdir nut-depends
cd ./nut-depends

# acscripts from source
wget
http://sourceforge.net/projects/acscripts.berlios/files/acscripts-0.0.1.13.tar.bz2
tar xf acscripts-0.0.1.13.tar.bz2
sudo mkdir /usr/lib/scripts
sudo mv acscripts-0.0.1.13 /usr/lib/scripts/acscripts

#autoreconf from source
wget
http://sourceforge.net/projects/autoreconf/files/0.0.0.1/autoreconf-0.0.0.1.tar.bz2
tar xf autoreconf-0.0.0.1.tar.bz2
cd autoreconf-0.0.0.1
./configure && sudo make install
cd ..

#libusb and libusb-compat from source
wget
"http://downloads.sourceforge.net/project/libusb/libusb-1.0/libusb-1.0.18/libusb-1.0.18.tar.bz2?r=http%3A%2F%2Fwww.libusb.org%2F&ts=1404210716&use_mirror=softlayer-ams"
-O libusb-1.0.18.tar.bz2

tar -xjf libusb-1.0.18.tar.bz2
cd libusb-1.0.18
./configure && sudo make install
cd ..
wget
"http://downloads.sourceforge.net/project/libusb/libusb-compat-0.1/libusb-compat-0.1.4/libusb-compat-0.1.4.tar.bz2?r=http%3A%2F%2Fwww.libusb.org%2F&ts=1404210428&use_mirror=softlayer-ams"
-O libusb-compat-0.1.4.tar.bz2

tar -xjf libusb-compat-0.1.4.tar.bz2
cd libusb-compat-0.1.4
./configure && sudo make install
cd ..

#get back to home root
cd ..

#download nut from dev repo
git clone git://github.com/networkupstools/nut.git
cd nut

# Run autogen
./autogen.sh

#create some groups and directories and mod some persmissions sudo groupadd nut
sudo usermod -a -G nut pi sudo usermod -a -G nut root sudo mkdir /var/run/nut
sudo chown root:nut /var/run/nut sudo mkdir -p /var/state/ups sudo chown
root:nut /var/state/ups sudo chmod 0770 /var/state/ups

#now we ./configure and make it
./configure --without-doc --with-drivers=tripplite_usb,upsdrvctl

#still tries to build docs, even though I said NO to docs cp Makefile
Makefile.orig sed -i 's/include common clients conf data tools docs
drivers/include common clients conf data tools drivers/' Makefile

make
sudo make install
Steve Ballantyne
Network Engineer
MCSE/MCDST; Novell CLA; LPIC-1; CTT+; A+; Network+; Linux+; Server+;
I-Net+; Security+; SonicWALL CSSA



On Thu, Jul 24, 2014 at 12:07 PM,  <pererivers at yahoo.es>
wrote:> Dear Charles,
>
> Thanks for your quick reply, but I can't install nut_2.7.2 in my
raspberry.
>
> 1) I create a [nut] directory and use wget to download three files:
> [nut_2.7.2-1.dsc] [nut_2.7.2.orig.tar.gz] [nut_2.7.2-1.debian.tar.xz] 
> 2)I
> unpack:
> dpkg-source -x nut_2.7.2-1.dsc
> 3) I use command
>   root at pi1:/nut/nut-2.7.2# debuild -us -uc .
> ..
> And I have the following error code:
> ---------------------------------------------
> root at pi1:/nut/nut-2.7.2# debuild -us -uc -d  dpkg-buildpackage 
> -rfakeroot -d -us -uc
> dpkg-buildpackage: aviso: est? usando una orden para convertirse en 
> administrador (?gain-root-command?), a pesar de que ya es el 
> administrador
> dpkg-buildpackage: paquete fuente nut
> dpkg-buildpackage: versi?n de las fuentes 2.7.2-1
> dpkg-buildpackage: fuentes modificadas por Laurent Bigonville 
> <bigon at debian.org>  dpkg-source --before-build nut-2.7.2
> dpkg-buildpackage: arquitectura del sistema armhf  fakeroot 
> debian/rules clean
> debian/rules:3: /usr/share/cdbs/1/rules/debhelper.mk: No existe el 
> fichero o el directorio
> debian/rules:4: /usr/share/cdbs/1/class/autotools.mk: No existe el 
> fichero o el directorio
> debian/rules:5: /usr/share/cdbs/1/class/python-module.mk: No existe el 
> fichero o el directorio
> debian/rules:7: /usr/share/cdbs/1/rules/autoreconf.mk: No existe el 
> fichero o el directorio
> debian/rules:15: /usr/share/cdbs/1/rules/utils.mk: No existe el 
> fichero o el directorio
> make: *** No hay ninguna regla para construir el objetivo 
> `/usr/share/cdbs/1/rules/utils.mk'.  Alto.
> dpkg-buildpackage: fallo: fakeroot debian/rules clean devolvi? un 
> estado de salida de error 2
> debuild: fatal error at line 1357:
> dpkg-buildpackage -rfakeroot -d -us -uc failed 
> root at pi1:/nut/nut-2.7.2#
> ----------------------------------------------------------
>
> Any idea? what am I doing wrong.
> I don't have installed 'apt-src' command to install
dependencies.
>
> Best regards,
> Pere Rius
>
>
>
> -----Mensaje original-----
> De: Charles Lepple [mailto:clepple at gmail.com] Enviado el: jueves, 17 
> de julio de 2014 14:41
> Para: pere at riusnebot.com
> CC: NUT List
> Asunto: Re: About your driver NUTDRV_ATCL_USB(8) for install
>
> On Jul 13, 2014, at 9:46 AM, pere at riusnebot.com wrote:
>
>> Dear Charles Lepple,
>> Sorry for my email intrusion.
>
> for next time:
>
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
>
>> I have an UPS called Ovislink 1000VA and it use a UPSMART2000R (with 
>> ?ATCL
> FOR UPS?).
>> I?m a beginner Linux user and I ?will install your new driver
> <nutdrv_atcl_usb > to work with networkupstools.org, but  I can?t.
>>
>> We have a raspberry pi with debian, and  I only installed a ?nut? 
>> with
> version:
>>
>> ii  nut            2.6.4-2.3+de all          network UPS tools -
> metapackage
>> ii  nut-client     2.6.4-2.3+de armhf        network UPS tools -
clients
>> ii  nut-server     2.6.4-2.3+de armhf        network UPS tools - core
> system
>>
>> ? But it not contain your NUTDRV_ATCL_USB to put in my ups.conf file 
>> configuration
>>
>> Could you help me how we can use your new driver ATCL FOR UPS? I 
>> don?t
> know how install unstable 2.7.2-1 version in RaspBerry that I think 
> that contents this new driver.
>
> There are a few options, depending on whether you prefer packages, or 
> if you need to install this quickly.
>
> One way might be to request a backport. I have no experience with this 
> particular group, but you could try requesting here:
> http://sourceforge.net/p/raspbian-backports/suggestions/
>
> Another way is to download the Debian source files for 2.7.2-1 from 
> https://packages.debian.org/sid/nut (three links under "Download 
> Source Package" in the right sidebar) and use 'debuild -us
-uc' from
> the devscripts package.
>
> Since I needed to build from the latest code, I used 'apt-src' to 
> install the build dependencies. Note that this will require a fair 
> amount of free space on your SD card (I am using a 4GB card with 
> Raspbian). In /etc/apt/sources.list, copy the first line, and change
'deb' to 'deb-src'
> like so:
>
> deb http://mirrordirector.raspbian.org/raspbian/ wheezy main contrib 
> non-free rpi deb-src http://mirrordirector.raspbian.org/raspbian/ 
> wheezy main contrib non-free rpi
>
> Then run 'sudo apt-src install nut'. This downloads the packages 
> needed to build NUT 2.6.4, but then you would want to grab the newer 
> NUT 2.7.2 package. You may also want to remove the nut* .deb binary 
> packages to avoid confusion.
>
> Unpack nut-2.7.2.tar.gz, and follow the installation instructions here:
> http://www.networkupstools.org/docs/user-manual.chunked/ar01s05.html
>
> If you need help, please subscribe to the nut-upsuser list and 
> describe the problem there.
>
> --
> Charles Lepple
> clepple at gmail
>
>
>
>
> ---
> Aquest correu electr?nic est? lliure de virus perqu? la protecci? de
l'avast! Antivirus est? habilitada.
> http://www.avast.com
>
>
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Charles Lepple

2015-Feb-09 13:56 UTC

head link

[Nut-upsuser] About your driver NUTDRV_ATCL_USB(8) for install

On Feb 9, 2015, at 6:48 AM, PERE (yahoo.es) <pererivers at yahoo.es>
wrote:
>   0.028188     Can't set USB configuration: could not set config 1:
Device or resource busy
>   0.029246     detached kernel driver from USB device...
>   0.030559     USB device [0001:0000] opened
>   0.866216     read: (8 bytes) => 03 00 00 00 00 00 00 00
>   0.866413     reply[0] = 0x03 -> OL
>   0.867461     dstate_init: sock /var/state/ups/nutdrv_atcl_usb-ups open on
fd 5
>   1.914346     read: (8 bytes) => 03 00 00 00 00 00 00 00
>   1.915850     reply[0] = 0x03 -> OL
>   5.872047     status interrupt read: error submitting URB: Device or
resource busy
"Device or resource busy" usually means that another kernel driver or
userspace program is accessing the same device. Check for another copy of
nutdrv_atcl_usb.

Which Raspberry Pi distribution are you using, and what is the kernel version?

-- 
Charles Lepple
clepple at gmail

Possibly Parallel Threads

Search for more apparently analagous threads

Nut upsuser - Feb 2015 - About your driver NUTDRV_ATCL_USB(8) for install

[Nut-upsuser] RV: About your driver NUTDRV_ATCL_USB(8) for install

[Nut-upsuser] About your driver NUTDRV_ATCL_USB(8) for install

[Nut-upsuser] RV: About your driver NUTDRV_ATCL_USB(8) for install

[Nut-upsuser] About your driver NUTDRV_ATCL_USB(8) for install

Possibly Parallel Threads