Vesta cant start, Files in Read Only

[Vegas10128]

I recently had a long term power outage which was unreported to me.
Caused the battery backup to shut off after being used on battery instantly shutting the vesta server off.

When starting the server, all of the vesta, apache, nginx, sql, services fail upon booting.

I type command
"Service Vesta Start"
and receive the following response.

Code: Select all

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

After seeing this i follow the following request typing in the systemctl status and have this

Code: Select all

● vesta.service - LSB: starts the vesta control panel
   Loaded: loaded (/etc/init.d/vesta; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2020-05-29 06:17:54 CDT; 3min 48s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 13622 ExecStart=/etc/init.d/vesta start (code=exited, status=1/FAILURE)

May 29 06:17:54 SRV1 systemd[1]: Starting LSB: starts the vesta control panel...
May 29 06:17:54 SRV1 vesta[13622]:  * Starting vesta-nginx vesta-nginx
May 29 06:17:54 SRV1 vesta[13622]: nginx: [alert] could not open error log file: open() "/usr/local/vesta/nginx/logs/
May 29 06:17:54 SRV1 vesta[13622]: 2020/05/29 06:17:54 [emerg] 13629#0: open() "/usr/local/vesta/log/nginx-error.log"
May 29 06:17:54 SRV1 systemd[1]: vesta.service: Control process exited, code=exited status=1
May 29 06:17:54 SRV1 systemd[1]: Failed to start LSB: starts the vesta control panel.
May 29 06:17:54 SRV1 systemd[1]: vesta.service: Unit entered failed state.
May 29 06:17:54 SRV1 systemd[1]: vesta.service: Failed with result 'exit-code'.

and this

Code: Select all

/error.log" failed (30: Read-only file system)
" failed (30: Read-only file system)

how can i fix this read only file system issue?
Has anyone ever experienced this before?

My O/s is Ubuntu 16.04, with PHP 7.1

UPDATE: The file system /dev/sda1 is in read only mode, cannot get the file system out of read only mode.
says "busy"

[iotheme]

Maybe:
- chmod 640
- remount with write
- sda1 full disk
- sda1 full inodes

[Vegas10128]

Hello iotheme!

Thank you for your help!

I recently was able to fix the issue by
unmounting dev/sda1

running fschk -f /dev/sda1

and then
sudo shutdown -f

did a complete power off, waited a minute, powered back on again.
Logged into the terminal, and
sudo service vesta start

did no receive any errors after that. I was able to log into vesta panel and all my sites are online now.

[iotheme]

Hello iotheme!

Thank you for your help!

I recently was able to fix the issue by
unmounting dev/sda1

running fschk -f /dev/sda1

and then
sudo shutdown -f

did a complete power off, waited a minute, powered back on again.
Logged into the terminal, and
sudo service vesta start

did no receive any errors after that. I was able to log into vesta panel and all my sites are online now.

You should check full disk and full inodes. When you restart, all file in /tmp and some dir will be delete and it look like good first time but not long time.