Open maxsvetlik opened 8 years ago
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:
sudo service autofs restart
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 believe current settings allow all users to connect through it. Do you think it needs to be disabled?
/var/log should contain some entries for when the autofs daemon stopped working.
On Wed, Oct 21, 2015 at 1:20 PM, jack-oquin notifications@github.com wrote:
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, but not via network manager, which leads me to suspect someone has been messing with the network configuration.
Running this seems to clear the problem, but does not answer the question of how the autofs daemon was stopped:
sudo service autofs restart
— Reply to this email directly or view it on GitHub https://github.com/utexas-bwi/bwi/issues/37#issuecomment-149983782.
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