Your message dated Sat, 21 Oct 2017 17:32:35 +0200 (CEST) with message-id <[email protected]> and subject line closing this bug has caused the Debian Bug report #789594, regarding apcupsd: apcaccess gives cryptic failure message to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 789594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789594 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: apcupsd Version: 3.14.12-1.1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Run apcaccess * What exactly did you do (or not do) that was effective (or ineffective)? Run apcaccess * What was the outcome of this action? Error contacting apcupsd @ :3551: No such process * What outcome did you expect instead? For it to print the output, or at least tell me what to fix apctest ran fine, as did service apcupsd start. The daemon is running and I can telnet to port 3551. This is all I see in apcupsd.events: 2015-06-22 08:14:52 -0400 apcupsd 3.14.12 (29 March 2014) debian startup succeeded What's wrong? What does the message mean? -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (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 ii libgcc1 1:5.1.1-11 ii libwrap0 7.6.q-25 Versions of packages apcupsd recommends: ii apcupsd-doc 3.14.12-1.1 Versions of packages apcupsd suggests: pn apcupsd-cgi <none> ii udev 220-7 -- Configuration Files: /etc/apcupsd/apcupsd.conf changed: UPSNAME downstairs UPSCABLE usb UPSTYPE usb DEVICE 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 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
--- End Message ---
--- Begin Message ---Version: 3.14.10-2 It seems to be that this bug has been resolved in a previous upload. So I am closing it manually. Feel free to reopen it or file a new report if you encounter the problem again. Thorsten
--- End Message ---
