SOLVED Error: ('Connection broken: OSError("(54, \'ECONNRESET\')")', OSError("(54, 'ECONNRESET')"))

[jyclaudel]

Hi,

Show : See my Freenas System

Version: TrueNAS-12.0-U6.1
CPU: Intel(R) Xeon(R) E-2224 CPU @ 3.40GHz
Memory: 15.9GiB with ZFS Cache: 9.9 GiB
Total Disks : 4 (data) RAIDZ1, Model WDC, type HDD
2 (caches), Model:256G TOSHIBA, type SSD
Ethernet: Media Subtype: 1000baseT with no vlan

It's impossible for me to install a plugin on my TrueNAS 12.
When installing, it's stuck to 20% "Initial validation complete"

and after a couple of seconds, it fails with the error above.

Show : Error

Code:

Error: ('Connection broken: OSError("(54, \'ECONNRESET\')")', OSError("(54, 'ECONNRESET')"))

I wanted to install nexcloud but it fails on others plugins too.


I have already done tests before on another TrueNAS 12 and it works perfectly after an upgrade from FreeNAS 11 to TrueNAS 12.

But on this TrueNAS 12, freshly updated from FreeNAS 11, it doesn't work.


I don't see any logs in the NAS system and I got nothing in the iocage storage.

How to know why the installation fails and how to fix it, please?


Maybe it's a bug here.
Regards.

 

[jyclaudel]

Hello,

Did nobody get this problem before?
And nobody can guide me for knowing where the problem is with some logs info or tips?

Regards.

 

[jyclaudel]

Problem solved, and it wasn't a bug, it was a connexion blocked by my firewall.

But there are no messages or logs to debug the issue.

 

[Patrick M. Hausen]

What kind of log do you expect? The error message clearly says that "something" is resetting the network connection. That's all the NAS can tell you ...

 

[jyclaudel]

Yeah, like you said "something" is resetting the network connection.
There is no display of the port used or whatever due to this reset connection.
It can be a lot of network problems, wrong port, DNS problems, upgrade to TrueNAS12 failed partially, etc...

But it's ok if the NAS can't display more. I understand it.
Have a nice day

 

[Patrick M. Hausen]

It would have reported "hostname lookup failed" or something similar if DNS wasn't working. And "no route to host" if routing was broken. So you can with some certainty conclude that routing and DNS were ok and someone was cutting the connection. As you found out.