Hello,
I've a problem with openafs in fedora 37.
Build and installation for openafs 1.8.9-1 works fine in fedora 35 and
37. The client fires up in fedora 35 without any problems.
In fedora 37 the client start fails.
Kernel 6.1.14-200.fc37.x86_64
systemd 251.13-5.fc37.x86_64
openafs 1.8.9-1
[root@charontmp ~]# systemctl status openafs-client
○ openafs-client.service - OpenAFS Client Service
Loaded: loaded (/usr/lib/systemd/system/openafs-client.service;
disabled; preset: disabled)
Active: inactive (dead)
Mär 10 10:18:32 charontmp systemd[1]:
/usr/lib/systemd/system/openafs-client.service:19: Unit configured to
use KillMode=none. This is unsafe, as it disables systemd's>
(Sorry... last line got truncated...)
Starting the client:
[root@charontmp ~]# systemctl start openafs-client
Job for openafs-client.service failed because the control process exited
with error code.
See "systemctl status openafs-client.service" and "journalctl -xeu
openafs-client.service" for details.
[root@charontmp ~]# systemctl status openafs-client
× openafs-client.service - OpenAFS Client Service
Loaded: loaded (/usr/lib/systemd/system/openafs-client.service;
disabled; preset: disabled)
Active: failed (Result: exit-code) since Fri 2023-03-10 10:19:56
CET; 5s ago
Process: 3920 ExecStartPre=/bin/bash -c fs sysname > /dev/null
2>/dev/null; test $? -ne 0 || (echo AFS client appears to be running --
not starting && exit 1) (cod>
Process: 3922 ExecStartPre=/bin/sed -n w/usr/vice/etc/CellServDB
/usr/vice/etc/CellServDB.local /usr/vice/etc/CellServDB.dist
(code=exited, status=0/SUCCESS)
Process: 3923 ExecStartPre=/bin/chmod 0644 /usr/vice/etc/CellServDB
(code=exited, status=0/SUCCESS)
Process: 3924 ExecStartPre=/sbin/modprobe openafs (code=exited,
status=0/SUCCESS)
Process: 3927 ExecStart=/usr/vice/etc/afsd $AFSD_ARGS (code=exited,
status=1/FAILURE)
CPU: 495ms
Mär 10 10:19:56 charontmp systemd[1]: Starting openafs-client.service -
OpenAFS Client Service...
Mär 10 10:19:56 charontmp afsd[3927]: afsd: ERROR: Cache dir check
failed (unable to stat cache base directory)
Mär 10 10:19:56 charontmp systemd[1]: openafs-client.service: Control
process exited, code=exited, status=1/FAILURE
Mär 10 10:19:56 charontmp systemd[1]: openafs-client.service: Failed
with result 'exit-code'.
Mär 10 10:19:56 charontmp systemd[1]: Failed to start
openafs-client.service - OpenAFS Client Service.
openafs-client.service:
[Unit]
Description=OpenAFS Client Service
Wants=network-online.target
After=syslog.target network-online.target dkms.service
Before=remote-fs.target
[Service]
Type=forking
RemainAfterExit=true
EnvironmentFile=/etc/sysconfig/openafs
ExecStartPre=/bin/bash -c "fs sysname > /dev/null 2>/dev/null; test $?
-ne 0 || (echo AFS client appears to be running -- not starting && exit 1)"
ExecStartPre=/bin/sed -n 'w/usr/vice/etc/CellServDB'
/usr/vice/etc/CellServDB.local /usr/vice/etc/CellServDB.dist
ExecStartPre=/bin/chmod 0644 /usr/vice/etc/CellServDB
ExecStartPre=/sbin/modprobe openafs
ExecStart=/usr/vice/etc/afsd $AFSD_ARGS
ExecStop=/bin/umount /afs
ExecStop=/usr/vice/etc/afsd -shutdown
ExecStop=/sbin/rmmod openafs
KillMode=none
[Install]
WantedBy=multi-user.target remote-fs.target
/etc/sysconfig/openafs:
# OpenAFS Client Configuration
AFSD_ARGS="-dynroot -fakestat -afsdb"
# OpenAFS Server Configuration
BOSSERVER_ARGS=
/usr/vice/etc/cacheinfo:
/afs:/usr/vice/cache:800000
And yes, the cache path exists.
After the failed start, the kernel module is loaded so I tried to run
afsd manually:
[root@charontmp ~]# /usr/vice/etc/afsd -dynroot -fakestat -afsdb
afsd: All AFS daemons started.
[root@charontmp ~]# ls -1 afs
acm-csuf.org
acm.jhu.edu
adrake.org
afs.ietfng.org
alteholz.eu
ams.cern.ch
.....
So this worked....
An almost identical configuration on fedora 35 works as designed.
I simply don't know, what to look for...
Regards,
Berthold Cogel
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
