- Server operating system version
- CentOS Linux 7.9.2009 (Core)
- Plesk version and microupdate number
- Plesk Obsidian Version 18.0.49 Update #2
Brief history:
Since 20 days I have a new dedicated server (fresh installation) Plesk Obsidian Version 18 on CentOS Linux 7.9.2009 (Core). Until the beginning of the year I had an identical configuration on identical hardware in use for nine months and increasingly (other post later) a frozen system from December onwards, so that a RESET was necessary at ever shorter intervals. Research into the causes of the hardware remained without any success. Finally, the Raid1 collapsed at the beginning of January and took the file system with it into nirvana, so that I am now productive again with a new server and restore of the webs.
The problem: The fresh dedicated server with only a few adjustments and only a restore of the websites (server adjustments were made manually after the IONOS rollout was completed) also had two "hang-ups" in 20 days and needed a RESET, after which the RAID1 was successfully rebuilt in each case (my provider only supports software RAID1).
Since I cannot identify any other activities on the server (and there was neither load nor traffic worth mentioning during the periods), I would like to find out whether the combination of CentOS Linux 7.9.2009 and Obsidian is the "best" choice for planning a pending repeated hardware change.
My previous system was Centos 6 and Plesk 11-12.5 and ran for eight years with no problems... so the many necessary hardware reboots are now not only a hassle, but a major topic for me.
Details of the provider's HW (if any relevance):
Possible OS variants on the part of the provider:
Many thanks in advance!
Since 20 days I have a new dedicated server (fresh installation) Plesk Obsidian Version 18 on CentOS Linux 7.9.2009 (Core). Until the beginning of the year I had an identical configuration on identical hardware in use for nine months and increasingly (other post later) a frozen system from December onwards, so that a RESET was necessary at ever shorter intervals. Research into the causes of the hardware remained without any success. Finally, the Raid1 collapsed at the beginning of January and took the file system with it into nirvana, so that I am now productive again with a new server and restore of the webs.
The problem: The fresh dedicated server with only a few adjustments and only a restore of the websites (server adjustments were made manually after the IONOS rollout was completed) also had two "hang-ups" in 20 days and needed a RESET, after which the RAID1 was successfully rebuilt in each case (my provider only supports software RAID1).
Since I cannot identify any other activities on the server (and there was neither load nor traffic worth mentioning during the periods), I would like to find out whether the combination of CentOS Linux 7.9.2009 and Obsidian is the "best" choice for planning a pending repeated hardware change.
My previous system was Centos 6 and Plesk 11-12.5 and ran for eight years with no problems... so the many necessary hardware reboots are now not only a hassle, but a major topic for me.
Details of the provider's HW (if any relevance):
- Supermicro H8SCM
- AMD Opteron(tm) Processor 4274 HE / 4228 HE
- 16 GB ECC
- SATA Enterprise HDD RAID1 (SW)
Possible OS variants on the part of the provider:
- CentOS 7
- Debian 10 (Dedicated)
- Debian 11 (vHost)
- Ubuntu 22.04 LTS
Many thanks in advance!