- Server operating system version
- Debian 12.12 (and Ubuntu 24.04.3 LTS)
- Plesk version and microupdate number
- Obsidian 18.0.73
Hello.
Quick summary :
I upgraded a Debian 10 server to Debian 11 and then to Debian 12 using this Plesk documentation : https://support.plesk.com/hc/en-us/...-upgrade-procedure-on-Linux-server-with-Plesk
While the server was on Debian 10 with Plesk in 18.0.70, there was a planified task on one website that previously worked.
After upgrading to Debian 12, I updated Plesk from 18.0.70 to 18.0.73.
At first, there was some dependencies issues :
I have resolved them by copying all wget’s dependencies into the lib/x86_64-linux-gnu folder of the website.
After that, the error changed into :
The task was and is still configured at the website's level (Domains > domain.tld > Development Tools -> Planified Task).
By going into the Tools & Settings menu, then in Tools & Ressources > Planified Task > Settings, the crontab's shell is selected on /bin/bash (chrooted).
It seemed odd to me that there was no error detail anymore from the task scheduler. So I looked into the following log file and got this error right after executing the task :
I tried to create a new website and then executing the same planified task, same error. I did plesk repair installation/all, nothing.
Even tried on another Plesk server that I upgraded from Ubuntu 20.04 to 22.04 and then 24.04, same error.
Maybe someone has an idea of what could possibly be wrong ?
I could provide more logs if necessary.
Kind regards,
Quick summary :
I upgraded a Debian 10 server to Debian 11 and then to Debian 12 using this Plesk documentation : https://support.plesk.com/hc/en-us/...-upgrade-procedure-on-Linux-server-with-Plesk
While the server was on Debian 10 with Plesk in 18.0.70, there was a planified task on one website that previously worked.
Bash:
wget -q -O - "https://domain.tld/module/gsitemap/cron?token=297d9f7x6q3&id_shop=1"
At first, there was some dependencies issues :
Bash:
wget: error while loading shared libraries: libnettle.so.8: cannot open shared object file: No such file or directory
I have resolved them by copying all wget’s dependencies into the lib/x86_64-linux-gnu folder of the website.
Bash:
cp `ldd /usr/bin/wget | grep "=>" | awk '{print $3}'` /var/www/vhosts/domain.tld/lib/x86_64-linux-gnu
After that, the error changed into :
Bash:
The task "wget -q -O - "https://domain.tld/module/gsitemap/cron?token=297d9f7x6q3&id_shop=1"" completed with an error in 0 seconds.
The task was and is still configured at the website's level (Domains > domain.tld > Development Tools -> Planified Task).
By going into the Tools & Settings menu, then in Tools & Ressources > Planified Task > Settings, the crontab's shell is selected on /bin/bash (chrooted).
It seemed odd to me that there was no error detail anymore from the task scheduler. So I looked into the following log file and got this error right after executing the task :
Bash:
cat /var/log/plesk/panel.log
[2025-10-02 15:52:29.683] 1527389:68de839d49383 ERR [panel] Task failed: id=49445, pid=1527389, type=scheduler-run-task, error=PleskUserException: Scheduled task failed
file: /opt/psa/admin/plib/Scheduler/RunTask.php
line: 54
code: 0
trace: #0 /opt/psa/admin/plib/Db/Table/Broker/LongTasks.php(178): Scheduler_RunTask->run()
#1 /opt/psa/admin/plib/Db/Table/Broker/LongTasks.php(113): Db_Table_Broker_LongTasks->_syncStart(object of type Db_Table_Row_LongTask)
#2 /opt/psa/admin/plib/Task/Async/Executor.php(54): Db_Table_Broker_LongTasks->runTaskWithinExecutor(object of type Db_Table_Row_LongTask)
#3 /opt/psa/admin/plib/scripts/task-async-executor.php(6): Task_Async_Executor->execute()
[2025-10-02 15:52:29.704] 1527389:68de839d49383 ERR [panel] Long task executor: id=49445 completed with error: Scheduled task failed:
0: /opt/psa/admin/plib/Task/Async/Executor.php:56
Task_Async_Executor->execute()
1: /opt/psa/admin/plib/scripts/task-async-executor.php:6
I tried to create a new website and then executing the same planified task, same error. I did plesk repair installation/all, nothing.
Even tried on another Plesk server that I upgraded from Ubuntu 20.04 to 22.04 and then 24.04, same error.
Maybe someone has an idea of what could possibly be wrong ?
I could provide more logs if necessary.
Kind regards,