Really weird, and I have no idea why. There's a backlog of about 3 weeks worth of files in my echomail directory. The log is showing:
+ Dec 17 09:10:42 Waiting for BUSY nodes
- Dec 17 09:10:49 LINKS:
try fidopoll killbusy and that will remove the .bsy and it should toss
Really weird, and I have no idea why. There's a backlog of about 3 weeks worth of files in my echomail directory. The log is showing:
+ Dec 17 09:10:42 Results: Auto-create prefix path does not exist in 0.00s ! Dec 17 09:10:42 Status: FATAL
21:1/100_bad_dir = c:\!files\badfile\
21:1/100_dir_prefix = c:\!files\fsx_
21:1/100_allow_replace = true
21:1/100_acs_list = z3
21:1/100_acs_ftp = s255
21:1/100_acs_download = s255
21:1/100_acs_upload = s255
21:1/100_acs_comment = s50
21:1/100_acs_sysop = s255
On 12/17/16, maskreet pondered and said...
Really weird, and I have no idea why. There's a backlog of about 3 w worth of files in my echomail directory. The log is showing:
+ Dec 17 09:10:42 Results: Auto-create prefix path does not exist in 0.00s ! Dec 17 09:10:42 Status: FATAL
OK the above tells me the main reason is the your auto create prefix path does not exist and therefore the rest of the process fails
21:1/100_bad_dir = c:\!files\badfile\
21:1/100_dir_prefix = c:\!files\fsx_
Are you sure you want to have and '!' in your path? I would remove that.
21:1/100_allow_replace = true
21:1/100_acs_list = z3
21:1/100_acs_ftp = s255
21:1/100_acs_download = s255
21:1/100_acs_upload = s255
21:1/100_acs_comment = s50
21:1/100_acs_sysop = s255
Consider adding a z ACS string to some of the other lines above :)
OK the above tells me the main reason is the your auto create prefix does not exist and therefore the rest of the process fails
That's the weird part. I haven't changed anything at all with regards to any of that in probably a year.
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 2 |
Nodes: | 8 (0 / 8) |
Uptime: | 110:25:23 |
Calls: | 2,124 |
Files: | 11,149 |
D/L today: |
36 files (21,434K bytes) |
Messages: | 950,836 |