Transport error: unable to list directory: Curl error: Access denied to remote resource

[Elliott_Veares]

Hi all, I seem to have an error with backing up to my personal FTP repository. I have only just noticed the issue, but i believe it originated when I upgraded Plesk Panel 11 to Plesk Panel 12. I am currently running version 12.0.18 on Cent OS 6.5.

Note whether i check the "Use passive mode" option makes no difference to my problem.

Below is what I get from the panel.log under /usr/local/psa/admin/logs

[2014-11-20 19:49:44] ERR [util_exec] proc_close() failed
[20-Nov-2014 19:49:44 UTC] PleskUtilException: '/usr/local/psa/admin/bin/pmm-ras' '--check-repository' '--dump-storage=ftp://USERNAME@IPADDRESS/MYFTPDIRECTORY/' '--use-ftp-passive-mode' failed with code 121.

stdout:
Transport error: unable to list directory: Curl error: Access denied to remote resource


stderr:

file: /usr/local/psa/admin/plib/Service/Agent/Transport/Local/Exec.php
line: 57
code: 0
trace: #0 /usr/local/psa/admin/plib/Service/Agent/Transport/Local.php(60): Service_Agent_Transport_Local_Exec->process(0, Object(Service_Agent_Command_Exec), Object(Service_Agent_Transport_LocalTransaction))
#1 /usr/local/psa/admin/plib/Service/Agent/Transport/Local.php(26): Service_Agent_Transport_Local->_command(0, Object(Service_Agent_Command_Exec), Object(Service_Agent_Transport_LocalTransaction))
#2 /usr/local/psa/admin/plib/Service/Agent.php(172): Service_Agent_Transport_Local->process('d212da78953cdf9...', Array)
#3 /usr/local/psa/admin/plib/backup/PmmRas/Connector.php(240): Service_Agent->commit()
#4 /usr/local/psa/admin/plib/backup/PmmRas/Connector.php(198): backup_PmmRas_Connector->_execNoThrow(Array, Array)
#5 /usr/local/psa/admin/plib/backup/BackupFTPRepositorySettings.php(237): backup_PmmRas_Connector->checkFtpRepository(Object(PMMDumpsStorageCredentials))
#6 /usr/local/psa/admin/plib/backup/BackupFTPRepositorySettings.php(211): BackupFTPRepositorySettings::testRepositoryConnection(Array)
#7 /usr/local/psa/admin/plib/backup/BackupFTPRepositorySettings.php(152): BackupFTPRepositorySettings::checkFtpConnectionParams(Array, true)
#8 /usr/local/psa/admin/plib/CommonPanel/Form/Backup/FtpSettings.php(133): BackupFTPRepositorySettings->check()
#9 /usr/local/psa/admin/plib/CommonPanel/Controller/Action/Backup/Trait.php(266): CommonPanel_Form_Backup_FtpSettings->isValid(Array)
#10 /usr/local/psa/admin/externals/Zend/Controller/Action.php(516): Admin_BackupController->ftpSettingsAction()
#11 /usr/local/psa/admin/externals/Zend/Controller/Dispatcher/Standard.php(295): Zend_Controller_Action->dispatch('ftpSettingsActi...')
#12 /usr/local/psa/admin/externals/Zend/Controller/Front.php(954): Zend_Controller_Dispatcher_Standard->dispatch(Object(Zend_Controller_Request_Http), Object(Zend_Controller_Response_Http))
#13 /usr/local/psa/admin/plib/Application/Web.php(38): Zend_Controller_Front->dispatch(NULL)
#14 /usr/local/psa/admin/htdocs/application.php(15): Plesk\Application_Web->run()
#15 {main}

Further more, this is what get from my backup manger's log.

Error: server "server"
Can't upload file 'backup_info_1411080213.xml' to ftp. Error code: 1
Warning: domain "mydomain.co.uk"
Domain mydomain.co.uk is skipped from backup due to error: Can't use string ("") as a HASH ref while "strict refs" in use at /usr/local/psa/PMM/agents/PleskX/DAL.pm line 924.

Also running "curl --list-only --user USERNAMEASSWORD ftp://IPADDRESS/" works fine from the shell/bash and lists my ftp servers directories.

I don't know what is casing my issues, but i want to resolve it asap. I have tried opening all high ports along with opening ports 20 and 21 and disabling firewall's etc... but these things have not helped.

Any help much appreciated.

Regards: Elliott Veares

Edit: solved - see latest post.

 

[domenik]

Hi all, I seem to have an error with backing up to my personal FTP repository. I am currently running version 12 on Cent OS 7.

Note whether i check the "Use passive mode" option makes no difference to my problem.

I get the following error message when trying to add my FTP Repository:
Transport error: unable to create directory: Curl error: Access denied to remote resource

Plesk 12 (newest) & CentOS7 // Debian 7 & Plesk 12 on both systems the same issue!

Also running "curl --list-only --user USERNAME : PASSWORD ftp://IPADDRESS/" works fine from the shell/bash and lists my ftp servers directories! Desktop clients like Filezilla are working normal.

I need this issue solved because I can't make ANY Backups....

 

[IgorG]

Looks like there is uncompleted successfully upgrade in initial issue. I think that DAL.pm has been changed but /usr/local/psa/admin/plib/backup/Serializer/DatabaseUsers.php not. Try to fix upgrade with bootstrapper repair procedure at least. Or contact Support Team if it not help.

 

[domenik]

I did the repair procedure on BOTH systems but the error persists! Check repair log for CentOS 7 machine:

Also i noticed a second issue on this machine, there is an emtpy /var/log/maillog no mail actions get logged. There a few mailaccounts used on this machine... something is really wrong!

START Bootstrapper 12.0.18 repair AT Mon Feb  2 18:54:21 CET 2015

**** Product repair started.

===> Checking for previous installation ... found.
Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.

Trying to start service mariadb... done
Trying to establish test connection... connected
done
Trying to start service mariadb... done
Trying to establish test connection... connected
done
Trying to find psa database... version is 012000018
Version is OK, no need to create psa database.
Trying to backup MySQL database... Warning: Not dumping MySQL database 'atmail' as it doesn't exist
done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.12.0.18-12.0.18.20150202-185421.dump.gz
Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
Upgrade or repair for 'apsc' (stage 'prep') is not required
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.apsc.12.0.18-12.0.18.20150202-185423.dump.gz
===> Cumulative upgrade and repair of APS controller database has been completed.
Connection to APSC DB is possible
===> Cumulative APS controller upgrade and repair (final stage) has been started.
Upgrade or repair for 'apsc' (stage 'post') is not required
===> Cumulative upgrade and repair of APS controller (final stage) has been completed.
ERROR 1045 (28000): Access denied for user 'pp_sb_db'@'localhost' (using password: NO)
Trying to reset database user password for 'pp_sb_db@'... ERROR 1133 (42000) at line 1: Can't find any matching row in the user table
ERROR 1133 (42000) at line 1: Can't find any matching row in the user table

WARNING!
Some problems are found during reset database user password for 'pp_sb_db@' - database user does not exist.(see log file: /var/log/plesk/install/plesk_12.0.18_repair.log)

Continue...

Trying to reset database user password for 'pma_IoU8hLkCbUeH@%'... done
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
Upgrade or repair for 'core' (stage 'prep') is not required
===> Preparing Plesk database upgrade (revertable stage).

Trying to set psa database version to 012000018... done
===> Cumulative upgrade and repair of Plesk database (revertable stage) has been completed.
Database is up-to-date
===> Cumulative Plesk upgrade and repair (final stage) has been started.
Upgrade or repair for 'core' (stage 'post') is not required
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade and repair of Plesk (final stage) has been completed.
Trying to upgrade and repair SpamAssassin service configuration... Upgrade or repair for 'spamassassin' (stage 'files') is not required
done
Trying to upgrade and repair Courier-IMAP services configuration (prep stage)... Upgrade or repair for 'courier_imap' (stage 'prep') is not required
done
Trying to upgrade and repair Courier-IMAP services configuration (post stage)... Upgrade or repair for 'courier_imap' (stage 'post') is not required
done
Trying to upgrade and repair Courier-IMAP services configuration (bootstrapper-post stage)... Upgrade or repair for 'courier_imap' (stage 'bootstrapper-post') is not required
done
Trying to condrestart service courier-imapd... done
Trying to condrestart service courier-imaps... done
Trying to condrestart service courier-pop3d... done
Trying to condrestart service courier-pop3s... done
Trying to upgrade and repair Roundcube webmail configuration... Upgrade or repair for 'roundcube' (stage 'files') is not required
done
Upgrade of Roundcube Web Based mail client configs and DB is not required - no previous version
Trying to upgrade and repair Horde webmail configuration...  Trying to convert Horde shares tables to sharesng... Delete existing shares from the NEW backend before migrating the OLD
backend? This should be done to avoid duplicate entries or primary key
collisions in the storage backend from earlier migrations.
    ([1my[0m) Yes
    ([1mn[0m) No

Type your choice [n]: Delete existing shares from the NEW backend before migrating the OLD
backend? This should be done to avoid duplicate entries or primary key
collisions in the storage backend from earlier migrations.
    ([1my[0m) Yes
    ([1mn[0m) No

Type your choice [n]: Delete existing shares from the NEW backend before migrating the OLD
backend? This should be done to avoid duplicate entries or primary key
collisions in the storage backend from earlier migrations.
    ([1my[0m) Yes
    ([1mn[0m) No

Type your choice [n]: done
done
Trying to upgrade and repair Fail2Ban configuration (bootstrapper-prep stage)... Upgrade or repair for 'fail2ban' (stage 'bootstrapper-prep') is not required
done
Trying to upgrade and repair Fail2Ban configuration (bootstrapper-post stage)... Upgrade or repair for 'fail2ban' (stage 'bootstrapper-post') is not required
done
Trying to upgrade and repair Firewall service configuration... Upgrade or repair for 'firewall' (stage 'post') is not required
done
Reconfiguring mail subsystem...
Trying to execute mail_restore to synchronize mail server settings and Plesk Database... ==> Checking for: mailsrv_conf_init... ok
==> Checking for: mail_handlers_init... ok
==> Checking for: mailsrv_entities_dump... ok
==> Checking for: mail_admin_aliases... ok
==> Checking for: mail_auth_dump... ok
==> Checking for: mailman_lists_dump... ok
==> Checking for: mail_kav8_restore... ok
==> Checking for: mail_responder_restore... ok
==> Checking for: mail_imap_restore... ok
==> Checking for: mail_spam_restore... ok
==> Checking for: mail_grey_restore... ok
==> Checking for: mail_mailbox_restore... ok
==> Checking for: mail_spf_restore... ok
==> Checking for: mail_dk_restore... ok
==> Checking for: mail_drweb_restore... not found, skipped
==> Checking for: mail_outgoing_restore... ok
==> Checking for: mail_transport_restore... ok
done
Reconfiguring Apache web server...
Reconfiguring ProFTPD FTP server...
Reconfiguring AWStats web statistics...
Reconfiguring WatchDog...
Restoring SELinux contexts...
Regenerating web servers' configuration files...
Cleaning active Panel sessions...

Bootstrapper repair finished.
If problems persist, please check installer logs ('/var/log/plesk/install/plesk_12.0.18_repair.log' and '/var/log/plesk/install/plesk_12.0.18_repair_problems.log') for errors.
If you can't resolve the issue on your own, please address Parallels support.

**** Product repair completed successfully.

STOP Bootstrapper 12.0.18 repair AT Mon Feb  2 18:55:41 CET 2015

 

[UFHH01]

Hi Domenik_Niemietz,

to solve your error with your "Presence Builder/Sitebuilder", you might have a look at:

Plesk upgrade failed - ERROR while trying to upgrade MySQL password format for Sitebuilder user ( KB - article 118 760 - this should work as well for Plesk 12, not only for Plesk 11 )


Please repeat the bootstrapper repair after you followed the suggestions from the KB - article and please post again your log - entries for the new procedure.

 

[domenik]

I repaired the issue with the sitebuilder. This does not fix the FTP and Maillogging issue!

Maillog is still empty.

Adding the FTP Repository still gives me this error:
http://droplr.c1d.me/1agjx/15zkCref

Repairlog:

**** Product repair started.

===> Checking for previous installation ... found.
Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.

Trying to start service mariadb... done
Trying to establish test connection... connected
done
Trying to start service mariadb... done
Trying to establish test connection... connected
done
Trying to find psa database... version is 012000018
Version is OK, no need to create psa database.
Trying to backup MySQL database... Warning: Not dumping MySQL database 'atmail' as it doesn't exist
done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.12.0.18-12.0.18.20150202-201418.dump.gz
Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
Upgrade or repair for 'apsc' (stage 'prep') is not required
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.apsc.12.0.18-12.0.18.20150202-201419.dump.gz
===> Cumulative upgrade and repair of APS controller database has been completed.
Connection to APSC DB is possible
===> Cumulative APS controller upgrade and repair (final stage) has been started.
Upgrade or repair for 'apsc' (stage 'post') is not required
===> Cumulative upgrade and repair of APS controller (final stage) has been completed.
Trying to reset database user password for 'pma_IoU8hLkCbUeH@'... done
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
Upgrade or repair for 'core' (stage 'prep') is not required
===> Preparing Plesk database upgrade (revertable stage).

Trying to set psa database version to 012000018... done
===> Cumulative upgrade and repair of Plesk database (revertable stage) has been completed.
Database is up-to-date
===> Cumulative Plesk upgrade and repair (final stage) has been started.
Upgrade or repair for 'core' (stage 'post') is not required
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade and repair of Plesk (final stage) has been completed.
Trying to upgrade and repair SpamAssassin service configuration... Upgrade or repair for 'spamassassin' (stage 'files') is not required
done
Trying to upgrade and repair Courier-IMAP services configuration (prep stage)... Upgrade or repair for 'courier_imap' (stage 'prep') is not required
done
Trying to upgrade and repair Courier-IMAP services configuration (post stage)... Upgrade or repair for 'courier_imap' (stage 'post') is not required
done
Trying to upgrade and repair Courier-IMAP services configuration (bootstrapper-post stage)... Upgrade or repair for 'courier_imap' (stage 'bootstrapper-post') is not required
done
Trying to condrestart service courier-imapd... done
Trying to condrestart service courier-imaps... done
Trying to condrestart service courier-pop3d... done
Trying to condrestart service courier-pop3s... done
Trying to upgrade and repair Roundcube webmail configuration... Upgrade or repair for 'roundcube' (stage 'files') is not required
done
Upgrade of Roundcube Web Based mail client configs and DB is not required - no previous version
Trying to upgrade and repair Horde webmail configuration... Upgrade or repair for 'horde' (stage 'files') is not required
done
Trying to upgrade and repair Fail2Ban configuration (bootstrapper-prep stage)... Upgrade or repair for 'fail2ban' (stage 'bootstrapper-prep') is not required
done
Trying to upgrade and repair Fail2Ban configuration (bootstrapper-post stage)... Upgrade or repair for 'fail2ban' (stage 'bootstrapper-post') is not required
done
Trying to upgrade and repair Firewall service configuration... Upgrade or repair for 'firewall' (stage 'post') is not required
done
Reconfiguring mail subsystem...
Trying to execute mail_restore to synchronize mail server settings and Plesk Database... ==> Checking for: mailsrv_conf_init... ok
==> Checking for: mail_handlers_init... ok
==> Checking for: mailsrv_entities_dump... ok
==> Checking for: mail_admin_aliases... ok
==> Checking for: mail_auth_dump... ok
==> Checking for: mailman_lists_dump... ok
==> Checking for: mail_kav8_restore... ok
==> Checking for: mail_responder_restore... ok
==> Checking for: mail_imap_restore... ok
==> Checking for: mail_spam_restore... ok
==> Checking for: mail_grey_restore... ok
==> Checking for: mail_mailbox_restore... ok
==> Checking for: mail_spf_restore... ok
==> Checking for: mail_dk_restore... ok
==> Checking for: mail_drweb_restore... not found, skipped
==> Checking for: mail_outgoing_restore... ok
==> Checking for: mail_transport_restore... ok
done
Reconfiguring Apache web server...
Reconfiguring ProFTPD FTP server...
Reconfiguring AWStats web statistics...
Reconfiguring WatchDog...
Restoring SELinux contexts...
Regenerating web servers' configuration files...
Cleaning active Panel sessions...

Bootstrapper repair finished.
If problems persist, please check installer logs ('/var/log/plesk/install/plesk_12.0.18_repair.log' and '/var/log/plesk/install/plesk_12.0.18_repair_problems.log') for errors.
If you can't resolve the issue on your own, please address Parallels support.

**** Product repair completed successfully.

STOP Bootstrapper 12.0.18 repair AT Mon Feb  2 20:15:28 CET 2015

 

[UFHH01]

Hi Domenik_Niemietz,

did you check the KB - article 124 055 ( => Personal FTP repository: 'Curl error: Access denied to remote resource' <= ) for your FTP issue? Be aware that "list" doesn't include write permissions.

 

[UFHH01]

Hi Domenik_Niemietz,

for your "empty maillog" - issue: Could you please check with the suggestions from KB - article 118 350 ( => Maillog is not updated <= ), if the solutions help to solve your issue?

 

[Elliott_Veares]

Sorry!; I forgot to post ages ago that I solved the problem. I was simply entering the wrong password into plesk what was giving me the errors. DOH!

Stupid mistake on my part not realizing that the password I entered was not correct and thus could not connect to my FTP drive!