Fix traceback when listing jails
In the UI I get an error when clicking on Plugins, see screenshot. Jails is empty. Listing the jails via CLI gives an error:
root@freenas:~ # iocage list
ifconfig: interface epair0b does not exist
Traceback (most recent call last):
File "/usr/local/bin/iocage", line 10, in <module>
File "/usr/local/lib/python3.6/site-packages/click/core.py", line 722, in call
return self.main(*args, **kwargs)
File "/usr/local/lib/python3.6/site-packages/click/core.py", line 697, in main
rv = self.invoke(ctx)
File "/usr/local/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
File "/usr/local/lib/python3.6/site-packages/click/core.py", line 895, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/local/lib/python3.6/site-packages/click/core.py", line 535, in invoke
return callback(*args, **kwargs)
File "/usr/local/lib/python3.6/site-packages/iocage_cli/list.py", line 81, in cli
dataset_type, header, _long, _sort, plugin=plugins, quick=quick)
File "/usr/local/lib/python3.6/site-packages/iocage_lib/iocage.py", line 1143, in list
File "/usr/local/lib/python3.6/site-packages/iocage_lib/ioc_list.py", line 75, in list_datasets
_all = self.list_all(ds)
File "/usr/local/lib/python3.6/site-packages/iocage_lib/ioc_list.py", line 227, in list_all
out = su.check_output(full_ip4_cmd)
File "/usr/local/lib/python3.6/subprocess.py", line 336, in check_output
File "/usr/local/lib/python3.6/subprocess.py", line 418, in run
subprocess.CalledProcessError: Command '['jexec', 'ioc-emby', 'ifconfig', 'epair0b', 'inet']' returned non-zero exit status 1.
#7 Updated by Waqar Ahmed over 2 years ago
- Status changed from In Progress to Blocked
- Reason for Blocked set to Waiting for feedback
Good Morning Gerry. I have been looking at the logs and your issue stems from a bug which was fixed recently. Could you kindly try
iocage stop emby
This should stop your emby jail. Now please don't start another jail and first upgrade your system to the latest nightlies to ensure that the patch exists on your system. Then you can start the jails/plugins and everything should work fine. I think another jail is also affected which you tried to run after emby. Once you perform a stop for emby, if another one is running you'll still be getting a traceback and you'll know which one it is from the traceback. Please try stopping that one as well and once you're done, starting them after updating to nightlies would clear your issue.
This is a temporary work around and we are working meantime to make the process more smoother so your other jails aren't affected by such issues. Kindly let us know if you run into any more issues. Many thanks for your time and effort!
#10 Updated by Waqar Ahmed over 2 years ago
- Status changed from Blocked to In Progress
Yes we have taken note of the issue and it has been fixed in the latest nightlies. However if one jail fails, that shouldn't affect iocage's functionality, so we will be working on ensuring that iocage is functional at all times. If you have any other issues, please feel free to make a new ticket and we'll have it covered. Thank you!
#20 Updated by Christopher Manns over 2 years ago
- File Blank Gui.jpg Blank Gui.jpg added
- File pool view.jpg pool view.jpg added
- File iocage list error.jpg iocage list error.jpg added
- Seen in changed from Master - FreeNAS Nightlies to 11.2-RC2
I don't think this is done, This continues to occur in RC2.
Specifically when migrating plex from a warden jail to the IOCAGE structure via the migrate_warden.py script.
"iocage list" from console reports the error messages as above.
Once the user leaves the web interface page the jail is no lo