From: nospam.Vitus.Zeel@f8001.n240.z2.binkp.net

forgot these here:

2018.20.01 12:02:20 MYSTIC 002 Irregular shutdown event!
2018.20.01 12:02:22 MYSTIC 003 Irregular shutdown event!
2018.20.01 15:33:26 MYSTIC 001 Irregular shutdown event!
2018.20.01 15:52:22 MYSTIC 001 An error has occured (216)
2018.20.01 15:52:41 MYSTIC 001 An error has occured (216)
2018.20.01 15:54:10 MYSTIC 002 An error has occured (216)
2018.20.01 15:55:19 MYSTIC 002 An error has occured (216)
2018.20.01 15:55:39 MYSTIC 002 An error has occured (216)
2018.20.01 15:56:17 MYSTIC 002 An error has occured (216)
2018.20.01 16:00:09 MYSTIC 002 An error has occured (216)
2018.20.01 16:03:17 MYSTIC 001 An error has occured (216)
2018.20.01 16:03:43 MYSTIC 001 An error has occured (216)
2018.20.01 16:23:23 MYSTIC 002 An error has occured (216)
2018.20.01 16:26:10 MYSTIC 001 An error has occured (216)
2018.20.01 16:39:23 MYSTIC 005 An error has occured (216)
2018.20.01 17:13:09 MYSTIC 004 An error has occured (216)
2018.20.01 17:13:36 MYSTIC 004 An error has occured (216)
2018.20.01 17:26:04 MYSTIC 001 An error has occured (216)
2018.20.01 17:43:42 MYSTIC 001 An error has occured (216)
2018.20.01 17:43:56 MYSTIC 001 An error has occured (216)
2018.20.01 17:43:56 MYSTIC 001 An error has occured (216)
2018.20.01 18:06:12 MYSTIC 001 An error has occured (216)
2018.20.01 18:28:52 MYSTIC 001 An error has occured (216)
2018.20.01 18:29:03 MYSTIC 001 An error has occured (216)
2018.20.01 18:29:12 MYSTIC 001 An error has occured (216)
2018.20.01 18:50:24 MYSTIC 001 An error has occured (216)
2018.20.01 18:52:23 MYSTIC 001 An error has occured (216)
2018.20.01 18:54:28 MYSTIC 001 An error has occured (216)
2018.20.01 19:00:54 MYSTIC 001 An error has occured (216)
2018.20.01 19:02:07 MYSTIC 001 An error has occured (216)
2018.20.01 19:13:10 MYSTIC 001 An error has occured (216)
2018.20.01 19:18:49 MYSTIC 001 An error has occured (216)
2018.20.01 19:20:01 MYSTIC 002 An error has occured (216)
2018.20.01 19:27:31 MYSTIC 001 An error has occured (216)
2018.20.01 19:28:12 MYSTIC 001 An error has occured (216)
2018.20.01 19:32:37 MYSTIC 002 An error has occured (216)
2018.20.01 19:55:50 MYSTIC 002 An error has occured (216)
2018.20.01 20:04:15 MYSTIC 002 An error has occured (216)
2018.20.01 20:06:36 MYSTIC 002 An error has occured (216)
2018.20.01 20:06:36 MYSTIC 002 An error has occured (216)
2018.20.01 20:15:33 MYSTIC 002 An error has occured (216)
2018.20.01 20:23:51 MYSTIC 002 An error has occured (216)
2018.20.01 20:32:30 MYSTIC 002 An error has occured (216)

meanwhile i switched complete back to my old mystic backup - to many issues with a38 on my site.

and i have no more busy nodes and a working text editor and i got my main aka at the first line back.

(:. BlackICE BBS <-> BlackICE.BBSIndex.com:23 <-> BlackICEbbs.de.vu .:) -----------------------------------------------------------------------------
twitter.com/BlackICEbbs - bbsfse.de.vu - bbs-list-europe.de.vu

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: nospam.Vitus.Zeel@f8001.n240.z2.binkp.net

hi,

i have busy nodes. can't delete the .bsy file by using fidopoll.exe killbusy also not by using fidopoll.exe killbusy force

if i start mutil it creates all .bsy files. if i delete all by hand during muti is running the tosser will do his work. in the new error.log which i will post at the end of my msg you can see every one mutil start with an error 216...

i think it has to do with the mail i send earlier about the first node-address

pls check this SAP.

(:. BlackICE BBS <-> BlackICE.BBSIndex.com:23 <-> BlackICEbbs.de.vu .:) -----------------------------------------------------------------------------
twitter.com/BlackICEbbs - bbsfse.de.vu - bbs-list-europe.de.vu

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: nospam.g00r00@f215.n129.z1.binkp.net

i have busy nodes. can't delete the .bsy file by using fidopoll.exe killbusy also not by using fidopoll.exe killbusy force

Sounds like an access issue or you have a process stuck running, although I
am not clear on what you're trying to show in the logs vs what you're reporting.

if i start mutil it creates all .bsy files. if i delete all by hand
during muti is running the tosser will do his work. in the new error.log which i will post at the end of my msg you can see every one mutil start with an error 216...

The errors in the log you posted do not show MUTIL errors it shows MYSTIC errors. Mystic has no interaction with .BSY files at all. Are you talking about nodes that are reporting users online when they're not? This is confusing.

Why are you trying to delete .BSY files while MUTIL is running? MUTIL needs those BSY files to run, thats why its creating them.

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: nospam.g00r00@f215.n129.z1.binkp.net

forgot these here:

2018.20.01 12:02:20 MYSTIC 002 Irregular shutdown event!
2018.20.01 12:02:22 MYSTIC 003 Irregular shutdown event!
2018.20.01 15:33:26 MYSTIC 001 Irregular shutdown event!
2018.20.01 15:52:22 MYSTIC 001 An error has occured (216)

This is logged when you improperly shut down Mystic either by shutting down the computer, closing console windows but not Mystic, etc. You may end up with all sorts of problems if you continue to stop applications improperly while they're running. Files may be left open, or corrupted because they were in mid write or copy (for example). BSY and ghost nodes would be the #1 issue followed by 216 crashes because of corruption.

Crashing can of course do this too, but the crashes show up in that log only after you were incorrectly shutting your BBS down multiple times. This makes it difficult to distinguish between corruption and an actual issue.

There was one person having similar issues that you are and it was a corrupted file because their system crashed and the disk had to repair. One of the data files wasn't recoverable entirely. This could also happen if you try to mix and match data files from A36 with A38 as there have been changes.

meanwhile i switched complete back to my old mystic backup - to many issues with a38 on my site.

and i have no more busy nodes and a working text editor and i got my
main aka at the first line back.

I don't know of any issue with the text editor and no one has reported any to me, including you to my knowledge. Can you elaborate?

From what I remember you reported an issue with a PKT in another BBS software saying it had something to do with the linefeed, but then you said it works fine with Mystic. If you provide a PKT you want me to look at I will, but I can't really do much based on what you mentioned to me. Can you provide a more technical explanation besides "there is a linefeed in a PKT that crashes MBSE BBS"?

As far as the address editor: If you continue to use the local address space for echomail then you will continue to experience the same issue. Unless you were using the very first releases of echomail support you would have had to ignore a "DO NOT EDIT" warning to do what you've done.

This isn't something I can "fix" the first address is your local address space for local message bases, file bases. It has to be 0:0/0 and thats why you cannot change it. In the past, Mystic used to allow you to change but had a warning. Now it won't even let you change it.

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)