Sorry we failed to cross paths on IRC for so long; thanks for filing the bug so we can communicate.
On Mon, 24 Nov 2014, Wolfgang Scheicher wrote: > Package: openafs-client > Version: 1.6.10-2 > Severity: normal > > After upgrading openafs-client, -krb5 and -modules-dkms from 1.6.10~pre1-1 to > 1.6.10-2 the openafs-client service does not start anymore. > /afs isn't mounted > > I verifyed that the client does start again if downgraded back to > 1.6.10~pre1-1. > > Trying different options in afs.conf.client or different cache settings > didn't seem to have any effect either. It is likely to be an issue with the systemd unit file introduced with 1.6.10-1, so such config changes would probably not have any effect (though, I can think of one case where they might, if the options are such that afsd does not keep any userspace processes around and systemd thinks it has exited, since we do not yet set RemainAfterExit). > root@debian ~ # service openafs-client status > ● openafs-client.service - OpenAFS client > Loaded: loaded (/lib/systemd/system/openafs-client.service; enabled) > Active: inactive (dead) since Mon 2014-11-24 11:30:55 CET; 16min ago > Process: 1333 ExecStopPost=/sbin/rmmod $KMOD (code=exited, status=0/SUCCESS) > Process: 1328 ExecStop=/bin/umount -af -t afs (code=exited, > status=0/SUCCESS) > Process: 1062 ExecStop=/bin/umount -a -t afs (code=exited, status=0/SUCCESS) > Process: 1051 ExecStop=/usr/share/openafs/openafs-client-postcheck > (code=exited, status=0/SUCCESS) > Process: 1048 ExecStop=/bin/grep -qv ^1$ /proc/sys/kernel/modules_disabled > (code=exited, status=0/SUCCESS) > Process: 1045 ExecStartPost=/usr/bin/fs sysname $AFS_SYSNAME (code=exited, > status=0/SUCCESS) > Process: 1035 ExecStartPost=/usr/bin/fs setcrypt $AFS_SETCRYPT > (code=exited, status=0/SUCCESS) > Process: 1003 ExecStart=/sbin/afsd $AFSD_ARGS (code=exited, > status=0/SUCCESS) > Process: 988 ExecStartPre=/usr/share/openafs/openafs-client-precheck > (code=exited, status=0/SUCCESS) > > Nov 24 11:30:55 debian afsd[1003]: ADVISEADDR: Error in specifying interface > addresses:No existing IP interfaces found > Nov 24 11:30:55 debian afsd[1003]: ADVISEADDR: Error in specifying interface > addresses:No existing IP interfaces found > Nov 24 11:30:55 debian afsd[1003]: ADVISEADDR: Error in specifying interface > addresses:No existing IP interfaces found > Nov 24 11:30:55 debian afsd[1003]: ADVISEADDR: Error in specifying interface > addresses:No existing IP interfaces found > Nov 24 11:30:55 debian afsd[1003]: afsd: All AFS daemons started. > Nov 24 11:30:55 debian afsd[1003]: ADVISEADDR: Error in specifying interface > addresses:No existing IP interfaces found > Nov 24 11:30:55 debian afsd[1003]: afsd: All AFS daemons started. > Nov 24 11:30:55 debian afsd[1003]: ADVISEADDR: Error in specifying interface > addresses:No existing IP interfaces found > Nov 24 11:30:55 debian afsd[1003]: ADVISEADDR: Error in specifying interface > addresses:No existing IP interfaces found > Nov 24 11:30:55 debian fs[1045]: Usage: /usr/bin/fs sysname [-newsys <new > sysname>+] [-help] Together, these show the client starting and then stopping again right away, as if systemd has decided that it should be stopped again. Can you please provide the contents of /var/cache/openafs-client/*.env ? Also please verify that you can 'modprobe openafs' and 'rmmod openafs' successfully. -Ben Kaduk
