• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Backup error: Runtime error: 'undef' password passed to makePasswordNode

T

Traged1

Guest
We get the following when trying to do a backup on RHEL3ES with PLESK 8.1

Runtime error: 'undef' password passed to makePasswordNode at /usr/local/psa/PMM/agents/shared/agent.include.pl line 282.

Anyone have any insight?
 
I'm getting the same exact error.

I'm getting that exact same error, i even tried "excluding" the domain where that line showed up, nothing happens, the error showes anyway.

but from the control panel, i can run backup for every client account. its a pain in the ***.
 
After Upgrade from 7.5.4 to 8.1 - i have the same Problem: Runtime error: 'undef' password passed to makePasswordNode at /usr/local/psa/PMM/agents/shared/agent.include.pl line 282. When i exclude the client-the backup works.

Lg
ps4you
 
i got rid of the problem by deleting 1 domain that was expired.

so i dont know what could have been happening.
 
I have problems with 2 Domains but they are not expired. When i backup this domains with the Plesk CP Backup the following error message are displayed:

Error in BackupState.doActivityRunner()
Traceback (most recent call last):
File "/usr/local/psa/admin/share/agent_runner/agent_runner.py", line 97, in doActivityRunner
newState = self.doActivity()
File "/usr/local/psa/admin/share/agent_runner/agent_runner.py", line 381, in doActivity
errtxt = runAgent(self, self.session)
File "/usr/local/psa/admin/share/agent_runner/agent_runner.py", line 249, in runAgent
cmd.spawn()
File "/usr/local/psa/admin/lib/python/subproc.py", line 237, in spawn
proc.run()
File "/usr/local/psa/admin/lib/python/subproc.py", line 193, in run
BaseSubprocess.run(self)
File "/usr/local/psa/admin/lib/python/subproc.py", line 177, in run
self.wait()
File "/usr/local/psa/admin/lib/python/subproc.py", line 197, in wait
BaseSubprocess.wait(self)
File "/usr/local/psa/admin/lib/python/subproc.py", line 187, in wait
raise NonzeroExitException(self, os.WEXITSTATUS(status))
NonzeroExitException: was finished with exit code 255

When i exclude this 2 Domains the backup is done without any error messages.

On the command line (cronjob)i must exclude the Client and the backup is working.

Kind regards

ps4you
 
We had to exlude the client to get the backup to complete, nothing else we tried would work at all.
 
Ok well this is still occurring, but I think i may have just found a new lead:

I have isolated the domain that is not able to be backed up by plesk.

Lets say domain1.com

Since the error refers to a password error, I tried resetting all the passwords for this domain account. that did not help,

I went in to the domain's setup button to see if there was any trouble I could find in there, and I noticed that I was unable to switch the webstats from being protected by the pleskdir login. This is the error I got:

Error: Unable to update hosting preferences: ProtDir::delete() failed: ProtectedDirUsersList::remove() failed: ProtDirUser::delete failed: Account::delete() failed:eek:bject ID is invalid

based on this error i believe that our backup trouble for this domain may in deed by becuase the username & password for the webstats protected directory is pooched.

Now I have to figuire out how to reset the password manually through Mysql console and we should have solved this issue for the back?
 
Back
Top