• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Failed sudo on Migration

P

Phoenix Rising

Guest
Hello All -

I need some help with a strange issue I'm encountering here.

I'm conducting a migration from one Plesk 8.1 server to another (also 8.1). Using the migration manager, I enter the correct IP address, login username (no SSH allowed as root on the "from" box), login password, and sudo password.

Hitting the next button of course makes Plesk do its thing, but then I get an interesting error:

Cannot send scout to the remote host


Failed to execute scout.
The return code is 1
The output on STDERR is

Sorry, try again.

Sorry, try again.

sudo: 2 incorrect password attempts



This is quite unusual as I double-checked the passwords five times to make sure they were right, and indeed executing a standard SSH request to the server works perfectly fine under the username I supplied, and I can indeed su - root on that server, with the exact password I supplied Plesk.

Just out of curiosity, I did a tail -f /var/log/messages WHILE this was going on. Here's a sample of what I found, and why I think there may be a problem - let's see what more experienced systems administrators here think.

Sep 14 04:40:20 zeus sshd(pam_unix)[2940]: session opened for user user by (uid=0)
Sep 14 04:40:34 zeus su(pam_unix)[2972]: authentication failure; logname=user uid=2525 euid=0 tty=pts/7 ruser=user rhost= user=root
Sep 14 04:40:42 zeus su(pam_unix)[2980]: session opened for user root by user(uid=2525)
Sep 14 04:40:55 zeus sshd(pam_unix)[3031]: session opened for user user by (uid=0)
Sep 14 04:40:56 zeus sudo(pam_unix)[3073]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=user
Sep 14 04:41:01 zeus sudo(pam_unix)[3098]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=user
Sep 14 04:41:09 zeus sshd(pam_unix)[3031]: session closed for user user

(Of course for privacy I've replaced the actual username from the logs with just "user" above.)

What I find interesting here is that in all cases, rhost is BLANK. In other words, is it possible that SSH and/or sudo are denying access to the root account because the remote host can't be identified?

If you think that's what's causing it, what could cause the remote host information to be blocked? I have a fairly fresh iptables setup on the new machine (where I'm initiating the migration from), could that be it? Or is there a problem with Plesk that I need to fix, or a setting I need to tweak?

Thanks for your help.

=============
Basic System Information
=============

"Old" Server w/ existing accounts: RHEL4, Plesk 8.1
"New" Server I'm trying to get accounts migrated to: FC4, Plesk 8.1
 
Back
Top