🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:

Response:

Calculated Shard: 10 (from laksa013)

2. Crawled Status Check

Query:

curl -X POST \
  'http://laksa010.int.ahrefs:8124/' \
  -H 'Content-Type: text/plain' \
  -H 'X-ClickHouse-Database: crawler3' \
  -H 'Authorization: Basic YXBpOg==' \
  -d 'SELECT getAhrefsURLFromUnparsed(src_unparsed) AS found_url, ifNull(toUnixTimestamp(download_stamp), 0) AS crawl_time, ifNull(toUnixTimestamp(props_url_first_seen), 0) AS first_indexed_time, download_http_code AS http_code, src_unparsed AS src_unparsed, src_root_hash AS src_root_hash, history_drop_reason AS history_drop_reason, meta_title AS meta_title, meta_descriptions AS meta_descriptions, attrs_boilerpipe_text AS attrs_boilerpipe_text, attrs_markdown AS attrs_markdown, attrs_readable_markdown AS attrs_readable_markdown, meta_canonical AS meta_canonical FROM crawler3.page_info_local FINAL PREWHERE (src_root_hash, src_unparsed) IN ((getAhrefsRootHashFromUnparsed(getAhrefsUnparsedNoserviceFromURL(\'https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/\')), getAhrefsUnparsedNoserviceFromURL(\'https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/\'))) FORMAT JSONEachRow'

Response:

{"found_url":"https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/","crawl_time":1769389789,"first_indexed_time":1645220954,"http_code":200,"src_unparsed":"com,proxmox!forum,\/threads\/debian-lxc-screen-killed-out-logout.105083\/ s443","src_root_hash":"9469933952248431210","history_drop_reason":null,"meta_title":"debian lxc - screen killed out logout | Proxmox Support Forum","meta_descriptions":["So I've been struggling with this for a few hours and everything I've found online leads to huge arguments about how systemd (back in 2016?) changed a..."],"attrs_boilerpipe_text":"#1\nSo I've been struggling with this for a few hours and everything I've found online leads to huge arguments about how systemd (back in 2016?) changed a default to kill all user processes on logout. Well that sounds ok, but it kills things like screen. screen has been used for many many years, specifically for the use of keeping something running after you logout.\nThey say the systemd default is enabled but it's up to distros to pick. Well I'm using a Debian container and it appears to be disabled by default but my screen session still gets killed as soon as I logout.\nThere have been a few suggestions, none have worked. Is this specific to being in a container?\n$ systemd-run --scope --user screen\nFailed to connect to bus: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined (consider using --machine=<user>@.host --user to connect to bus of other user)\n\n$ systemd-run --scope --machine=clickwir@.host --user screen  \nExecution in user context is not supported on non-local systems.\n\n$ systemd-run --scope --machine=clickwir@.localhost --user screen  \nExecution in user context is not supported on non-local systems.\n\n$ systemd-run --scope --machine=clickwir@localhost --user screen  \nExecution in user context is not supported on non-local systems.\n\n$ systemd-run --scope --machine=clickwir@ --user ls\nExecution in user context is not supported on non-local systems.\n\n$ loginctl enable-linger    \nCould not enable linger: Connection timed out\nIt was suggested to add 'export XDG_RUNTIME_DIR=\/run\/user\/$(id -u)' to .bashrc\nWell that did result in something different, but still doesn't work.\n$ systemd-run --scope --user screen\nFailed to connect to bus: No such file or directory\nI need to have screen continue to run on logout\/disconnect. Honestly it's more the ungraceful disconnect I'm concerned with. Just because my desktop system disconnects\/dies\/locks shouldn't affect screen.\n#2\nWas talking about this with a co-worker today. To recreate, it should be this simple:\nInstall Debian bullseye container.\nWithin that container, install screen.\nRun screen.\nWithin screen, run something like 'top' that will keep running.\nCtrl+A, D to detach screen.\nLogout.\nLogin.\nRun 'screen -list'.\nGet error 'No Sockets found'\nBe sad that screen is broken.\nOr maybe it works for you?\n#3\nHas no one else tried to run screen on a container? This is still a problem. Screen is entirely broken when you logout.\n#4\ni still got the same problem, any idea?\n#5\nSadly, I haven't found a solution yet.\nIMO, systemd is overstepping it's bounds by a lot. Was meant to be an init system replacement and it's morphed into a lot more than that and is slowly replacing everything in a linux system with a systemd method\/application\/service\/way of life. And I don't really care for it.\nThis problem being a prime example. Screen is meant to be able to run after you logout and systemd is completely doing away with that and taking a stance that simply doesn't work with how users need a system to function. Especially one they've been using like this for, literally, decades.\nThat complaint out of the way, I'm considering using Devuan instead. It's a Debian fork but with without systemd. It's been around for a few years and looks like the only way to get back basic functions.\nSome more info on Devuan\nhttps:\/\/www.devuan.org\/\nhttps:\/\/www.makeuseof.com\/tag\/debian-without-systemd-devuan\/\n#6\nIs there a solution to this other than using a different fork? In my case it is impacting pm2 also, it just feels super odd to kills such a core function of how linux has worked for decades.  Everything works as normal with Ubuntu 20.04 but not 22.04 or 23.04.\n#7\nI don't know why, but reinstalling sshd fixes the problem.\nCode:\napt-get install --reinstall openssh-server\n#8\nAs it turns out,\n$ loginctl enable-linger\nCould not enable linger: Connection timed out\nThis was very close to the correct answer.\nloginctl enable-linger <USERNAME>\nis what's needed to make it work. I just tried it with root. Before enabling linger, tmux was killed on logout. After, it is left running.","attrs_markdown":"[![Proxmox Support Forum](https:\/\/forum.proxmox.com\/styles\/uix\/images\/Proxmox-logo-500px.png)](https:\/\/forum.proxmox.com\/)\n\n[![Proxmox Support Forum](https:\/\/forum.proxmox.com\/styles\/uix\/images\/Proxmox-logo-black-800.png)](https:\/\/forum.proxmox.com\/)\n\n[![Proxmox Support Forum](https:\/\/forum.proxmox.com\/styles\/uix\/images\/Proxmox-logo-500px.png)](https:\/\/forum.proxmox.com\/)\n\n[![Proxmox Support Forum](https:\/\/forum.proxmox.com\/styles\/uix\/images\/Proxmox-logo-black-800.png)](https:\/\/forum.proxmox.com\/)\n\n- [Home](https:\/\/forum.proxmox.com\/)\n- [Forums](https:\/\/forum.proxmox.com\/)\n  \n  [New posts](https:\/\/forum.proxmox.com\/whats-new\/posts\/) [Search forums](https:\/\/forum.proxmox.com\/search\/?type=post)\n- [What's new](https:\/\/forum.proxmox.com\/whats-new\/)\n  \n  [Featured content](https:\/\/forum.proxmox.com\/featured\/) [New posts](https:\/\/forum.proxmox.com\/whats-new\/posts\/) [Latest activity](https:\/\/forum.proxmox.com\/whats-new\/latest-activity)\n- [Members](https:\/\/forum.proxmox.com\/members\/)\n  \n  [Current visitors](https:\/\/forum.proxmox.com\/online\/) [New profile posts](https:\/\/forum.proxmox.com\/whats-new\/profile-posts\/) [Search profile posts](https:\/\/forum.proxmox.com\/search\/?type=profile_post)\n\n[Log in](https:\/\/forum.proxmox.com\/login\/)\n\n[Register](https:\/\/forum.proxmox.com\/register\/)\n\n[What's new](https:\/\/forum.proxmox.com\/whats-new\/ \"What's new\")\n\n- [New posts](https:\/\/forum.proxmox.com\/whats-new\/posts\/)\n- [Search forums](https:\/\/forum.proxmox.com\/search\/?type=post)\n\nMenu\n\nInstall the app\n\nInstall\n\nHow to install the app on iOS\n\nFollow along with the video below to see how to install our site as a web app on your home screen.\n\n**Note:** This feature may not be available in some browsers.\n\n# debian lxc - screen killed out logout\n- Thread starter [clickwir](https:\/\/forum.proxmox.com\/members\/clickwir.52592\/)\n- Start date\n  [Feb 17, 2022](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/)\n- Tags\n  \n  [lxc](https:\/\/forum.proxmox.com\/tags\/lxc\/)   [screen](https:\/\/forum.proxmox.com\/tags\/screen\/)   [systemd](https:\/\/forum.proxmox.com\/tags\/systemd\/)\n\n- [Home](https:\/\/forum.proxmox.com\/)\n- [Forums](https:\/\/forum.proxmox.com\/)\n- [Proxmox Virtual Environment](https:\/\/forum.proxmox.com\/#proxmox-virtual-environment.11)\n- [Proxmox VE: Installation and configuration](https:\/\/forum.proxmox.com\/forums\/proxmox-ve-installation-and-configuration.16\/)\n\nJavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.\n\nYou are using an out of date browser. It may not display this or other websites correctly.  \nYou should upgrade or use an [alternative browser](https:\/\/www.google.com\/chrome\/).\n\n[C](https:\/\/forum.proxmox.com\/members\/clickwir.52592\/)\n\n#### [clickwir](https:\/\/forum.proxmox.com\/members\/clickwir.52592\/)\n##### Member\n\nDec 21, 2017\n\n8\n\n1\n\n23\n\n- [Feb 17, 2022](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/post-452410)\n\n- [\\#1](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/post-452410)\n\nSo I've been struggling with this for a few hours and everything I've found online leads to huge arguments about how systemd (back in 2016?) changed a default to kill all user processes on logout. Well that sounds ok, but it kills things like screen. screen has been used for many many years, specifically for the use of keeping something running after you logout.   \n   \n They say the systemd default is enabled but it's up to distros to pick. Well I'm using a Debian container and it appears to be disabled by default but my screen session still gets killed as soon as I logout.  \n   \n There have been a few suggestions, none have worked. Is this specific to being in a container?\n```\n\n$ systemd-run --scope --user screen\nFailed to connect to bus: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined (consider using --machine=<user>@.host --user to connect to bus of other user)\n\n$ systemd-run --scope --machine=clickwir@.host --user screen  \nExecution in user context is not supported on non-local systems.\n\n$ systemd-run --scope --machine=clickwir@.localhost --user screen  \nExecution in user context is not supported on non-local systems.\n\n$ systemd-run --scope --machine=clickwir@localhost --user screen  \nExecution in user context is not supported on non-local systems.\n\n$ systemd-run --scope --machine=clickwir@ --user ls\nExecution in user context is not supported on non-local systems.\n\n$ loginctl enable-linger    \nCould not enable linger: Connection timed out\n```\nIt was suggested to add 'export XDG\\_RUNTIME\\_DIR=\/run\/user\/\\$(id -u)' to .bashrc  \n Well that did result in something different, but still doesn't work.\n```\n\n$ systemd-run --scope --user screen\nFailed to connect to bus: No such file or directory\n```\nI need to have screen continue to run on logout\/disconnect. Honestly it's more the ungraceful disconnect I'm concerned with. Just because my desktop system disconnects\/dies\/locks shouldn't affect screen.\n\n[C](https:\/\/forum.proxmox.com\/members\/clickwir.52592\/)\n\n#### [clickwir](https:\/\/forum.proxmox.com\/members\/clickwir.52592\/)\n##### Member\n\nDec 21, 2017\n\n8\n\n1\n\n23\n\n- [Feb 18, 2022](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/post-452674)\n\n- [\\#2](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/post-452674)\n\nWas talking about this with a co-worker today. To recreate, it should be this simple:  \n   \n Install Debian bullseye container.  \n Within that container, install screen.  \n Run screen.  \n Within screen, run something like 'top' that will keep running.  \n Ctrl+A, D to detach screen.  \n Logout.  \n Login.  \n Run 'screen -list'.  \n Get error 'No Sockets found'  \n Be sad that screen is broken.  \n   \n Or maybe it works for you?\n\n[C](https:\/\/forum.proxmox.com\/members\/clickwir.52592\/)\n\n#### [clickwir](https:\/\/forum.proxmox.com\/members\/clickwir.52592\/)\n##### Member\n\nDec 21, 2017\n\n8\n\n1\n\n23\n\n- [Jul 14, 2022](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/post-484088)\n\n- [\\#3](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/post-484088)\n\nHas no one else tried to run screen on a container? This is still a problem. Screen is entirely broken when you logout.\n\n[S](https:\/\/forum.proxmox.com\/members\/syxcrrropp.162126\/)\n\n#### [syxcrrropp](https:\/\/forum.proxmox.com\/members\/syxcrrropp.162126\/)\n##### New Member\n\nSep 14, 2022\n\n1\n\n0\n\n1\n\n- [Sep 14, 2022](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/post-497825)\n\n- [\\#4](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/post-497825)\n\ni still got the same problem, any idea?\n\n[C](https:\/\/forum.proxmox.com\/members\/clickwir.52592\/)\n\n#### [clickwir](https:\/\/forum.proxmox.com\/members\/clickwir.52592\/)\n##### Member\n\nDec 21, 2017\n\n8\n\n1\n\n23\n\n- [Sep 15, 2022](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/post-497995)\n\n- [\\#5](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/post-497995)\n\nSadly, I haven't found a solution yet.   \n   \n IMO, systemd is overstepping it's bounds by a lot. Was meant to be an init system replacement and it's morphed into a lot more than that and is slowly replacing everything in a linux system with a systemd method\/application\/service\/way of life. And I don't really care for it.   \n   \n This problem being a prime example. Screen is meant to be able to run after you logout and systemd is completely doing away with that and taking a stance that simply doesn't work with how users need a system to function. Especially one they've been using like this for, literally, decades.   \n   \n That complaint out of the way, I'm considering using Devuan instead. It's a Debian fork but with without systemd. It's been around for a few years and looks like the only way to get back basic functions.  \n   \n Some more info on Devuan  \n <https:\/\/www.devuan.org\/>  \n <https:\/\/www.makeuseof.com\/tag\/debian-without-systemd-devuan\/>\n\n[P](https:\/\/forum.proxmox.com\/members\/parmdhoot.226371\/)\n\n#### [parmdhoot](https:\/\/forum.proxmox.com\/members\/parmdhoot.226371\/)\n##### New Member\n\nMar 8, 2024\n\n1\n\n0\n\n1\n\n- [Mar 8, 2024](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/post-642029)\n\n- [\\#6](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/post-642029)\n\nIs there a solution to this other than using a different fork? In my case it is impacting pm2 also, it just feels super odd to kills such a core function of how linux has worked for decades. Everything works as normal with Ubuntu 20.04 but not 22.04 or 23.04.\n\n[R](https:\/\/forum.proxmox.com\/members\/rafterhat.231027\/)\n\n#### [RafterHat](https:\/\/forum.proxmox.com\/members\/rafterhat.231027\/)\n##### New Member\n\nApr 2, 2024\n\n1\n\n0\n\n1\n\n- [Apr 2, 2024](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/post-649446)\n\n- [\\#7](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/post-649446)\n\nI don't know why, but reinstalling sshd fixes the problem.\n\nCode:\n```\napt-get install --reinstall openssh-server\n```\n\n[D](https:\/\/forum.proxmox.com\/members\/danw.295649\/)\n\n#### [danw](https:\/\/forum.proxmox.com\/members\/danw.295649\/)\n##### New Member\n\nMar 18, 2025\n\n1\n\n0\n\n1\n\n- [Mar 18, 2025](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/post-756739)\n\n- [\\#8](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/post-756739)\n\nAs it turns out,\n\n> [clickwir said:](https:\/\/forum.proxmox.com\/goto\/post?id=452410)\n> \n> `$ loginctl enable-linger`  \n>  `Could not enable linger: Connection timed out`\n> \n> [Click to expand...]()\n\nThis was very close to the correct answer.  \n loginctl enable-linger \\<USERNAME\\>   \n is what's needed to make it work. I just tried it with root. Before enabling linger, tmux was killed on logout. After, it is left running.\n\n[You must log in or register to reply here.](https:\/\/forum.proxmox.com\/login\/)\n\nShare:\n\n[Bluesky](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/#_xfUid-1-1769389789)   [LinkedIn](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/#_xfUid-1-1769389789)   [Reddit](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/#_xfUid-1-1769389789)   [Email](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/#_xfUid-1-1769389789)   [Share](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/#_xfUid-1-1769389789)   [Link](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/#_xfUid-1-1769389789)\n\n- [Home](https:\/\/forum.proxmox.com\/)\n- [Forums](https:\/\/forum.proxmox.com\/)\n- [Proxmox Virtual Environment](https:\/\/forum.proxmox.com\/#proxmox-virtual-environment.11)\n- [Proxmox VE: Installation and configuration](https:\/\/forum.proxmox.com\/forums\/proxmox-ve-installation-and-configuration.16\/)\n\n## About\nThe Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.  \n We think our community is one of the best thanks to people like you\\!\n\n### Quick Navigation\n[Home](https:\/\/forum.proxmox.com\/) [Get Subscription](https:\/\/www.proxmox.com\/proxmox-virtual-environment\/pricing) [Wiki](https:\/\/pve.proxmox.com\/wiki) [Downloads](https:\/\/www.proxmox.com\/downloads) [Proxmox Customer Portal](https:\/\/my.proxmox.com\/) [About](https:\/\/www.proxmox.com\/about\/company)\n\n### Get your subscription\\!\nThe Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.\n\n[Buy now\\!](https:\/\/shop.proxmox.com\/)\n\n- [Cookies](https:\/\/forum.proxmox.com\/misc\/cookies \"Cookie consent\")\n- [Proxmox Support Forum - Light Mode](https:\/\/forum.proxmox.com\/misc\/style \"Style chooser\")\n\n- [Contact us](https:\/\/www.proxmox.com\/en\/about\/contact)\n- [Terms and rules](https:\/\/forum.proxmox.com\/help\/terms\/)\n- [Privacy policy](https:\/\/www.proxmox.com\/en\/privacy-policy)\n- [Help](https:\/\/forum.proxmox.com\/help\/)\n- [Home](https:\/\/forum.proxmox.com\/)\n- [RSS](https:\/\/forum.proxmox.com\/forums\/-\/index.rss \"RSS\")\n\n[Community platform by XenForo® © 2010-2025 XenForo Ltd.](https:\/\/xenforo.com\/)\n\n[Top](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/#top) [Bottom](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/#footer)\n\n[Back]()\n\n- ## We value your privacy\n  We use essential [cookies](https:\/\/forum.proxmox.com\/help\/cookies) to make this site work, and optional cookies to enhance your experience.\n  \n  [See further information and configure your preferences](https:\/\/forum.proxmox.com\/threads\/debian-lxc-screen-killed-out-logout.105083\/)\n  \n  [Accept all cookies](https:\/\/forum.proxmox.com\/misc\/cookies?update=1&accept=1&t=1769389789%2C9242063c0b2ae86a144e57488ec4d988)   [Reject optional cookies](https:\/\/forum.proxmox.com\/misc\/cookies?update=1&reject=1&t=1769389789%2C9242063c0b2ae86a144e57488ec4d988)","attrs_readable_markdown":null,"meta_canonical":null}

3. Robots.txt Check

Query:

Response:

4. Spam/Ban Check

Query:

Response:

5. Seen Status Check

ℹ️ Skipped - page is already crawled

📄

INDEXABLE

✅

CRAWLED

2 months ago

🤖

ROBOTS ALLOWED

Page Info Filters

Filter	Status	Condition	Details
HTTP status	PASS	`download_http_code = 200`	HTTP 200
Age cutoff	PASS	`download_stamp > now() - 6 MONTH`	2.8 months ago
History drop	PASS	`isNull(history_drop_reason)`	No drop reason
Spam/ban	PASS	`fh_dont_index != 1 AND ml_spam_score = 0`	ml_spam_score=0
Canonical	PASS	`meta_canonical IS NULL OR = '' OR = src_unparsed`	Not set

Page Details

Property	Value
URL	https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/
Last Crawled	2026-01-26 01:09:49 (2 months ago)
First Indexed	2022-02-18 21:49:14 (4 years ago)
HTTP Status Code	200
Meta Title	debian lxc - screen killed out logout \| Proxmox Support Forum
Meta Description	So I've been struggling with this for a few hours and everything I've found online leads to huge arguments about how systemd (back in 2016?) changed a...
Meta Canonical	null
Boilerpipe Text	#1 So I've been struggling with this for a few hours and everything I've found online leads to huge arguments about how systemd (back in 2016?) changed a default to kill all user processes on logout. Well that sounds ok, but it kills things like screen. screen has been used for many many years, specifically for the use of keeping something running after you logout. They say the systemd default is enabled but it's up to distros to pick. Well I'm using a Debian container and it appears to be disabled by default but my screen session still gets killed as soon as I logout. There have been a few suggestions, none have worked. Is this specific to being in a container? $ systemd-run --scope --user screen Failed to connect to bus: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined (consider using --machine=<user>@.host --user to connect to bus of other user) $ systemd-run --scope --machine=clickwir@.host --user screen Execution in user context is not supported on non-local systems. $ systemd-run --scope --machine=clickwir@.localhost --user screen Execution in user context is not supported on non-local systems. $ systemd-run --scope --machine=clickwir@localhost --user screen Execution in user context is not supported on non-local systems. $ systemd-run --scope --machine=clickwir@ --user ls Execution in user context is not supported on non-local systems. $ loginctl enable-linger Could not enable linger: Connection timed out It was suggested to add 'export XDG_RUNTIME_DIR=/run/user/$(id -u)' to .bashrc Well that did result in something different, but still doesn't work. $ systemd-run --scope --user screen Failed to connect to bus: No such file or directory I need to have screen continue to run on logout/disconnect. Honestly it's more the ungraceful disconnect I'm concerned with. Just because my desktop system disconnects/dies/locks shouldn't affect screen. #2 Was talking about this with a co-worker today. To recreate, it should be this simple: Install Debian bullseye container. Within that container, install screen. Run screen. Within screen, run something like 'top' that will keep running. Ctrl+A, D to detach screen. Logout. Login. Run 'screen -list'. Get error 'No Sockets found' Be sad that screen is broken. Or maybe it works for you? #3 Has no one else tried to run screen on a container? This is still a problem. Screen is entirely broken when you logout. #4 i still got the same problem, any idea? #5 Sadly, I haven't found a solution yet. IMO, systemd is overstepping it's bounds by a lot. Was meant to be an init system replacement and it's morphed into a lot more than that and is slowly replacing everything in a linux system with a systemd method/application/service/way of life. And I don't really care for it. This problem being a prime example. Screen is meant to be able to run after you logout and systemd is completely doing away with that and taking a stance that simply doesn't work with how users need a system to function. Especially one they've been using like this for, literally, decades. That complaint out of the way, I'm considering using Devuan instead. It's a Debian fork but with without systemd. It's been around for a few years and looks like the only way to get back basic functions. Some more info on Devuan https://www.devuan.org/ https://www.makeuseof.com/tag/debian-without-systemd-devuan/ #6 Is there a solution to this other than using a different fork? In my case it is impacting pm2 also, it just feels super odd to kills such a core function of how linux has worked for decades. Everything works as normal with Ubuntu 20.04 but not 22.04 or 23.04. #7 I don't know why, but reinstalling sshd fixes the problem. Code: apt-get install --reinstall openssh-server #8 As it turns out, $ loginctl enable-linger Could not enable linger: Connection timed out This was very close to the correct answer. loginctl enable-linger <USERNAME> is what's needed to make it work. I just tried it with root. Before enabling linger, tmux was killed on logout. After, it is left running.
Markdown	[![Proxmox Support Forum](https://forum.proxmox.com/styles/uix/images/Proxmox-logo-500px.png)](https://forum.proxmox.com/) [![Proxmox Support Forum](https://forum.proxmox.com/styles/uix/images/Proxmox-logo-black-800.png)](https://forum.proxmox.com/) [![Proxmox Support Forum](https://forum.proxmox.com/styles/uix/images/Proxmox-logo-500px.png)](https://forum.proxmox.com/) [![Proxmox Support Forum](https://forum.proxmox.com/styles/uix/images/Proxmox-logo-black-800.png)](https://forum.proxmox.com/) - [Home](https://forum.proxmox.com/) - [Forums](https://forum.proxmox.com/) [New posts](https://forum.proxmox.com/whats-new/posts/) [Search forums](https://forum.proxmox.com/search/?type=post) - [What's new](https://forum.proxmox.com/whats-new/) [Featured content](https://forum.proxmox.com/featured/) [New posts](https://forum.proxmox.com/whats-new/posts/) [Latest activity](https://forum.proxmox.com/whats-new/latest-activity) - [Members](https://forum.proxmox.com/members/) [Current visitors](https://forum.proxmox.com/online/) [New profile posts](https://forum.proxmox.com/whats-new/profile-posts/) [Search profile posts](https://forum.proxmox.com/search/?type=profile_post) [Log in](https://forum.proxmox.com/login/) [Register](https://forum.proxmox.com/register/) [What's new](https://forum.proxmox.com/whats-new/ "What's new") - [New posts](https://forum.proxmox.com/whats-new/posts/) - [Search forums](https://forum.proxmox.com/search/?type=post) Menu Install the app Install How to install the app on iOS Follow along with the video below to see how to install our site as a web app on your home screen. Note: This feature may not be available in some browsers. # debian lxc - screen killed out logout - Thread starter [clickwir](https://forum.proxmox.com/members/clickwir.52592/) - Start date [Feb 17, 2022](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/) - Tags [lxc](https://forum.proxmox.com/tags/lxc/) [screen](https://forum.proxmox.com/tags/screen/) [systemd](https://forum.proxmox.com/tags/systemd/) - [Home](https://forum.proxmox.com/) - [Forums](https://forum.proxmox.com/) - [Proxmox Virtual Environment](https://forum.proxmox.com/#proxmox-virtual-environment.11) - [Proxmox VE: Installation and configuration](https://forum.proxmox.com/forums/proxmox-ve-installation-and-configuration.16/) JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding. You are using an out of date browser. It may not display this or other websites correctly. You should upgrade or use an [alternative browser](https://www.google.com/chrome/). [C](https://forum.proxmox.com/members/clickwir.52592/) #### [clickwir](https://forum.proxmox.com/members/clickwir.52592/) ##### Member Dec 21, 2017 8 1 23 - [Feb 17, 2022](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/post-452410) - [\#1](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/post-452410) So I've been struggling with this for a few hours and everything I've found online leads to huge arguments about how systemd (back in 2016?) changed a default to kill all user processes on logout. Well that sounds ok, but it kills things like screen. screen has been used for many many years, specifically for the use of keeping something running after you logout. They say the systemd default is enabled but it's up to distros to pick. Well I'm using a Debian container and it appears to be disabled by default but my screen session still gets killed as soon as I logout. There have been a few suggestions, none have worked. Is this specific to being in a container? ``` $ systemd-run --scope --user screen Failed to connect to bus: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined (consider using --machine=<user>@.host --user to connect to bus of other user) $ systemd-run --scope --machine=clickwir@.host --user screen Execution in user context is not supported on non-local systems. $ systemd-run --scope --machine=clickwir@.localhost --user screen Execution in user context is not supported on non-local systems. $ systemd-run --scope --machine=clickwir@localhost --user screen Execution in user context is not supported on non-local systems. $ systemd-run --scope --machine=clickwir@ --user ls Execution in user context is not supported on non-local systems. $ loginctl enable-linger Could not enable linger: Connection timed out ``` It was suggested to add 'export XDG\_RUNTIME\_DIR=/run/user/\$(id -u)' to .bashrc Well that did result in something different, but still doesn't work. ``` $ systemd-run --scope --user screen Failed to connect to bus: No such file or directory ``` I need to have screen continue to run on logout/disconnect. Honestly it's more the ungraceful disconnect I'm concerned with. Just because my desktop system disconnects/dies/locks shouldn't affect screen. [C](https://forum.proxmox.com/members/clickwir.52592/) #### [clickwir](https://forum.proxmox.com/members/clickwir.52592/) ##### Member Dec 21, 2017 8 1 23 - [Feb 18, 2022](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/post-452674) - [\#2](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/post-452674) Was talking about this with a co-worker today. To recreate, it should be this simple: Install Debian bullseye container. Within that container, install screen. Run screen. Within screen, run something like 'top' that will keep running. Ctrl+A, D to detach screen. Logout. Login. Run 'screen -list'. Get error 'No Sockets found' Be sad that screen is broken. Or maybe it works for you? [C](https://forum.proxmox.com/members/clickwir.52592/) #### [clickwir](https://forum.proxmox.com/members/clickwir.52592/) ##### Member Dec 21, 2017 8 1 23 - [Jul 14, 2022](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/post-484088) - [\#3](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/post-484088) Has no one else tried to run screen on a container? This is still a problem. Screen is entirely broken when you logout. [S](https://forum.proxmox.com/members/syxcrrropp.162126/) #### [syxcrrropp](https://forum.proxmox.com/members/syxcrrropp.162126/) ##### New Member Sep 14, 2022 1 0 1 - [Sep 14, 2022](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/post-497825) - [\#4](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/post-497825) i still got the same problem, any idea? [C](https://forum.proxmox.com/members/clickwir.52592/) #### [clickwir](https://forum.proxmox.com/members/clickwir.52592/) ##### Member Dec 21, 2017 8 1 23 - [Sep 15, 2022](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/post-497995) - [\#5](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/post-497995) Sadly, I haven't found a solution yet. IMO, systemd is overstepping it's bounds by a lot. Was meant to be an init system replacement and it's morphed into a lot more than that and is slowly replacing everything in a linux system with a systemd method/application/service/way of life. And I don't really care for it. This problem being a prime example. Screen is meant to be able to run after you logout and systemd is completely doing away with that and taking a stance that simply doesn't work with how users need a system to function. Especially one they've been using like this for, literally, decades. That complaint out of the way, I'm considering using Devuan instead. It's a Debian fork but with without systemd. It's been around for a few years and looks like the only way to get back basic functions. Some more info on Devuan <https://www.devuan.org/> <https://www.makeuseof.com/tag/debian-without-systemd-devuan/> [P](https://forum.proxmox.com/members/parmdhoot.226371/) #### [parmdhoot](https://forum.proxmox.com/members/parmdhoot.226371/) ##### New Member Mar 8, 2024 1 0 1 - [Mar 8, 2024](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/post-642029) - [\#6](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/post-642029) Is there a solution to this other than using a different fork? In my case it is impacting pm2 also, it just feels super odd to kills such a core function of how linux has worked for decades. Everything works as normal with Ubuntu 20.04 but not 22.04 or 23.04. [R](https://forum.proxmox.com/members/rafterhat.231027/) #### [RafterHat](https://forum.proxmox.com/members/rafterhat.231027/) ##### New Member Apr 2, 2024 1 0 1 - [Apr 2, 2024](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/post-649446) - [\#7](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/post-649446) I don't know why, but reinstalling sshd fixes the problem. Code: ``` apt-get install --reinstall openssh-server ``` [D](https://forum.proxmox.com/members/danw.295649/) #### [danw](https://forum.proxmox.com/members/danw.295649/) ##### New Member Mar 18, 2025 1 0 1 - [Mar 18, 2025](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/post-756739) - [\#8](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/post-756739) As it turns out, > [clickwir said:](https://forum.proxmox.com/goto/post?id=452410) > > `$ loginctl enable-linger` > `Could not enable linger: Connection timed out` > > [Click to expand...]() This was very close to the correct answer. loginctl enable-linger \<USERNAME\> is what's needed to make it work. I just tried it with root. Before enabling linger, tmux was killed on logout. After, it is left running. [You must log in or register to reply here.](https://forum.proxmox.com/login/) Share: [Bluesky](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/#_xfUid-1-1769389789) [LinkedIn](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/#_xfUid-1-1769389789) [Reddit](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/#_xfUid-1-1769389789) [Email](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/#_xfUid-1-1769389789) [Share](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/#_xfUid-1-1769389789) [Link](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/#_xfUid-1-1769389789) - [Home](https://forum.proxmox.com/) - [Forums](https://forum.proxmox.com/) - [Proxmox Virtual Environment](https://forum.proxmox.com/#proxmox-virtual-environment.11) - [Proxmox VE: Installation and configuration](https://forum.proxmox.com/forums/proxmox-ve-installation-and-configuration.16/) ## About The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you\! ### Quick Navigation [Home](https://forum.proxmox.com/) [Get Subscription](https://www.proxmox.com/proxmox-virtual-environment/pricing) [Wiki](https://pve.proxmox.com/wiki) [Downloads](https://www.proxmox.com/downloads) [Proxmox Customer Portal](https://my.proxmox.com/) [About](https://www.proxmox.com/about/company) ### Get your subscription\! The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop. [Buy now\!](https://shop.proxmox.com/) - [Cookies](https://forum.proxmox.com/misc/cookies "Cookie consent") - [Proxmox Support Forum - Light Mode](https://forum.proxmox.com/misc/style "Style chooser") - [Contact us](https://www.proxmox.com/en/about/contact) - [Terms and rules](https://forum.proxmox.com/help/terms/) - [Privacy policy](https://www.proxmox.com/en/privacy-policy) - [Help](https://forum.proxmox.com/help/) - [Home](https://forum.proxmox.com/) - [RSS](https://forum.proxmox.com/forums/-/index.rss "RSS") [Community platform by XenForo® © 2010-2025 XenForo Ltd.](https://xenforo.com/) [Top](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/#top) [Bottom](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/#footer) [Back]() - ## We value your privacy We use essential [cookies](https://forum.proxmox.com/help/cookies) to make this site work, and optional cookies to enhance your experience. [See further information and configure your preferences](https://forum.proxmox.com/threads/debian-lxc-screen-killed-out-logout.105083/) [Accept all cookies](https://forum.proxmox.com/misc/cookies?update=1&accept=1&t=1769389789%2C9242063c0b2ae86a144e57488ec4d988) [Reject optional cookies](https://forum.proxmox.com/misc/cookies?update=1&reject=1&t=1769389789%2C9242063c0b2ae86a144e57488ec4d988)
Readable Markdown	null
Shard	10 (laksa)
Root Hash	9469933952248431210
Unparsed URL	com,proxmox!forum,/threads/debian-lxc-screen-killed-out-logout.105083/ s443