Just switched back to normal telnet & binkp vis mis to see if it works. mis2 worked a few times, but was a real battle to get it to work. I'll try them
off and on till I can figure out what's going on with them. There is a lot going on in the mis2.log, mostly + 19:46:52 TELNET Blocked connection: 88.149.171.132 as it blocks the hacking. I also have iptables blocking most Russian and Chinese hacking (big lists).

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)

On 09/06/17, bcw142 pondered and said...

Just switched back to normal telnet & binkp vis mis to see if it works. mis2 worked a few times, but was a real battle to get it to work. I'll

Welcome back. Yep I have just switched 1/100 over to A35 proper and using MIS and MIS2 until g00r00 moves events system across to MIS2 then I can migrate.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Just switched back to normal telnet & binkp vis mis to see if it works. mis2 worked a few times, but was a real battle to get it to work. I'll

What is the battle you're having? You just have to enable the server and
type "mis2 server" to get it up. It can be a little confusing since there
are configuration options for both MIS and MIS2 in there though.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 09/07/17, g00r00 said the following...

Just switched back to normal telnet & binkp vis mis to see if it work mis2 worked a few times, but was a real battle to get it to work. I'l

What is the battle you're having? You just have to enable the server and type "mis2 server" to get it up. It can be a little confusing since
there are configuration options for both MIS and MIS2 in there though.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

I started it up on Sunday, I got a few messages from Sunday through last
night when I put mis back and everything has worked since with only one
reboot. I don't really know what the problems were except - well wait I'll
see if I can pull up some of the logs:

---------- Mystic v1.12 A35 Wed, Sep 06 2017 (loglevel 3)
+ 20:10:38 MANAGER Starting 1 server(s)
+ 20:10:38 MANAGER Starting servers in DAEMON mode
+ 20:10:38 RLOGIN Listening on IPV4 port 513 using interface "0.0.0.0"
+ 20:10:38 RLOGIN Listening on IPV6 port 513 using interface "::"

---------- Mystic v1.12 A35 Thu, Sep 07 2017 (loglevel 3)
+ 04:27:28 MANAGER Starting 1 server(s)
+ 04:27:28 MANAGER Starting servers in DAEMON mode
+ 04:27:28 RLOGIN Listening on IPV4 port 513 using interface "0.0.0.0"
+ 04:27:28 RLOGIN Listening on IPV6 port 513 using interface "::"

Now it shows as running, but nothing connected. This is how it was when I finally switched back over to mis and rebooted, it's been fine since then. At first it did work fine, the log is long, but mostly shows a functional system that's under attack but working, then the logs even stopped and above is what shows for all of Monday-Wednesday, looks like I rebooted it Wednesday
(likely). Then I must have rebooted again Thursday at 4:27am, then nothing till I switched to mis and rebooted. I know I rebooted Thursday evening and it's worked since on mis (so no real mis2 log). From Sept. 4 through 6 it ran and the only thing in mis2 log is above, mis shows:
Sep 04 20:00:13 MIS startup complete
Sep 06 11:58:48 MIS received SIGTERM; shutting down
Sep 06 12:00:43 MIS startup complete
Sep 06 20:10:23 MIS received SIGTERM; shutting down
Sep 06 20:10:23 MIS shutdown complete
Sep 06 20:10:38 MIS startup complete
Sep 06 23:57:57 MIS received SIGTERM; shutting down
Sep 07 04:13:36 MIS received SIGTERM; shutting down
Sep 07 04:27:01 MIS received SIGTERM; shutting down
Sep 07 04:27:28 MIS startup complete
So that shows the up and down with reboots between. There is a mis2.1.log but it's really long showing I guess what was going on.

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Workpoint (21:1/145.3)

+ 20:10:38 MANAGER Starting 1 server(s)
+ 20:10:38 MANAGER Starting servers in DAEMON mode
+ 20:10:38 RLOGIN Listening on IPV4 port 513 using interface "0.0.0.0"
+ 20:10:38 RLOGIN Listening on IPV6 port 513 using interface "::"

You haven't configured it to use TELNET. Are you only trying to use RLOGIN?

Now it shows as running, but nothing connected. This is how it was when I

This may be because you only have the RLOGIN server enabled.

Sep 06 12:00:43 MIS startup complete
Sep 06 20:10:23 MIS received SIGTERM; shutting down
Sep 06 20:10:23 MIS shutdown complete

Do you have some sort of script running? SIGTERM is your operating system or
a process you created telling MIS to shut down. It is not from Mystic, its from something you're doing.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 09/07/17, g00r00 said the following...

+ 20:10:38 MANAGER Starting 1 server(s)
+ 20:10:38 MANAGER Starting servers in DAEMON mode
+ 20:10:38 RLOGIN Listening on IPV4 port 513 using interface "0.0.0. + 20:10:38 RLOGIN Listening on IPV6 port 513 using interface "::"

You haven't configured it to use TELNET. Are you only trying to use RLOGIN?

Now it shows as running, but nothing connected. This is how it was wh

This may be because you only have the RLOGIN server enabled.

Sep 06 12:00:43 MIS startup complete
Sep 06 20:10:23 MIS received SIGTERM; shutting down
Sep 06 20:10:23 MIS shutdown complete

That's the current case yes. It's only trying to do rlogin now. Like I said I shutdown mis2 on telnet and binkp and put them back on mis. I did that at 20:10:23 as it shows. I believe at the time I did 'sudo killall mis mis2' to take them down. I used ./mystic -cfg to reconfigure and then did a reboot to bring things back from a clean boot.

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)

It just did it again, multiple mis took it down:
pi 563 1 0 04:27 ? 00:00:10 ./mis -d
pi 616 1 0 04:27 ? 00:00:05 ./mis2 DAEMON
pi 29499 29497 0 18:14 pts/2 00:00:00 grep mis
pi 29523 563 0 14:38 ? 00:00:09 ./mis -d
total 16
drwxrwxrwx 2 pi pi 4096 Sep 7 17:28 .
drwxr-xr-x 29 pi pi 4096 Sep 7 17:27 ..
-rw-r--r-- 1 pi pi 4 Sep 7 04:27 mis2.bsy
-rw-r--r-- 1 pi pi 4 Sep 7 04:27 mis.bsy
-rwxrwxrwx 1 pi pi 0 Sep 3 10:48 nodeinfo.now
-rw-r--r-- 1 pi pi 0 Sep 7 02:07 qwkmail.out

My quickest solution for now is reboot. I can try to shutdown but it won't
work on both mis tasks for unknown reasons. A reboot will do it. You can tell me what to check the next time. It should happen again tomorrow or Saturday
(if history continues). I see the second process happened at 14:38. Time for
a reboot to the Pi (via ssh).

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)

On 09/07/17, Avon said the following...

On 09/06/17, bcw142 pondered and said...

Just switched back to normal telnet & binkp vis mis to see if it work mis2 worked a few times, but was a real battle to get it to work. I'l

Welcome back. Yep I have just switched 1/100 over to A35 proper and
using MIS and MIS2 until g00r00 moves events system across to MIS2 then
I can migrate.

So what are you running on MIS2? I only have rlogin which isn't working on it right now. MIS has the rest which is why things are mostly working. MIS duplicates itself every now and then and I have to reboot to clear it so far, but I can do that on a daily basis and still run fine (it will auto-start).

--- Mystic BBS v1.12 A35 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

I upgraded to the version Paul hatched out 9/7, so we'll find out if it works better. After that I'll try Telnet & binkp on mis2 again and see what happens ;)

--- Mystic BBS v1.12 A35 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

It just did it again, multiple mis took it down:
pi 563 1 0 04:27 ? 00:00:10 ./mis -d
pi 616 1 0 04:27 ? 00:00:05 ./mis2 DAEMON
pi 29523 563 0 14:38 ? 00:00:09 ./mis -d

My quickest solution for now is reboot. I can try to shutdown but it
won't work on both mis tasks for unknown reasons. A reboot will do it.

I don't know if I saw your answer but are you using any start up scripts or scripts to restart or cron events?

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 09/09/17, g00r00 said the following...

It just did it again, multiple mis took it down:
pi 563 1 0 04:27 ? 00:00:10 ./mis -d
pi 616 1 0 04:27 ? 00:00:05 ./mis2 DAEMON
pi 29523 563 0 14:38 ? 00:00:09 ./mis -d

My quickest solution for now is reboot. I can try to shutdown but it won't work on both mis tasks for unknown reasons. A reboot will do it

I don't know if I saw your answer but are you using any start up scripts or scripts to restart or cron events?

Just startup in /etc/rc.local no cron tasks at all, no restarting scripts.
I'm not sure what is doing it, my guess is the hacking. They tie up multiple ports, as many as four. and likely cause the issue.

--- Mystic BBS v1.12 A35 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)