• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Recent content by adijeff

  1. A

    Issue Server shut down randomly

    /var/log/dmesg doesn't have any timestamps on it, so I can't be sure. The server admins have said they will investigate the issue next Wednesday, so any hardware failures should be known then. I will post any results here. Thanks for all your help.
  2. A

    Issue Server shut down randomly

    /etc/yum.conf is there with 644 permissions: [main] cachedir=/var/cache/yum/$basearch/$releasever keepcache=0 debuglevel=2 logfile=/var/log/yum.log exactarch=1 obsoletes=1 gpgcheck=1 plugins=1 installonly_limit=5...
  3. A

    Issue Server shut down randomly

    No it's not OpenVZ, it's a dedicated server.
  4. A

    Issue Server shut down randomly

    Thanks Mark. I ran # yum -y update kernel: [root@server ~]# yum -y update kernel Loaded plugins: fastestmirror Setting up Update Process Loading mirror speeds from cached hostfile * rpmforge: mirror1.hs-esslingen.de base...
  5. A

    Issue Server shut down randomly

    Thanks Emerson. I already asked them, and they said: As for your link How to find out from the logs what caused system shutdown? I still don't know. When I use I get this which doesn't really help: [root@server ~]# last -x shutdown reboot reboot system boot 2.6.32-696.13.2. Wed Mar 7 08:27...
  6. A

    Issue Server shut down randomly

    Hi, My server randomly shut down yesterday morning at 5:01am and I'd be grateful for some help to work out why. CentOS 6.9 (Final)‬ Plesk 12.5.30 Update #74 Looking at the log files doesn't give me any clues. They are below. The only cron job except cron.hourly that is close to that time is...
  7. A

    No backup after update #52

    I can confirm MU#53 works. Thanks very much. I had to force the latest microupdate using: # /usr/local/psa/admin/sbin/autoinstaller --select-release-current --upgrade-installed-components
Back
Top