Can't start Vesta CP service
#1
Hello,

I setup a DO vps and installed security measures such as LES, Maldet, and CSF. I also disabled root logins. I then proceeded to install VestaCP but it failed to start. When I try starting the service, I get the following error: 

$ systemctl status vesta.service
vesta.service - SYSV: Run vesta web server
   Loaded: loaded (/etc/rc.d/init.d/vesta; bad; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2018-04-30 04:04:46 UTC; 9s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1522 ExecStart=/etc/rc.d/init.d/vesta start (code=exited, status=1/FAILURE)

Apr 30 04:04:46 nyc3-web-1 systemd[1]: Starting SYSV: Run vesta web server...
Apr 30 04:04:46 nyc3-web-1 vesta[1522]: /etc/rc.d/init.d/vesta: line 12: /etc/profile.d/vesta.sh: No such file or directory
Apr 30 04:04:46 nyc3-web-1 systemd[1]: vesta.service: control process exited, code=exited status=1
Apr 30 04:04:46 nyc3-web-1 systemd[1]: Failed to start SYSV: Run vesta web server.
Apr 30 04:04:46 nyc3-web-1 systemd[1]: Unit vesta.service entered failed state.
Apr 30 04:04:46 nyc3-web-1 systemd[1]: vesta.service failed.

Here's what happens when I try starting it up:

# systemctl start vesta.service
Job for vesta.service failed because the control process exited with error code. See "systemctl status vesta.service" and "journalctl -xe" for details.

Running  - journalctl -xe  - I get this: 

Apr 30 04Happywide3Happywide5 nyc3-web-1 polkitd[549]: Registered Authentication Agent for unix-process:2425:206832 (system bus name :1.48 [/usr/bin/pkttyagent --notify-fd 5 --fallb
Apr 30 04Happywide3Happywide5 nyc3-web-1 systemd[1]: Starting SYSV: Run vesta web server...
-- Subject: Unit vesta.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/lis...temd-devel
-- 
-- Unit vesta.service has begun starting up.
Apr 30 04Happywide3Happywide5 nyc3-web-1 vesta[2431]: /etc/rc.d/init.d/vesta: line 12: /etc/profile.d/vesta.sh: No such file or directory
Apr 30 04Happywide3Happywide5 nyc3-web-1 systemd[1]: vesta.service: control process exited, code=exited status=1
Apr 30 04Happywide3Happywide5 nyc3-web-1 systemd[1]: Failed to start SYSV: Run vesta web server.
-- Subject: Unit vesta.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/lis...temd-devel
-- 
-- Unit vesta.service has failed.
-- 
-- The result is failed.
Apr 30 04Happywide3Happywide5 nyc3-web-1 systemd[1]: Unit vesta.service entered failed state.
Apr 30 04Happywide3Happywide5 nyc3-web-1 systemd[1]: vesta.service failed.
Apr 30 04Happywide3Happywide5 nyc3-web-1 polkitd[549]: Unregistered Authentication Agent for unix-process:2425:206832 (system bus name :1.48, object path /org/freedesktop/PolicyKit1
lines 2636-2668/2668 (END)


Your help would be appreciated.
Reply
#2
Code:
Apr 30 04:04:46 nyc3-web-1 vesta[1522]: /etc/rc.d/init.d/vesta: line 12: /etc/profile.d/vesta.sh: No such file or directory

This particular line in the systemd journalctl logs suggests that you're missing a vital file (vesta.sh in /etc/profile.d) required for VestaCP to start. This file is called from the startup script of VestaCP in /etc/rc.d/init.d (a file just named vesta).

Check if the file is really gone. If it is there then there might be a problem with permissions and the system simply can't run it.

A side question: are you running VestaCP on a supported OS?


Try this:
Code:
echo "export VESTA='$VESTA'" > /etc/profile.d/vesta.sh
chmod 755 /etc/profile.d/vesta.sh
source /etc/profile.d/vesta.sh

Replace $VESTA with the path where stuff like bin/v-add-cron-vesta-autoupdate or /data/sessions is. $VESTA seems to define the main folder of VestaCP where all the executables are and so on. This is saved in a special file to make it available system wide.
Reply
#3
(2018-04-30, 2:52:51 pm)Monad Wrote:  
Code:
Apr 30 04:04:46 nyc3-web-1 vesta[1522]: /etc/rc.d/init.d/vesta: line 12: /etc/profile.d/vesta.sh: No such file or directory

This particular line in the systemd journalctl logs suggests that you're missing a vital file (vesta.sh in /etc/profile.d) required for VestaCP to start. This file is called from the startup script of VestaCP in /etc/rc.d/init.d (a file just named vesta).

Check if the file is really gone. If it is there then there might be a problem with permissions and the system simply can't run it.

A side question: are you running VestaCP on a supported OS?


Try this:
Code:
echo "export VESTA='$VESTA'" > /etc/profile.d/vesta.sh
chmod 755 /etc/profile.d/vesta.sh
source /etc/profile.d/vesta.sh

Replace $VESTA with the path where stuff like bin/v-add-cron-vesta-autoupdate or /data/sessions is. $VESTA seems to define the main folder of VestaCP where all the executables are and so on. This is saved in a special file to make it available system wide.

Thanks Monad! I checked that path and the vesta.sh file is completely gone. I'm on CentOS 7 x64. I'm not so sure the export will work if the file is missing. Should I try reinstalling or is the file somewhere else?
Reply
#4
I will backup data and reinstall the os as soon as possible. It may be other files that gone missing too. So in my advice please reinstall the vestaCP.
Reply
#5
@bennun

The echo command will create the file if it doesn't exist and the second command will give it the right permissions. The third command will make the variable and the path for it globally available by simply running the file and therefore setting the variable to the path of VestaCP.

If after that VestaCP still doesn't work I don't know what the best would be to do. Maybe a reinstallation could indeed help. I don't use VestaCP. Just tried to debug the error messages you got and find solutions for them. Of course a failed installation might keep throwing error after error until a clean and successful installation is performed.
Reply
#6
(2018-05-02, 1:31:29 am)Monad Wrote:  @bennun

The echo command will create the file if it doesn't exist and the second command will give it the right permissions. The third command will make the variable and the path for it globally available by simply running the file and therefore setting the variable to the path of VestaCP.

If after that VestaCP still doesn't work I don't know what the best would be to do. Maybe a reinstallation could indeed help. I don't use VestaCP. Just tried to debug the error messages you got and find solutions for them. Of course a failed installation might keep throwing error after error until a clean and successful installation is performed.

@Monad - Thanks for all your help. I tried your first method and got past the error, only to get similar error with nginx. I finally reinstalled and it all came up as expected. Very strange, but we're good now. Thanks everyone for your help!
Reply




Users browsing this thread: 1 Guest(s)