[arch-general] user management error
Readers, A previously existing /home directory was mounted into the file system during the installation process; this directory contained files in a directory 'a'. A user was created from the root user account: useradd -M -p [password] -s /bin/bash [username'a'] After reboot, the system is restarted as root because the user 'a' is stated to not exist. The command 'cat /etc/passwd' reveals a password 'x', but this is not the password that was entered. How to solve this error?
On 17.03.14 at 18:25, message wrote:
Readers,
A previously existing /home directory was mounted into the file system during the installation process; this directory contained files in a directory 'a'.
A user was created from the root user account:
useradd -M -p [password] -s /bin/bash [username'a']
After reboot, the system is restarted as root because the user 'a' is stated to not exist. The command 'cat /etc/passwd' reveals a password 'x', but this is not the password that was entered.
How to solve this error?
From passwd(5): If the password field is a lower-case “x”, then the encrypted password is actually stored in the shadow(5) file instead. So look into /etc/shadow if you are looking for the password.
Hello, /etc/passwd does not store the password, a hashed version of the password is stored in /etc/shadow If the directory isn't being mounted, can you please post the contents of /etc/fstab ? You can also check dmesg and journalctl to see if you have messages relating to the mounting of the /home/ partition On Mon, Mar 17, 2014 at 2:25 PM, message <letter@openmailbox.org> wrote:
Readers,
A previously existing /home directory was mounted into the file system during the installation process; this directory contained files in a directory 'a'.
A user was created from the root user account:
useradd -M -p [password] -s /bin/bash [username'a']
After reboot, the system is restarted as root because the user 'a' is stated to not exist. The command 'cat /etc/passwd' reveals a password 'x', but this is not the password that was entered.
How to solve this error?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 03/17/2014 02:50 PM, Gerald Stuhrberg wrote:
Hello,
/etc/passwd does not store the password, a hashed version of the password is stored in /etc/shadow
If the directory isn't being mounted, can you please post the contents of /etc/fstab ?
You can also check dmesg and journalctl to see if you have messages relating to the mounting of the /home/ partition
On Mon, Mar 17, 2014 at 2:25 PM, message <letter@openmailbox.org> wrote:
Readers,
A previously existing /home directory was mounted into the file system during the installation process; this directory contained files in a directory 'a'.
A user was created from the root user account:
useradd -M -p [password] -s /bin/bash [username'a']
After reboot, the system is restarted as root because the user 'a' is stated to not exist. The command 'cat /etc/passwd' reveals a password 'x', but this is not the password that was entered.
How to solve this error?
Salutations, What do you mean the system restarted as root? Do you mean that the system logged you in as root automatically? If that is the case, how did you enable auto login? If that is not the case, login as root and try '# su a' to login as the user and 'passwd' to change the user's password. Regards, Mark -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlMnUOMACgkQZ/Z80n6+J/awCgD/U7rp52hyj1JpAQhx08D2Xxyy XUlKFFf4hk99AtsVdWQBAJMPWcEWifNpeizP7HUgoBYpy3pc3m5JOlL+oephu6+K =GtnO -----END PGP SIGNATURE-----
On Tue, 2014-03-18 at 10:28 +0000, message wrote:
No, the system does not start as root. After many reboots, am unable to sign-in directly as normal user 'a'. Have to sign in as 'root' (command 'su' not recognised), then change to 'a' using 'su a'. Access to /home directory 'a' (/home/a) is successful.
OP, if you want to get help, at least consider not to break the thread and the subject line at the same time. Instead of explaining your issue, why don't you follow the hints others already made? And/or explain exactly what you do. Please post the output of ls -l /home cat /etc/fstab I don't understand you. "su" isn't recognised, but you su to user "a"? Regards, Ralf
PS: On Tue, 2014-03-18 at 10:28 +0000, message wrote:
No, the system does not start as root.
You can't login as user, you log in as root. There seems to be a serious language barrier between you and the Arch community. On Tue, 2014-03-18 at 10:41 +0000, Paul Gideon Dann wrote:
If that's no good, can you show us the relevant line in /etc/passwd
cat /etc/passwd However, what exactly do you do? You boot into Arch Linux, then you are asked to type "root" or "a" and after that you are asked to type the password for "root" or user "a" right? Please in detail describe what you're doing and what happens. I assume we are talking about tty, no display manager is involved?
Op 17 mrt. 2014 19:25 schreef "message" <letter@openmailbox.org> het volgende:
Readers,
A previously existing /home directory was mounted into the file system
during the installation process; this directory contained files in a directory 'a'.
A user was created from the root user account:
useradd -M -p [password] -s /bin/bash [username'a']
After reboot, the system is restarted as root because the user 'a' is
stated to not exist. The command 'cat /etc/passwd' reveals a password 'x', but this is not the password that was entered.
How to solve this error?
My first guess would be that the newly created user has no permissions on "his" homedirectory. A quick ls -l /home should reveal this. mvg, Guus
On Tuesday 18 Mar 2014 10:28:05 message wrote:
No, the system does not start as root.
After many reboots, am unable to sign-in directly as normal user 'a'. Have to sign in as 'root' (command 'su' not recognised), then change to 'a' using 'su a'. Access to /home directory 'a' (/home/a) is successful.
What do you mean by "command 'su' not recognised"? Is this a message displayed when you try to log in as "a"? Clearly 'su' does work, as you say you can use it after logging in as root.
From your root account, can you do "passwd a" and set a new password for the "a" account to see if that helps?
If that's no good, can you show us the relevant line in /etc/passwd, so we can check it looks OK? (The password isn't stored in there, as has been explained already.) Paul
On Mon, Mar 17, 2014 at 06:25:22PM +0000, message wrote:
Readers,
A previously existing /home directory was mounted into the file system during the installation process; this directory contained files in a directory 'a'.
A user was created from the root user account:
useradd -M -p [password] -s /bin/bash [username'a']
After reboot, the system is restarted as root because the user 'a' is stated to not exist. The command 'cat /etc/passwd' reveals a password 'x', but this is not the password that was entered.
How to solve this error?
Log in as `root` on your system, then 1. Since you have `/home` on a separate partition, check that it is properly mounted # mount | grep home 2. Check the ownership of a's home directory # ls -lh /home a's home directory should show up as being owned by a, with the group being a (unless you've modified /etc/login.defs, but if you have you already know what the group should be). 3. Check that the user is set up properly # su <username> That should let you become your created user. 4. Change the password for a # passwd a 5. Try to log in as a again. That's all I can think of at the moment. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus Perl is another example of filling a tiny, short-term need, and then being a real problem in the longer term. -- Alan Kay
participants (8)
-
Gerald Stuhrberg
-
Guus Snijders
-
Jakub Klinkovský
-
Magnus Therning
-
Mark Lee
-
message
-
Paul Gideon Dann
-
Ralf Mardorf