Mike Wayne
New Member
- Joined
- Jan 18, 2018
- Messages
- 18
- Reaction score
- 1
I told Ward but putting this here as a warning to others.
Fresh VM at Vultr running CentOS 7 x64
Followed the install instructions at http://nerdvittles.com/?p=23948 exactly, multiple times. After the scripts does the first reboot, there is no way to log in to the machine, even in single user mode from the console. Tried a second account using tcsh, that can not log in either so something very vital is getting corrupted. Server is online but it seems that no shell works.
There is an issue with the code that updates the nameserver. I commented out the reboot and went looking. Saw this in etc:
That ? is a <LF>. And of course resolv.conf has the original values that Vultr installed and is now immutable.
But this should not prevent logins
Fresh VM at Vultr running CentOS 7 x64
Followed the install instructions at http://nerdvittles.com/?p=23948 exactly, multiple times. After the scripts does the first reboot, there is no way to log in to the machine, even in single user mode from the console. Tried a second account using tcsh, that can not log in either so something very vital is getting corrupted. Server is online but it seems that no shell works.
There is an issue with the code that updates the nameserver. I commented out the reboot and went looking. Saw this in etc:
[root@r3 /etc]# ls -l res*
-rw-r--r--. 1 root root 65 Nov 29 00:34 resolv.conf
-rw-r--r--. 1 root root 47 Nov 29 01:51 resolv.conf? echo nameserver
-rw-r--r--. 1 root root 65 Nov 29 00:34 resolv.conf
-rw-r--r--. 1 root root 47 Nov 29 01:51 resolv.conf? echo nameserver
That ? is a <LF>. And of course resolv.conf has the original values that Vultr installed and is now immutable.
But this should not prevent logins