Re: [opensuse] SOLVED: apcupsd lock file ??

* Per Jessen [05-02-15 07:58]:

Patrick Shanahan wrote:

...

* Per Jessen [05-02-15 03:47]:

...

Per Jessen wrote:

...

Andrei Borzenkov wrote:

...

В Wed, 29 Apr 2015 20:43:49 +0200 Per Jessen пишет:

...

Carlos E. R. wrote:

> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 2015-04-29 16:44, Patrick Shanahan wrote: > >> and no other entries :^( > > Don't know if you did, but perhaps you have an old, stale, lock > file. >

Yes, that is what the source code suggest for that error : "Lock file data error". What I don't understand is - there's an open() and a read() before the code that evaluates the read data - I don't understand why I don't see those calls in the strace.

open("/etc/apcupsd/LCK..", O_RDONLY) = 4

Huh? That can't be it, the default lock path is "/var/lock/". Well, maybe that's the issue then - the lockpath is wrong?

Patrick, could you verify the lockpath in your config? As Andrei says, it looks like apcupsd is trying to use /etc/apcupsd/ for the lockfile, which is crazy.

Indeed it does, as provided in apcupsd-3.14.13-95.5.x86_64.rpm, /etc/apcupsd/apcupsd.conf: LOCKFILE /etc/apcupsd

and changing to: LOCKFILE /var/log

/var/lock ? :-)

yes, forgive fatfinger|oldtimers|coffee|diminished capacity :^) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org