Hello,

I am new on this forum as I installed recently a FAN 1.1 distribution to deploy Nagios on my network.

This distribution is based on CentOs 5.2.

I managed to get a full working installation with Nagios and Centreon.

Then I decided to install OCS Inventory and GLPI on the same server. this worked also.

Then I joined the server to the AD domain, installing samba and winbind.

Everything worked fine.

This monday I found the server completely freezed and had no other choice than shutting it down. But when it restarted, I went into a lot of problems.

The first one I could not resolve is that I cannot log anymore on the console : I receive "Incorrect login" for all the valid users I know, even with root.

When I connect with PuTTY I can specify root and the password and I get logged. su accepts the other users.

Does anybody have any idea about it?


Here is my system-auth :
#%PAM-1.0
# This file is auto-generated.
# User changes will be destroyed the next time authconfig is run.
auth required pam_env.so
auth sufficient pam_unix.so nullok try_first_pass
auth requisite pam_succeed_if.so uid >= 500 quiet
auth sufficient pam_winbind.so use_first_pass
auth required pam_deny.so

account required pam_unix.so broken_shadow
account sufficient pam_localuser.so
account sufficient pam_succeed_if.so uid < 500 quiet
account [default=bad success=ok user_unknown=ignore] pam_winbind.so
account required pam_permit.so

password requisite pam_cracklib.so try_first_pass retry=3
password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok
password sufficient pam_winbind.so use_authtok
password required pam_deny.so

session optional pam_keyinit.so revoke
session required pam_limits.so
session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid
session required pam_unix.so
session required pam_oddjob_mkhomedir.so skel=/etc/skel/ umak=022

Thanks in advance

Does /etc/securetty contain "console", "tty0", or "ttyS0"?

Have you ruled out any full filesystems? Experience has taught me to always do a 'df' before getting carried away with the detail. I've seen a full rootfs cause these sorts of issues in the past.

Hello,

Here is the content of securetty : console appears but not tty0 :

[root@PCNagios etc]# cat securetty
console
vc/1
vc/2
vc/3
vc/4
vc/5
vc/6
vc/7
vc/8
vc/9
vc/10
vc/11
tty1
tty2
tty3
tty4
tty5
tty6
tty7
tty8
tty9
tty10
tty11

What concerns df :

[root@PCNagios etc]# df
Sys. de fich. 1K-blocs Occupé Disponible Capacité Monté sur
/dev/mapper/VolGroup00-LogVol00
18156292 4208868 13010260 25% /
/dev/hda1 101086 18136 77731 19% /boot
tmpfs 257744 0 257744 0% /dev/shm

[root@PCNagios etc]# df -h
Sys. de fich. Tail. Occ. Disp. %Occ. Monté sur
/dev/mapper/VolGroup00-LogVol00
18G 4,1G 13G 25% /
/dev/hda1 99M 18M 76M 19% /boot
tmpfs 252M 0 252M 0% /dev/shm


It does not seem to be a problem. But after the hard reboot, I got a lot of errors in the boot process because a lot of files were universally accessible and not taken into account by the applications.

I corrected it with chmod and now I do not get any one of these warnings.

Thank you for your help.

Try adding "tty0", and "ttyS0" if you are connecting via serial cable and have configured the server to output on serial.

A first class response.

I added tty0 , rebooted and got no difference. As the server is not yet in the computer room, I still use a PS2 keyboard and a screen attached to the video port and did not think that ttyS0 should be used.

Then I added ttyS0 and could log on the console.

This problem is now resolved.

I didn't think ttyS0 worked that way either, but glad you solved it.