Score:0

systemd out of memory log entry systemd-user:session

ne flag

I have problem finding out reason of 'Out of memory' systemd log entry. Log for particular PID looks as follows - line 2:

Sep 05 09:24:32 myServer systemd[24454]: pam_unix(systemd-user:session): session opened for user myUser by (uid=0)
Sep 05 09:24:32 myServer systemd[24454]: Out of memory.
Sep 05 09:24:32 myServer systemd[24454]: Reached target Paths.
Sep 05 09:24:32 myServer systemd[24454]: Starting D-Bus User Message Bus Socket.
Sep 05 09:24:32 myServer systemd[24454]: Listening on REST API socket for snapd user session agent.
Sep 05 09:24:32 myServer systemd[24454]: Listening on GnuPG cryptographic agent and passphrase cache.
Sep 05 09:24:32 myServer systemd[24454]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Sep 05 09:24:32 myServer systemd[24454]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Sep 05 09:24:32 myServer systemd[24454]: Listening on GnuPG network certificate management daemon.
Sep 05 09:24:32 myServer systemd[24454]: Reached target Timers.
Sep 05 09:24:32 myServer systemd[24454]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Sep 05 09:24:32 myServer systemd[24454]: Listening on D-Bus User Message Bus Socket.
Sep 05 09:24:32 myServer systemd[24454]: Reached target Sockets.
Sep 05 09:24:32 myServer systemd[24454]: Reached target Basic System.
Sep 05 09:24:32 myServer systemd[24454]: Reached target Default.
Sep 05 09:24:32 myServer systemd[24454]: Startup finished in 44ms.
Sep 05 09:24:33 myServer systemd[24454]: Stopped target Default.
Sep 05 09:24:33 myServer systemd[24454]: Stopped target Basic System.
Sep 05 09:24:33 myServer systemd[24454]: Stopped target Sockets.
Sep 05 09:24:33 myServer systemd[24454]: Closed D-Bus User Message Bus Socket.
Sep 05 09:24:33 myServer systemd[24454]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Sep 05 09:24:33 myServer systemd[24454]: Closed REST API socket for snapd user session agent.
Sep 05 09:24:33 myServer systemd[24454]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Sep 05 09:24:33 myServer systemd[24454]: Stopped target Paths.
Sep 05 09:24:33 myServer systemd[24454]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Sep 05 09:24:33 myServer systemd[24454]: Closed GnuPG network certificate management daemon.
Sep 05 09:24:33 myServer systemd[24454]: Stopped target Timers.
Sep 05 09:24:33 myServer systemd[24454]: Closed GnuPG cryptographic agent and passphrase cache.
Sep 05 09:24:33 myServer systemd[24454]: Reached target Shutdown.
Sep 05 09:24:33 myServer systemd[24454]: Starting Exit the Session...
Sep 05 09:24:33 myServer systemd[24454]: Received SIGRTMIN+24 from PID 24649 (kill).

I did not manage to find any additional information searching through logs. Server acts mainly as webserver with some (many?) docker containers. I have no additional feedback from users. It happens from time to time and have no idea how to dig into it.

Looks like some kind of session memory limit?

systemd 245 (245.4-4ubuntu3.17) Operating System: Ubuntu 20.04.4 LTS Kernel: Linux 5.15.0-48-generic

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.