Some processes do not start in multi-user mode. 2

[protos78]

Hi all,

Here is the issue:

Few days ago, the server did not respond to a ssh request from a user at night. A user tried to check what went wrong with computer and tried to login from terminal next morning. As the computer was unresponsive, he somehow decided to boot it by turning the power off. To make the story short, the server rebooted; however, he can't login to his account. Actually, the server could not start some processes; but was able to ask user to enter his account username. Even though, he enters the correct username and password, server does not accept the request. I also could not login as root.

I just checked the server logs by booting it in single user mode. Here are some interesting lines:

Before the reboot:
irqbalance : can't balance irqs on a uniprocessor system: failed

After the reboot:
irqbalance : can't balance irqs on a uniprocessor system: failed
fsck:
fsck /: (this is repeated 900+ times)
sshd: failed
ntpd: failed
httpd: httpd: bad user name apache
httpd: httpd startup failed
runuser: runuser:
runuser: user htt doesnot exist
iiim: htt startup failed
cannaserver: cannaserver : -u flag spesified, but can not run as root
cannaserver:
canna: failed
atd : atd startup failed
atd : failed
dbus-daemon-1: Could not get password database information for UID of current process user "???" unknown or no memory to allocate password entry
dbus-daemon-1: Unknown username "haldaemon" in message bus configuration file
dbus-daemon-1: Unknown username "root" in message bus configuration file


This might be something related with shadow file.
Here is part of /etc/shadow

root:$1$blah_blah_blah:14274:0:99999:7:::
bin:*:12761:0:99999:7:::
sshd:!!:12761:0:99999:7:::

I have to solve this issue as soon as possible. Any idea/help is appreciated.

 

[Kozusnik]

I've had issues also with the power being cut. Have you tried performing a normal reboot or is it possible?

Mark

 

[Annihilannic]

Those /etc/shadow entries look fine... anything wrong with /etc/passwd?

Annihilannic.

 

[protos78]

Thank you for your comments.

It turns out to be a bad sector issue and fsck could not solve it. I had to format the hard drive.