Bug#919602: apache2: reload via systemd: apache2.service: Failed to set up mount namespacing: No such file or directory
I got this issue on Debian sid right now. I have this in my /etc/fstab: tmpfs /tmp tmpfs defaults,noatime,mode=1777,nosuid 0 0 tmpfs /var/spool/rsyslog tmpfsdefaults,noatime,mode=1777 0 0 tmpfs /var/spool/anacron tmpfsdefaults,noatime,mode=1777 0 0 tmpfs /var/spool/mqueuetmpfsdefaults,noatime,mode=1777 0 0 tmpfs /var/spool/mqueue-client tmpfsdefaults,noatime,mode=1777 0 0 tmpfs /var/cache tmpfs defaults,noatime,nodiratime 0 0 tmpfs /var/cache/locatetmpfs defaults,noatime,nodiratime 0 0 tmpfs /var/cache/ntpsectmpfs defaults,noatime,nodiratime 0 0 tmpfs /var/cache/apt-show-versions tmpfs defaults,noatime,nodiratime 0 0 tmpfs /var/tmp tmpfsdefaults,noatime 0 0 dic 10 11:27:43 KITT (apachectl)[564309]: apache2.service: Failed to set up mount namespacing: /var/cache/apache2/mod_cache_disk: No such file or directory dic 10 11:27:43 KITT (apachectl)[564309]: apache2.service: Failed at step NAMESPACE spawning /usr/sbin/apachectl: No such file or directory The issue was fixed with: mkdir -p /var/cache/apache2/mod_cache_disk I have to see if the issue still persist at next reboot of the machine as I am mount the /var/cache folder with tmpfs
Bug#919602: apache2: reload via systemd: apache2.service: Failed to set up mount namespacing: No such file or directory
On Wed, 23 Oct 2019 16:31:39 +0200 Sven Bartscher wrote: > Hi, > > do you use tools to age out files in /var/tmp or /tmp? I recently > encountered this problem myself (on Jessie) and the cause was, that > tmpreaper deleted the private tmp directories of the apache2.service > unit. I didn't observe the apache2 service being stopped after receiving > the error though, so you problem might actually be separate from mine. I'm having the same issue on a fresh buster install, and don't have tmpreaper installed. I only see systemd-tmpfiles-clean.service run a few hours before.
Bug#919602: apache2: reload via systemd: apache2.service: Failed to set up mount namespacing: No such file or directory
Hi, On Thu, 17 Jan 2019 19:59:45 +0100 Philipp Marek wrote: > Package: apache2 > Version: 2.4.37-1 > Severity: normal > > During a reload for log rotation, apache was stopped instead of reloaded: > > [...] do you use tools to age out files in /var/tmp or /tmp? I recently encountered this problem myself (on Jessie) and the cause was, that tmpreaper deleted the private tmp directories of the apache2.service unit. I didn't observe the apache2 service being stopped after receiving the error though, so you problem might actually be separate from mine. Regards Sven signature.asc Description: OpenPGP digital signature
Bug#919602: apache2: reload via systemd: apache2.service: Failed to set up mount namespacing: No such file or directory
Package: apache2 Version: 2.4.37-1 Severity: normal During a reload for log rotation, apache was stopped instead of reloaded: Jän 17 01:00:38 systemd[1]: Starting Rotate log files... -- Subject: A start job for unit logrotate.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit logrotate.service has begun execution. -- -- The job identifier is 25118. Jän 17 01:00:38 systemd[1]: Reloading The Apache HTTP Server. -- Subject: A reload job for unit apache2.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A reload job for unit apache2.service has begun execution. -- -- The job identifier is 25186. Jän 17 01:00:38 systemd[12733]: apache2.service: Failed to set up mount namespacing: No such file or directory Jän 17 01:00:38 systemd[12733]: apache2.service: Failed at step NAMESPACE spawning /usr/sbin/apachectl: No such file or directo -- Subject: Process /usr/sbin/apachectl could not be executed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The process /usr/sbin/apachectl could not be executed and failed. -- -- The error number returned by this process is ERRNO. Jän 17 01:00:38 systemd[1]: apache2.service: Control process exited, code=exited, status=226/NAMESPACE -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- An ExecReload= process belonging to unit apache2.service has exited. -- -- The process' exit code is 'exited' and its exit status is 226. Jän 17 01:00:39 systemd[1]: apache2.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit apache2.service has entered the 'failed' state with result 'exit-code'. Jän 17 01:00:39 systemd[1]: Reload failed for The Apache HTTP Server. -- Subject: A reload job for unit apache2.service has finished -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A reload job for unit apache2.service has finished. -- -- The job identifier is 25186 and the job result is failed. Jän 17 01:00:39 logrotate[12713]: error: error running shared postrotate script for '/var/log/apache2/*.log ' I'm not sure whether that bug should be sent to cron, logrotate, or apache2; I chose apache2 because I thought that a reload more or less just sends a signal to the active process, and so shouldn't cause any stop or other downtime. (Be it directly or via the systemd integration.) (OTOH, perhaps this is a systemd bug, in that a failed reload causes a stop?) Thanks for any help you can offer. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de_AT:de (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --
