Hello Avon!

There seams to be a issue with the apod* file in the fsx_img area.
They are comming across as zero bytes in size, and has been going on for a few days now.
The last one of any size was dated Sep 22nd.


- 26 Sep 17:06:26 [709516] receiving 1dtm78hd.tic (2390 byte(s), off 0)
+ 26 Sep 17:06:26 [709516] 1dtm78hd.tic -> /husky/inbound.sec/1dtm78hd.tic
+ 26 Sep 17:06:26 [709516] rcvd: 1dtm78hd.tic (2390, 2390.00 CPS, 3:57/0@fidonet)
- 26 Sep 17:06:26 [709516] receiving apod0926.zip (0 byte(s), off 0)
+ 26 Sep 17:06:26 [709516] apod0926.zip -> /husky/inbound.sec/apod0926.zip
+ 26 Sep 17:06:26 [709516] rcvd: apod0926.zip (0, 0.00 CPS, 3:57/0@fidonet)
+ 26 Sep 17:06:26 [709516] done (from 3:57/0@fidonet, OK, S/R: 0/2 (0/2390 bytes))
26 Sep 17:06:26 [709516] session closed, quitting...



Vorlon


--- GoldED+/LNX 1.1.5-b20240302
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (21:1/195)

There seams to be a issue with the apod* file in the fsx_img area.
They are comming across as zero bytes in size, and has been going on for
a few days now.

I am also seeing this issue.

--- Mystic BBS v1.12 A48 (Windows/32)
* Origin: bbs.CabanaBar.net:11123 (21:1/246)

There seams to be a issue with the apod* file in the fsx_img area.
They are comming across as zero bytes in size, and has been going on for
a few days now.

In case it can help troubleshooting, I'm not seeing this issue .

|11ogg
|11SysOp, Altair IV BBS
|11altairiv.ddns.net:2323

... Radioactive cats have 18 half-lives

--- Mystic BBS v1.12 A49 2024/05/29 (Windows/64)
* Origin: Altair IV BBS (21:2/147)

There seams to be a issue with the apod* file in the fsx_img area.
They are comming across as zero bytes in size, and has been going on for a few days now.

I am seeing this here too.

I currently have a 0 byte fsxnet.zip and FSXNET.Z71 in my inbound.

That's the first time I have recieved 0 byte files from fsxNet.

--- BBBS/Li6 v4.10 Toy-7
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Hello Al!

26 Sep 24 13:52, you wrote to me:

There seams to be a issue with the apod* file in the fsx_img area.
They are comming across as zero bytes in size, and has been going on
for a few days now.

I am seeing this here too.

I currently have a 0 byte fsxnet.zip and FSXNET.Z71 in my inbound.

These have also came in with 0 byte size this morning.


Vorlon


--- GoldED+/LNX 1.1.5-b20240302
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (21:1/195)

Re: fsx_img file area
By: Vorlon to Avon on Thu Sep 26 2024 10:18 pm

Howdy,

There seams to be a issue with the apod* file in the fsx_img area.
They are comming across as zero bytes in size, and has been going on for a few days now.
The last one of any size was dated Sep 22nd.

Be interested to see what your log looks like sending to Hub 3.

Clrghouz should be "skipping" 0 byte sized files, but I notice after you attempting to send me a file, I think the connection gets lost.

[2024-09-27 10:07:23] production.INFO: PB-:+ About to receive a file [apod0923.zip 0 1727075957 -1] {"pid":4822}
What's not clear is if your side is not liking the SKIP I send, or if clrghouz barfs because of something else.


...δεσ∩
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Hello Vorlon!

26 Sep 24 22:18, you wrote to Avon:

Hello Avon!

There seams to be a issue with the apod* file in the fsx_img area.
They are comming across as zero bytes in size, and has been going on
for a few days now. The last one of any size was dated Sep 22nd.

Also seeing this


TheCivvie


--- GoldED+/OSX 1.1.5-b20240309
* Origin: TCOB1 Mail Only (21:1/229.1)