Re: MRC Module
By: DesotoFireflite to echicken on Tue Feb 22 2022 17:28:00

No, it's coming from outside of my system, I checked, and no one has been

Okay. That helps and means I probably have similar errors in my own log. I'll see if that's the case; if so, it'll help me narrow things down.

No promises though. I have limited patience with MRC.

I tried changing the line in mrc-connector.js:
from
log(LOG_ERR, 'Invalid MRC line: ' + line):
to
log(LOG_INFO, 'Invalid MRC line: ' + line):

but it didn't like it, and gave me another error, which I can't remember.

I can't imagine why that would be, but you might have been better off changing that to LOG_DEBUG.

Hope this info helps. Where is the actual log file kept, and what is it's name for the info and debug info.

That depends a lot on how your system is set up. These log messages are going wherever the logs for your other JS services go (like the NNTP server, or JSON-DB, or anything from services.ini), if that helps.

---
echicken
electronic chicken bbs - bbs.electronicchicken.com
---
þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com

Re: MRC Module
By: echicken to DesotoFireflite on Wed Feb 23 2022 03:21 am

Hope this info helps. Where is the actual log file kept, and what is it's name for the info and debug info.

That depends a lot on how your system is set up. These log messages are going wherever the logs for your other JS services go (like the NNTP server, or JSON-DB, or anything from services.ini), if that helps.

Also check data/error.log. Any messages logged with an "Error" severity (or worse) should also be logged in that file.
--
digital man (rob)

This Is Spinal Tap quote #30:
Big bottom, big bottom / Talk about mud flaps, my girl's got 'em!
Norco, CA WX: 45.0øF, 86.0% humidity, 11 mph SSE wind, 0.01 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: MRC Module
By: Digital Man to echicken on Tue Feb 22 2022 18:15:46

Does it barf if a user sends a message containing a '~' character maybe?

Technically not barfing (as in crashing or doing anything it shouldn't) - these lines are illegal; it's logging but otherwise ignoring them.

The protocol description I was given in 2019 says:

- Each 'message' is a single line of seven ~ delimited fields
- Each message is terminated with a ~ and a newline
- No field may contain the ~ character
- Only ASCII 32-125 are permitted in any field
- Some fields only allow ASCII 33-125
- Any message not conforming to the above must be dropped

I have a suspicion that these are long messages being broken up into multiple lines, with subsequent lines lacking all but the "message text" field. Very possibly the protocol was amended to allow this but I didn't hear about it (or
ignored it).

Or there's a busted client out there sending bad messages.

I've heard of two people working on MRC-related things in recent months. If these errors are new, maybe they're related. (Meatlotion, are you reading this?)

That's it for this edition of the MRC super funtime show. Thanks for tuning in.

---
echicken
electronic chicken bbs - bbs.electronicchicken.com
---
þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com

Re: MRC Module
By: DesotoFireflite to echicken on Wed Feb 23 2022 08:40:52

This is the latest. It actually looks like it's coming from another

Yep, I've got the same log output here. Actually, most anybody using the Synchronet MRC module will have this in their log.

Some hints in the text tell me that this latest message (and possibly the rest) came from an MRC-to-IRC gateway. I know who was working on such a thing recently, so I'll see if they can share some details.

---
echicken
electronic chicken bbs - bbs.electronicchicken.com
---
þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com

Re: MRC Module
By: DesotoFireflite to Digital Man on Wed Feb 23 2022 08:06 am

Re: MRC Module
By: Digital Man to echicken on Tue Feb 22 2022 07:56 pm

Re: MRC Module
By: echicken to DesotoFireflite on Wed Feb 23 2022 03:21 am

Hope this info helps. Where is the actual log file kept, and what De>> is it's name for the info and debug info.

That depends a lot on how your system is set up. These log messages
are going wherever the logs for your other JS services go (like the
NNTP server, or JSON-DB, or anything from services.ini), if that
helps.

Also check data/error.log. Any messages logged with an "Error" severity (or worse) should also be logged in that file.

That's where I'm seeing the errors, but I can't find the other logged activity for it.

In the Synchronet control panel for Windows, I think you'd find that activitiy in your "Services" window.
--
digital man (rob)

This Is Spinal Tap quote #13:
Nigel Tufnel: You can't really dust for vomit.
Norco, CA WX: 50.5øF, 53.0% humidity, 5 mph E wind, 0.01 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net