Waiting for data timed out, asking user what to do.

I have I problem. I have a scheduled task running a script and it stoped working one week ago. When I run the exact same script "manualy" (logging on an start the task) it woks fine. In the logfile the differense is;

! 2010-01-30 07:20:09.553 Using username "username".
. 2010-01-30 07:20:24.553 Waiting for data timed out, asking user what to do.
. 2010-01-30 07:20:24.553 Asking user:
. 2010-01-30 07:20:24.553 Host has not answered for 15 seconds.
. 2010-01-30 07:20:24.553
. 2010-01-30 07:20:24.553 Wait for another 15 seconds? Pressing 'Abort' button will close session. ()
. 2010-01-30 07:20:24.553 Attempt to close connection due to fatal exception:
* 2010-01-30 07:20:24.553 Terminated by user.
. 2010-01-30 07:20:24.553 Closing connection.

! 2010-02-01 09:12:05.990 Using username "username".
. 2010-02-01 09:12:06.005 Session password prompt (username@sftpserver's password: )
. 2010-02-01 09:12:06.005 Using stored password.
! 2010-02-01 09:12:06.005 Authenticating with pre-entered password.
. 2010-02-01 09:12:06.005 Sent password
. 2010-02-01 09:12:06.005 Access granted
. 2010-02-01 09:12:06.005 Opened channel for session
. 2010-02-01 09:12:06.021 Started a shell/command

And the question is :
How can I change this behavior. It looks as if it's in a interactive mode in some way, waiting for user input at the screen.

It is not interactive. Maybe you internet connection is not valid until you start a session.

martin wrote:

It is not interactive. Maybe you internet connection is not valid until you start a session.

Well, I have put in a ping prior to connecting. Didn't help. Any tips on verifying that the connection is established before login on? And if not rety.

svenjonas wrote:

martin wrote:

It is not interactive. Maybe you internet connection is not valid until you start a session.

Well, I have put in a ping prior to connecting. Didn't help. Any tips on verifying that the connection is established before login on? And if not rety.

It works if the user that runs the scheduled task is loged on. So, my workaround is creating a autologon on the machine.

Hi,

I am facing same issue once in a day where scripts runs for every 30 mins and works fine.


! 2010-11-12 21:00:56.447 Using username "xyz".
. 2010-11-12 21:00:56.463 Offered public key
. 2010-11-12 21:00:56.463 Offer of public key accepted
! 2010-11-12 21:00:56.463 Authenticating with public key "rsakey"
. 2010-11-12 21:01:11.557 Waiting for data timed out, asking user what to do.
. 2010-11-12 21:01:11.557 Asking user:
. 2010-11-12 21:01:11.557 Host has not answered for 15 seconds.
. 2010-11-12 21:01:11.557
. 2010-11-12 21:01:11.557 Wait for another 15 seconds? ()
. 2010-11-12 21:01:11.557 Attempt to close connection due to fatal exception:
* 2010-11-12 21:01:11.557 Terminated by user.
. 2010-11-12 21:01:11.557 Closing connection.