set net:persist-retries 1

Is this set to one?

Mine seems to try forever..

---- Connecting to box_with_no_ftp (1.2.3.4) port 21
**** Socket error (Connection refused) - reconnecting
---- Closing control socket
---- Connecting to box_with_no_ftp (1.2.3.4) port 21
**** Socket error (Connection refused) - reconnecting
---- Closing control socket
---- Connecting to box_with_no_ftp (1.2.3.4) port 21
**** Socket error (Connection refused) - reconnecting
---- Closing control socket
---- Connecting to box_with_no_ftp (1.2.3.4) port 21
**** Socket error (Connection refused) - reconnecting
---- Closing control socket
---- Connecting to box_with_no_ftp (1.2.3.4) port 21
**** Socket error (Connection refused) - reconnecting
---- Closing control socket
---- Connecting to box_with_no_ftp (1.2.3.4) port 21
**** Socket error (Connection refused) - reconnecting
---- Closing control socket
---- Connecting to box_with_no_ftp (1.2.3.4) port 21
**** Socket error (Connection refused) - reconnecting
---- Closing control socket
---- Connecting to box_with_no_ftp (1.2.3.4) port 21
**** Socket error (Connection refused) - reconnecting
---- Closing control socket
---- Connecting to box_with_no_ftp (1.2.3.4) port 21
**** Socket error (Connection refused) - reconnecting
---- Closing control socket
---- Connecting to box_with_no_ftp (1.2.3.4) port 21
**** Socket error (Connection refused) - reconnecting
---- Closing control socket
---- Connecting to box_with_no_ftp (1.2.3.4) port 21
**** Socket error (Connection refused) - reconnecting
---- Closing control socket
---- Connecting to box_with_no_ftp (1.2.3.4) port 21
**** Socket error (Connection refused) - reconnecting
---- Closing control socket



On Sat, 7 Jan 2006, Fredrik Arnell wrote:

Tried setting net:persist-retries to 1, 2, 3 and 10. On 1-3 nothing changed,
but with 10 the script just stalls and nothing happens.

Current line:
lftp -e "debug off -o /dev/null && set ftp:retry-530 "" && set
net:max-retries 2 && set net:persist-retries 2 && site $cmd && quit" -u
$user,$pass -p $port $host`;

One thing here, both ftp:retry-530 and net:persistas-retries seems to be
settings that are in use when CONNECTED to the server. My problem with the
fatal error is when I tries to connect to a server that is offline.

/ Fredrik

-----Ursprungligt meddelande-----
Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] För Justin
Piszcz
Skickat: den 7 januari 2006 22:22
Till: Fredrik Arnell
Kopia: [email protected]
Ämne: Re: SV: Disable fatal errors?

From the man page, what is this number set to?  Did you try setting it
higher?

       net:persist-retries (number)
              ignore  this number of hard errors. Useful to login to buggy
ftp
              servers which reply 5xx when there is too many users.


On Sat, 7 Jan 2006, Fredrik Arnell wrote:

That didn’t help, still getting those errors I'm afraid.

It maybe helps a bit to see the command I use:
lftp -e "debug off -o /dev/null && set ftp:retry-530 "" && set
net:max-retries 2 && site $cmd && quit" -u $user,$pass -p $port $host

and when I run it I get this:
[EMAIL PROTECTED]:~$ ./ftp_check.pl
site: Fatal error: max-retries exceeded
[EMAIL PROTECTED]:~$


/ Fredrik Arnell


-----Ursprungligt meddelande-----
Från: Justin Piszcz [mailto:[EMAIL PROTECTED]
Skickat: den 7 januari 2006 21:42
Till: Fredrik Arnell
Kopia: [email protected]
Ämne: Re: Disable fatal errors?

If you type set -a it will show you all of the things you can set.

set ftp:retry-530 "too many|overloaded|try (again |back )?later|is
restricted to|maximum number|number of connect|only.*session.*allowed|more
connection"

I believe this defines the regexes that determine whether the error is
fatal or not, perhaps setting it to "" may fix your problem?

Justin.

On Sat, 7 Jan 2006, Fredrik Arnell wrote:

Hi everyone. Im currently developing a perl script to connect and send a
command to an ftp server and return the answer.
Everything works, BUT if the remote server doesn't allow me to connect I
get
this error msg:
site: Fatal error: max-retries exceeded

Is there any switch or parameter to NOT send this kind of errors? Because
that sort of error messages makes crond to send a mail to the user I run
my
script as, because it detects as an "error". If I run the script "by
hand"
I
get those errors too, but the script continues to run until its done.

I tried with "debug off -o /dev/null", no luck there.

So is it possible to turn off this sort of errors without editing out the
event rising code about errors from the source code?



/ Fredrik Arnell








Reply via email to