• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Can't connect to a server with plesk

clubcouleurs

New Pleskian
Server operating system version
Debian 10
Plesk version and microupdate number
Plesk Obsidian
Hey everyone,
I have this VPS (Linux, Debian 10) running until two days ago,
I discover that it is because of disk space, I fix the problem by making some space ...
It worked for like an Hour, and then it stopped completely,
I can't connect to my server via PLESK web interface anymore or to any websites hosted on that VPS,
I tried rescuing the system, now i can't connect via SSH or VNC, but I can't see any of my old data or files,
I'm sure they are somewhere else (sda2, ...) because my server is 100G, and when I tried to reinstall plesk it told me "Not enough space" ...

Please if anyone can help,
Thank you very much
 
Do you login as "root" via SSH? Or with another user and then escalate privileges to root with the "su" command? Could you please show the output of "df" afterwards?
 
Hey dear Peter,
Thank you for taking time to respond, I appreciate it.
Yes, I can login as "root" via SSH,
Here is the input of "df" :
Filesystem 1K-blocks Used Available Use% Mounted on
udev 4070360 0 4070360 0% /dev
tmpfs 816996 18796 798200 3% /run
/dev/sda2 101724144 54436480 42077296 57% /
tmpfs 4084964 0 4084964 0% / dev/shm
tmpfs 5120 0 5120 0% /run/lock
tmpfs 4084964 0 4084964 0% / sys/fs/cgroup
/dev/sda1 944120 47540 831404 6% /boot
tmpfs 816992 0 816992 0% /run/user/0

Thank you again
 
Looks o.k., because / is filled with 57%, so there must be something on it.
What's the output of these commands? As root:
systemctl status psa
systemctl status apache2
systemctl status nginx
?
 
Thank you dear Peter,
//////////////
CMD : systemctl status psa :
● psa.service - Plesk Panel
Loaded: loaded (/lib/systemd/system/psa.service; enabled; vendor preset: enabled)
Active: active (exited) since Wed 2023-08-30 18:36:48 CEST; 35min ago
Process: 782 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
Main PID: 782 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
Memory: 0B
CGroup: /system.slice/psa.service

Aug 30 18:36:48 vmi712061.contaboserver.net systemd[1]: Starting Plesk Panel...
Aug 30 18:36:48 vmi712061.contaboserver.net systemd[1]: Started Plesk Panel.
////////////
CMD : systemctl status apache2 :
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: failed (Result: resources)
Docs: Apache HTTP Server Version 2.4 Documentation - Apache HTTP Server Version 2.4

Aug 30 18:36:47 vmi712061.contaboserver.net systemd[1]: apache2.service: Failed to run 'start' task: Read-only file system
Aug 30 18:36:47 vmi712061.contaboserver.net systemd[1]: apache2.service: Failed with result 'resources'.
Aug 30 18:36:47 vmi712061.contaboserver.net systemd[1]: Failed to start The Apache HTTP Server.
///////////
CMD : systemctl status nginx
● nginx.service - Startup script for nginx service
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Drop-In: /usr/lib/systemd/system/nginx.service.d
└─respawn.conf
Active: activating (auto-restart) (Result: exit-code) since Wed 2023-08-30 19:13:55 CEST; 2s ago
Process: 31194 ExecStartPre=/bin/sh -c [ '${NGINX_ENABLED}' = 'yes' ] || { echo Not starting nginx as it is disabled in Ples
Process: 31196 ExecStartPre=/usr/sbin/nginx -t (code=exited, status=1/FAILURE)
 
The two interesting lines are:
Aug 30 18:36:47 vmi712061.contaboserver.net systemd[1]: apache2.service: Failed to run 'start' task: Read-only file system
Aug 30 18:36:47 vmi712061.contaboserver.net systemd[1]: apache2.service: Failed with result 'resources'.
This is related to an operating system or disk issue. It can have various reasons. Maybe you can work through some suggestions from How to Fix the "Read-Only File System" Error on Ubuntu
 
Hey dear Peter,
Thank you very much for your help,
I did a fsck as the article suggested it and reboot the system and everything is working perfectly as usual :)
Thank you again.
 
Back
Top