Hello,
I upgraded one of my servers from Leap 15.1 to 15.4 (first to 15.2, then
15.3, eventually 15.4). Since the update to 15.2 it fails to start:
# systemctl status ipmievd.service
× ipmievd.service - Ipmievd Daemon
Loaded: loaded (/usr/lib/systemd/system/ipmievd.service; enabled;
vendor preset: disabled)
Active: failed (Result: timeout) since Thu 2023-06-01 08:30:05
CEST; 40min ago
Process: 2369 ExecStart=/usr/sbin/ipmievd $IPMIEVD_OPTIONS
(code=exited, status=0/SUCCESS)
Jun 01 08:28:35 theta systemd[1]: Starting Ipmievd Daemon...
Jun 01 08:28:35 theta systemd[1]: ipmievd.service: Can't open PID file
/run/ipmievd.pid (yet?) after start: Operation not permitted
Jun 01 08:28:35 theta ipmievd[2370]: Reading sensors...
Jun 01 08:28:36 theta ipmievd[2370]: Waiting for events...
Jun 01 08:30:05 theta systemd[1]: ipmievd.service: start operation timed
out. Terminating.
Jun 01 08:30:05 theta systemd[1]: ipmievd.service: Failed with result
'timeout'.
Jun 01 08:30:05 theta systemd[1]: Failed to start Ipmievd Daemon.
# cat /etc/ipmievd
IPMIEVD_OPTIONS="sel daemon pidfile=/run/ipmievd.pid"
# zypper if ipmitool
Loading repository data...
Reading installed packages...
Information for package ipmitool:
---------------------------------
Repository : openSUSE_main
Name : ipmitool
Version : 1.8.18.238.gb7adc1d-150400.1.14
Arch : x86_64
Vendor : SUSE LLC <https://www.suse.com/>
Installed Size : 5.8 MiB
Installed : Yes
Status : up-to-date
Source package : ipmitool-1.8.18.238.gb7adc1d-150400.1.14.src
Upstream URL : https://github.com/ipmitool/ipmitool
Summary : Utility for IPMI Control
Description :
ipmitool itself runs fine.
# ipmitool sel
SEL Information
Version : 1.5 (v1.5, v2 compliant)
Entries : 5
Free Space : 8112 bytes
Percent Used : 0%
Last Add Time : 05/31/2023 11:46:21 AM CEST
Last Del Time : 08/27/2019 04:52:20 PM CEST
Overflow : false
Supported Cmds : 'Reserve'
what may the problem be?
Thanks and regards
Paul Neuwirth
Hello,
System is a Leap 15.5. I try to change the mount options of the root
device (here: /dev/sda4 mountetd on /).
I changed the options in the fstab and built the initrd via "mkinitrd".
But after a reboot, the partition is mounted like before.
Any ideas what I'm doing wrong here?
Regards
Daniel
--
Daniel Spannbauer Systemadministration
marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11
Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220
https://www.marco.de Email ds(a)marco.de
Geschäftsführer Martin Reuter, Torsten Lukas HRB 171775 Amtsgericht München
Am 31.05.23 um 10:50 schrieb Felix Miata:
> That's because it's a meaningless placeholder used to make an fstab file valid.
> Something must be in field 4 when otherwise only default options are to be used
> for that line's mount. If any valid mount option(s) is/are to be included in field
> 4, defaults in field 4 is nothing but litter. I have hundreds of fstabs here. I
> doubt any of them, except for backups of original files created by the installer,
> contain string defaults in field 4.
As far as I undestand "defaults" should use the file systems default
mount options, which are vissible via tune2fs -l
But the "defaults" here was only a desperate try to change ANYTHING on
the mounted options.....
--
Daniel Spannbauer Systemadministration
marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11
Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220
https://www.marco.de Email ds(a)marco.de
Geschäftsführer Martin Reuter, Torsten Lukas HRB 171775 Amtsgericht München
