132
Weird issue, hoping ya'll might help:

My BBS is setting SOME users time left to 0... I have an account, Mastermind, that is me... and I've been noticing for a week the time left was set to
zero. Then The Godfather wrote me an email saying it happened to him too... I went thru the node logs and they are at the bottom; why is Mystic 'setting
time left to 0'???

-----
------------------- Node 1 (Mystic v1.12 A45 2020/02/18)
2020.08.29 09:31:36 Connect from 199.229.249.144 (Unknown)
2020.08.29 09:31:36 Country: Unknown
2020.08.29 09:31:36 Set time left 10 TE=581
2020.08.29 09:31:36 Asking for system password
2020.08.29 09:31:39 MPL execute: /home/pi/mystic/themes/default/scripts/botcheck1_2.mpx
2020.08.29 09:31:40 MPL execute: /home/pi/mystic/themes/default/scripts/startup.mpx
2020.08.29 09:31:40 Python: /home/pi/mystic/themes/default/scripts/threatsentry.mpy
2020.08.29 09:31:40 Executing: /home/pi/mystic/themes/default/scripts/threatsentry/threatsentry-api.sh /home/pi/mystic/temp1/ 199.229.249.144 1
2020.08.29 09:31:40 Execution complete: 0
2020.08.29 09:31:40 INFO: User coordinates are: 45.4994, -73.5703
2020.08.29 09:31:40 INFO: API request count is: 5
2020.08.29 09:31:40 INFO: User is calling from city: Montreal
2020.08.29 09:31:40 INFO: User is calling from country: Canada
2020.08.29 09:31:40 INFO: User is calling from timezone: America/Toronto 2020.08.29 09:31:40 INFO: User local time is: 2020-08-29 12:31:40.875141-04:00 2020.08.29 09:31:40 INFO: User IP have no threat indicators
2020.08.29 09:31:46 Mastermind logged in
2020.08.29 09:31:46 First login today, setting time to 0
2020.08.29 09:31:46 Set time left 0 TE=571
2020.08.29 09:31:46 Setting time left to 0
2020.08.29 09:31:47 User ran out of time
2020.08.29 09:31:47 Shutting down


------------------- Node 1 (Mystic v1.12 A45 2020/02/18)
2020.08.29 08:03:17 Connect from 208.38.246.199 (1400868-v112.1208-static.wsfdindl.metronetinc.net)
2020.08.29 08:03:17 Country: Unknown
2020.08.29 08:03:17 Set time left 30 TE=513
2020.08.29 08:03:17 Asking for system password
2020.08.29 08:03:37 Bad password attempt
2020.08.29 08:06:38 MPL execute: /home/pi/mystic/themes/default/scripts/botcheck1_2.mpx
2020.08.29 08:06:42 MPL execute: /home/pi/mystic/themes/default/scripts/startup.mpx
2020.08.29 08:06:42 Python: /home/pi/mystic/themes/default/scripts/threatsentry.mpy
2020.08.29 08:06:42 Executing: /home/pi/mystic/themes/default/scripts/threatsentry/threatsentry-api.sh /home/pi/mystic/temp1/ 208.38.246.199 1
2020.08.29 08:06:42 Execution complete: 0
2020.08.29 08:06:42 INFO: User coordinates are: 40.0538, -86.1433
2020.08.29 08:06:42 INFO: API request count is: 2
2020.08.29 08:06:42 INFO: User is calling from city: Westfield
2020.08.29 08:06:42 INFO: User is calling from country: United States 2020.08.29 08:06:42 INFO: User is calling from timezone: America/Indiana/Indianapolis
2020.08.29 08:06:42 INFO: User local time is: 2020-08-29 11:06:42.729837-04:00 2020.08.29 08:06:42 INFO: User IP have no threat indicators
2020.08.29 08:06:58 The Godfather logged in
2020.08.29 08:06:58 First login today, setting time to 0
2020.08.29 08:06:58 Set time left 0 TE=486
2020.08.29 08:06:58 Setting time left to 0
2020.08.29 08:06:58 MPL execute: /home/pi/mystic/themes/default/scripts/xq-ilc_send.mpx
2020.08.29 08:06:59 User ran out of time
2020.08.29 08:06:59 Shutting down

-----



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
* Origin: American Pi BBS (21:2/150)

On 29 Aug 2020, paulie420 said the following...

134
Weird issue, hoping ya'll might help:

My BBS is setting SOME users time left to 0... I have an account, Mastermind, that is me... and I've been noticing for a week the time
left was set to zero. Then The Godfather wrote me an email saying it happened to him too... I went thru the node logs and they are at the bottom; why is Mystic 'setting time left to 0'???

Might just be the version of Mystic you're using, which is kind of old. The newest version of Mystic was released a few days ago, or so. It might fix
your issue. Give it a whack!

--- Mystic BBS v1.12 A46 2020/08/25 (Linux/64)
* Origin: throwbackbbs.com -\- meriden, ct -\- (21:1/114)

132

happened to him too... I went thru the node logs and they are at the bottom; why is Mystic 'setting time left to 0'???

Just to rule out the extremely obvious, in the Security Level editor, are any of the "Time Per Day" set to 0?

I added a level recently, and the default was 0. I was assuming that it
would wind up meaning "unlimited", but decided to add a number regardless.

I don't know what the expected behavior is, but I figured I'd ask in case
that was an issue.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Storm BBS (21:2/108)

132

happened to him too... I went thru the node logs and they are at the bottom; why is Mystic 'setting time left to 0'???

Just to rule out the extremely obvious, in the Security Level editor,
are any of the "Time Per Day" set to 0?

I added a level recently, and the default was 0. I was assuming that it would wind up meaning "unlimited", but decided to add a number
regardless.

I don't know what the expected behavior is, but I figured I'd ask in case that was an issue.

Adept, thank you!!! So just so everyone understands MY issue. 'Mastermind' is my other handle... 'The Godfather' is a visiting sysop whom I wanted to have access to my 'testing' menu... so yea... I set both of those users to sec
level 50 and then they had the security to access those menus.

However, I didn't add any security levels in that editor... When I just now added it; and now I can just Ctrl+U(pgrade) a user to that security level, it fixed the issue. The default was set to all 0s - including time per day.

SO ISSUE FIXED. :/ geez.

The Godfather; did you see this? Hopefully you can login now... Man, smh.

Mystic was working perfectly - altho its kinda a thing that you NEED to set security levels to ANY level you assign to any user.
Makes enough sense... got it. THANK YOU ADEPT!



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
* Origin: American Pi BBS (21:2/150)

132

However, I didn't add any security levels in that editor... When I just

Ah, yeah, that certainly wouldn't have occurred to me. It's also odd, since
(I think) every security level from 0 to 255 exists; it's just that they're normally hidden until you edit them in a particular way (or turn off hiding
the unused levels)

Makes enough sense... got it. THANK YOU ADEPT!

Yay! I'm glad it worked out.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Storm BBS (21:2/108)

132

However, I didn't add any security levels in that editor... When I ju

Ah, yeah, that certainly wouldn't have occurred to me. It's also odd, since (I think) every security level from 0 to 255 exists; it's just
that they're normally hidden until you edit them in a particular way (or turn off hiding the unused levels)

Makes enough sense... got it. THANK YOU ADEPT!

Yay! I'm glad it worked out.

Yea, glad that you hinted me to the exact cause. Thanks much...

It makes sense, too, that you'd want to fine tune any users/levels that you
use so... in the broader picture I'm going to go over the 3 or 4 levels that
I use and make sure they are all setup just so.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
* Origin: American Pi BBS (21:2/150)