When mystic get's a bad file or thinks it's a bad file, the *.tic file get's moved to the bad file area, but the file that
goes with the tic file get's deleted/fails.
/opt/mystic/files/badfile/MYS112A39_L64.RAR.tic
+ Apr 27 09:55:46 File MYS112A39_L64.RAR Area FSX_MYST From 21:1/195 ! Apr 27 09:55:46 Bad filename; Moved to /opt/mystic/files/badfile/
! Apr 27 09:55:46 Failed moving file
+ Apr 27 09:55:46 Scanning Hatches
+ Apr 27 09:55:46 Process: Toss FDN/TIC Files
+ Apr 27 09:55:46 Tossing 5a0620c8.tic
- Apr 27 09:55:46 Unknown Key (ORIGIN) Value (Origin 21:1/1)
- Apr 27 09:55:46 Unknown Key (LFILE) Value (Lfile mys112a39_l64.rar) - Apr 27 09:55:46 Unknown Key (CREATED) Value (Created by MBSE BBS 1.0.7 Copyright (C) 1997-2017 MBSE DevTm)
- Apr 27 09:55:46 Unknown Key (PATH) Value (Path 21:1/1 1524729603
+ Apr 27 09:55:46 Process: Toss FDN/TIC Files
+ Apr 27 09:55:46 Tossing 5a0620c8.tic
- Apr 27 09:55:46 Unknown Key (ORIGIN) Value (Origin
21:1/1) - Apr 27 09:55:46 Unknown Key (LFILE) Value (Lfile
mys112a39_l64.rar) - Apr 27 09:55:46 Unknown Key (CREATED)
Value (Created by MBSE BBS 1.0.7 Copyright (C) 1997-2017 MBSE
DevTm) - Apr 27 09:55:46 Unknown Key (PATH) Value (Path
21:1/1 1524729603
How is this TIC and File being processed, it looks like the TIC has already been amended by MBSE? I may be looking at this incorrectly?
Which node is it being tossed in to?
This system is 21:1:195 MBSE hub, to Mystic 21:1/196.
That is only one file I pulled out of the badarea, there are others. Yet other's toss fine.
When mystic get's a bad file or thinks it's a bad file, the *.tic file get's moved to the bad file area, but the file that
goes with the tic file get's deleted/fails.
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 2 |
Nodes: | 8 (0 / 8) |
Uptime: | 133:22:57 |
Calls: | 2,128 |
Calls today: | 1 |
Files: | 11,149 |
D/L today: |
22 files (9,952K bytes) |
Messages: | 951,018 |