I upgraded to A36 last night. This morning I found all my diskspace on that system 10GB filled up. Looking into things I found that the following file
ate up all the disk space.

eventsignal.txt -> it was around 8.6GB when I looked at it.

It was basically filled entries such as the following which it seemed to have gotten many a second of.

Dec 05 14:54:32 MIS Received 11

Since I'm on a Linux system, I have temporarily set a symbolic link of eventsignal.txt to /dev/null.

I'm wondering a few different things.

First is is safe to do my temp fix?
Second what is causing that?
Third is there a way to keep the eventsignal.txt file to a certain size? aka
is there a setting I can set?

- Jeff

--- Mystic BBS v1.12 A36 2017/12/03 (Linux/32)
* Origin: RPG Circus BBS (21:2/109)

Since I'm on a Linux system, I have temporarily set a symbolic link of eventsignal.txt to /dev/null.

Well the log file is there for a reason to help fix any issues with the new MIS. You might be able to dev/null it - I don't think it will break anything if you try. You can also delete it whenever you want. It shouldn't grow really big unless you have a major crash.

Signal 11 in Linux is SEGFAULT which is a major problem. Is there any sort of errors in your log, whether it mis.log, a node.log or errors.log that might help identify where it happened? Or if you don't want to dig around you can e-mail them to me at mysticbbs@gmail.com

I'd prefer to identify and fix the issue causing it :)

First is is safe to do my temp fix?
Second what is causing that?
Third is there a way to keep the eventsignal.txt file to a certain size? aka is there a setting I can set?

No there is no way to keep it a certain size. Its just a temporary file to help debug something in an alpha build its been there for all of the
pre-alphas too. When the problem is fixed, the log will go away. It doesn't typically grow super large unless a critical problem happens where Linux is freaking out.

--- Mystic BBS v1.12 A37 2017/12/05 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

I think I figured out my issue. Seems I forgot to set the adapter type to
just IPV4 on each of the servers Right now I don't have an IPV6 address on that machine. Likely I should get one. Once I set all the servers to just IPV4, no more entries in the eventsignals.txt file. (YES, I removed the link to /dev/null)

- Jeff

--- Mystic BBS v1.12 A36 2017/12/03 (Linux/32)
* Origin: RPG Circus BBS (21:2/109)

I think I figured out my issue. Seems I forgot to set the adapter type to just IPV4 on each of the servers Right now I don't have an IPV6 address
on that machine. Likely I should get one. Once I set all the servers to just IPV4, no more entries in the eventsignals.txt file. (YES, I
removed the link to /dev/null)

This doesn't sound like it'd be the cause of you getting segmentation faults from Linux. Was this something you could reproduce every time? Did you
happen to peak at the logs I mentioned?

That log exists to identify when a segmentation fault occurs, so being able
to investigate this would be helpful.

--- Mystic BBS v1.12 A37 2017/12/05 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

I did peak at the log. There was just this error

FTP Cannot resolve IPV6 domain, using: ::

Which is what made me look at the fact my machine didn't have a IPV6
address and that I should set the servers to just be IPV4. Once I did
that, all the errors seemed to stop. It could be an issue with my setup
as it's a VPS that I re-purposed from another use I had. As far as I can
tell, everything seems to be running fine now.

- Jeff

This doesn't sound like it'd be the cause of you getting segmentation faults from Linux. Was this something you could reproduce every time? Did you happen to peak at the logs I mentioned?

That log exists to identify when a segmentation fault occurs, so being able to investigate this would be helpful.

--- Mystic BBS v1.12 A37 2017/12/05 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

--- Mystic BBS/NNTP v1.12 A36 2017/12/03 (Linux/32)
* Origin: RPG Circus BBS (21:2/109)

Signal 11 in Linux is SEGFAULT which is a major problem. Is there any
sort of errors in your log, whether it mis.log, a node.log or errors.log that might help identify where it happened? Or if you don't want to dig around you can e-mail them to me at mysticbbs@gmail.com

damn

i got the signal 11. like, 11 gigs in an hour -rate. had to kill the mis
server and restart it, then it mysteriously went away. mis wasn't running in server window at that time, something like a ghost process or so.

|08\ |07H7|08 of |07Blocktronics/dIVINE sTYLERS!/aCCESSiON/TRSi/Break!Ascii |08\ |07Haciend bbs sysop |08(|15telnet://haciend.com|08)|07

--- Mystic BBS v1.12 A36 2017/12/03 (Linux/64)
* Origin: Haciend.com | Scandinavian demoscene bbssince 1996 (21:1/155)