Bug 904821
| Summary: | Systemd fails when PrivateTmp is used | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Artemy Kapitula, Mail.Ru Cloud Solutions <dalt74> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 18 | CC: | johannbg, lnykryn, masao-takahashi, metherid, msekleta, notting, plautrba, systemd-maint, vpavlin |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-03-08 00:08:30 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
mounted filesystems: [root@localhost viking]# mount proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) devtmpfs on /dev type devtmpfs (rw,nosuid,size=1541696k,nr_inodes=211634,mode=755) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) /dev/sdb2 on / type ext4 (ro,noatime,discard) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=300,minproto=5,maxproto=5,direct) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) mqueue on /dev/mqueue type mqueue (rw,relatime) none on /var/log type tmpfs (rw,relatime) none on /tmp type tmpfs (rw,relatime) configfs on /sys/kernel/config type configfs (rw,relatime) /dev/sdb3 on /home type ext4 (ro,noatime,discard) A later investigation shows that problem is present when /var/tmp is a symlink to /tmp with /tmp mounted as tmpfs. *** This bug has been marked as a duplicate of bug 901926 *** |
Description of problem: Systemd fails when /tmp is mounted as tmpfs and service unit specifies PrivateTmp=true. Version-Release number of selected component (if applicable): systemd-197-1.fc18.1.i686 How reproducible: Always Steps to Reproduce: 1. boot with /tmp mounted as tmpfs 2. try activate any service having privatetmp=yes (i.e. cups.service) Actual results: The "top" output: Tasks: 138 total, 5 running, 133 sleeping, 0 stopped, 0 zombie %Cpu(s): 53.0 us, 46.8 sy, 0.0 ni, 0.0 id, 0.0 wa, 0.0 hi, 0.2 si, 0.0 st KiB Mem: 3102468 total, 560152 used, 2542316 free, 25036 buffers KiB Swap: 0 total, 0 used, 0 free, 287180 cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 6400 3536 2072 R 98.8 0.1 2:27.62 systemd 288 root 20 0 270m 11m 10m R 95.6 0.4 2:20.40 systemd-journal 675 root 20 0 92196 28m 14m S 1.3 0.9 0:04.62 Xorg 55 root 20 0 0 0 0 R 1.0 0.0 0:00.69 kworker/1:2 journalctl output: Jan 27 23:53:19 localhost.localdomain systemd[1]: cups.service: main process exited, code=exited, status=226/NAMESPACE Jan 27 23:53:19 localhost.localdomain systemd[1]: Unit cups.service entered failed state Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: cups.service start request repeated too quickly, refusing to start. Jan 27 23:53:19 localhost.localdomain systemd[1]: Failed to start CUPS Printing Service. Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: cups.service start request repeated too quickly, refusing to start. Jan 27 23:53:19 localhost.localdomain systemd[1]: Failed to start CUPS Printing Service. Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: cups.service start request repeated too quickly, refusing to start. Jan 27 23:53:19 localhost.localdomain systemd[1]: Failed to start CUPS Printing Service. Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: cups.service start request repeated too quickly, refusing to start. Jan 27 23:53:19 localhost.localdomain systemd[1]: Failed to start CUPS Printing Service. Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: Failed to start CUPS Printing Service. Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: Failed to start CUPS Printing Service. Jan 27 23:53:19 localhost.localdomain systemd[1]: Failed to start CUPS Printing Service. Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: cups.service start request repeated too quickly, refusing to start. Jan 27 23:53:19 localhost.localdomain systemd[1]: Failed to start CUPS Printing Service. Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: cups.service start request repeated too quickly, refusing to start. Jan 27 23:53:19 localhost.localdomain systemd[1]: Failed to start CUPS Printing Service. Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: cups.service start request repeated too quickly, refusing to start. Jan 27 23:53:19 localhost.localdomain systemd[1]: Failed to start CUPS Printing Service. Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: cups.service start request repeated too quickly, refusing to start. Jan 27 23:53:19 localhost.localdomain systemd[1]: Failed to start CUPS Printing Service. Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Jan 27 23:53:19 localhost.localdomain systemd[1]: Starting CUPS Printing Service... Expected results: cups must start. If cups is not not started via _cups_ reason, it can be restarted. If it's not started due systemds' reasons (like here), service must NOT be restarted, because it's not a service, but systemd failure. Anyway, systemd should not utilize all cpu with useless and helpless thousands of error messages and must to make difference between systemd and service fails.