You are not logged in.

#1 2018-07-11 09:07:52

CountZukula
Member
Registered: 2017-11-04
Posts: 26

[solved] Fresh thumbdrive install - can't log in with custom user

Hi all,

Short story, running into this error when logging in:

user@1000.service: Failed to connect stdout to the journal socket, ignoring: Permission denied
user@1000.service: Failed with result 'protocol'.
systemd[1]: Failed to start User Manager for UID 1000.
systemd[1]: user-runtime-dir@1000.service: Unit not needed anymore. Stopping.
login[509]: pam_systemd(login:session): Failed to create session: Start job for unit user@1000.service failed with 'failed'

Long story: I've just completed a basic installation using the typical steps, but this time I'm encountering something I'm unfamiliar with: I cannot log in with the user that I create myself.

The steps that I took to create the installation:
- use a flash thumbdrive, format it to BTRFS
- mount it, 'pacstrap base' to the root
- do the typical installation steps (time / locale / ...)
- set up grub
- installed sudo
- added a user with `useradd`
- visudo to give the user sudo privileges

Then I rebooted on the USB stick, which is successful. I can log in through root (set a password beforehand), but I cannot log in with my own user: journalctl logs the following error...

Jul 11 10:52:38 mnemosyne login[509]: pam_unix(login:session): session opened for user joachim by LOGIN(uid=0)
Jul 11 10:52:38 mnemosyne systemd[1]: Started /run/user/1000 mount wrapper.
Jul 11 10:52:38 mnemosyne systemd[1]: Created slice User Slice of UID 1000.
Jul 11 10:52:38 mnemosyne systemd[1]: Starting User Manager for UID 1000...
Jul 11 10:52:38 mnemosyne systemd-logind[397]: New session c10 of user joachim.
Jul 11 10:52:38 mnemosyne systemd[547]: user@1000.service: Failed to connect stdout to the journal socket, ignorin
g: Permission denied
Jul 11 10:52:38 mnemosyne systemd[1]: Started Session c10 of user joachim.
Jul 11 10:52:38 mnemosyne systemd[547]: pam_unix(systemd-user:session): session opened for user joachim by (uid=0)
Jul 11 10:52:38 mnemosyne systemd[548]: pam_unix(systemd-user:session): session closed for user joachim
Jul 11 10:52:38 mnemosyne systemd[1]: user@1000.service: Failed with result 'protocol'.
Jul 11 10:52:38 mnemosyne systemd[1]: Failed to start User Manager for UID 1000.
Jul 11 10:52:38 mnemosyne systemd[1]: user-runtime-dir@1000.service: Unit not needed anymore. Stopping.
Jul 11 10:52:38 mnemosyne login[509]: pam_systemd(login:session): Failed to create session: Start job for unit use
r@1000.service failed with 'failed'
Jul 11 10:52:38 mnemosyne login[509]: LOGIN ON tty2 BY joachim
Jul 11 10:52:38 mnemosyne systemd[1]: Stopping /run/user/1000 mount wrapper...
Jul 11 10:52:38 mnemosyne login[509]: pam_unix(login:session): session closed for user joachim
Jul 11 10:52:38 mnemosyne systemd[1]: getty@tty2.service: Service has no hold-off time (RestartSec=0), scheduling 
restart.
Jul 11 10:52:38 mnemosyne systemd[1]: getty@tty2.service: Scheduled restart job, restart counter is at 3.
Jul 11 10:52:38 mnemosyne systemd[1]: Stopped /run/user/1000 mount wrapper.
Jul 11 10:52:38 mnemosyne systemd[1]: Stopped Getty on tty2.
Jul 11 10:52:38 mnemosyne systemd-logind[397]: Session c10 logged out. Waiting for processes to exit.
Jul 11 10:52:38 mnemosyne systemd[1]: Started Getty on tty2.
Jul 11 10:52:38 mnemosyne systemd-logind[397]: Removed session c10.
Jul 11 10:52:38 mnemosyne systemd[1]: Removed slice User Slice of UID 1000.

I never had this error pop up, and the steps I took to do the installation were familiar to me. Anyone have an idea on how to get the user to function properly, I guess giving it the correct journal privileges somehow?

Last edited by CountZukula (2018-07-11 21:24:07)

Offline

#2 2018-07-11 21:23:50

CountZukula
Member
Registered: 2017-11-04
Posts: 26

Re: [solved] Fresh thumbdrive install - can't log in with custom user

Okay, solved this by finding a related post on the german forum: https://bbs.archlinux.de/viewtopic.php?id=31207

The root of the usb stick was apparently having the wrong permissions, so I did `chmod 755 /mnt/usbroot` on the mounted stick before rebooting, and then everything worked as expected.

Offline

Board footer

Powered by FluxBB