I screwed up sudoers and I haven't root access (remote server).

[nomikos]

This is the hard way to learn when you MUST use visudo, specially in a remote server. That's right. I did something stupid like:

$ sudo vi /etc/sudoers

and now have:

$ sudo
>>> /etc/sudoers: syntax error near line 79 <<<
sudo: parse error in /etc/sudoers near line 79
sudo: no valid sudoers sources found, quitting

So what if I have locked the root account (passwd -l root) and now I can't do su to fix sudoers file???

As i said this is in a remote server (VPS) so I can not use recovering special tools via CD or similar.

thanks.-

[beyerservice]

no recovery mode or something like that?

the thing is that it supposed to be nothing that you can do if you do not have recovery terminal.

[falko]

You can boot from a recovery or live CD and try to fix the file. This should give you the idea: http://www.howtoforge.com/how-to-res...d-with-knoppix

[beyerservice]

Originally Posted by nomikos

As i said this is in a remote server (VPS) so I can not use recovering special tools via CD or similar.

Originally Posted by falko

You can boot from a recovery or live CD and try to fix the file. This should give you the idea: http://www.howtoforge.com/how-to-res...d-with-knoppix

???not really helping.

[nomikos]

Thanks for your answers.
Yes, I do not have physical access.
I am thinking in trying code some simple routine (as I have ssh access as user at least ) using something like http://www.kernel.org/doc/man-pages/...etpwent.3.html
Obviously I am not hurry and may be fun. Any idea to start?
Thanks.-

[nomikos]

What a odyssey! I was thinking in very rare things to solve this.
===
Solution:
I have webmin installed. So as the root account WAS locked, I have another webmin user with access to all modules.
Webmin > Users and Groups > root account > password: No password required
===
Can you believe it?

[beyerservice]

no. thats too much luck for you :-D

[falko]

Originally Posted by beyerservice

???not really helping.

Why? He could boot from a live system, mount his hard drive and then try to fix /etc/sudoers.