[systemd-devel] Intermittent failure of user@<uid>.service

Hemanth Kumar hemanthkumar.t at vakilsearch.com
Sat Aug 11 16:31:15 UTC 2018


Some time disk may be full.
Please check the disk once

Regards,
Hemanth
System Admin
+91 9962614999
*Legal* *is now* *Simple*
India's No.1 Professional Service <http://www.vakilsearch.com/> is on
Facebook <http://www.facebook.com/pages/Vakil-Search/132311446825878> I
*Twitter* I LinkedIn <http://www.linkedin.com/in/datar> I YouTube!
<http://www.youtube.com/user/legalsolutionsvakil?feature=watch>
----------------------------------------------------------
*All e-mails sent are privileged information, and not meant to be shared
without the permission of the sender*

On Sat, Aug 11, 2018 at 8:13 PM, Ryan Gonzalez <rymg19 at gmail.com> wrote:

> Most likely, the permissions of *something* are messed up... It looks
> like, in particular, the systemd user instance isn't starting.
>
> What does 'systemd --user status' say?
>
>
> On Fri, Aug 10, 2018, 11:01 PM Johannes Ernst <johannes.ernst at gmail.com>
> wrote:
>
>> This is Arch. I boot the system, and ssh in as user “shepherd”. Something
>> goes wrong, but from the log (below) I cannot tell what it is. I do get a
>> shell and everything seems to work fine. If I terminate ssh and re-log in,
>> everything is fine.
>>
>> This happens often enough I’m wondering … ideas?
>>
>> Cheers,
>>
>>
>> Johannes.
>>
>>
>> Aug 11 03:52:38 ubosbox sshd[1263]: Accepted publickey for shepherd from
>> 192.168.138.43 port 55537 ssh2: RSA SHA256:XCCJJyl2rx5wgyP0Blqm3qW2s6ImZG
>> PZA9fI4ofOe+8
>> Aug 11 03:52:38 ubosbox sshd[1263]: pam_unix(sshd:session): session
>> opened for user shepherd by (uid=0)
>> Aug 11 03:52:38 ubosbox systemd[1]: Created slice User Slice of UID 979.
>> Aug 11 03:52:38 ubosbox systemd[1266]: pam_unix(systemd-user:session):
>> session opened for user shepherd by (uid=0)
>> Aug 11 03:52:38 ubosbox systemd[1]: Created slice
>> system-user\x2druntime\x2ddir.slice.
>> Aug 11 03:52:38 ubosbox systemd[1267]: pam_unix(systemd-user:session):
>> session closed for user shepherd
>> Aug 11 03:52:38 ubosbox systemd[1]: Started /run/user/979 mount wrapper.
>> Aug 11 03:52:38 ubosbox systemd[1]: Starting User Manager for UID 979...
>> Aug 11 03:52:38 ubosbox systemd-logind[345]: New session c1 of user
>> shepherd.
>> Aug 11 03:52:38 ubosbox systemd[1]: Started Session c1 of user shepherd.
>> Aug 11 03:52:38 ubosbox systemd[1266]: Failed to fully start up daemon:
>> Permission denied
>> Aug 11 03:52:38 ubosbox systemd[1]: user at 979.service: Failed with result
>> 'protocol'.
>> Aug 11 03:52:38 ubosbox systemd[1]: Failed to start User Manager for UID
>> 979.
>> Aug 11 03:52:38 ubosbox systemd[1]: user-runtime-dir at 979.service: Unit
>> not needed anymore. Stopping.
>> Aug 11 03:52:38 ubosbox sshd[1263]: pam_systemd(sshd:session): Failed to
>> create session: Start job for unit user at 979.service failed with 'failed'
>> Aug 11 03:52:38 ubosbox systemd[1]: Stopping /run/user/979 mount
>> wrapper...
>> Aug 11 03:52:38 ubosbox systemd[1]: Stopped /run/user/979 mount wrapper.
>>
>> _______________________________________________
>> systemd-devel mailing list
>> systemd-devel at lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>
> --
>
> Ryan (ライアン)
> Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else
> https://refi64.com/
>
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20180811/180210ce/attachment.html>


More information about the systemd-devel mailing list