• Strange binkd behaviour

    From Tommi Koivula@2:221/1 to Björn Felten on Fri Mar 29 17:49:42 2019

    *** Answering a msg posted in area 'wwb_z2'.

    29 Mar 19 12:55, Björn Felten wrote to All:

    Since this is the most serious echo that I know of, with the best experts, I ask this question here.

    But this is the echo for binkd problems.

    It's happened two times now, that my binkd suddenly "died".

    I don't think it "dies". I see the same happening also, it just exits. I don't now why but it is related to the config change. Here only in Windows, not in OS/2 or Linux.

    The first time it happened a year ago or so, I discovered it after just a few hours and could restart it,

    And still you don't restart it automagically?

    but today Real Life caused me not to notice it for more than 12 hours.

    Bad excuse. :)

    This is what happened:

    + 29 Mar 00:19:31 [14804] addr: 2:423/81@fidonet
    - 29 Mar 00:19:31 [14804] OPT ND
    + 29 Mar 00:19:31 [14804] Remote requests ND mode

    + 29 Mar 00:19:42 [2212] binkd.inc changed!
    + 29 Mar 00:19:42 [2212] Reloading configuration...

    This is where I compiled the new nodelist for binkd.

    - 29 Mar 00:19:43 [2212] servmgr listen on *:24555
    + 29 Mar 00:19:49 [14804] sending r:\binkd\outbound\01A70051.CUT as 5c9d56be.pkt (1865)

    29 Mar 00:19:56 [9140] previous config is no longer in use, unloading

    And this is where binkd should change?

    + 29 Mar 00:19:57 [14804] sent: r:\binkd\outbound\01A70051.CUT (1865, 233.12 CPS, 2:423/81@fidonet) + 29 Mar 00:19:57 [14804] done (to 2:423/81@fidonet, failed, S/R: 1/0 (1865/0 bytes))

    29 Mar 00:19:57 [14804] restoring poll with `C' flavour
    ? 29 Mar 00:19:57 [14804] fidonet: unknown domain
    29 Mar 00:19:57 [14804] session closed, quitting...

    Uh huh?

    + 29 Mar 00:19:57 [12900] call to 2:201/0@fidonet
    29 Mar 00:19:57 [12900] trying bejo.dyndns.org [85.24.133.193]:9090...
    + 29 Mar 00:19:57 [13356] call to 2:203/412@fidonet
    29 Mar 00:19:57 [13356] trying p.itu.se [92.35.143.132]...
    + 29 Mar 00:19:57 [15856] call to 2:203/124@fidonet
    29 Mar 00:19:57 [15856] trying pepzi.eu [46.162.120.16]...
    29 Mar 00:19:57 [12900] connected
    + 29 Mar 00:19:57 [14204] call to 2:211/37@fidonet
    + 29 Mar 00:19:57 [12900] outgoing session with bejo.dyndns.org:9090 [85.24.133.193] + 29 Mar 00:19:57 [9092] call to 2:221/1@fidonet 29 Mar 00:19:57 [9092] trying f1.n221.z2.rbb.fidonet.fi [2001:470:1f15:cb0:f1d0:2:221:1]... + 29 Mar 00:19:57 [10484] call to 2:230/150@fidonet 29 Mar 00:19:57 [15856] connected

    And here's where binkd exited without prior notice. In the middle of sessions? Wazzup?

    'Tommi

    ---
    * Origin: rbb.fidonet.fi (2:221/1)
  • From Tommi Koivula@2:221/6 to Bj÷rn Felten on Fri Mar 29 18:19:30 2019
    Hi Bj÷rn.

    29 Mar 19 17:49:42, I wrote to you:

    *** Answering a msg posted in area 'wwb_z2'.

    29 Mar 19 12:55, Bj÷rn Felten wrote to All:

    Since this is the most serious echo that I know of, with the best experts,
    I ask this question here.

    But this is the echo for binkd problems.

    It's happened two times now, that my binkd suddenly "died".

    I don't think it "dies". I see the same happening also, it just exits. I don't now why but it is related to the config change. Here only in
    Windows,
    not in OS/2 or Linux.

    And here's the log:

    === Cut ===
    29 Mar 03:55:07 [1036] \bbs\binkd\nl2binkd.inc changed!
    29 Mar 03:55:07 [1036] Reloading configuration...
    29 Mar 03:55:07 [1036] previous config is no longer in use, unloading
    29 Mar 03:55:07 [1036] servmgr setsockopt (IPV6_V6ONLY): Protocol not avai
    29 Mar 03:55:07 [1036] servmgr listen on *:24554
    29 Mar 03:55:14 [5832] \bbs\binkd\nl2binkd.inc changed!
    29 Mar 03:55:14 [5832] Reloading configuration...
    29 Mar 03:55:14 [5832] previous config is no longer in use, unloading
    29 Mar 03:55:14 [1036] client manager (pid=5832) exited by signal 6
    === Cut ===

    Binkd 1.1a-99 (Feb 16 2019 19:09:59/CYGWIN_NT-5.2)
    Compilation flags: gcc, zlib, bzlib2, https, bwlim, af_force.
    Facilities: fts5004 ipv6

    'Tommi


    ---
    * Origin: 2001:470:1f15:cb0:f1d0:2:221:6 (2:221/6)
  • From Michiel van der Vlist@2:280/5555.1 to Tommi Koivula on Fri Mar 29 17:35:56 2019
    Hello Tommi,

    On Friday March 29 2019 17:49, you wrote to Björn Felten:

    It's happened two times now, that my binkd suddenly "died".

    I don't think it "dies". I see the same happening also, it just exits.
    I don't now why but it is related to the config change. Here only in Windows, not in OS/2 or Linux.

    I have always had the same problem, never was able to solve it. I just disabled
    binkd reloading on a change of config.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: Michiel's laptop (2:280/5555.1)
  • From Wilfred van Velzen@2:280/464 to Bjrn Felten on Fri Mar 29 17:49:15 2019

    *** Answering a msg posted in area WWB_Z2.

    Hi Bjrn,

    On 2019-03-29 17:09:12, you wrote to me:

    I know Michiel had comparable unexpected exits of the windows binkd
    he was using. I don't know if that's still happening or if it's
    fixed. Are you using a linux or windows version, and what version
    number?

    R:\binkd>> binkd -vv
    Binkd 1.1a-65 (Sep 21 2014 18:59:33/Win32)
    Compilation flags: mingw32, perldl, https, ntlm, amiga_4d_outbound, bwlim, ipv6, fsp1035.
    Facilities: fsp1035 ipv6

    That's a bit old, although nothing substantial has changed in later versions afair.

    Do you run it as a windows service? Under what windows version? There probably is an option you can set, what to do when the service exits. Look in your windows settings regarding this service...

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)