So, I updated to A34 on Sunday and everything seemed to be running smoothly. Two days in a row now I have tried connecting via telnet and mystic is not answering. MIS appears to be running as BINKP is up and
my events are executing, however the mis.log shows:
MIS received SIGTERM; shutting down
So, I updated to A34 on Sunday and everything seemed to be running smoothly. Two days in a row now I have tried connecting via telnet and mystic is not answering. MIS appears to be running as BINKP is up and
my events are executing, however the mis.log shows:
MIS received SIGTERM; shutting down
So, I updated to A34 on Sunday and everything seemed to be running smoothly. Two days in a row now I have tried connecting via telnet and mystic is not answering. MIS appears to be running as BINKP is up and
my events are executing, however the mis.log shows:
MIS received SIGTERM; shutting down
Curious you have a reload script for MIS/MIS2 correct? The apps
crashing for one reason or another led most of us to create a reload script in case of these issues. :)
On 07/04/17, Pequito said the following...
Curious you have a reload script for MIS/MIS2 correct? The apps crashing for one reason or another led most of us to create a reload script in case of these issues. :)
If he's having the same issue I was, the reload script doesn't work because the system still shows MIS is running with multiple PIDs. I couldn't even kill the hung processes without rebooting when I was
having this issue.
On 07/05/17, Zero Reader said the following...
On 07/04/17, Pequito said the following...
Curious you have a reload script for MIS/MIS2 correct? The apps crashing for one reason or another led most of us to create a re script in case of these issues. :)
If he's having the same issue I was, the reload script doesn't work because the system still shows MIS is running with multiple PIDs. I couldn't even kill the hung processes without rebooting when I was having this issue.
That sounds like a dead pool, the script I created for this issue works without loading more than one and ensures to kill the mis.bsy files if needed.
Most of the time that is the biggest issue.
That sounds like a dead pool, the script I created for this issue works without loading more than one and ensures to kill the mis.bsy files if needed.
On 07/04/17, Immortal pondered and said...
So, I updated to A34 on Sunday and everything seemed to be running smoothly. Two days in a row now I have tried connecting via telnet an mystic is not answering. MIS appears to be running as BINKP is up an my events are executing, however the mis.log shows:
MIS received SIGTERM; shutting down
Thank you for this report.
Curious you have a reload script for MIS/MIS2 correct? The apps
crashing for one reason or another led most of us to create a reload script in case of these issues. :)
On 07/04/17, Pequito said the following...
Curious you have a reload script for MIS/MIS2 correct? The apps crashing for one reason or another led most of us to create a reload script in case of these issues. :)
If he's having the same issue I was, the reload script doesn't work because the system still shows MIS is running with multiple PIDs. I couldn't even kill the hung processes without rebooting when I was
having this issue.
On 07/05/17, Pequito said the following...
That sounds like a dead pool, the script I created for this issue wor without loading more than one and ensures to kill the mis.bsy files i needed.
Is there somewhere I can look at it?
I'm using Tony's reload script now, but the dead pool as you called it, was being created before I started using any script. MIS would fail repeatedly during the day. Went back to an earlier version and I don't have these issues anymore.
I'm happy to remain on the older version until things settle down!
On 07/04/17, Pequito said the following...
Curious you have a reload script for MIS/MIS2 correct? The apps crashing for one reason or another led most of us to create a reload script in case of these issues. :)
Hey Pequito, glad to see you're back. I do have it running using your reload script. I'm assuming the script never re-starts MIS because MIS never actually stops running, just the telnet server.
On 07/05/17, Zero Reader said the following...
script I use the KORN shell vs bash and works without a hitch.
https://paste.ofcode.org/5bCXF6Q7e3dtt8SF6iYJVk
because the system still shows MIS is running with multiple PIDs. I couldn't even kill the hung processes without rebooting when I was
On 07/05/17, Immortal said the following...
On 07/04/17, Pequito said the following...
Curious you have a reload script for MIS/MIS2 correct? The apps crashing for one reason or another led most of us to create a re script in case of these issues. :)
Hey Pequito, glad to see you're back. I do have it running using you reload script. I'm assuming the script never re-starts MIS because M never actually stops running, just the telnet server.
Thanks Immortal, just posted a link for it to Zero but check this one using the KORN shell.
https://paste.ofcode.org/5bCXF6Q7e3dtt8SF6iYJVk
Yes! I had this very same issue on the Raspberry Pi. I tried MIS2 but it was throwing an error 214 when I'd try to connect. I just rolled back to the previous version I was on and haven't had any issues.
Try A33, A34 doesn't run well on the Pi I've found. A33 does pretty good but you need to have badip.txt, goodip.txt setup and likely BLOCK
Russia, China Turkey and such.
Try A33, A34 doesn't run well on the Pi I've found. A33 does pretty good but you need to have badip.txt, goodip.txt setup and likely BLOCK
Russia, China Turkey and such.
Try A33, A34 doesn't run well on the Pi I've found. A33 does pretty good but you need to have badip.txt, goodip.txt setup and likely BLOCK
Russia, China Turkey and such.
--- Mystic BBS v1.12 A34 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 31 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 201:16:47 |
| Calls: | 2,083 |
| Calls today: | 1 |
| Files: | 11,139 |
| Messages: | 947,934 |