Here's odd one. MBBSv10-R33 locked up on me during the nightly cleanup.
it looks like it got to Server Shutdown in the audit trail, and then it seems to have frozen. The screen is unresponsive.
I attempt to restart and it's asking me for my activation code again, which is strange.
Noting particularly suspicious in the audit log:
20260222 010828 TELNET CALL ACCEPTED Chan 01 from 14.1.104.12 port 42201
20260222 010842 TELNET CALL TERMINATED Chan 01 connected to 14.1.104.12 for 14 seconds
20260222 032010 SYSTEM USAGE SINCE LAST CLEANUP Cleanup Calls: 0 Signups: 0 Hrs used: 0 Creds used: 0
20260222 032010 SERVER SHUTDOWN Cleanup
The only change made was a couple days before where I added a couple modem channels, but that seems like an unlikely sticking point.
Not sure where to go next for anything useful.
Lockup at Maintenance
-
iunderwood
- Posts: 7
- Joined: Sun Jan 04, 2026 6:19 pm
- Location: Cherry Valley, MA
Lockup at Maintenance
## Ian Underwood (Agent Green / Eyetack)
## Domain of the Unknown - MBBS/WG1 (1995-1996)
## telnet://dotu3.us:2323 | pots: +1-508-50-DOTU-3
## Domain of the Unknown - MBBS/WG1 (1995-1996)
## telnet://dotu3.us:2323 | pots: +1-508-50-DOTU-3
Re: Lockup at Maintenance
Is this happening repeatedly or only once? Has it produced any error logs?
-- Duckula
// Site admin
// Galacticomm IP owner
// Site admin
// Galacticomm IP owner
-
iunderwood
- Posts: 7
- Joined: Sun Jan 04, 2026 6:19 pm
- Location: Cherry Valley, MA
Re: Lockup at Maintenance
Sorry for the delay ... I had to run this more before I felt the failure was reliable.
I've got a pair of modem channels sitting in Channel Group 14, 2, locked at 38400 starting at COM4.
I have been able to reliably get the lockup on maintenance if I managed to disrupt communication the modem for any reason (e.g. disconnect serial, kick out the power brick, etc.). I am guessing this is related to the busy-out routine that puts modems off-hook at the start of maintenance.
I've got a pair of modem channels sitting in Channel Group 14, 2, locked at 38400 starting at COM4.
I have been able to reliably get the lockup on maintenance if I managed to disrupt communication the modem for any reason (e.g. disconnect serial, kick out the power brick, etc.). I am guessing this is related to the busy-out routine that puts modems off-hook at the start of maintenance.
## Ian Underwood (Agent Green / Eyetack)
## Domain of the Unknown - MBBS/WG1 (1995-1996)
## telnet://dotu3.us:2323 | pots: +1-508-50-DOTU-3
## Domain of the Unknown - MBBS/WG1 (1995-1996)
## telnet://dotu3.us:2323 | pots: +1-508-50-DOTU-3