When nis server is not reachable during startup, system gets very slow and HAL fails to initialise
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nis (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
When the nis server is not reachable during start up (e.g. cable not connected, network not reachable, ...) an error with HAL (hardware abstraction layer) is raised and system gets incredibly slow.
First during boot it fails to connect to ypbind server (expected behaviour int his case).
(see first screenshot)
After that the boot process and start of gdm gets incredibly slow (two or more minutes). Login as local user is possible (although lasting several minutes, again very slow), then GNOME settings manager raises an error. (see second screenshot)
After confirming, the following error message is raised after two or more minutes:
--------------
Internal error - failed to initialize HAL!
--------------
(see third screenshot)
I assigned this bug to package 'nis' although I'm not sure if this is really a nis issue but an issue with the init process.
Error can be reproduced inside a virtual machine (e.g. virtualbox) with virtual network cable not connected.
Poor performance when the NIS server is unavailable is expected: the clients will attempt to contact the NIS server and have to time out when that fails.