! Feb 23 18:30:03 Import from /mystic/echomail/in/
+ Feb 23 18:30:03 Extracting 0000fc7d.fr7
- Feb 23 18:30:03 unzip -oqqjC "/mystic/echomail/in/0000fc7d.fr7" "*.pkt" -d /mystic/temputil/
+ Feb 23 18:30:03 Importing 0e9287d1.pkt (21:1/100 to 21:1/999)
+ Feb 23 18:30:03 Import #0 to FSX_BOT
+ Feb 23 18:30:03 Import #0 to FSX_BOT
+ Feb 23 18:30:03 Shutdown Corrupted memory (216)
The worst part is that once this happens, you have to delete the packet manually.
Has anyone seen this before?
Interesting, do you see this happening across all echoareas of just FSX_BOT?
Best, Paul
On Thursday, February 23, 2017 at 7:54:13 PM UTC-5, Paul Hayton wrote:FSX_BOT?
Interesting, do you see this happening across all echoareas of just
downloaded something that makes mutil throw this error. If there's a way to know where it came from, I'll be happy to look and report back. Let me know.Best, Paul
I don't know which base it's coming from. I just see that fidopoll has
I don't know which base it's coming from. I just see that fidopoll hasdownloaded something that makes mutil throw this error. If there's a way to know where it came from, I'll be happy to look and report back. Let
me know.
Here is the packet in question: https://www.dropbox.com/s/avvamslh71wr0xh/0e9287d1.pkt?dl=0
It seems to be from SpaceSST BBS, and specifically the file bases.
Thanks, I'll take a look tomorrow, it's late as I reply and I need to get some zzzz. :)
Best, Paul
Paul, I may have solved it. Somehow (again) some of the message files
got owned by root, rather than the normal user. I thought I was extra careful, but I must have run ./mystic -cfg as the root user. I'll keep
an eye on this, but for now, it seems like
things are working.
Sorry for the trouble.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,123 |
Nodes: | 15 (1 / 14) |
Uptime: | 136:45:44 |
Calls: | 227,988 |
Calls today: | 5 |
Files: | 41,376 |
D/L today: |
4 files (17,074K bytes) |
Messages: | 290,161 |