File creation issues on u/g from x86 to 64 bit v1.8.1

[rusty.hill]

Hi

I've been using the x86 version of the server to enable a group of CCTV cameras to regularly upload a still image to our FTP server. Works fine, has done for years. Today I decided to u/g to the (to me) new x64 version.

Server = W2019 server running on ESXi 8.x
Backups up/exported config just to be safe
Made screen grabs to help

Ran new x64 installed, ir removed old x86 and I did *not* remove existing config.

Run up new x64 version, CCTV cameras connected all seemed fine. But...

On inspection, whilst the server is allowing the cameras to create the files, they are blank. see pic. The u/g was done at 1004h.. see the file sizes go to zero..

https://pixeldrain.com/u/CfRrQe4J

I can upload via an FTP client OK.

I've checked the config xml files from before & after and so no real changes.

I've also reinstalled the x64 version but to no effect.

Anyone got any thoughts pls?

Thanks

Rusty

[rusty.hill]

I've now removed the x64 version and reinstalled 0.9.60 beta - and it just works with the default config.

Anyone got any suggestions?

Thanks!

[botg]

Please post a log of a transfer attempt.

[rusty.hill]

Thanks for the prompt reply - I'll have to re-install the x64 version which I'll do later today & revert.
R.

[rusty.hill]

Ok, I've re-installed the x64 version, allowed old x86 settings to remain, and it installed OK. Once again, I can see zero byte files being created.

2024-02-06T12:09:01.179Z DD [File-based Authenticator, FTP Session: 12] Invoked authenticate(()) on worker 0x22e3d3c88a0, with available methods = []
2024-02-06T12:09:01.179Z DD [File-based Authenticator, FTP Session: 12] Authentication for user 'LL-Terrace' not complete. Remaning methods: [password]
2024-02-06T12:09:01.179Z DD [File-based Authenticator, FTP Session: 12] Worker 0x22e3d3c88a0 created new operation 0x22e3d3cb580, with shared_user = 0x0, methods = [password], error = 0

The snippet above looks interesting.....

and attached is a section of the log in 'debug' mode.

Thanks for your help & looking forward to your comments.

R.

[rusty.hill]

and might this relate? viewtopic.php?f=6&t=56791&p=186289&hili ... 5D#p186289

[oibaf]

The log you posted shows that the Server responds to the client that it's ready to receive the file(s):

Code: Select all

2024-02-06T12:08:52.132Z << [FTP Session 11 192.168.0.201 LL-Barn] 227 Entering Passive Mode (192,168,0,12,225,124)
[...]
2024-02-06T12:08:52.140Z << [FTP Session 11 192.168.0.201 LL-Barn] 150 About to start data transfer.

But the client probably never starts sending, and after 30 seconds (a timeout?) it sends the QUIT command:

Code: Select all

2024-02-06T12:09:22.175Z >> [FTP Session 11 192.168.0.201 LL-Barn] QUIT

The QUIT command doesn't get executed immediately, because there's a transfer pending which has not completed yet:

Code: Select all

2024-02-06T12:09:22.175Z == [FTP Session 11 192.168.0.201 LL-Barn] A command is already being processed. Queuing the new one until the current one is finished.

Nonetheless, the client decides to close the connection itself:

Code: Select all

2024-02-06T12:09:22.177Z == [FTP Server] Session 11 ended gracefully.

Do you have any logs on the client side you can analyze? Is there any firewall on the server computer that might be blocking incoming connections on the passive ports?

[rusty.hill]

Thanks for the prompt reply.

1) the clients are CCTV cameras and so, no logs I'm afraid.

2) Recall this set up works fine with the x86 version, on the same W2019 server.

3) The client seems to start to transfer data as it creates the sequential file name (timestamp based) but with the x64 version appears not to send data.. is this a clue? (see pic)

https://pixeldrain.com/u/DpEbX3XL

4) Also, same server, no firewalls that differ between x86 & x64 versions.

Thanks!

[oibaf]

2) Recall this set up works fine with the x86 version, on the same W2019 server.

If you've set any firewall rules for the x86 version, they will not apply to the new version, because they are two different applications.

3) The client seems to start to transfer data as it creates the sequential file name (timestamp based) but with the x64 version appears not to send data.. is this a clue? (see pic)

The file gets created because that's where the data has to flow in, but if the client sends no data, then the file stays empty.

4) Also, same server, no firewalls that differ between x86 & x64 versions.

See response to (2).

[rusty.hill]

Thanks for that - now resolved & working (see pic) https://pixeldrain.com/u/6k4fkT2F

The issue was, as you said, the Windows Defender firewall on the server, which was on and blocks all in bound traffic unless set up to allow. Turn the f/w off, it all works, turn it back on, it stops. Simply adding the (new x64) Filezilla exe as an exception allowed traffic to flow.

Sorry to have been so dense! Thanks again & best wishes - great product & great support.

R.