Fstab change causes Ubuntu 16.04 to enter maintanance mode on boot
Hello, when I boot our Ubuntu 16.04 host it runs into the maintenance mode.
When running 'journalctl -xb' the output is as following:
The start-up result is done.
Mar 27 13:46:10 www1 systemd[1]: var-www-clients-client6-web9-log.mount: Failed to check directory /var/www/clients/client6/web9/log: No such file or directory
Mar 27 13:46:10 www1 systemd[1]: Mounting /var/www/clients/client6/web9/log...
-- Subject: Unit var-www-clients-client6-web9-log.mount has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit var-www-clients-client6-web9-log.mount has begun starting up.
Mar 27 13:46:10 www1 systemd[1]: var-www-clients-client2-web2-log.mount: Failed to check directory /var/www/clients/client2/web2/log: No such file or directory
Mar 27 13:46:10 www1 mount[832]: mount: mount point /var/www/clients/client6/web9/log does not exist
Mar 27 13:46:10 www1 systemd[1]: Mounting /var/www/clients/client2/web2/log...
-- Subject: Unit var-www-clients-client2-web2-log.mount has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit var-www-clients-client2-web2-log.mount has begun starting up.
Mar 27 13:46:10 www1 systemd[1]: var-www-clients-client4-web6-log.mount: Failed to check directory /var/www/clients/client4/web6/log: No such file or directory
Mar 27 13:46:10 www1 mount[835]: mount: mount point /var/www/clients/client2/web2/log does not exist
Mar 27 13:46:10 www1 systemd[1]: Mounting /var/www/clients/client4/web6/log...
-- Subject: Unit var-www-clients-client4-web6-log.mount has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit var-www-clients-client4-web6-log.mount has begun starting up.
Mar 27 13:46:10 www1 systemd[1]: Starting File System Check on /dev/disk/by-uuid/ed7fdcae-8afa-4349-a442-99483213a69f...
-- Subject: Unit systemd-fsck@dev-disk-by\x2duuid-ed7fdcae\x2d8afa\x2d4349\x2da442\x2d99483213a69f.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-fsck@dev-disk-by\x2duuid-ed7fdcae\x2d8afa\x2d4349\x2da442\x2d99483213a69f.service has begun starting up.
Mar 27 13:46:10 www1 mount[838]: mount: mount point /var/www/clients/client4/web6/log does not exist
Mar 27 13:46:10 www1 systemd[1]: var-www-clients-client6-web9-log.mount: Mount process exited, code=exited status=32
Mar 27 13:46:10 www1 systemd[1]: Failed to mount /var/www/clients/client6/web9/log.
-- Subject: Unit var-www-clients-client6-web9-log.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit var-www-clients-client6-web9-log.mount has failed.
--
-- The result is failed.
Mar 27 13:46:10 www1 systemd[1]: Dependency failed for Local File Systems.
-- Subject: Unit local-fs.target has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit local-fs.target has failed.
--
-- The result is dependency.
Mar 27 13:46:10 www1 systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Mar 27 13:46:10 www1 systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
Mar 27 13:46:10 www1 systemd[1]: var-www-clients-client6-web9-log.mount: Unit entered failed state.
Mar 27 13:46:10 www1 systemd[1]: var-www-clients-client2-web2-log.mount: Mount process exited, code=exited status=32
Mar 27 13:46:10 www1 systemd[1]: Failed to mount /var/www/clients/client2/web2/log.
-- Subject: Unit var-www-clients-client2-web2-log.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit var-www-clients-client2-web2-log.mount has failed.
--
-- The result is failed.
Mar 27 13:46:10 www1 systemd[1]: var-www-clients-client2-web2-log.mount: Unit entered failed state.
Mar 27 13:46:10 www1 systemd[1]: var-www-clients-client4-web6-log.mount: Mount process exited, code=exited status=32
Mar 27 13:46:10 www1 systemd[1]: Failed to mount /var/www/clients/client4/web6/log.
-- Subject: Unit var-www-clients-client4-web6-log.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit var-www-clients-client4-web6-log.mount has failed.
--
-- The result is failed.
Mar 27 13:46:10 www1 systemd[1]: var-www-clients-client4-web6-log.mount: Unit entered failed state.
Mar 27 13:46:10 www1 systemd-fsck[840]: /dev/sdb1: clean, 31195/8192000 files, 758357/32767744 blocks
Mar 27 13:46:10 www1 systemd[1]: Started File System Check Daemon to report status.
-- Subject: Unit systemd-fsckd.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-fsckd.service has finished starting up.
--
Looking at the first error: 'Failed to check directory /var/www/clients/client6/web9/log: No such file or directory' is kinda strange as the folder does exist when I ls into.. And this is the same for all other directories mensioned in the journal output.
When looking in fstab file, I see ISPConfig has added three lines:
/var/log/ispconfig/httpd/... /var/www/clients/client2/web2/log none bind,nobootwait 0 0
/var/log/ispconfig/httpd/... /var/www/clients/client4/web6/log none bind,nobootwait 0 0
/var/log/ispconfig/httpd/... /var/www/clients/client6/web9/log none bind,nobootwait 0 0
When I comment these lines with an # and reboot the server it boots up correctly.
Our machine is running on Ubuntu 16.04 with ISPConfig 3.1.2 with nginx as webserver.