Admin UI [Error] Session ended with error from source 0. Reason: ECONNABORTED - Connection aborted.

[pavan.kumar]

I have been using FileZilla server for some time, however, since I updated to the latest version, the server closes every day, the GUI is still open perfectly, what seems to close is the FileZilla server.
When it disconnects and I get the error message, I have to run Start FileZilla Server again to get it to connect again.

It doesn't happen every day at the same time, it happens at different times, basically it's as if it was disconnected, please review the log information below.


<Date> Info [Type] Message
<20/10/2022 7:14:59> Admin UI [Error] Session ended with error from source 0. Reason: ECONNABORTED - Connection aborted.
<20/10/2022 7:14:59> [Error] Disconnected from server 127.0.0.1:14147 with error 106 (ECONNABORTED - Connection aborted).
<20/10/2022 7:14:59> Admin UI [Status] Attempting reconnection to server 127.0.0.1:14147 in 2 seconds...
<20/10/2022 7:15:03> Admin UI [Error] Client failed connection. Reason: ECONNREFUSED - Connection refused by server.
<20/10/2022 7:15:03> Admin UI [Error] Failed connection to server 127.0.0.1:14147. Reason: ECONNREFUSED - Connection refused by server.
<20/10/2022 7:15:03> Admin UI [Status] Attempting reconnection to server 127.0.0.1:14147 in 2 seconds...
<20/10/2022 7:15:07> Admin UI [Error] Client failed connection. Reason: ECONNREFUSED - Connection refused by server.
<20/10/2022 7:15:07> Admin UI [Error] Failed connection to server 127.0.0.1:14147. Reason: ECONNREFUSED - Connection refused by server.
<20/10/2022 7:15:07> Admin UI [Status] Attempting reconnection to server 127.0.0.1:14147 in 2 seconds...
<20/10/2022 7:15:11> Admin UI [Error] Client failed connection. Reason: ECONNREFUSED - Connection refused by server.
<20/10/2022 7:15:11> Admin UI [Error] Failed connection to server 127.0.0.1:14147. Reason: ECONNREFUSED - Connection refused by server.

OS Version – 10.0.17763 Build 17763
FileZilla Server Version- 1.7.3

[botg]

It might be that the server service has crashed. If so, it should have automatically created crash dumps in the %LOCALAPPDATA%\CrashDumps directory of the Windows user account the FileZilla Server service runs under.

By default the FileZilla Server service runs under the SYSTEM account, so the corresponding CrashDumps directory should be under C:\Windows\System32\config\systemprofile\AppData\Local\CrashDumps.

Please email the latest crash dump from FileZilla Server to tim.kosse@filezilla-project.org

[pavan.kumar]

I sent a mail to the respective mail ID that you provided. kindly check and advise.

[botg]

Thank you for the crash dump. We have identified a potential cause and will make changes in in an upcoming version.

[pavan.kumar]

Thank you for your response. Could you kindly let us know which version and when we should expect this issue to be resolved?

[botg]

When it's done.

[pavan.kumar]

Hello Tim,
Hope you are doing well.

We have about thirty users on the FileZilla server, but three of them are giving us trouble with the error message "socket.error: [Errno 146] Connection refused." The error description is sent to you through email.

We have experienced a significant production issue during the last few days. Are these errors related to the one we highlighted earlier?

Please let us know when we can expect a patch for the error that we previously reported, since it is causing issues with production. Thank you for your support.

[pavan.kumar]

We are also able to view the messages below several times throughout the day. Does this indicate that the server is crashing and restarting several times?
We are not getting these messages on the stage server; this is exclusive to production. I was grateful for your comment on this.

2023-11-03T01:29:01.422Z == ===== FileZilla Server 1.7.3 new logging started =====
2023-11-03T03:19:29.286Z == ===== FileZilla Server 1.7.3 new logging started =====
2023-11-03T04:03:51.118Z == ===== FileZilla Server 1.7.3 new logging started =====

[botg]

The "new logging started" line is printed each time the server is started, or the log file path is changed.

We're still working on the next version. It will be ready when it is ready.

[pavan.kumar]

Thanks for your response. Much appreciated.

We have noticed that the current version in the production server is 1.7.3 and in the stage server is 1.8.0-rc1, yet we have chosen for updates to be automatically applied to both servers. We were not observer this problem in the stage server i.e. "Admin UI [problem] Error from source 0 caused the session to stop. Reason: ECONNABORTED - Aborted connection." perhaps as a result of 1.8.0-rc1 version. In production, how can we update to 1.8.0-rc1?

Please find the attachment for reference

[botg]

There are known, crippling bugs in 1.8.0-rc1, it is not fit for production.

[pavan.kumar]

I see. Thank you. To resolve this matter, we shall wait our time until the subsequent release.