After 24 hours usage of the MRC client (upon exiting) the following error is produced:
term Node 2 !JavaScript /sbbs/mods/chat_sec.js line 163: Error: Infinite loop (864336 operation callbacks) detected
After running MRC client for several hours, I get this error message which aborts the MRC client.
!JavaScript inputline.js line 150: Error: Infinite loop (864001 operation callbacks) detected
The original issue was fixed (MRC client exiting during use) and now we have a different issue with the client reporting an error after closing the client after 24 hours.
Will submit new issue to cover the latest issue as recommended by nelgin.
For clarification, the error occurs after quiting MRC client after 24 hours.
Line 17 in mrc-client.js on my system has:
js.time_limit=0;
but still produces the message:
term Node 2 !JavaScript /sbbs/mods/chat_sec.js line 163: Error: Infinite loop (864336 operation callbacks) detected
When I exit the client after 24 hours ...
Sun Apr 17 02:43:16 2022 master/632e51d8 srvc 0079 IMAPS !JavaScript /sbbs/exec/imapservice.js line 1861: TypeError: args.shift().toUpperCase is not a function
This issue has been resolved.
Well I'm glad you did add it
I'm still getting the timeout after 24 hours... I think this is due to a safety feature in JS?
Thoughts?
I'm seeing this in my data/crash.log on a Sunday after the 5am maint window:
L! 06:36 Sun Sep 10 2023 End of preexisting log entry (possible crash on Sun Sep 10 06:36:47 2023)
I usually leave myself logged in overnight, and every Sunday afternoon when I check the BBS, I am always logged off - which is the expected behaviour. Question is - why does this result in an entry in crash.log?
Nelgin is also seeing this in his crash.log file about the same time:
L! 06:32 Sun Sep 10 2023 End of preexisting log entry (possible crash on Sun Sep 10 06:32:35 2023)
This issue seems to have gone away - so closing.
Since updating to the latest Synchronet code, which includes multiple updates to Crypto related code, I have one occurance of this error message:
Sun Jan 28 00:00:02 2024 master/3a4a59ed
evnt SYNCRYPT !JavaScript /sbbs/exec/load/http.js line 147: Error: Unable to read status
Please let me know if you require any additional info.
Not had this problem since 30th Jan 2024 so I will close this issue.
Add SSH no auth capability so that ssh users can get to the login screen after seeing the welcome messages etc that they would do with telnet, but using an encrypted session.
This change would negate the need to add TELNETS to sbbs.
Umonitor is currently unable to properly display a spy session on a node which is currently in UTF-8 mode.
Add functionality to support UTF-8 similarly to mqtt_spy.js.
Nelgin: what have you changed to 10 mins? The max user inactivity or max new user inactivity?
Iām going to try that on mine.
Would 10 mins be a suitable value? Why is it 1 hour for new users?
Thanks DM.
I have the same problem and end up giving regular users the G exemption so that they can login to multiple nodes at the same time.
Yes - was before previous SSL related fix.
Since updating recently, I am now seeing errors appearing in data/error.log
Sat Jan 27 23:52:20 2024 master/3a4a59ed
srvc 0119 IMAPS TLS ERROR 'Resources/space exhausted' (-30) setting session active
These errors did not appear before the recent changes to the crypto functionality within Synchronet.
For reference, I'm using my iPhone to regularly check my BBS inbox using the IMAPS service.