Skip to content
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

Open
maxsvetlik opened this issue Oct 20, 2015 · 9 comments
Open

lab machines: autofs daemon sometimes crashes #37

maxsvetlik opened this issue Oct 20, 2015 · 9 comments

Comments

@maxsvetlik
Copy link
Member

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

@jack-oquin
Copy link
Member

I just logged in via ssh with partial success. My id and password were accepted, but my home directory is missing.

@jack-oquin
Copy link
Member

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.

@piyushk
Copy link
Member

piyushk commented Oct 21, 2015

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 [email protected]
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
#37 (comment).

@jack-oquin
Copy link
Member

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.

@jack-oquin
Copy link
Member

As it seems to work again, I am closing this issue. Please re-open if it recurs.

@maxsvetlik
Copy link
Member Author

This same issue happened this week on kif. The solution was the same; log in to tty and restart autofs

@jack-oquin
Copy link
Member

I was afraid that might happen.

Perhaps there is some way to automatically respawn the daemon.

@jack-oquin jack-oquin reopened this Oct 28, 2015
@jack-oquin jack-oquin changed the title Zapp Lab Machine not able to connect to internet lab machines: autofs daemon sometimes crashes Oct 28, 2015
@jack-oquin
Copy link
Member

We had a similar problem with Ubuntu 16.04 on nibbler yesterday, and @rdelfin ended up reinstalling it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants