VestaCP Multiple services stopped on boot (but still works)
Posted: Thu Mar 26, 2015 12:37 am
Hi,
Im on Debian 7.8 (3.2.0-4-amd64 #1 SMP Debian 3.2.65-1+deb7u2 x86_64 GNU/Linux)
since a couple of days my server says

It also reports that fail2ban is stopped (further down the list)
I've checked the services in the terminal and it says:
The only thing that differs from the standard core-vesta-package is that i installed MySQL 5.6.23, but i did that when i installed Vesta and it worked like a charm for like 3 weeks.
If i reboot the server, some services would not be recognized as started and i cant use the Vesta panel to admin them.
Anyone else got this? Saw a post from last year, but that thread was dead.
PS. I can restart the services in console with service exim4 restart or /etc/init.d/exim4 restart, and the server restarts and works, but dont show up in Vesta.
Thanks in advance.
Pierre
Im on Debian 7.8 (3.2.0-4-amd64 #1 SMP Debian 3.2.65-1+deb7u2 x86_64 GNU/Linux)
since a couple of days my server says

It also reports that fail2ban is stopped (further down the list)
I've checked the services in the terminal and it says:
Code: Select all
root@xxxxx~ # service exim4 status
exim4.service - LSB: exim Mail Transport Agent
Loaded: loaded (/etc/init.d/exim4)
Active: active (running) since Thu, 26 Mar 2015 01:19:02 +0100; 6min ago
Process: 8917 ExecStop=/etc/init.d/exim4 stop (code=exited, status=0/SUCCESS)
Process: 8929 ExecStart=/etc/init.d/exim4 start (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/exim4.service
â”” 8938 /usr/sbin/exim4 -bd -q30m
root@xxxxx~ # service apache2 status
apache2.service - LSB: Start/stop apache2 web server
Loaded: loaded (/etc/init.d/apache2)
Active: active (running) since Thu, 26 Mar 2015 01:06:21 +0100; 18min ago
Process: 4510 ExecStop=/etc/init.d/apache2 stop (code=exited, status=0/SUCCESS)
Process: 4534 ExecStart=/etc/init.d/apache2 start (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/apache2.service
├ 4545 /usr/sbin/apache2 -k start
├ 4547 /usr/sbin/apache2 -k start
├ 4548 /usr/sbin/apache2 -k start
├ 4549 /usr/sbin/apache2 -k start
├ 4550 /usr/sbin/apache2 -k start
├ 4551 /usr/sbin/apache2 -k start
├ 4552 /usr/sbin/apache2 -k start
├ 4553 /usr/sbin/apache2 -k start
├ 4554 /usr/sbin/apache2 -k start
â”” 4555 /usr/sbin/apache2 -k start
root@xxxxx~ # service bind9 status
bind9.service - LSB: Start and stop bind9
Loaded: loaded (/etc/init.d/bind9)
Active: active (running) since Thu, 26 Mar 2015 01:11:18 +0100; 14min ago
Process: 6342 ExecStop=/etc/init.d/bind9 stop (code=exited, status=0/SUCCESS)
Process: 6353 ExecStart=/etc/init.d/bind9 start (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/bind9.service
â”” 6362 /usr/sbin/named -u bind
If i reboot the server, some services would not be recognized as started and i cant use the Vesta panel to admin them.
Anyone else got this? Saw a post from last year, but that thread was dead.
PS. I can restart the services in console with service exim4 restart or /etc/init.d/exim4 restart, and the server restarts and works, but dont show up in Vesta.
Thanks in advance.
Pierre