• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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