[EFAULT] Failed to connect to libvirt
Description
Problem/Justification
Impact
SmartDraw Connector
Katalon Manual Tests (BETA)
Activity
Bug Clerk December 18, 2020 at 5:47 PM
Christian Grosch December 11, 2020 at 5:52 PM
Hello @Waqar Ahmed,
yesterday i made the update to 12.0-U1 and after the update was done, the 3 autostat Jails and 4 autostart VMs where starting correct. Can we set the case please on "on hold" and if you do not get any further information from my site, the issuie is fixed with U1
Thanks and regards
Christian
Waqar Ahmed December 11, 2020 at 12:21 AM
Thank you for the report @Christian Grosch, can you please confirm if you are able to reproduce this somehow ? We will of course fix the behavior but that will be a band aid and not really address the problem at it's root as to why this happens in the first place.
Jails are independent and do not rely on middleware to be running so that they can continue their execution. Something else might be up. Please let me know if you have a minimal reproduction case and i can try to reproduce to see what might be happening.
Christian Grosch December 8, 2020 at 4:31 PM
Yesterday, after the middleware daemon is stopped and restarted, i noticed at this time that the jails were in status UP, the IP was displayed but not reachable. after restart the Jails (trough GUI) the Jails are running as required. Can this be related to the middleware daemon being stopped and restartet ?
Regards
Christian
Christian Grosch December 7, 2020 at 4:12 PMEdited
Hello Bonnie Follweiler,
attatched the debug file, as required for detailed information.
$ service middlewared restart is not working in this case. so i looks like, a sub process of the middlewared is crashing but middlewared is reporting running.
Regards
Christian
Dear ixSystems Team,
since migration from FreeNAS to TureNAS i get the error as shown in the screenshot recurring.
At FreeNAS this issue was not existing. To fix the issue without rebooting the host is my following workarround:
$ service middlewared stop
Stopping middlewared.
Waiting for PIDS: 512, 512.
Wait a view seconds....
$ service middlewared start
Chekup status with
service middlewared status
middlewared is running as pid 36503
Re-Login to TureNAS Web-Infterface... the VMs are shown corret.
My Host values
TrueNAS Mini E Case
TrueNAS-12.0-RELEASE
Xeon(R) E-2176G CPU @ 3.70GHz
32 GB RAM
4x4GB Raid 5
the error occurred again today (after 6 days uptime of the host). the error is not a one-time error, but recurring. therefore i ask you to analyze this known bug and fix it in a future update.
Regards
Christian