Results 1 to 5 of 5

Thread: apcupsd fails to start - lock file has incorrect pid#

  1. #1
    Join Date
    Feb 2009
    Location
    Concordia, MO, USA
    Posts
    151

    Default apcupsd fails to start - lock file has incorrect pid#

    apcupsd used to work under 12.3, but not any more. I've looked at the recent threads regarding this and none of them address my issue. The version of apcupsd I'm running is 3.14.10 (13 September 2011) suse.

    My UPS is an APC Back-UPS BX1500, attached via USB, as shown in KInfoCenter. I have set /etc/apcupsd/apcupsd.conf (changes are bold) to use the following settings:
    Code:
    UPSCABLE       usb
    UPSTYPE        usb
    UPSCLASS       standalone
    UPSMODE        disable
    DEVICE
    NOLOGON        disable
    NETSERVER      on
    LOGSTATS       off
    LOCKFILE       /var/lock
    SCRIPTDIR      /etc/apcupsd
    PWRFAILDIR     /etc/apcupsd
    NOLOGINDIR     /etc
    EVENTSFILE     /var/log/apcupsd.events
    STATFILE       /var/log/apcupsd.status
    NISPORT        3551
    NISIP          0.0.0.0
    ONBATTERYDELAY    6
    BATTERYLEVEL      5
    MINUTES           3
    TIMEOUT           0
    ANNOY           300
    ANNOYDELAY       60
    KILLDELAY         0
    EVENTSFILEMAX    10
    STATTIME          0
    DATATIME          0
    When I start apcupsd with the YaST Services Manager I see the following:
    Code:
    apcupsd.service - APC UPS Power Control Daemon for Linux
       Loaded: loaded (/usr/lib/systemd/system/apcupsd.service; enabled)
       Active: failed (Result: exit-code) since Fri 2014-08-08 11:09:35 CDT; 2h 31min ago
      Process: 7997 ExecStart=/usr/sbin/apcupsd -b -f /etc/apcupsd/apcupsd.conf (code=exited, status=1/FAILURE)
      Process: 7994 ExecStartPre=/bin/rm -f /etc/apcupsd/powerfail (code=exited, status=0/SUCCESS)
     Main PID: 7997 (code=exited, status=1/FAILURE)
       CGroup: /system.slice/apcupsd.service
    
    Aug 08 11:09:35 pinto systemd[1]: Started APC UPS Power Control Daemon for Linux.
    Aug 08 11:09:35 pinto apcupsd[7997]: apcupsd FATAL ERROR in smartsetup.c at line 70
    Aug 08 11:09:35 pinto apcupsd[7997]: Cannot open UPS port : No such file or directory
    Aug 08 11:09:35 pinto apcupsd[7997]: apcupsd FATAL ERROR in smartsetup.c at line 70
                                         Cannot open UPS port : No such file or directory
    Aug 08 11:09:35 pinto apcupsd[7997]: apcupsd error shutdown completed
    Aug 08 11:09:35 pinto systemd[1]: apcupsd.service: main process exited, code=exited, status=1/FAILURE
    Aug 08 11:09:35 pinto systemd[1]: Unit apcupsd.service entered failed state.
    Aug 08 13:34:41 pinto systemd[1]: Stopped APC UPS Power Control Daemon for Linux.
    Aug 08 13:38:20 pinto systemd[1]: Stopped APC UPS Power Control Daemon for Linux.
    Aug 08 13:40:35 pinto systemd[1]: Stopped APC UPS Power Control Daemon for Linux.
    When I run gapcupsd the Active Monitors tab has no entries.

    YaST says apcupsd is reporting "Cannot open UPS port : No such file or directory"; does that mean it cannot find the USB device?

  2. #2
    Join Date
    Feb 2009
    Location
    Concordia, MO, USA
    Posts
    151

    Default Re: apcupsd fails to start - lock file has incorrect pid#

    Quote Originally Posted by jlturriff View Post
    apcupsd used to work under 12.3, but not any more. I've looked at the recent threads regarding this and none of them address my issue. The version of apcupsd I'm running is 3.14.10 (13 September 2011) suse.

    My UPS is an APC Back-UPS BX1500, attached via USB, as shown in KInfoCenter. I have set /etc/apcupsd/apcupsd.conf (changes are bold) to use the following settings:
    Code:
    UPSCABLE       usb
    UPSTYPE        usb
    UPSCLASS       standalone
    UPSMODE        disable
    DEVICE
    NOLOGON        disable
    NETSERVER      on
    LOGSTATS       off
    LOCKFILE       /var/lock
    SCRIPTDIR      /etc/apcupsd
    PWRFAILDIR     /etc/apcupsd
    NOLOGINDIR     /etc
    EVENTSFILE     /var/log/apcupsd.events
    STATFILE       /var/log/apcupsd.status
    NISPORT        3551
    NISIP          0.0.0.0
    ONBATTERYDELAY    6
    BATTERYLEVEL      5
    MINUTES           3
    TIMEOUT           0
    ANNOY           300
    ANNOYDELAY       60
    KILLDELAY         0
    EVENTSFILEMAX    10
    STATTIME          0
    DATATIME          0
    When I start apcupsd with the YaST Services Manager I see the following:
    Code:
    apcupsd.service - APC UPS Power Control Daemon for Linux
       Loaded: loaded (/usr/lib/systemd/system/apcupsd.service; enabled)
       Active: failed (Result: exit-code) since Fri 2014-08-08 11:09:35 CDT; 2h 31min ago
      Process: 7997 ExecStart=/usr/sbin/apcupsd -b -f /etc/apcupsd/apcupsd.conf (code=exited, status=1/FAILURE)
      Process: 7994 ExecStartPre=/bin/rm -f /etc/apcupsd/powerfail (code=exited, status=0/SUCCESS)
     Main PID: 7997 (code=exited, status=1/FAILURE)
       CGroup: /system.slice/apcupsd.service
    
    Aug 08 11:09:35 pinto systemd[1]: Started APC UPS Power Control Daemon for Linux.
    Aug 08 11:09:35 pinto apcupsd[7997]: apcupsd FATAL ERROR in smartsetup.c at line 70
    Aug 08 11:09:35 pinto apcupsd[7997]: Cannot open UPS port : No such file or directory
    Aug 08 11:09:35 pinto apcupsd[7997]: apcupsd FATAL ERROR in smartsetup.c at line 70
                                         Cannot open UPS port : No such file or directory
    Aug 08 11:09:35 pinto apcupsd[7997]: apcupsd error shutdown completed
    Aug 08 11:09:35 pinto systemd[1]: apcupsd.service: main process exited, code=exited, status=1/FAILURE
    Aug 08 11:09:35 pinto systemd[1]: Unit apcupsd.service entered failed state.
    Aug 08 13:34:41 pinto systemd[1]: Stopped APC UPS Power Control Daemon for Linux.
    Aug 08 13:38:20 pinto systemd[1]: Stopped APC UPS Power Control Daemon for Linux.
    Aug 08 13:40:35 pinto systemd[1]: Stopped APC UPS Power Control Daemon for Linux.
    When I run gapcupsd the Active Monitors tab has no entries.

    YaST says apcupsd is reporting "Cannot open UPS port : No such file or directory"; does that mean it cannot find the USB device?
    I was getting the message quoted in the thread title earlier, but that doesn't seem to be happening now. :-(

    I installed KRecord to do some testing, but it doesn't seem to be able to find my sound card. When I start it I get the message
    Code:
    can't open sound card: No such file or directory.
    It gives no clue as to the resource it's trying to access.

  3. #3
    Join Date
    Feb 2009
    Location
    Concordia, MO, USA
    Posts
    151

    Default Re: apcupsd fails to start - lock file has incorrect pid#

    Quote Originally Posted by jlturriff View Post
    I was getting the message quoted in the thread title earlier, but that doesn't seem to be happening now. :-(

    I installed KRecord to do some testing, but it doesn't seem to be able to find my sound card. When I start it I get the message
    Code:
    can't open sound card: No such file or directory.
    It gives no clue as to the resource it's trying to access.
    Also arecord does not capture anything (except possibly a beep; don't know where that came from):
    Code:
    $cd ~;arecord -vv sample.wav
    [1]+  Done                    krecord
    Recording WAVE 'sample.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono
    Plug PCM: Rate conversion PCM (48000, sformat=U8)
    Converter: libspeex (builtin)
    Protocol version: 10002
    Its setup is:
      stream       : CAPTURE
      access       : RW_INTERLEAVED
      format       : U8
      subformat    : STD
      channels     : 1
      rate         : 8000
      exact rate   : 8000 (8000/1)
      msbits       : 8
      buffer_size  : 2730
      period_size  : 170
      period_time  : 21333
      tstamp_mode  : NONE
      period_step  : 1
      avail_min    : 170
      period_event : 0
      start_threshold  : 1
      stop_threshold   : 2730
      silence_threshold: 0
      silence_size : 0
      boundary     : 768426686420090880
    Slave: Route conversion PCM (sformat=S32_LE)
      Transformation table:
        0 <- 0
    Its setup is:
      stream       : CAPTURE
      access       : MMAP_INTERLEAVED
      format       : U8
      subformat    : STD
      channels     : 1
      rate         : 48000
      exact rate   : 48000 (48000/1)
      msbits       : 8
      buffer_size  : 16384
      period_size  : 1024
      period_time  : 21333
      tstamp_mode  : NONE
      period_step  : 1
      avail_min    : 1024
      period_event : 0
      start_threshold  : 6
      stop_threshold   : 16384
      silence_threshold: 0
      silence_size : 0
      boundary     : 4611686018427387904
    Slave: Soft volume PCM
    Control: Digital Capture Volume
    min_dB: -30
    max_dB: 30
    resolution: 121
    Its setup is:
      stream       : CAPTURE
      access       : MMAP_INTERLEAVED
      format       : S32_LE
      subformat    : STD
      channels     : 2
      rate         : 48000
      exact rate   : 48000 (48000/1)
      msbits       : 32
      buffer_size  : 16384
      period_size  : 1024
      period_time  : 21333
      tstamp_mode  : NONE
      period_step  : 1
      avail_min    : 1024
      period_event : 0
      start_threshold  : 6
      stop_threshold   : 16384
      silence_threshold: 0
      silence_size : 0
      boundary     : 4611686018427387904
    Slave: Direct Snoop PCM
    Its setup is:
      stream       : CAPTURE
      access       : MMAP_INTERLEAVED
      format       : S32_LE
      subformat    : STD
      channels     : 2
      rate         : 48000
      exact rate   : 48000 (48000/1)
      msbits       : 32
      buffer_size  : 16384
      period_size  : 1024
      period_time  : 21333
      tstamp_mode  : NONE
      period_step  : 1
      avail_min    : 1024
      period_event : 0
      start_threshold  : 6
      stop_threshold   : 16384
      silence_threshold: 0
      silence_size : 0
      boundary     : 4611686018427387904
    Hardware PCM card 0 'HDA Intel MID' device 0 subdevice 0
    Its setup is:
      stream       : CAPTURE
      access       : MMAP_INTERLEAVED
      format       : S32_LE
      subformat    : STD
      channels     : 2
      rate         : 48000
      exact rate   : 48000 (48000/1)
      msbits       : 32
      buffer_size  : 16384
      period_size  : 1024
      period_time  : 21333
      tstamp_mode  : ENABLE
      period_step  : 1
      avail_min    : 1024
      period_event : 0
      start_threshold  : 1
      stop_threshold   : 0
      silence_threshold: 0
      silence_size : 0
      boundary     : 4611686018427387904
      appl_ptr     : 0
      hw_ptr       : 570291232
    #+                                                 | 00%
    The old Microphone Settings in OpenSuse mentions Phonon; could there be a problem with that? I see nothing relevant when I px fax | grep ph.

  4. #4
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: apcupsd fails to start - lock file has incorrect pid#

    On 2014-08-08 23:36, jlturriff wrote:

    > I was getting the message quoted in the thread title earlier, but that
    > doesn't seem to be happening now. :-(
    >
    > I installed *KRecord* to do some testing, but it doesn't seem to be able
    > to find my sound card. When I start it I get the message


    Please, no, one issue per thread. If you now don't have an issue with
    apcupsd, just say so, and the thread ends.

    If you now have an issue with sound, please open a new thread with sound
    somewhere in the title. Perhaps in the multimedia forum, perhaps in
    hardware one, perhaps here.

    --
    Cheers / Saludos,

    Carlos E. R.

    (from 13.1 x86_64 "Bottle" (Minas Tirith))

  5. #5
    Join Date
    Feb 2009
    Location
    Concordia, MO, USA
    Posts
    151

    Default Re: apcupsd fails to start - lock file has incorrect pid#

    Quote Originally Posted by robin_listas View Post
    On 2014-08-08 23:36, jlturriff wrote:

    > I was getting the message quoted in the thread title earlier, but that
    > doesn't seem to be happening now. :-(
    >
    > I installed *KRecord* to do some testing, but it doesn't seem to be able
    > to find my sound card. When I start it I get the message


    Please, no, one issue per thread. If you now don't have an issue with
    apcupsd, just say so, and the thread ends.

    If you now have an issue with sound, please open a new thread with sound
    somewhere in the title. Perhaps in the multimedia forum, perhaps in
    hardware one, perhaps here.

    --
    Cheers / Saludos,

    Carlos E. R.

    (from 13.1 x86_64 "Bottle" (Minas Tirith))

    Oops! Posted that to the wrong thread. Ignore the reference to KRecord.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •