Log files bind mounts missing after reboot

**mikerhyner** · Jul 9th 2015

Issue:
When rebooting the i-mscp server, all the bind mounts providing log file access to the users to /var/www/virtual/<main_domain>/logs/<domain> are missing.
That bind mounts are not added to "/etc/fstab" (in difference to the bind mounts of the CronJobs and InstantSSH Plugins), but interestingly, after a configuration change (or de-activating, then activating a domain), the mount commands will be executed... but obviously, I don't want to manually disable and enable every domain manually to get the bind mounts back!

Expected Results:
After a server reboot, all mounts are there again. Imho, this can be done trough:
a) adding the mount commands to the fstab (can get huge, so probably not a really good idea)
b) triggering the code part that executes the bind mount commands when the imscp_daemon is started

Or do I miss something (e.g. startup script) so that doesn't happen?

Version: 1.2.9, Build: 20150703, Codename: Andromeda

Thank you for having a look on that...

**Nuxwin** · Jul 9th 2015

@mikerhyner

Which distro, codename?

The logs folders are normally mounted on reboot through a @reboot cronjob.

/etc/cron.d/imscp

Code

...
# Mount customer's httpd logs at reboot
@reboot root perl /var/www/imscp/engine/tools/imscp-httpd-logs-mngr > /var/log/imscp/imscp-httpd-logs-mngr.log 2>&1
...

Thus, there is maybe another problem.

**mikerhyner** · Jul 9th 2015

OK thank. But I get an error message (cannot connect to database) as the cronjob kicks in within /var/log/imscp/imscp-httpd-logs-mngr.log:

[^[[0;31mFATAL^[[0m] iMSCP::Bootstrapper::boot: Unable to connect to the SQL server: DBI connect('database=imscp;host=localhost;port=3306','root',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /var/www/imscp/engine/tools/../PerlLib/iMSCP/Database/mysql.pm line 102

ql.pm line 102

Where do you catch up the password for mysql root user?

Possibly helpful, I've installed:
- Debian 7.8
- MariaDB 5.5
- i-mscp 1.2.9

**Nuxwin** · Jul 9th 2015

@mikerhyner

The panel is running well? No database access problem for him?

The password is taken from the /etc/imscp/imscp.conf file. Don't change it there because it is encrypted.

The problem is maybe that the cronjob is run before the Mysql is started at reboot. I need to check that. Can you run the script manually:

Shell-Script

# perl /var/www/imscp/engine/tools/imscp-httpd-logs-mngr -v

And post the output?

You should see something like

Shell-Script

root@trusty:/usr/share/awstats# perl /var/www/imscp/engine/tools/imscp-httpd-logs-mngr -v
[DEBUG] iMSCP::Bootstrapper::lock: Acquire exclusive lock on /tmp/imscp-httpd-logs-mngr.lock
[DEBUG] iMSCP::Bootstrapper::boot: Booting backend...
[DEBUG] iMSCP::Config::_init: Tying /etc/imscp/imscp.conf
[DEBUG] iMSCP::Config::_loadConfig: Loading /etc/imscp/imscp.conf
[DEBUG] iMSCP::Config::_parseConfig: Parsing /etc/imscp/imscp.conf
[DEBUG] iMSCP::EventManager::register: Registering listener on the afterHttpdBuildConfFile event from Servers::httpd::apache_itk::_init
[DEBUG] iMSCP::Config::_init: Tying /etc/imscp/apache/apache.data
[DEBUG] iMSCP::Config::_loadConfig: Loading /etc/imscp/apache/apache.data
[DEBUG] iMSCP::Config::_parseConfig: Parsing /etc/imscp/apache/apache.data
[DEBUG] iMSCP::Execute::execute: mount 2>/dev/null | grep -q ' /var/www/virtual/test.tld/logs/test.tld '
[DEBUG] iMSCP::Execute::getExitCode: Command exited with value: 0
[DEBUG] iMSCP::Bootstrapper::unlock: Release exclusive lock on /tmp/imscp-httpd-logs-mngr.lock

Display More

**mikerhyner** · Jul 9th 2015

Yes, panel is running well besides that problem.

Because if I run the cronjob script maually, the log bind mounts are done, I guess that the @reboot cronjob will be started before mysql server(mariadb on my system to be exact, but shouldn't matter) is up & running.

For the moment as a "dirty" hack, I've added a sleep before perl, so the line within /etc/cron.d/imscp looks like this:
@reboot root sleep 30; perl /var/www/imscp/engine/tools/imscp-httpd-logs-mngr > /var/log/imscp/imscp-httpd-logs-mngr.log 2>&1

**Nuxwin** · Jul 9th 2015

@mikerhyner

Thank for your report. I'll check and fix in next release.

Could you open a ticket on our bugtracker?

**mikerhyner** · Jul 9th 2015

Thank you! Our thoughts have crossed

I will do if you open an account for me on bugtracker...

**Nuxwin** · Jul 9th 2015

@mikerhyner

You can register here: http://youtrack.i-mscp.net/registerUserForm

**rauschr** · Aug 3rd 2015

Why have to mount logs file?

The df -h output very strange.

**Nuxwin** · Aug 3rd 2015

@rauschr

Did you ever read the CHANGELOG?

https://github.com/i-MSCP/imscp/blob/1.2.x/CHANGELOG#L51

To resume, the log directories which are stored in /var/log/apache2 are now mounted in the logs directory of their respective owners (customers). This allow the customers to access their HTTP logs in real time and also to access the archived logs.

Also this allow to save diskspace and CPU time (The logs are no longer copied and thus, a cron task to copy them is no longer needed). This change has been introduced in i-MSCP version 1.2.9. However a small bug has been found: When you reboot the server, the logs are not automatically re-mounted because at time where the cron job which is responsible to mount them is run, the storage from which data are pulled from (The MySQL server) has not been started yet. This is fixed in the 1.2.x branch.

And please, saying The df -h output very strange." without give us further info is irrelevant...

Log files bind mounts missing after reboot

Share

Daily visitors