Subj : Re: BUSY NODES on A38 (windows) issue since updating
To   : Vitus Zeel
From : Vitus Zeel
Date : Sat Jan 20 2018 20:44:27

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

--- Mystic BBS v1.12 A34 (Windows/32)
 * Origin: BlackICE BBS (BlackICE.BBSindex.com:23) (2:240/8001)

.