Package: apcupsd
Version: 3.14.12-1.1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Each time I use my USB printer, the communication with BackUps Pro650 is lost
while it is cable connected to tty with a UPSCABLE 940-0095A cable.
So I have to stop apcupsd and restart it again.
When I do not use my usb print er all goes well.

Log /var/log/apcupsd.events show:
2016-12-28 08:35:03 +0100  apcupsd 3.14.12 (29 March 2014) debian startup
succeeded
2016-12-28 12:36:59 +0100  Communications with UPS lost.
..... snip ....             Communications with UPS lost.
2016-12-28 22:57:25 +0100  Communications with UPS lost.
2016-12-28 23:03:34 +0100  apcupsd exiting, signal 15
2016-12-28 23:03:34 +0100  apcupsd shutdown succeeded


Server : Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19)
x86_64 GNU/Linux
Os : Debian GNU/Linux 8.6 (jessie)   (uptodate)

# apctest
2016-12-30 11:06:22 apctest 3.14.12 (29 March 2014) debian
Checking configuration ...
sharenet.type = Network & ShareUPS Disabled
cable.type = Custom Cable Smart
mode.type = APC Smart UPS (any)
Setting up the port ...
Doing prep_device() ...

You are using a SMART cable type, so I'm entering SMART test mode
Hello, this is the apcupsd Cable Test program.
This part of apctest is for testing Smart UPSes.
Please select the function you want to perform.

1) Query the UPS for all known values
2) Perform a Battery Runtime Calibration
3) Abort Battery Calibration
4) Monitor Battery Calibration progress
5) Program EEPROM
6) Enter TTY mode communicating with UPS
Q) Quit

Select function number: 1

I am going to run through the series of queries of the UPS
that are used in initializing apcupsd.

Simulating UPSlinkCheck ...
Wrote: Y Got: SM
Attempting to use smart_poll() ...
Sent: Y Got: SM  Good -- smart_poll() works!.

Going to ask for valid commands...
Wrote: a Got: 3.?=.')-89@ABDEFGKLMNOPQRSUVWXYZabcdefgjklmnopqrsuxyz~
Protocol version is: 3
Alert characters are: ?=
Command characters are: ^A^N^Z')-89@ABDEFGKLMNOPQRSUVWXYZabcdefgjklmnopqrsuxyz~

Now running through apcupsd get_UPS capabilities().
NA  indicates that the feature is Not Available

UPS Status: 08
Line quality: FF
Reason for last transfer to batteries: S
Self-Test Status: NO
Line Voltage: 230.4
Line Voltage Max: 233.2
Line Voltage Min: 230.4
Output Voltage: 230.4
Batt level percent: 100.0
Batt voltage: 13.77
UPS Load: 012.3
Line freq: 50.00
Runtime left: 0067
UPS Internal temp: NA
Dip switch settings: NA
Register 1: 00
Register 2: 00
Register 3: 00
Sensitivity: H
Wakeup delay: 000
Sleep delay: 020
Low transfer voltage: 208
High transfer voltage: 253
Batt charge for return: 00
Alarm status: 0
Low battery shutdown level: 02
UPS Name: UPS_IDEN
UPS Self test interval: 336
UPS manufacture date: 09/30/99
UPS serial number: NB9940151901
Date battery replaced: 09/30/99
Output voltage when on batteries: 230
Nominal battery voltage: 012
Percent humidity: NA
Ambient temperature: NA
Firmware revision: 12.4.I
Number of external batteries installed: NA
Number of bad batteries installed: NA
UPS model as defined by UPS: Back-UPS Pro 650
UPS EPROM capabilities string:
uD43127130133136uA43108110112114uI43253257261265lD43106103100097lA43092090088086lI43208204200196e44200155090oD13115oA13100oI13230s441HMLLq44202050710p443020180300600k4410TLNr443000060180300E443336168ON
OFF
The EPROM string is 205 characters long!
Hours since last self test: 010.7

That is all for now.


# apcaccess
APC      : 001,048,1102
DATE     : 2016-12-30 11:15:26 +0100
HOSTNAME : phlsys
VERSION  : 3.14.12 (29 March 2014) debian
UPSNAME  : PHLUPS
CABLE    : Custom Cable Smart
DRIVER   : APC Smart UPS (any)
UPSMODE  : Stand Alone
STARTTIME: 2016-12-30 11:15:14 +0100
MODEL    : Back-UPS Pro 650
STATUS   : ONLINE
LINEV    : 233.2 Volts
LOADPCT  : 12.3 Percent
BCHARGE  : 100.0 Percent
TIMELEFT : 69.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
MAXLINEV : 233.2 Volts
MINLINEV : 233.2 Volts
OUTPUTV  : 233.2 Volts
SENSE    : High
DWAKE    : 0 Seconds
DSHUTD   : 20 Seconds
DLOWBATT : 2 Minutes
LOTRANS  : 208.0 Volts
HITRANS  : 253.0 Volts
RETPCT   : 0.0 Percent
ALARMDEL : 5 Seconds
BATTV    : 13.8 Volts
LINEFREQ : 50.0 Hz
LASTXFER : Automatic or explicit self test
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
SELFTEST : NO
STESTI   : 336
STATFLAG : 0x05000008
REG1     : 0x00
REG2     : 0x00
REG3     : 0x00
MANDATE  : 09/30/99
SERIALNO : NB9940151901
BATTDATE : 09/30/99
NOMOUTV  : 230 Volts
NOMBATTV : 12.0 Volts
FIRMWARE : 12.4.I
END APC  : 2016-12-30 11:15:30 +0100







-- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages apcupsd depends on:
ii  libc6     2.19-18+deb8u6
ii  libgcc1   1:4.9.2-10
ii  libwrap0  7.6.q-25

Versions of packages apcupsd recommends:
ii  apcupsd-doc  3.14.12-1.1

Versions of packages apcupsd suggests:
ii  apcupsd-cgi  3.14.12-1.1
ii  udev         215-17+deb8u5

-- Configuration Files:
/etc/apcupsd/apcupsd.conf changed:
UPSNAME PHLUPS
UPSCABLE 940-0095A
UPSTYPE apcsmart
DEVICE /dev/ttyS0
LOCKFILE /var/lock
SCRIPTDIR /etc/apcupsd
PWRFAILDIR /etc/apcupsd
NOLOGINDIR /etc
ONBATTERYDELAY 6
BATTERYLEVEL 5
MINUTES 3
TIMEOUT 0
ANNOY 300
ANNOYDELAY 60
NOLOGON disable
KILLDELAY 0
NETSERVER on
NISIP 127.0.0.1
NISPORT 3551
EVENTSFILE /var/log/apcupsd.events
EVENTSFILEMAX 10
UPSCLASS standalone
UPSMODE disable
STATTIME 0
STATFILE /var/log/apcupsd.status
LOGSTATS off
DATATIME 0

/etc/default/apcupsd changed:
APCACCESS=/sbin/apcaccess
ISCONFIGURED=yes


-- no debconf information

Reply via email to