snip<=-+ 21:06:59 BINKP 1-Receiving: 021B0104.030 (257 bytes)
Hi All,
I'm still having issues where MIS2 will stop accepting connections to
both telnet and binkd servers. It is usually when MIS2 has been running for a number of hours, from 10-24 hours. At some point, connections are not accepted, until it is restarted.
--- Mystic BBS v1.12 A36 2017/11/23 (Linux/64)
I'm still having issues where MIS2 will stop accepting connections to both telnet and binkd servers. It is usually when MIS2 has been runni for a number of hours, from 10-24 hours. At some point, connections a not accepted, until it is restarted.
--- Mystic BBS v1.12 A36 2017/11/23 (Linux/64)
upgrade to 2017/11/25
upgrade to 2017/11/25I just did. We'll see what happens by morning...
I'm not sure what the problem is. I didn't have the issue in A35 running MIS2 or MIS. I like all of the additions being made to A36, but it's getting to the point, I will be unable to run it if this continues to be
a problem.
Please remember: The A36 pre-alphas are to *TEST WITH* if you want to
test a specific new feature. You are welcome to use it to run your BBS with, but do not turn around and complain if something doesn't work. Its not supposed to work thats why its a pre-alpha. :)
I'm not sure what the problem is. I didn't have the issue in A35 runni MIS2 or MIS. I like all of the additions being made to A36, but it's getting to the point, I will be unable to run it if this continues to a problem.
Please remember: The A36 pre-alphas are to *TEST WITH* if you want to
test a specific new feature. You are welcome to use it to run your BBS with, but do not turn around and complain if something doesn't work. Its not supposed to work thats why its a pre-alpha. :)
I am not able to reproduce a problem where MIS2 stops accepting connections, and the logging you are showing is actually showing that
MIS2 is still accepting connections.... So what really is the problem
you are having?
The log shows a failed authentication but those can happen sometimes. Connections are lost, packets are lost, etc. Does it happen over and
over again? Can you clarify what the repeatable and reoccuring issue is?
The only thing that I was complaining about, was that I had posted three messages in reference to this problem over the last week, and had not received a reply. I kept trying the newer pre-alphas, in hopes the
problem would be corrected.
Once it stops accepting the connections, telnet 'callers' will be immediately disconnected. The binkp connections will continuously
receive the 'Cannot authenticate client', until MIS2 is restarted. Even the events come back with an error result of 2, and do not run.
I'm not sure if the problem is with Mystic, or something on my end. I'm also not sure where to start looking on my end for a potential problem.
I wish I had more logs or something to share with you to help.
The only thing that I was complaining about, was that I had posted th messages in reference to this problem over the last week, and had not received a reply. I kept trying the newer pre-alphas, in hopes the problem would be corrected.
Mystic is a part of my life that I love working on, but I don't always have time or sometimes just not the motivation. I already spend an unreasonable amount of my non-working time on Mystic so much so that its caused strain in my relationships in my past! But even so, for one
reason or another I don't always respond directly to people. Its
nothing personal, I promise. I am very greatful for your help testing, along with everyone else here who does.
In this particular case I did see your messages. I set up a Linux/64 machine and I left it up for 2 days. I just took it down this morning. Over the two days it got hammered with scanner telnet connections but it had no crashes or ghost nodes or anything. I only ran a telnet server
and one event.
Error 2 seems to be a strange error that could be a "lack of
permissions" Is there anything you are running that could possibly
change permissions of files or their open/closed status while the BBS is running?
I hate to fall back to my standard "permission" blaming but that would also explain the authentication. If BINKP cannot open the data file, it won't be able to authenticate nodes. If MIS2 cannot create new
processes it will not be able to spawn the Mystic node.
I'm not sure if the problem is with Mystic, or something on my end. I also not sure where to start looking on my end for a potential proble I wish I had more logs or something to share with you to help.
We'll get it figured out eventually. :)
I was, in no way, stating that the work you put into Mystic isn't appreciated. You are doing a fantastic job.
All programs are being run under my login. The only exception to that, is starting MIS2 with the SUDO command. I have, however, noticed that at times, the MIS2.LOG file will have the permission changed to root. That
is the only file that I've noticed...
All programs are being run under my login. The only exception to that starting MIS2 with the SUDO command. I have, however, noticed that at times, the MIS2.LOG file will have the permission changed to root. Th is the only file that I've noticed...
This was a bug I just fixed in the most recent alpha I think... where it would create the log, and its temp directory with root access. I don't think it will have any positive affect on the issue you're seeing though.
I added a log during BINKP authentication if it cannot open the echomail nodes data file just in case that is the issue but so far I don't have
any other leads.
Oh I know, I didn't get that impression. I was mostly just thinking with my fingers lol
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 2 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 100:53:59 |
| Calls: | 2,124 |
| Files: | 11,149 |
| D/L today: |
13 files (10,484K bytes) |
| Messages: | 950,735 |