Re: Fedora 37: openafs 1.8.9-1 not starting

Hi Berthold,

what is the selinux status on this machine: 'sestatus'
If selinux is enabled and mode is enforcing there is some additional 
work needed.

After trying to start openafs-client you could run 'ausearch -m AVC -ts 
recent' to see the recent deny messages.
Also 'sealert -l "*"' can show you more.

So if your problem is related to selinux you could change the mode to 
permissive, reboot the system and try again.
I'm currently working on a rpm package that will installs and sets up 
the SELinux policy security module for openafs.
If you are interested to test it, please let me know.

Regards,
-- 
Ralf Brunckhorst
[email protected]

On 14 Mar 2023, at 15:30, Berthold Cogel wrote:

> Am 10.03.23 um 11:09 schrieb Berthold Cogel:
>
>>
>> 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.
>>
>
> To clarify things:
>
> openafs-client is still disabled. I tried to start it manually. So 
> /usr/vice/cache is mounted at this time.
>
>
> Regards
> Berthold Cogel
>
>
>
> _______________________________________________
> OpenAFS-info mailing list
> [email protected]
> https://lists.openafs.org/mailman/listinfo/openafs-info