As niter3 noted, *.bbi files don't work in bbslist.mps anymore after that
last update. Gryphon's gy-blam.mps & node2bbi.mps appear to work fine though (and use the same *.bbi files). Were there changes to MPL?
Also my BBS hung again under mis. Doing ps -ef | grep mis I see:
pi 582 1 0 Sep07 ? 00:00:03 ./mis -d
pi 625 1 0 Sep07 ? 00:00:00 ./mis2 DAEMON
pi 7007 582 0 Sep07 ? 00:00:11 ./mis -d
pi 7556 582 0 Sep07 ? 00:00:11 ./mis -d
pi 20540 20538 0 04:20 pts/10 00:00:00 grep mis
pi 30951 582 0 01:55 ? 00:00:05 ./mis -d
pi 31008 582 0 01:55 ? 00:00:05 ./mis -d

I tried:
sudo kill 582 7007 7556 30951
sudo killall mis

Neither had an effect. I did sudo reboot and that seemed to hang so after 5 minutes I pulled the power and plugged it back in and it all came back up.
What I notice is tried to login I get instantly dropped with the [OK] prompt like I logged out or dropped telnet. When I checked the mis.log what I see is that mis was shutdown, but ps -ef | grep mis shows it as running. Not sure
what is going on here, but it's the version Paul hatched out 9/7 of A35
that's running. Next time I'll try just doing sudo ./mid -d to see if the
tasks are just 'ghosts' and they are all really shutdown as the log suggests.

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

I tried:
sudo kill 582 7007 7556 30951
sudo killall mis

do a kill -9 proc_id

--- Mystic BBS v1.12 A35 (Linux/32)
* Origin: Clutch BBS * telnet://clutch.darktech.org (21:1/199)

On 09/08/17, bcw142 said the following...

As niter3 noted, *.bbi files don't work in bbslist.mps anymore after that last update. Gryphon's gy-blam.mps & node2bbi.mps appear to work fine though (and use the same *.bbi files). Were there changes to MPL?
Also my BBS hung again under mis. Doing ps -ef | grep mis I see:

The fact that the MPL still works and the BBS List menu functions don't work, leads me to believe that there is a problem with the main mystic app and not the MPL module.

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Cyberia BBS | cyberia.darktech.org | San Jose, CA (21:1/120)

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

I tried:
sudo kill 582 7007 7556 30951
sudo killall mis

do a kill -9 proc_id

Too late, switched back to mis2 :P Oddly I still see mis multiplying:
pi 9708 1 0 Sep08 ? 00:01:01 ./mis -d
pi 12449 1 0 Sep08 ? 00:00:10 ./mis -d
pi 17262 12449 0 Sep08 ? 00:00:41 ./mis -d
pi 24593 1 0 Sep08 ? 00:00:13 ./mis2 DAEMON
pi 25296 25294 0 08:04 pts/13 00:00:00 grep mis
pi 29348 12449 0 Sep08 ? 00:00:46 ./mis -d
pi 29350 12449 0 Sep08 ? 00:00:47 ./mis -d
pi 29723 12449 0 Sep08 ? 00:00:45 ./mis -d

No Idea why or what that is doing. Time to experiment I guess. Hmmm,
pi@npie:~ $ sudo killall mis
pi@npie:~ $ s
pi 9708 1 0 Sep08 ? 00:01:01 ./mis -d
pi 12449 1 0 Sep08 ? 00:00:10 ./mis -d
pi 17262 12449 0 Sep08 ? 00:00:41 ./mis -d
pi 24593 1 0 Sep08 ? 00:00:14 ./mis2 DAEMON
pi 25653 25651 0 08:07 pts/13 00:00:00 grep mis
pi 29348 12449 0 Sep08 ? 00:00:46 ./mis -d
pi 29350 12449 0 Sep08 ? 00:00:47 ./mis -d
pi 29723 12449 0 Sep08 ? 00:00:45 ./mis -d

pi@npie:~ $ sudo kill -9 9708 12449 17262
pi@npie:~ $ s
pi 24593 1 0 Sep08 ? 00:00:14 ./mis2 DAEMON
pi 25866 25864 0 08:08 pts/13 00:00:00 grep mis
pi 29348 1 0 Sep08 ? 00:00:46 ./mis -d
pi 29350 1 0 Sep08 ? 00:00:47 ./mis -d
pi 29723 1 0 Sep08 ? 00:00:45 ./mis -d

Well, that works. The real question is what is going on? Why aren't they 'Zombie' tasks and killed by the OS? Taking a lot of time, mystic is now the top of top taking 99-100% of the CPU. I guess I'll kill -9 a couple more.
Still top, but it is a BBS so it should be top I guess.

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

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

I tried:
sudo kill 582 7007 7556 30951
sudo killall mis

do a kill -9 proc_id

Too late, switched back to mis2 :P Oddly I still see mis multiplying:
pi 9708 1 0 Sep08 ? 00:01:01 ./mis -d
pi 12449 1 0 Sep08 ? 00:00:10 ./mis -d
pi 17262 12449 0 Sep08 ? 00:00:41 ./mis -d
pi 24593 1 0 Sep08 ? 00:00:13 ./mis2 DAEMON
pi 25296 25294 0 08:04 pts/13 00:00:00 grep mis
pi 29348 12449 0 Sep08 ? 00:00:46 ./mis -d
pi 29350 12449 0 Sep08 ? 00:00:47 ./mis -d
pi 29723 12449 0 Sep08 ? 00:00:45 ./mis -d

No Idea why or what that is doing. Time to experiment I guess. Hmmm, pi@npie:~ $ sudo killall mis
pi@npie:~ $ s
pi 9708 1 0 Sep08 ? 00:01:01 ./mis -d
pi 12449 1 0 Sep08 ? 00:00:10 ./mis -d
pi 17262 12449 0 Sep08 ? 00:00:41 ./mis -d
pi 24593 1 0 Sep08 ? 00:00:14 ./mis2 DAEMON
pi 25653 25651 0 08:07 pts/13 00:00:00 grep mis
pi 29348 12449 0 Sep08 ? 00:00:46 ./mis -d
pi 29350 12449 0 Sep08 ? 00:00:47 ./mis -d
pi 29723 12449 0 Sep08 ? 00:00:45 ./mis -d

pi@npie:~ $ sudo kill -9 9708 12449 17262
pi@npie:~ $ s
pi 24593 1 0 Sep08 ? 00:00:14 ./mis2 DAEMON
pi 25866 25864 0 08:08 pts/13 00:00:00 grep mis
pi 29348 1 0 Sep08 ? 00:00:46 ./mis -d
pi 29350 1 0 Sep08 ? 00:00:47 ./mis -d
pi 29723 1 0 Sep08 ? 00:00:45 ./mis -d

Well, that works. The real question is what is going on? Why aren't they 'Zombie' tasks and killed by the OS? Taking a lot of time, mystic is now the top of top taking 99-100% of the CPU. I guess I'll kill -9 a couple more. Still top, but it is a BBS so it should be top I guess.

Looks like mis is locking up.. Not sure what's going on here. Do you run a script to restart mis? I wonder if it's your script at fault?

--- Mystic BBS v1.12 A35 (Linux/32)
* Origin: Clutch BBS * telnet://clutch.darktech.org (21:1/199)

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

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

I tried:
sudo kill 582 7007 7556 30951
sudo killall mis

do a kill -9 proc_id

Too late, switched back to mis2 :P Oddly I still see mis multiplying: pi 9708 1 0 Sep08 ? 00:01:01 ./mis -d
pi 12449 1 0 Sep08 ? 00:00:10 ./mis -d
pi 17262 12449 0 Sep08 ? 00:00:41 ./mis -d
pi 24593 1 0 Sep08 ? 00:00:13 ./mis2 DAEMON
pi 25296 25294 0 08:04 pts/13 00:00:00 grep mis
pi 29348 12449 0 Sep08 ? 00:00:46 ./mis -d
pi 29350 12449 0 Sep08 ? 00:00:47 ./mis -d
pi 29723 12449 0 Sep08 ? 00:00:45 ./mis -d

No Idea why or what that is doing. Time to experiment I guess. Hmmm, pi@npie:~ $ sudo killall mis
pi@npie:~ $ s
pi 9708 1 0 Sep08 ? 00:01:01 ./mis -d
pi 12449 1 0 Sep08 ? 00:00:10 ./mis -d
pi 17262 12449 0 Sep08 ? 00:00:41 ./mis -d
pi 24593 1 0 Sep08 ? 00:00:14 ./mis2 DAEMON
pi 25653 25651 0 08:07 pts/13 00:00:00 grep mis
pi 29348 12449 0 Sep08 ? 00:00:46 ./mis -d
pi 29350 12449 0 Sep08 ? 00:00:47 ./mis -d
pi 29723 12449 0 Sep08 ? 00:00:45 ./mis -d

pi@npie:~ $ sudo kill -9 9708 12449 17262
pi@npie:~ $ s
pi 24593 1 0 Sep08 ? 00:00:14 ./mis2 DAEMON
pi 25866 25864 0 08:08 pts/13 00:00:00 grep mis
pi 29348 1 0 Sep08 ? 00:00:46 ./mis -d
pi 29350 1 0 Sep08 ? 00:00:47 ./mis -d
pi 29723 1 0 Sep08 ? 00:00:45 ./mis -d

Well, that works. The real question is what is going on? Why aren't t 'Zombie' tasks and killed by the OS? Taking a lot of time, mystic is the top of top taking 99-100% of the CPU. I guess I'll kill -9 a coup more. Still top, but it is a BBS so it should be top I guess.

Looks like mis is locking up.. Not sure what's going on here. Do you run
a script to restart mis? I wonder if it's your script at fault?

Pretty sure it is the script not catching that the proc is already running properly.

Cheers!
Pequito

--- Mystic BBS v1.12 A35 (Linux/32)
* Origin: Twinkle BBS # (21:1/126)

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

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

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

I tried:
sudo kill 582 7007 7556 30951
sudo killall mis

do a kill -9 proc_id

Too late, switched back to mis2 :P Oddly I still see mis multipl pi 9708 1 0 Sep08 ? 00:01:01 ./mis -d
pi 12449 1 0 Sep08 ? 00:00:10 ./mis -d
pi 17262 12449 0 Sep08 ? 00:00:41 ./mis -d
pi 24593 1 0 Sep08 ? 00:00:13 ./mis2 DAEMON
pi 25296 25294 0 08:04 pts/13 00:00:00 grep mis
pi 29348 12449 0 Sep08 ? 00:00:46 ./mis -d
pi 29350 12449 0 Sep08 ? 00:00:47 ./mis -d
pi 29723 12449 0 Sep08 ? 00:00:45 ./mis -d

No Idea why or what that is doing. Time to experiment I guess. H pi@npie:~ $ sudo killall mis
pi@npie:~ $ s
pi 9708 1 0 Sep08 ? 00:01:01 ./mis -d
pi 12449 1 0 Sep08 ? 00:00:10 ./mis -d
pi 17262 12449 0 Sep08 ? 00:00:41 ./mis -d
pi 24593 1 0 Sep08 ? 00:00:14 ./mis2 DAEMON
pi 25653 25651 0 08:07 pts/13 00:00:00 grep mis
pi 29348 12449 0 Sep08 ? 00:00:46 ./mis -d
pi 29350 12449 0 Sep08 ? 00:00:47 ./mis -d
pi 29723 12449 0 Sep08 ? 00:00:45 ./mis -d

pi@npie:~ $ sudo kill -9 9708 12449 17262
pi@npie:~ $ s
pi 24593 1 0 Sep08 ? 00:00:14 ./mis2 DAEMON
pi 25866 25864 0 08:08 pts/13 00:00:00 grep mis
pi 29348 1 0 Sep08 ? 00:00:46 ./mis -d
pi 29350 1 0 Sep08 ? 00:00:47 ./mis -d
pi 29723 1 0 Sep08 ? 00:00:45 ./mis -d

Well, that works. The real question is what is going on? Why are 'Zombie' tasks and killed by the OS? Taking a lot of time, mysti the top of top taking 99-100% of the CPU. I guess I'll kill -9 a more. Still top, but it is a BBS so it should be top I guess.

Looks like mis is locking up.. Not sure what's going on here. Do you a script to restart mis? I wonder if it's your script at fault?

Pretty sure it is the script not catching that the proc is already
running properly.

best to verify the semaphore directory is correct. path, capital letters, etc.

--- Mystic BBS v1.12 A35 (Linux/32)
* Origin: Clutch BBS * telnet://clutch.darktech.org (21:1/199)

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

Looks like mis is locking up.. Not sure what's going on here. Do you run
a script to restart mis? I wonder if it's your script at fault?

No script to restart, that's the odd part. I did use a script on older
versions (pre-A35), but stopped on A35. It's not a script and all the
versions of mis are dead (not working) when that happens. I can kill them
with -9 and start mis -d normally and things work till it happens again.
I moved telnet back to mis2 and left binkp and other stuff on mis and it's worked over a day that way on the Pi (first time with any A35 version).
mis2 is doing telnet and rlogin and seems stable. No mis copies running or hanging around.

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

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

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

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

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

I tried:
sudo kill 582 7007 7556 30951
sudo killall mis

do a kill -9 proc_id

Too late, switched back to mis2 :P Oddly I still see mis mu pi 9708 1 0 Sep08 ? 00:01:01 ./mis -d
pi 12449 1 0 Sep08 ? 00:00:10 ./mis -d
pi 17262 12449 0 Sep08 ? 00:00:41 ./mis -d
pi 24593 1 0 Sep08 ? 00:00:13 ./mis2 DAEM pi 25296 25294 0 08:04 pts/13 00:00:00 grep mis
pi 29348 12449 0 Sep08 ? 00:00:46 ./mis -d
pi 29350 12449 0 Sep08 ? 00:00:47 ./mis -d
pi 29723 12449 0 Sep08 ? 00:00:45 ./mis -d

No Idea why or what that is doing. Time to experiment I gue pi@npie:~ $ sudo killall mis
pi@npie:~ $ s
pi 9708 1 0 Sep08 ? 00:01:01 ./mis -d
pi 12449 1 0 Sep08 ? 00:00:10 ./mis -d
pi 17262 12449 0 Sep08 ? 00:00:41 ./mis -d
pi 24593 1 0 Sep08 ? 00:00:14 ./mis2 DAEM pi 25653 25651 0 08:07 pts/13 00:00:00 grep mis
pi 29348 12449 0 Sep08 ? 00:00:46 ./mis -d
pi 29350 12449 0 Sep08 ? 00:00:47 ./mis -d
pi 29723 12449 0 Sep08 ? 00:00:45 ./mis -d

pi@npie:~ $ sudo kill -9 9708 12449 17262
pi@npie:~ $ s
pi 24593 1 0 Sep08 ? 00:00:14 ./mis2 DAEM pi 25866 25864 0 08:08 pts/13 00:00:00 grep mis
pi 29348 1 0 Sep08 ? 00:00:46 ./mis -d
pi 29350 1 0 Sep08 ? 00:00:47 ./mis -d
pi 29723 1 0 Sep08 ? 00:00:45 ./mis -d

Well, that works. The real question is what is going on? Wh 'Zombie' tasks and killed by the OS? Taking a lot of time, the top of top taking 99-100% of the CPU. I guess I'll kill more. Still top, but it is a BBS so it should be top I gues

Looks like mis is locking up.. Not sure what's going on here. Do a script to restart mis? I wonder if it's your script at fault?

Pretty sure it is the script not catching that the proc is already running properly.

best to verify the semaphore directory is correct. path, capital
letters, etc.

I check the proc when I do my checks etc so never have those issues, unsure
how others are checking to make sure that MIS or MIS2 are not running.

Cheers!
Pequito

--- Mystic BBS v1.12 A35 (Linux/32)
* Origin: Twinkle BBS # (21:1/126)

No script to restart, that's the odd part. I did use a script on older versions (pre-A35), but stopped on A35. It's not a script and all the versions of mis are dead (not working) when that happens. I can kill them with -9 and start mis -d normally and things work till it happens again.
I moved telnet back to mis2 and left binkp and other stuff on mis and
it's worked over a day that way on the Pi (first time with any A35 version). mis2 is doing telnet and rlogin and seems stable. No mis
copies running or hanging around.

honestly, i wouldnt spend that much effort on mis. g00r00 wants to get tod of it entirely.

--- Mystic BBS v1.12 A35 (Linux/32)
* Origin: Clutch BBS * telnet://clutch.darktech.org (21:1/199)

On 09/10/17, niter3 said the following...

honestly, i wouldnt spend that much effort on mis. g00r00 wants to get
tod of it entirely.

Yes, but on the Pi it didn't work till this last hatched version. I do know in the version before Paul hatched it, if you put both telnet & binkp on mis2 it didn't work. Not sure at present, the newer A35 that was hatched out telnet works best on mis2 with everything else on mis. Been running for two days that way - haven't been able to do that all week. I was just trying to get the BBS running again and that way worked and is the first that did.

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

I tried:
sudo kill 582 7007 7556 30951
sudo killall mis

do a kill -9 proc_id

Just a note: Never ever kill -9 anything with Mystic unless you absolutely have to. It will corrupt data files and leave BUSY files everywhere. It doesn't allow the software to shutdown properly whereas just using KILL without the -9 will send the proper termination to Mystic, allowing it to stop gracefully.

The same holds true with using CTRL+C CTRL+Z stuff too, or closing windows in Windows without shutting down Mystic first. These are all things people seem to commonly do.

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

Too late, switched back to mis2 :P Oddly I still see mis multiplying:
pi 9708 1 0 Sep08 ? 00:01:01 ./mis -d
pi 12449 1 0 Sep08 ? 00:00:10 ./mis -d
pi 17262 12449 0 Sep08 ? 00:00:41 ./mis -d

As I said a few times before, are you SURE you're not running a script
someone gave you or a cron?

Its not possible for a program to start itself. You have to be instructing
the computer to start it.

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

Just a note: Never ever kill -9 anything with Mystic unless you
absolutely have to. It will corrupt data files and leave BUSY files everywhere. It doesn't allow the software to shutdown properly whereas just using KILL without the -9 will send the proper termination to
Mystic, allowing it to stop gracefully.

The only reason i suggested this is becausr kill pid wasnt working. his work around was a reboot.

--- Mystic BBS v1.12 A35 (Linux/32)
* Origin: Clutch BBS * telnet://clutch.darktech.org (21:1/199)

niter3 wrote to g00r00 <=-

The only reason i suggested this is becausr kill pid wasnt working. his work around was a reboot.

It may take a few seconds for mis/mis2 to clean up and shut down properly. My automated scripts wait 5 seconds for shutdown, before checking again.


... California Driving: To change lanes, first pull out your 9mm...
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

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

Just a note: Never ever kill -9 anything with Mystic unless you
absolutely have to. It will corrupt data files and leave BUSY files everywhere. It doesn't allow the software to shutdown properly whereas just using KILL without the -9 will send the proper termination to
Mystic, allowing it to stop gracefully.

True. I tried kill, killall, then when multiple kills didn't work I did -9.
The tasks appeared to zombies. They also seemed to take a lot of CPU time,
was up near 100%. They had to be killed that way. Doesn't seem to be
happening with mis2 doing telnet - the release A35 is doing that fine. No trouble since.

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

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

Too late, switched back to mis2 :P Oddly I still see mis multiplying: pi 9708 1 0 Sep08 ? 00:01:01 ./mis -d
pi 12449 1 0 Sep08 ? 00:00:10 ./mis -d
pi 17262 12449 0 Sep08 ? 00:00:41 ./mis -d

As I said a few times before, are you SURE you're not running a script someone gave you or a cron?
Its not possible for a program to start itself. You have to be instructing the computer to start it.

No scripts. Something the hackers trying to get in and take over are doing. I've seen them tie up all 8 ports which shouldn't be possible from the same
IP, but I've seen it that way. Who knows what weird holes they found to do that. Anyway the released A35 using mis2 for telnet doesn't do that so it's solved.

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