-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lab machines: autofs daemon sometimes crashes #37
Comments
I just logged in via ssh with partial success. My id and password were accepted, but my home directory is missing. |
There is something peculiar about the network administration. The machine was configured to use wifi. Is there even a wifi device present? It is automatically connecting to the ethernet. Running this command seems to clear the problem:
But, that does not answer the question of how the autofs daemon got stopped. Maybe wifi snafu confused it. |
All desktops have a wireless interface, but it is not typically used. I /var/log should contain some entries for when the autofs daemon stopped On Wed, Oct 21, 2015 at 1:20 PM, jack-oquin [email protected]
|
I don't know. The only visible problem was that it tried and failed to connect via wifi. Maybe that had nothing to do with the autofs problem. |
As it seems to work again, I am closing this issue. Please re-open if it recurs. |
This same issue happened this week on kif. The solution was the same; log in to tty and restart autofs |
I was afraid that might happen. Perhaps there is some way to automatically respawn the daemon. |
We had a similar problem with Ubuntu 16.04 on nibbler yesterday, and @rdelfin ended up reinstalling it. |
Zapp.csres is not online. The user bwilab is able to log in, but no other users due to the lack of communication with the LDAP server
The text was updated successfully, but these errors were encountered: