Anyone see this before?

First of all:

Binkd 1.1a-95 (Dec 10 2016 21:44:31/Win32)
Compilation flags: mingw32, zlib, perldl, https, ntlm, amiga_4d_outbound, bwlim,
ipv6.
Facilities: fts5004 ipv6

In the log:

- 16:48 [58216] SYS BlackIce
- 16:48 [58216] ZYZ fU
- 16:48 [58216] VER Mystic/1.12A39 binkp/1.0
+ 16:48 [58216] addr: 9:92/1@survnet (n/a or busy)
+ 16:48 [58216] addr: 46:2/104@agoranet
+ 16:48 [58216] addr: 39:170/8001@amiganet (n/a or busy)
+ 16:48 [58216] addr: 169:1/159@battlnet (n/a or busy)
+ 16:48 [58216] addr: 16:4901/4333@zyxelnet (n/a or busy)
+ 16:48 [58216] addr: 44:49/0@dorenet (n/a or busy)
+ 16:48 [58216] addr: 21:1/106@fsxnet
+ 16:48 [58216] addr: 80:49/0@retronet
+ 16:48 [58216] addr: 24:301/0@sportnet
+ 16:48 [58216] addr: 24:301/1@sportnet
+ 16:48 [58216] addr: 75:49/0@BBSnet (n/a or busy)
+ 16:48 [58216] addr: 432:1/124@vkradio (n/a or busy)
+ 16:48 [58216] addr: 75:0/0@BBSnet (n/a or busy)
+ 16:48 [58216] addr: 2:240/8001@fidonet
+ 16:48 [58216] pwd protected session (plain text)
? 16:48 [58216] send: {W32 API error 10055} No buffer space available
+ 16:48 [58216] done (from 46:2/104@agoranet, failed, S/R: 0/0 (0/0 bytes))
16:48 [58216] session closed, quitting...

Nick

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

On 26 Nov 18 16:49, Nick Andre said the following to All:

? 16:48 [58216] send: {W32 API error 10055} No buffer space available

Just to follow up on this.

This system was running for 3 months of up-time before this started occuring.

There was no choice but to reboot to fix this problem. BinkD would crash every time it was restarted, on the "buffer space" problem.

Nick

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

Hallo Nick!

26.11.2018 20:15, Nick Andre schrieb an All:

There was no choice but to reboot to fix this problem. BinkD would
crash every time it was restarted, on the "buffer space" problem.

Well, 2:240/8001 has problems receiving crashmail. If you send /8001 something,
the buggy buildin binkd mailer of mystic crashes the system by pulling up the cpu load to 100 percent. The Sysop needs to restart the computer, to solve the problem.

Nick

Bye/2 Torsten

... MAILBOX01 on OS2: up 10d 17h 00m load: 37 proc, 157 threads (tbupv1.0)
--- GoldED+ 1.1.5-18
* Origin: DatenBahn BBS Hamburg (2:240/5832)

On 27 Nov 18 17:39:00, Torsten Bamberg said the following to Nick Andre:

There was no choice but to reboot to fix this problem. BinkD would crash every time it was restarted, on the "buffer space" problem.

Well, 2:240/8001 has problems receiving crashmail. If you send /8001 something, the buggy buildin binkd mailer of mystic crashes the system by pulling up the cpu load to 100 percent. The Sysop needs to restart the computer, to solve the problem.

I am not running Mystic...

Nick

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

Hallo Nick!

27.11.2018 11:49, Nick Andre schrieb an Torsten Bamberg:

crash every time it was restarted, on the "buffer space"

problem. Well, 2:240/8001 has problems receiving crashmail. If you
send /8001 something, the buggy buildin binkd mailer of mystic
crashes the system by pulling up the cpu load to 100 percent. The
Sysop needs to restart the computer, to solve the problem.

I am not running Mystic...

I know, but /8001 is running mystic bbs.

Nick

Bye/2 Torsten

... MAILBOX01 on OS2: up 10d 18h 52m load: 37 proc, 157 threads (tbupv1.0)
--- GoldED+ 1.1.5-18
* Origin: DatenBahn BBS Hamburg (2:240/5832)

On 27 Nov 18 19:31:07, Torsten Bamberg said the following to Nick Andre:

crash every time it was restarted, on the "buffer space"

problem. Well, 2:240/8001 has problems receiving crashmail. If you
send /8001 something, the buggy buildin binkd mailer of mystic
crashes the system by pulling up the cpu load to 100 percent. The
Sysop needs to restart the computer, to solve the problem.

I am not running Mystic...

I know, but /8001 is running mystic bbs.

I do not understand how that relates to a Windows version of BinkD running fine for months, then suddenly crashing.

Nick

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

Binkd 1.1a-95 (Dec 10 2016 21:44:31/Win32)

Do you have some special reason to use an old alpha version of Binkd?

--- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0) Gecko/20100101 Thunderbir
* Origin: *** smapinntpd/linux @ nntp://news.fidonet.fi *** (2:221/10.0)

On 30 Nov 18 15:52:38, Tommi Koivula said the following to Nick Andre:

Binkd 1.1a-95 (Dec 10 2016 21:44:31/Win32)

Do you have some special reason to use an old alpha version of Binkd?

Interesting, I was not aware the latest version appears to be:

Binkd 1.1a-99 (Jun 25 2018 22:50:08/Win32)
Compilation flags: mingw32, zlib, bzlib2, perldl, https, ntlm, amiga_4d_outbound
, bwlim, ipv6, af_force.
Facilities: fts5004 ipv6

I am hopeful this will resolve the long-term stability... It runs perfectly fine otherwise.

Nick

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

  NA> Binkd 1.1a-95 (Dec 10 2016 21:44:31/Win32)

Do you have some special reason to use an old alpha version of Binkd?

Interesting, I was not aware the latest version appears to be:

Binkd 1.1a-99 (Jun 25 2018 22:50:08/Win32)
Compilation flags: mingw32, zlib, bzlib2, perldl, https, ntlm, amiga_4d_outbound , bwlim, ipv6, af_force. Facilities: fts5004 ipv6

I am hopeful this will resolve the long-term stability... It runs

perfectly

fine otherwise.

I have a Win 2008 R2 x64 server running perfectly fine also. Anyway it
doesn't harm if you reboot windows machines time to time...

'Tommi

\\PYY has been up for: 49 day(s), 7 hour(s), 31 minute(s), 16 second(s)

--- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0) Gecko/20100101 Thunderbir
* Origin: *** smapinntpd/linux @ nntp://news.fidonet.fi *** (2:221/10.0)

Hello Nick!

Friday November 30 2018 09:30, you wrote to Tommi Koivula:

Binkd 1.1a-95 (Dec 10 2016 21:44:31/Win32)

Do you have some special reason to use an old alpha version of
Binkd?

Interesting, I was not aware the latest version appears to be:
Binkd 1.1a-99 (Jun 25 2018 22:50:08/Win32)

Isn't it just a compilation date and time?

This is what my build says, and it seems to be the date when I compiled it :) Binkd 1.1a-99 (Nov 5 2018 13:34:52/Linux)

Roman

--- GoldED+/LNX 1.1.5-b20180707
* Origin: New origin (4) (1:267/67)

Hi Roman.

30 Nov 18 14:14:14, you wrote to Nick Andre:

Binkd 1.1a-95 (Dec 10 2016 21:44:31/Win32)

Do you have some special reason to use an old alpha version of
Binkd?

Interesting, I was not aware the latest version appears to be:
Binkd 1.1a-99 (Jun 25 2018 22:50:08/Win32)

Isn't it just a compilation date and time?

It is. But take a look at the history file:

=== Cut ===
2018/05/14 22:32:47 1.1a-99 git
=== Cut ===

-99 still is the latest.

This is what my build says, and it seems to be the date when I
compiled it
:) Binkd 1.1a-99 (Nov 5 2018 13:34:52/Linux)

Binkd 1.1a-99 (Nov 30 2018 01:00:17/OS2)
Compilation flags: gcc (klibc), zlib, bzlib2, https, ntlm, amiga_4d_outbound, bwlim. Facilities: fts5004 rfc2553emu

'Tommi

---
* Origin: 2001:470:1f15:cb0:f1d0:2:221:6 (2:221/6)

On 30 Nov 18 17:10:10, Tommi Koivula said the following to Nick Andre:

I am hopeful this will resolve the long-term stability... It runs

perfectly

fine otherwise.

I have a Win 2008 R2 x64 server running perfectly fine also. Anyway it doesn't harm if you reboot windows machines time to time...

I know... it should not be necessary. When this problem happens, the rest of the Windows environment and programs appear to be perfectly fine.

I have a simular "quirk" with Net2BBS; a Telnet server. After long periods of running it will suddenly stop accepting connections, with no error or reason.

Nick

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

Hallo Tommi!

30.11.2018 22:16, Tommi Koivula schrieb an Roman Litvinenko:

Binkd 1.1a-99 (Nov 30 2018 01:00:17/OS2)
Compilation flags: gcc (klibc), zlib, bzlib2, https, ntlm, amiga_4d_outbound, bwlim. Facilities: fts5004 rfc2553emu

Hm... ;-)

Binkd 1.1a-99 (Nov 2 2018 21:42:34/OS2)
Compilation flags: gcc (klibc), zlib, bzlib2, https, ntlm, amiga_4d_outbound, bwlim.
Facilities: fts5004 rfc2553emu

Compiled with gcc 8.1.0

'Tommi

Bye/2 Torsten

... MAILBOX01 on OS2: up 13d 21h 24m load: 37 proc, 157 threads (tbupv1.0)
--- GoldED+ 1.1.5-18
* Origin: DatenBahn BBS Hamburg (2:240/5832)

Torsten Bamberg <2:240/5832> wrote:

TK> Binkd 1.1a-99 (Nov 30 2018 01:00:17/OS2)
TK> Compilation flags: gcc (klibc), zlib, bzlib2, https, ntlm,
TK> amiga_4d_outbound, bwlim. Facilities: fts5004 rfc2553emu
Hm... ;-)

Binkd 1.1a-99 (Nov 2 2018 21:42:34/OS2)
Compilation flags: gcc (klibc), zlib, bzlib2, https, ntlm, amiga_4d_outbound, bwlim.
Facilities: fts5004 rfc2553emu

Compiled with gcc 8.1.0

Hm... ;-)

I'm still using the old and trusty gcc 3.3.5. Maybe I should take a look at that one also.

'Tommi

--- Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
* Origin: *** smapinntpd/linux @ nntp://news.fidonet.fi *** (2:221/10.0)

Hallo Tommi!

01.12.2018 10:05, Tommi Koivula schrieb an Torsten Bamberg:

Compiled with gcc 8.1.0

Hm... ;-)
I'm still using the old and trusty gcc 3.3.5. Maybe I should take a
look at that one also.

Well, it is a bit tricky to get gcc8 working. Also the old 'AS' does not work.

'Tommi

Bye/2 Torsten

... MAILBOX01 on OS2: up 14d 12h 27m load: 37 proc, 157 threads (tbupv1.0)
--- GoldED+ 1.1.5-18
* Origin: DatenBahn BBS Hamburg (2:240/5832)

Hello Tommi!

Friday November 30 2018 22:16, you wrote to me:

Binkd 1.1a-99 (Jun 25 2018 22:50:08/Win32)

Isn't it just a compilation date and time?

It is. But take a look at the history file:
=== Cut ===
2018/05/14 22:32:47 1.1a-99 git
=== Cut ===

Updated autoconf scripts

I think there were no major code changes within last few years.

Roman

--- GoldED+/LNX 1.1.5-b20180707
* Origin: New origin (9) (1:267/67)