[Bug 1318168] Re: su: Failed to create session: No such file or directory

2021-06-30 Thread Dan Streetman
** Changed in: systemd (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318168

Title:
  su: Failed to create session: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1318168/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1318168] Re: su: Failed to create session: No such file or directory

2016-10-19 Thread Philipp Huebner
** Package changed: ejabberd (Ubuntu) => systemd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318168

Title:
  su: Failed to create session: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1318168/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1318168] Re: su: Failed to create session: No such file or directory

2015-07-09 Thread Moses Moore
I'm getting the same superfluous errors.  Doesn't interfere with logging
in by ssh or switching user with su, but it does add noise to logwatch
or other alert systems.

This is what I tried:

# strace su munin-async -s /bin/sh -c sleep\ 2  2/tmp/strace.log
# tail /var/log/auth.log
Jul  9 16:26:45 mt su[12025]: Successful su for munin-async by root
Jul  9 16:26:45 mt su[12025]: + /dev/pts/5 root:munin-async
Jul  9 16:26:45 mt su[12025]: pam_unix(su:session): session opened for user 
munin-async by root(uid=0)
Jul  9 16:26:45 mt su[12025]: pam_systemd(su:session): Failed to create 
session: No such file or directory
Jul  9 16:26:47 mt su[12025]: pam_unix(su:session): session closed for user 
munin-async

Therefore, the last message sent to syslog with 16:26:45 should be
immediately after the problem.  This is what I found:

socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC, 0) = 4
connect(4, {sa_family=AF_LOCAL, sun_path=/var/run/dbus/system_bus_socket}, 
33) = 0
fcntl(4, F_GETFL)   = 0x2 (flags O_RDWR)
fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK)= 0
geteuid()   = 0
getsockname(4, {sa_family=AF_LOCAL, NULL}, [2]) = 0
poll([{fd=4, events=POLLOUT}], 1, 0)= 1 ([{fd=4, revents=POLLOUT}])
sendto(4, \0, 1, MSG_NOSIGNAL, NULL, 0) = 1
sendto(4, AUTH EXTERNAL 30\r\n, 18, MSG_NOSIGNAL, NULL, 0) = 18
poll([{fd=4, events=POLLIN}], 1, 4294967295) = 1 ([{fd=4, revents=POLLIN}])
read(4, OK b48a6f42e045c3b9b9a4d61153bd3..., 2048) = 37
poll([{fd=4, events=POLLOUT}], 1, 4294967295) = 1 ([{fd=4, revents=POLLOUT}])
sendto(4, NEGOTIATE_UNIX_FD\r\n, 19, MSG_NOSIGNAL, NULL, 0) = 19
poll([{fd=4, events=POLLIN}], 1, 4294967295) = 1 ([{fd=4, revents=POLLIN}])
read(4, AGREE_UNIX_FD\r\n, 2048)  = 15
poll([{fd=4, events=POLLOUT}], 1, 4294967295) = 1 ([{fd=4, revents=POLLOUT}])
sendto(4, BEGIN\r\n, 7, MSG_NOSIGNAL, NULL, 0) = 7
poll([{fd=4, events=POLLIN|POLLOUT}], 1, 4294967295) = 1 ([{fd=4, 
revents=POLLOUT}])
sendmsg(4, {msg_name(0)=NULL, 
msg_iov(2)=[{l\1\0\1\0\0\0\0\1\0\0\0n\0\0\0\1\1o\0\25\0\0\0/org/fre..., 128}, 
{, 0}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 128
clock_gettime(CLOCK_MONOTONIC, {31561567, 529226967}) = 0
poll([{fd=4, events=POLLIN}], 1, 25000) = 1 ([{fd=4, revents=POLLIN}])
recvmsg(4, {msg_name(0)=NULL, 
msg_iov(1)=[{l\2\1\1\r\0\0\0\1\0\0\0E\0\0\0\6\1s\0\10\0\0\0:1.66129..., 
2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 282
recvmsg(4, 0x7fff66502390, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily 
unavailable)
sendmsg(4, {msg_name(0)=NULL, 
msg_iov(2)=[{l\1\0\1l\0\0\0\2\0\0\0\227\0\0\0\1\1o\0\27\0\0\0/org/fre..., 
168}, {r\0\0\0\371.\0\0\2\0\0\0su\0\0\3\0\0\0tty\0\4\0\0\0user..., 108}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 276
clock_gettime(CLOCK_MONOTONIC, {31561567, 529804611}) = 0
poll([{fd=4, events=POLLIN}], 1, 25000) = 1 ([{fd=4, revents=POLLIN}])
recvmsg(4, {msg_name(0)=NULL, 
msg_iov(1)=[{l\3\1\1\36\0\0\0a\377\0\0e\0\0\0\6\1s\0\10\0\0\0:1.66129..., 
2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 150
recvmsg(4, 0x7fff66502480, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily 
unavailable)
sendto(3, 83Jul  9 16:26:45 su[12025]: p..., 107, MSG_NOSIGNAL, NULL, 0) = 
107
close(4)= 0

Looks like dbus isn't responding to requests.  The mention of /org/fre
makes me think that is /org/freedesktop, but this is a headless server
so I don't know why pam_systemd is mentioning things like desktops to
dbus.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318168

Title:
  su: Failed to create session: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1318168/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1318168] Re: su: Failed to create session: No such file or directory

2015-01-20 Thread Arie Skliarouk
Same here. Ubuntu 13.10 guest on ubuntu 14.04 host worked properly
before.

After upgrading ubungu 13.10 guest (using do-release-upgrade) password-
based ssh login stopped working. The example has the same result here.

It is interesting that key-based ssh login works *and* causes the same
pam_systemd(sshd:session): Failed to create session: No such file or
directory message in /var/log/auth.log.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318168

Title:
  su: Failed to create session: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1318168/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1318168] Re: su: Failed to create session: No such file or directory

2014-06-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ejabberd (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318168

Title:
  su: Failed to create session: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1318168/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1318168] Re: su: Failed to create session: No such file or directory

2014-05-10 Thread Oliver Mueller
Maybe I should add, that this problem occurs on a LXC guest system.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318168

Title:
  su: Failed to create session: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1318168/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs