- Newest
- Most votes
- Most comments
Hello,
The connecting to your Lightsail instance via SSH. Free up disk space by clearing old log files with the commandsudo find /var/log -type f -name "*.log" -delete, and remove any unnecessary or large files. After freeing up space, restart Plesk and web services using sudo service psa restart, sudo service apache2 restart and sudo service nginx restartFinally monitor your disk space regularly with df -h to prevent future issues. https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-viewing-instance-burst-capacity.html
Hi Check Disk Space:
- Confirm Disk Usage: Verify that /dev/root is indeed using 100% disk space. You can use the df command in the terminal to check the disk usage.
- Identify Consuming Files or Processes: Use tools like du or ncdu to identify the files or processes that are consuming the most disk space. This will help you pinpoint the root cause of the issue.
. Analyze Logs:
- Plesk Logs: Check the Plesk logs for any error messages or clues related to the issue. Look for patterns that might indicate a specific problem.
- System Logs: Examine the system logs (e.g., /var/log/messages) for any relevant error messages. These logs can provide insights into system-wide issues that might be affecting Plesk.
Check Network Configuration:
- Firewall Rules: Ensure that your firewall rules are configured correctly to allow incoming traffic to Plesk and your websites. Check for any blocking rules that might be preventing access.
- DNS Settings: Verify that your DNS settings are pointing to the correct IP address of your Lightsail instance. Incorrect DNS settings can prevent users from accessing your Plesk control panel and websites.
Consider Temporary Solutions:
- Disable Plugins: If you're running WordPress sites, temporarily disable any plugins that might be causing issues. This can help isolate the problem and determine if a specific plugin is the culprit.
- Increase Disk Space: If disk space is indeed the primary issue, consider increasing the disk size of your Lightsail instance. This will provide more space for your files and prevent future disk space-related problems.
Lightsail Support: If you're unable to resolve the issue on your own, contact Lightsail support for assistance. They can provide expert guidance and help you troubleshoot the problem effectively.
Plesk Documentation: https://docs.plesk.com/en-US/obsidian/
Amazon Lightsail Documentation: https://docs.aws.amazon.com/lightsail/
Plesk Community Forums: https://talk.plesk.com/
AWS Forums: https://repost.aws/forums
Relevant content
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 2 years ago
Okay, so i got that and was able to get Apache and NGINX to work but now my MariaDB isn't starting up:
Sep 02 13:28:25 # mariadbd[3947]: 2024-09-02 13:28:25 0 [Note] InnoDB: FTS optimize thread exiting. Sep 02 13:28:25 # mariadbd[3947]: 2024-09-02 13:28:25 0 [Note] InnoDB: Starting shutdown... Sep 02 13:28:25 # mariadbd[3947]: 2024-09-02 13:28:25 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1" Sep 02 13:28:25 # mariadbd[3947]: 2024-09-02 13:28:25 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. Sep 02 13:28:25 # mariadbd[3947]: 2024-09-02 13:28:25 0 [Note] Plugin 'FEEDBACK' is disabled. Sep 02 13:28:25 # mariadbd[3947]: 2024-09-02 13:28:25 0 [ERROR] Unknown/unsupported storage engine: InnoDB Sep 02 13:28:25 # mariadbd[3947]: 2024-09-02 13:28:25 0 [ERROR] Aborting Sep 02 13:28:25 # systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE Sep 02 13:28:25 # systemd[1]: mariadb.service: Failed with result 'exit-code'. Sep 02 13:28:25 # systemd[1]: Failed to start MariaDB 10.6.18 database server.