On 2023-06-01 13:59, Paul Neuwirth via openSUSE Users wrote:
On Thursday 2023-06-01 13:33, Andrei Borzenkov wrote:
Date: Thu, 1 Jun 2023 13:33:42 From: Andrei Borzenkov <arvidjaar@gmail.com> To: oS-EN <users@lists.opensuse.org> Subject: Re: Leap 15.2+ ipmievd times out on start
On Thu, Jun 1, 2023 at 2:12 PM Paul Neuwirth via openSUSE Users <users@lists.opensuse.org> wrote:
as I would have expected: # ls -l /run/ipmievd.pid ls: cannot access '/run/ipmievd.pid': No such file or directory
So run it manually, see what it does, whether there are any errors, use options to increase verbose/debug, run it under strace ... or wait for someone intimately familiar with this specific program.
Service startup fails because systemd does not see the PID file. You need to debug why this file is not created.
This came to my mind just a few moments earlier ;-) running it manually works fine. It seems systemd times out, only because of the missing pid file, as process is running, until the timeout. a pid file named /run/ipmievd.pid0 is being created. I then deleted the config file and re-installed ipmitool. config file kept the same.
running with -vv I get following line: ipmievd: using pidfile /run/ipmievd.pid0 no matter how much I increase verbosity, nothing is displayed, why the pidfile is named that way, although pidfile is set in the arguments explicitely: ipmievd -vv sel daemon pidfile=/run/ipmievd.pid
manual says pidfile=<filename> Save process ID to this file when in daemon mode. Defaults to /run/ipmievd.pidN (where N is the ipmi device number -- defaults to 0).
so the argument is not used at all. I can set it to whatever, file keeps to be /run/ipmievd.pid0
appears to be a bug in ipmitool ?
The manual says that it will use /run/ipmievd.pid0, it is doing what it says. It wants a number. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)