1. Forum
  2. FIDO
  3. ELIST

  • Can't connect for update

    From Dan Clough@1:123/115 to Vincent Coen on Wed Feb 2 19:57:11 2022
    Hello Vince,

    Trying to do the MOD-UPD for the NHL echo, and can't seem to connect to your system... I see others have recently updated other echos, so it's a little strange. Haven't changed anything here, and have done UPD's in the past. Here's what I see in my logs:

    BINKOUT Attempting callout for 2:250/1@fidonet, file: /sbbs/fido/outbound.002/00fa0001.dlo
    BINKOUT JSBinkP/4 callout to 2:250/1@fidonet started
    BINKOUT Connecting to 2:250/1@fidonet at 80.229.38.173:24554
    BINKOUT Connection to 80.229.38.173:24554 failed (Error: Unable to connect)

    Any idea why I can't connect? Thanks
    --- SBBSecho 3.14-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)
  • From Vincent Coen@2:250/1 to Dan Clough on Thu Feb 3 13:25:04 2022
    Hello Dan!

    Wednesday February 02 2022 19:57, you wrote to me:

    Hello Vince,

    Trying to do the MOD-UPD for the NHL echo, and can't seem to connect
    to your system... I see others have recently updated other echos, so
    it's a little strange. Haven't changed anything here, and have done
    UPD's in the past. Here's what I see in my logs:

    BINKOUT Attempting callout for 2:250/1@fidonet, file: /sbbs/fido/outbound.002/00fa0001.dlo BINKOUT JSBinkP/4 callout to 2:250/1@fidonet started BINKOUT Connecting to 2:250/1@fidonet at 80.229.38.173:24554 BINKOUT Connection to 80.229.38.173:24554 failed
    (Error: Unable to connect)

    Any idea why I can't connect? Thanks

    Nope as I cannot find a failed inbound poll but I notice that you had a successful update a few hours later.

    It could have been because my system was busy as one site was rejecting some files and my system retried multi times to resend all 12+ hours of it.

    This is usually caused by the receiving system not ack'g the file once
    received - I Think.

    So all sorted then ?

    Vincent
    --- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
    * Origin: The Elist Maintainer (2:250/1)
  • From Dan Clough@1:123/115 to Vincent Coen on Thu Feb 3 19:44:00 2022
    Vincent Coen wrote to Dan Clough <=-

    Trying to do the MOD-UPD for the NHL echo, and can't seem to connect
    to your system... I see others have recently updated other echos, so
    it's a little strange. Haven't changed anything here, and have done
    UPD's in the past. Here's what I see in my logs:

    BINKOUT Attempting callout for 2:250/1@fidonet, file: /sbbs/fido/outbound.002/00fa0001.dlo BINKOUT JSBinkP/4 callout to 2:250/1@fidonet started BINKOUT Connecting to 2:250/1@fidonet at 80.229.38.173:24554 BINKOUT Connection to 80.229.38.173:24554 failed
    (Error: Unable to connect)

    Any idea why I can't connect? Thanks

    Nope as I cannot find a failed inbound poll but I notice that you
    had a successful update a few hours later.

    It could have been because my system was busy as one site was
    rejecting some files and my system retried multi times to resend
    all 12+ hours of it.

    This is usually caused by the receiving system not ack'g the file
    once received - I Think.

    So all sorted then ?

    Yes, all good. I did make another post here explaining what I found
    wrong - I was using an OLD fidonet nodelist so it was trying to connect
    to an old/wrong IP address. All updated and good, thanks.



    ... If it weren't for Edison we'd be using computers by candlelight
    === MultiMail/Linux v0.52
    --- SBBSecho 3.14-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)
  • From Vincent Coen@2:250/1 to Dan Clough on Sat Feb 5 15:16:52 2022
    Hello Dan!

    Thursday February 03 2022 19:44, you wrote to me:

    Vincent Coen wrote to Dan Clough <=-

    Trying to do the MOD-UPD for the NHL echo, and can't seem to
    connect to your system... I see others have recently updated other
    echos, so it's a little strange. Haven't changed anything here,
    and have done UPD's in the past. Here's what I see in my logs:

    BINKOUT Attempting callout for 2:250/1@fidonet, file:
    /sbbs/fido/outbound.002/00fa0001.dlo BINKOUT JSBinkP/4 callout to
    2:250/1@fidonet started BINKOUT Connecting to 2:250/1@fidonet at
    80.229.38.173:24554 BINKOUT Connection to 80.229.38.173:24554
    failed (Error: Unable to connect)

    Any idea why I can't connect? Thanks

    Nope as I cannot find a failed inbound poll but I notice that you
    had a successful update a few hours later.

    It could have been because my system was busy as one site was
    rejecting some files and my system retried multi times to resend
    all 12+ hours of it.

    This is usually caused by the receiving system not ack'g the file
    once received - I Think.

    So all sorted then ?

    Yes, all good. I did make another post here explaining what I found
    wrong - I was using an OLD fidonet nodelist so it was trying to
    connect to an old/wrong IP address. All updated and good, thanks.

    All sysop's should be obtaining and installing the latest nodelist - I have now
    switched to also using Z2DAILY as it is on a daily update from all zones.

    For the moment the NODELIST also comes in and updates the system although it might only last minutes or hours before the DAILY comes in - I will give it a few more weeks and drop NODELIST and stick to the Dailies providing there are no issues but so far it is good.


    Vincent

    --- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
    * Origin: The Elist Maintainer (2:250/1)