[Bug 1811295] [NEW] systemctl daemon-reexec does not update group membership
Public bug reported: On Ubuntu 16.04.4 LTS using Package: systemd Architecture: amd64 Version: 229-4ubuntu21.10 Changes the group membership are not picked up by the systemd process for a logged-in user or for a user with enable-linger set regardless of login status. Evidently the systemctl --user daemon-reexec command preserves group membership across the daemon restart. This is bad. It means that only a reboot or sudo loginctl terminate-user will update the group membership to the proper set. Both of those things are extreme disruptions for a system/user that runs servers. Can systemctl daemon-reexec be made to update group membership for the user in the systemd process? ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811295 Title: systemctl daemon-reexec does not update group membership To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810351] Re: journalctl fails to work inside systemd service
Part of the mystery is solved and part not. SOLVED: The problem was that journal entries were not being stored on disk and journalctl was not showing entries from memory. The default Ubuntu config has settings Storage=auto SplitMode=uid Also, the directory /var/log/journal does not exist by default and does not get created in Storage=auto mode. Creating the /var/log/journal directory and restarting journald so that entries get stored to disk fixes the problem. NOT SOLVED: It is still unclear why journalctl would display output when run from the shell but not when run from systemd. It would seem that in a systemd --user unit it could not access the in-memory logs. I would suggest that the default Ubuntu install should have the /var/log/journal directory in place so that journalctl will work correctly out-of-the-box. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810351 Title: journalctl fails to work inside systemd service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1810351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808432] Re: systemctl template units not enabled per docs
This is related to https://github.com/systemd/systemd/issues/661 ** Bug watch added: github.com/systemd/systemd/issues #661 https://github.com/systemd/systemd/issues/661 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808432 Title: systemctl template units not enabled per docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1808432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810351] [NEW] journalctl fails to work inside systemd service
Public bug reported: Using Ubuntu 16.04.4 LTS and Package: systemd Architecture: amd64 Version: 229-4ubuntu21.10 Multi-Arch: foreign Priority: required Section: admin Origin: Ubuntu The journalctl(1) command cannot be used in a systemd OnFailure service to get error logs. To replicate the issue 1) Create a service unit [Unit] Description=%n [Service] #ExecStart=/bin/sh -xv -c 'systemctl --user status -o cat -n 20 | mail -s "Unit failed" ' ExecStart=/bin/sh -c 'journalctl --user-unit= -o verbose -q -n 20 | mail -s "Unit failed" ' 2) enable the unit 3) start the unit You will get a failure message from journalctl and mail of sh[28225]: No journal files were opened due to insufficient permissions. sh[28225]: mail: Null message body; hope that's ok 4) switch the comment # to the journalctl ExecStart and uncomment the systemctl ExecStart line >From systemctl you will get journal output in the email. The man page for systemctl states "In addition, journalctl --unit=NAME or journalctl --user-unit=NAME use a similar filter for messages and might be more convenient." and indeed it would if it worked properly. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810351 Title: journalctl fails to work inside systemd service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1810351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809989] [NEW] deluser does not clean up systemd files
Public bug reported: In Description:Ubuntu 16.04.4 LTS Release:16.04 using adduser package Version: 3.113+nmu3ubuntu4 systemd package Version: 229-4ubuntu21.10 deluser will not clean up data in /run/user/ directory. If a user is created then under many circumstances, such as systemd enable-linger being called for the user, data for that user will exist in /run/user/. Running deluser for such as user will remove the user, home directory, etc. but not the /run/user data. ** Most importantly **, the next user creation will be given the open uid formerly held by the deleted user. The new user can then have broken systemd sessions so that the systemctl --user command will always fail with the error Failed to connect to bus: No such file or directory A system reboot seems to be the only thing that will reliably clean up the cruft in /run/user/ Expected behavior would be that if a user is successfully removed then there should be no directory remaining for that user's uid under /run/user. ** Affects: adduser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809989 Title: deluser does not clean up systemd files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1809989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809162] [NEW] systemctl show -p doesn't show all properties
Public bug reported: In Description:Ubuntu 16.04.4 LTS Release:16.04 using systemd package Version: 229-4ubuntu21.10 The systemctl show -p or --property= command shows some properties but not others. To reproduce create a unit some_unit.path [Unit] Description=%n [Path] PathExistsGlob=%h/foo* Unit=remove.service Using systemctl show --all some_unit.path you'll see properties PathExistsGlob and LoadState shown Now try systemctl show -p LoadState some_unit.path and you will see the property value Then try systemctl show -p PathExistsGlob some_unit.path and you will get no value back. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809162 Title: systemctl show -p doesn't show all properties To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1809162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809084] [NEW] Confirm prompt for systemctl --full edit is redundant and interferes with scripting
Public bug reported: On Ubuntu version Distributor ID: Ubuntu Description:Ubuntu 16.04.4 LTS Release:16.04 and systemd package Version: 229-4ubuntu21.10 When the --full argument is used with systemctl edit a confirm prompt of ...some.service" already exists. Overwrite with "..."? [(y)es, (n)o] is issued. Since the systemctl edit command won't function w/o a unit file in place the message tells the user something they already know. There appears to be no way to bypass this message, so it makes running systemctl edit from a script more difficult. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809084 Title: Confirm prompt for systemctl --full edit is redundant and interferes with scripting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1809084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808432] [NEW] systemctl template units not enabled per docs
Public bug reported: Report is for Description:Ubuntu 16.04.4 LTS Release:16.04 Package data is Package: systemd Architecture: amd64 Version: 229-4ubuntu21.10 Multi-Arch: foreign No log file is applicable The problem is that systemctl enable does not perform according to documentation in enabling template unit files. If a template unit file exists /full_path_to/tmpl@.service and you try to enable it with systemctl per the docs sudo systemctl enable /full_path_to/tmpl@instance.service or systemctl --user enable /full_path_to/tmpl@instance.service you get the error Failed to execute operation: No such file or directory What should happen is that systemctl fails to find /full_path_to/tmpl@instance.service so it then tries the template name /full_path_to/tmpl@.service, finds it, and creates a symlink to that template file. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808432 Title: systemctl template units not enabled per docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1808432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808251] Re: systemctl disable fails to clean up override
No applicable logs ** Package changed: linux (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808251 Title: systemctl disable fails to clean up override To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1808251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808251] Re: systemctl disable fails to clean up override
This bug is easily reproduced and will not leave any meaningful log entries. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808251 Title: systemctl disable fails to clean up override To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1808251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808251] [NEW] systemctl disable fails to clean up override
Public bug reported: I am using Ubuntu 16.04.4 LTS and package version systemd: Installed: 229-4ubuntu21.10 Candidate: 229-4ubuntu21.10 Version table: *** 229-4ubuntu21.10 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages When a unit is enabled with systemctl enable and overrides are applied with systemctl edit and subsequently the unit is disabled with systemctl disable the override file that is created and its directory /etc/systemd/system/.d/override.conf is not removed. Subsequent attempts to enable the same unit will fail with the misleading and unhelpful error message Failed to execute operation: Invalid argument Removing the override file and directory will fix the problem. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808251 Title: systemctl disable fails to clean up override To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1490777] [NEW] adduser does not behave as documented in man page
Public bug reported: The man page for the adduser utility clearly states the exit code behavior to be expected as: EXIT VALUES 0 The user exists as specified. This can have 2 causes: The user was created by adduser or the user was already present on the system before adduser was invoked. If adduser was returning 0 , invoking adduser a second time with the same parameters as before also returns 0. 1 Creating the user or group failed because it was already present with other UID/GID than specified. The username or groupname was rejected because of a mismatch with the configured regular expressions, see adduser.conf(5). Adduser has been aborted by a signal. Or for many other yet undocumented reasons which are printed to console then. You may then consider to remove --quiet to make adduser more verbose. In actual operation, adduser returns 1 if the user already exists. The documented behavior would be preferable. System details: Description:Ubuntu 12.04.5 LTS Release:12.04 adduser: Installed: 3.113ubuntu2 Candidate: 3.113ubuntu2 Version table: *** 3.113ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: adduser 3.113ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-49.81~precise1-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 Date: Mon Aug 31 16:43:48 2015 InstallationMedia: Ubuntu-Server 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.2) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: adduser UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: adduser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1490777 Title: adduser does not behave as documented in man page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1490777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
