You are not logged in.
Pages: 1
Hi there,
i did a fresh archlinux install and i can login as root perfectly (directly in the tty/login).
However its impossible to login as root using "su" as a user.
I already tried adding them to the wheel group, nothing changed.
Journalctl tells the following
Apr 15 02:01:50 VampPC su[2126]: pam_unix(su:auth): authentication failure; logname=vamp898 uid=1000 euid=1000 tty=pts/0 ruser=vamp898 rhost= user=root
Apr 15 02:01:52 VampPC su[2126]: FAILED SU (to root) vamp898 on /dev/pts/0
any idea?
Last edited by Vamp898 (2013-04-15 12:51:43)
Offline
Are you putting in root's password? That you tried to circumvent the problem by adding the user to wheel suggests that you're trying to use your user's password, like is the default when using sudo.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Online
Is hostname set correctly?
Offline
Hostname seems to be correct
[vamp898@VampPC vamp898]$ cat /etc/hostname
VampPC
[vamp898@VampPC vamp898]$ hostname
VampPC
I tried su with the root passwort, but sudo is a good idea.
[vamp898@VampPC vamp898]$ LANG=C sudo su
sudo: effective uid is not 0, is sudo installed setuid root?
to be honest, i never seen this error before
The root entry in the passwd file looks also fine
[vamp898@VampPC vamp898]$ cat /etc/passwd | head -n 1
root:x:0:0:root:/root:/bin/bash
This is weird...
$ chmod 4755 /usr/bin/sudo
helped that i finally can run sudo...
The same to /bin/su also helped, su now works again.
The 4 seems to set that the file is always executed as the file-owner and not by the one who executes the file.
So su is always executed as root, even if vamp898 executes su.
To bo honest, i seen this the first time..... good to learn something new
Ah and i know why this happened at all, me idiot copied the files from one partition to an other without taking care of the attributes -.- i shouldn´t do such things in the late night!
Last edited by Vamp898 (2013-04-15 10:39:37)
Offline
Interesting. I was going to ask you if you are using a file system without proper attributes, but this is also a good reason. Mark as solved?
Offline
Any chance you still have the original partition around? You may well have other problems like this that you don't know about yet.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Online
Any chance you still have the original partition around? You may well have other problems like this that you don't know about yet.
Im really sure i have other problems like this but as this is just a test-system (i have separate systems for arch stable and arch testing (for good reason
)) i dont really care that much.
Im Curious if a
$ pacman -S `pacman -Qq` --asdeps --force
would clear things up, afaik it should re-install all files with the attributes set by the package manager, or?
But anyway, except for the su problem, everything worked fine. As far as i keen see most attributes were correct, only the "special" attribut was lost... mysterious.
Last edited by Vamp898 (2013-04-15 12:51:31)
Offline
Pages: 1