* Per Jessen [04-27-15 03:52]:

Patrick Shanahan wrote:

...

openSUSE Tumbleweed 20150425 3.19.4-1-desktop

The last three or four days my apc ups unit displays network error and asking systemctl reveals it has failed to start, "Unable to create UPS lock file.". But I find no lock file under /run, /var/run or /var/spool. wtf ??

The default location is /var/lock.

Sorry, I had also looked there and it is not there either. tks, Still the problem?? -- (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

* Per Jessen [04-27-15 11:37]:

Patrick Shanahan wrote:

...

* Per Jessen [04-27-15 03:52]:

...

Patrick Shanahan wrote:

...

openSUSE Tumbleweed 20150425 3.19.4-1-desktop

The last three or four days my apc ups unit displays network error and asking systemctl reveals it has failed to start, "Unable to create UPS lock file.". But I find no lock file under /run, /var/run or /var/spool. wtf ??

The default location is /var/lock.

Sorry, I had also looked there and it is not there either. tks,

Still the problem??

Hmm, weird - I'm not bleeding edge, so I can't compare. It sounds like a permission problem? Or is a 2nd apcupsd already running?

I have just discovered that I have the same problem with plymouth-start, postfix and privoxy. And no idea why. ● plymouth-start.service - Show Plymouth Boot Screen Loaded: loaded (/usr/lib/systemd/system/plymouth-start.service; disabled; vendor preset: disabled) Active: failed (Result: signal) since Mon 2015-04-27 18:53:32 EDT; 23min ago Main PID: 429 (code=killed, signal=SEGV) Apr 27 18:53:04 crash systemd[1]: Starting Show Plymouth Boot Screen... Apr 27 18:53:04 crash systemd[1]: Started Show Plymouth Boot Screen. Apr 27 18:53:32 Crash systemd[1]: plymouth-start.service: main process exited, code=killed, status=11/SEGV Apr 27 18:53:32 Crash systemd[1]: Unit plymouth-start.service entered failed state. Apr 27 18:53:32 Crash systemd[1]: plymouth-start.service failed. ● postfix.service - Postfix Mail Transport Agent Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2015-04-27 19:07:36 EDT; 9min ago Process: 2166 ExecStart=/usr/sbin/postfix start (code=exited, status=1/FAILURE) Process: 2163 ExecStartPre=/etc/postfix/system/update_postmaps (code=exited, status=0/SUCCESS) Process: 2160 ExecStartPre=/etc/postfix/system/update_chroot (code=exited, status=0/SUCCESS) Process: 2157 ExecStartPre=/etc/postfix/system/config_postfix (code=exited, status=0/SUCCESS) Process: 2154 ExecStartPre=/bin/echo Starting mail service (Postfix) (code=exited, status=0/SUCCESS) Apr 27 19:07:35 Crash systemd[1]: Starting Postfix Mail Transport Agent... Apr 27 19:07:35 Crash echo[2154]: Starting mail service (Postfix) Apr 27 19:07:35 Crash postfix/postsuper[2201]: fatal: scan_dir_push: open directory defer: Permission denied Apr 27 19:07:35 Crash postfix[2166]: postsuper: fatal: scan_dir_push: open directory defer: Permission denied Apr 27 19:07:36 Crash systemd[1]: postfix.service: control process exited, code=exited status=1 Apr 27 19:07:36 Crash systemd[1]: Failed to start Postfix Mail Transport Agent. Apr 27 19:07:36 Crash systemd[1]: Unit postfix.service entered failed state. Apr 27 19:07:36 Crash systemd[1]: postfix.service failed. ● privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities Loaded: loaded (/usr/lib/systemd/system/privoxy.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2015-04-27 18:53:31 EDT; 23min ago Process: 1497 ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config (code=exited, status=1/FAILURE) Process: 1486 ExecStartPre=/usr/bin/cp -upf /lib64/libresolv.so.2 /lib64/libnss_dns.so.2 /var/lib/privoxy/lib64/ (code=exited, status=0/SUCCESS) Process: 1469 ExecStartPre=/usr/bin/cp -upf /etc/resolv.conf /etc/host.conf /etc/hosts /etc/localtime /var/lib/privoxy/etc/ (code=exited, status=0/SUCCESS) Apr 27 18:53:30 Crash systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... Apr 27 18:53:31 Crash systemd[1]: privoxy.service: control process exited, code=exited status=1 Apr 27 18:53:31 Crash systemd[1]: Failed to start Privoxy Web Proxy With Advanced Filtering Capabilities. Apr 27 18:53:31 Crash systemd[1]: Unit privoxy.service entered failed state. Apr 27 18:53:31 Crash systemd[1]: privoxy.service failed. And journalctl -xe offeres only confirmation that the services failed or I cannot understand them. ??? -- (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

* Per Jessen [04-28-15 02:08]:

Patrick Shanahan wrote:

...

* Per Jessen [04-27-15 11:37]:

...

Patrick Shanahan wrote:

...

* Per Jessen [04-27-15 03:52]:

...

Patrick Shanahan wrote:

...

openSUSE Tumbleweed 20150425 3.19.4-1-desktop

The last three or four days my apc ups unit displays network error and asking systemctl reveals it has failed to start, "Unable to create UPS lock file.". But I find no lock file under /run, /var/run or /var/spool. wtf ??

The default location is /var/lock.

Sorry, I had also looked there and it is not there either. tks,

Still the problem??

Hmm, weird - I'm not bleeding edge, so I can't compare. It sounds like a permission problem? Or is a 2nd apcupsd already running?

I have just discovered that I have the same problem with plymouth-start, postfix and privoxy. And no idea why.

It seems to be quite clearly about permissions - is there apparmor in the mix?

If memory serves, yes, but reports inactive (dead). Starting apparmor is successful but errant services still will not successfully start :^( The last boot also had different backgrounds and rearranged items (kde) from normal and now has a common background between all six screens where they were different previous. tks, ?? note: this is the box which reported full fill system and magically recovered 30% of subject space while being powered off overnight. -- (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

* Carlos E. R. [04-28-15 10:37]:

On 2015-04-28 13:29, Patrick Shanahan wrote:

...

* Per Jessen <> [04-28-15 02:08]:

...

...

It seems to be quite clearly about permissions - is there apparmor in the mix?

If memory serves, yes, but reports inactive (dead). Starting apparmor is successful but errant services still will not successfully start :^(

Well, obviously the idea is that you stop apparmor and retry. The job of AA is prohibiting things from running.

Well, some progress. After stopping apparmor, plymouth-start is successfully started, but that service other that showing success in starting is of little help :^|. privoxy, apcupsd and postfix still fail. ps> apparmour was not running when I started this thread and was not considered as causing the problem. tks, -- (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

* Per Jessen [04-29-15 02:11]:

Patrick Shanahan wrote:

...

* Carlos E. R. [04-28-15 10:37]:

...

On 2015-04-28 13:29, Patrick Shanahan wrote:

...

* Per Jessen <> [04-28-15 02:08]:

...

...

It seems to be quite clearly about permissions - is there apparmor in the mix?

If memory serves, yes, but reports inactive (dead). Starting apparmor is successful but errant services still will not successfully start :^(

Well, obviously the idea is that you stop apparmor and retry. The job of AA is prohibiting things from running.

Well, some progress. After stopping apparmor, plymouth-start is successfully started, but that service other that showing success in starting is of little help :^|. privoxy, apcupsd and postfix still fail.

ps> apparmour was not running when I started this thread and was not considered as causing the problem.

I still think it could be useful to see an strace of the apcupsd startup.

strace -oapcupsd.trc /usr/sbin/apcupsd -b -f /etc/apcupsd/apcupsd.conf

Output is: http://wahoo.no-ip.org/~pat/apcupsd.trc.txt

Is your /var a separate filesystem? Both the apcupsd and postfix problems seem to be /var related.

No, part of the btrfs / (root) install. I would prefer it and /tmp were separate filesystems. They do seem to be related, lock file, but asound.state.lock is successfully created. tks, -- (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

* Per Jessen [04-29-15 09:57]:

Patrick Shanahan wrote:

...

* Per Jessen [04-29-15 02:11]:

...

I still think it could be useful to see an strace of the apcupsd startup.

strace -oapcupsd.trc /usr/sbin/apcupsd -b -f /etc/apcupsd/apcupsd.conf

Output is: http://wahoo.no-ip.org/~pat/apcupsd.trc.txt

Hmm, less interesting than I'd hoped - I don't see anything trying to access /var/lock/ at all.

Do you have anything in /var/log/apcupsd.events ?

repeated on each startup attempt: 2015-04-29 07:15:20 -0400 Lock file data error: ^CP 2015-04-29 07:15:20 -0400 apcupsd FATAL ERROR in apcupsd.c at line 224 Unable to create UPS lock file. If apcupsd or apctest is already running, please stop it and run this program again. 2015-04-29 07:15:20 -0400 Lock file data error: <F7>D<CE><FF>^? 2015-04-29 07:15:20 -0400 apcupsd error shutdown completed and no other entries :^( tks, -- (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

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. -- Per Jessen, Zürich (12.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

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? -- Per Jessen, Zürich (9.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* 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 solves the problem. I will file a bug report, tks much Bugzilla – Bug 929444 Submitted https://bugzilla.opensuse.org/show_bug.cgi?id=929444 -- (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

* 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

* Carlos E. R. [04-29-15 16:03]:

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.

Not one that I am able to find :^( -- (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

* David C. Rankin [05-01-15 20:55]:

On 04/28/2015 03:37 PM, Patrick Shanahan wrote:

...

Well, some progress. After stopping apparmor, plymouth-start is successfully started, but that service other that showing success in starting is of little help :^|. privoxy, apcupsd and postfix still fail.

ps> apparmour was not running when I started this thread and was not considered as causing the problem.

tks,

I suspect postfix may be the result of daemon_directory change and an older config file?:

#daemon_directory = /usr/lib/postfix daemon_directory = /usr/lib/postfix/bin

This got me a while ago...

As to the rest? Don't know

I have daemon_directory = /usr/lib/postfix there is no /usr/lib/postfix/bin tks, -- (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

David C. Rankin wrote:

On 04/28/2015 03:37 PM, Patrick Shanahan wrote:

...

Well, some progress. After stopping apparmor, plymouth-start is successfully started, but that service other that showing success in starting is of little help :^|. privoxy, apcupsd and postfix still fail.

ps> apparmour was not running when I started this thread and was not considered as causing the problem.

tks,

I suspect postfix may be the result of daemon_directory change and an older config file?:

#daemon_directory = /usr/lib/postfix daemon_directory = /usr/lib/postfix/bin

The postfix messages complained about 'defer' which is in /var/spool/postfix/ (by default). -- Per Jessen, Zürich (13.3°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Patrick Shanahan wrote:

* Per Jessen [04-27-15 03:52]:

...

Patrick Shanahan wrote:

...

openSUSE Tumbleweed 20150425 3.19.4-1-desktop

The last three or four days my apc ups unit displays network error and asking systemctl reveals it has failed to start, "Unable to create UPS lock file.". But I find no lock file under /run, /var/run or /var/spool. wtf ??

The default location is /var/lock.

Sorry, I had also looked there and it is not there either. tks,

Still the problem??

You could try running apcupsd from the console, maybe with strace, to see what really happens. -- Per Jessen, Zürich (20.7°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Carlos E. R. [04-27-15 19:58]:

On 2015-04-27 05:49, Patrick Shanahan wrote:

...

openSUSE Tumbleweed

You know that TW questions should be asked in the factory mail list? :-)

Certainly, but do not believe the problem is confined to Tw. -- (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