• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Migration Error "tty"

J

jjsull49

Guest
Hello,

I've tried the documentation, but could not find a reference to this problem. Could someone here point me in the right direction.

Here's the error message I receive.
-----------------------
Cannot send scout to the remote host



Failed to execute scout.
The return code is 1
The output on STDERR is
sudo: sorry, you must have a tty to run sudo
-------------------

Thanks,

Jerry
 
Hello! Look as this.

Your sudo configuration file probably forbid execution of commands/scripts that are not attached to a TTY. You should edit your sudo configuration file to disable the requiretty option :

Code:
%visudo
#Defaults    requiretty
 
What about this?

Hello! Look as this.

Your sudo configuration file probably forbid execution of commands/scripts that are not attached to a TTY. You should edit your sudo configuration file to disable the requiretty option :

Code:
%visudo
#Defaults    requiretty

I've got the same situation, but the source box is virtual under Virtuozzo and I'm not certain why it won't let me do the visudo command I've seen mentioned and you've mentioned here?

Is that a restriction of Virt or what other options do I have to edit the sudo file to allow me to get the migration manager to work properly? It fails the same way as his and won't allow 'root' to work at all - even could log in that way via SSH or otherwise, always had to su root inside. So I apparently have to use sudo, but can't do that either!
 
Back
Top