Thank you for your answer. Unfortunately, I'll not be able to answer so quick, but I'll do my best.
I think I found something in /var/log/messages, this line appears 4 times: Sep 2 08:06:17 client1 kernel: [ 113.230480] afs: byte-range locks only enforced for processes on this machine (pid 2430 (zeitgeist-daemo), user 5000, fid 536870921.300.500). Sep 2 08:06:36 client1 kernel: [ 132.165684] afs: byte-range locks only enforced for processes on this machine (pid 2409 (tracker-store), user 5000, fid 536870921.660.863186). Sep 2 08:06:52 client1 kernel: [ 148.373147] afs: byte-range locks only enforced for processes on this machine (pid 2692 (localStorage DB), user 5000, fid 536870921.22438.708412). Sep 2 08:09:09 client1 kernel: [ 284.963197] afs: byte-range locks only enforced for processes on this machine (pid 2692 (localStorage DB), user 5000, fid 536870921.22438.708412). And I have to correct myself: the whole rebooting process takes 2 or 3 minutes, according to this line: Sep 2 08:09:25 client1 rsyslogd: [origin software="rsyslogd" swVersion="8.4.0" x-pid="759" x-info="http://www.rsyslog.com";] exiting on signal 15. Sep 2 08:11:47 client1 rsyslogd: [origin software="rsyslogd" swVersion="8.4.0" x-pid="759" x-info="http://www.rsyslog.com";] start Anyway, shutting down the machine takes still too long... May I copy a bigger part of /var/log/messages? István 2014. 09. 1, hétfő keltezéssel 00.42-kor Benjamin Kaduk ezt írta: > On Sun, 31 Aug 2014, Kuklin István wrote: > > > There is a network with central LDAP+Kerberos+AFS users. > > If a central user tries to access an afs share, shutting down the client > > is going to take about 3 minutes. It can be done using PAM modules, or > > with a local (non-central) user using kinit <ldap+krb5-username>, then > > aklog commands. > > If user logs out correctly using unlog and kdestroy, it doesn't solve > > the problem, shutting down is going to take about 3 minutes. > > If I stop openafs-client service and umount /afs before shutdown, it > > doesn't help. > > It affects rebooting as well. > > It seems that the system is trying to stop some "User Manager job" at > > shutdown as far as I remember. > > This problem affects Debian Jessie, shutdown was quite quick on Wheezy. > > It affects all the client machines. > > I'm writing this report from a client machine. > > The kernel messages during the hang (ideally with timestamps) would be > quite helpful for understanding what's going on here. > > I'll have to double-check, but I may only have wheezy and sid machines > sitting around. I would expect any issues to also be present on sid, but > one never knows... > > -Ben
signature.asc
Description: This is a digitally signed message part
