Hi,

I've been having an issue with receiving TIC files. For some reasons, occassionally, the file transfer would be bad and my uplink would send a new file which gets stored as .<number>.ZIP. i.e. Z1DAILY.1.Z30. the old one Z1DAILY.Z30 would be a bad file (truncated file).

Can someone point out how I can troubleshoot this?

Edmund

... No one knows what's next, but everybody does it.

--- Mystic BBS v1.12 A47 2021/11/22 (Linux/32)
* Origin: Eagle's BBS (1:153/7083)

Hello Edmund,

I've been having an issue with receiving TIC files. For some reasons, occassionally, the file transfer would be bad and my uplink would send
a new file which gets stored as .<number>.ZIP. i.e. Z1DAILY.1.Z30.
the old one Z1DAILY.Z30 would be a bad file (truncated file).

Can someone point out how I can troubleshoot this?

If this happens again can you post the log from the session?

I can post my log also for that session and we'll see if we can get a better idea of what the problem is.

Ttyl :-),
Al

... We won the election, by a lot! -Donald Trump - 2020
--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

On 26 Nov 2021 at 02:09a, Al pondered and said...

I can post my log also for that session and we'll see if we can get a better idea of what the problem is.

I wonder if TIC processing is not happening so files build up and get renamed?

--- Mystic BBS v1.12 A47 2021/11/06 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Hello Paul,

I can post my log also for that session and we'll see if we can
get a better idea of what the problem is.

I wonder if TIC processing is not happening so files build up and get renamed?

Tic processing is working for him, I think.

There is sometimes (but not always) some kind of communication error between the mailers and so they give up when a partial file is received. That partial file will not toss because the CRC is incorrect.

Then on the next poll my mailer will send that file again and since that file is in the inbound already the new one renamed to *.1.zip, *.2.zip etc.

If I have been following what Edmund has been reporting he sometimes sees several *.#.zip files in his inbound. One of them may be the correct file and if so he has to rename it to the correct filename and retoss it.

I am not sure just what the problem is or what the solution might be but if we can get a better idea on what the problem is we can look to a solution.

Ttyl :-),
Al

... My message above. Your response here: __________________
--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)