Vestacp fails to start after server restart, system enters read-only mode

Vestacp fails to start after server restart, system enters read-only mode

When the server is restarted, vestacp does not start properly.

Error Tips:

[[email protected] vesta]# 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 Fri 2019-11-01 09:31:19 EDT; 2min 55s ago
Docs: man:systemd-sysv-generator(8)
Process: 6018 ExecStart=/etc/rc.d/init.d/vesta start (code=exited, status=1/FAILURE)

Nov 01 09:31:19 vestacp.xen.tn systemd[1]: Starting SYSV: Run vesta web server...
Nov 01 09:31:19 vestacp.xen.tn vesta[6018]: Starting vesta-nginx: nginx: [alert] could not open error log file: open() "/usr/local/vesta/nginx/logs/error.log" failed (30: Read-only file system)
Nov 01 09:31:19 vestacp.xen.tn vesta[6018]: 2019/11/01 09:31:19 [emerg] 6024#0: open() "/usr/local/vesta/log/nginx-error.log" failed (30: Read-only file system)
Nov 01 09:31:19 vestacp.xen.tn vesta[6018]: [FAILED]
Nov 01 09:31:19 vestacp.xen.tn systemd[1]: vesta.service: control process exited, code=exited status=1
Nov 01 09:31:19 vestacp.xen.tn systemd[1]: Failed to start SYSV: Run vesta web server.
Nov 01 09:31:19 vestacp.xen.tn systemd[1]: Unit vesta.service entered failed state.
Nov 01 09:31:19 vestacp.xen.tn systemd[1]: vesta.service failed.

The correct way:

sudo mount -o remount,rw /dev/vda1 /

/dev/vda1 Need to change to the drive letter used by your current system, we can query by the command “df -h”

Now we restart vestacp and we will see that the panel has run successfully.

systemctl restart vesta