Issue "Import Dump" from file on server fails since update to 18.0.79

Steve Jeffery

New Pleskian
Server operating system version
Debian 12
Plesk version and microupdate number
18.0.79
We're in the process of migrating sites from Plesk on CentOS 7 to a new Debian 12 server. I've been rehearsing transferring database dumps using Export dump on the old server, and Import dump using "Import a dump stored on your hosting server" on the new, using *.sql.zip file(s) copied to the Subscription's hosting directory as this is quicker than using "Upload a dump from your local computer".
Up until today this worked perfectly but now reports:
  • filemng failed: filemng: Cannot open destination file '/tmp/duppcjllgq15qbf6cX5AiV': Permission denied
  • System error 13: Permission denied
The "Upload a dump from your local computer" option does still work but is far from ideal as one of our databases is 1.7GB even compressed.
The only change I'm aware of to the server since last week was the automatic update to Obsidian 18.0.79 this morning.
 
Further information from stderr, from the Task Manager


Code:
[2026-06-29 15:32:56.240] 12640:6a42821833943 ERR [util_exec] proc_close() failed ['/opt/psa/admin/bin/filemng' 'catdata' 'perm2cp' '/var/www/vhosts/test.catalyst-data.co.uk/catdata_2026-06-29_13-20-53.sql.zip' '/tmp/dup9rgi5gblai2p5OwsnWy' '0600'] with exit code [255]
[2026-06-29 15:32:56.365] 12640:6a42821833943 ERR [panel] Task failed: id=519, pid=12640, type=database-upload, error=PleskUtilException: filemng failed: filemng: Cannot open destination file '/tmp/dup9rgi5gblai2p5OwsnWy': Permission denied
System error 13: Permission denied
file: /opt/psa/admin/plib/Service/Agent.php
line: 159
code: 0
trace: #0 /opt/psa/admin/plib/Service/Driver/Filesystem/Plesk/Unix.php(577): Service_Agent->execAndGetResponse(string 'filemng', array, NULL null, array, boolean false, boolean false)
#1 /opt/psa/admin/plib/Service/Driver/Filesystem/Plesk/Unix.php(484): Service_Driver_Filesystem_Plesk_Unix->_execAndGetResponse(array)
#2 /opt/psa/admin/plib/FileManager.php(419): Service_Driver_Filesystem_Plesk_Unix->perm2cp(string 'catdata', string '/var/www/vhosts/test.catalyst-data.co.uk/catdata_2026-06-29_13-20-53.sql.zip', string '/tmp/dup9rgi5gblai2p5OwsnWy', string '0600')
#3 /opt/psa/admin/plib/Database/Task/Upload.php(40): FileManager->copyFromWebspace(string '/var/www/vhosts/test.catalyst-data.co.uk/catdata_2026-06-29_13-20-53.sql.zip', string '/tmp/dup9rgi5gblai2p5OwsnWy', string '0600')
#4 /opt/psa/admin/plib/Db/Table/Broker/LongTasks.php(178): Plesk\Database\Task\Upload->run()
#5 /opt/psa/admin/plib/Db/Table/Broker/LongTasks.php(113): Db_Table_Broker_LongTasks->_syncStart(object of type Db_Table_Row_LongTask)
#6 /opt/psa/admin/plib/Task/Async/Executor.php(54): Db_Table_Broker_LongTasks->runTaskWithinExecutor(object of type Db_Table_Row_LongTask)
#7 /opt/psa/admin/plib/scripts/task-async-executor.php(6): Task_Async_Executor->execute()

[2026-06-29 15:32:56.368] 12640:6a42821833943 ERR [panel] Long task executor: id=519 completed with error: filemng failed: filemng: Cannot open destination file '/tmp/dup9rgi5gblai2p5OwsnWy': Permission denied
System error 13: Permission denied:
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
 
Hi, @Steve Jeffery . I was able to replicate the behavior and opened an internal report for our team to further review the matter. I will follow up with more details as soon as possible. Thank you for your patience in the meantime.
 
@Steve Jeffery , thank you for bringing our attention to the issue. The behavior was recognized as a bug identified with ID PPPM-15419. Until the bug is fixed, the only workaround we can suggest is downloading the database dump locally and then importing it using “Upload a dump from your local computer” option. At this point, I cannot provide an ETA for the fix.
 
@Steve Jeffery , thank you for bringing our attention to the issue. The behavior was recognized as a bug identified with ID PPPM-15419. Until the bug is fixed, the only workaround we can suggest is downloading the database dump locally and then importing it using “Upload a dump from your local computer” option. At this point, I cannot provide an ETA for the fix.
I have worked around it by unzipping the dump on the target server and importing using the sql command line, which, now I've included that in my sync script after I rsync the content across from the old server, is more straightforward than having to go via the control panel. No urgency from me for now then, thank you.
 
Back
Top