zzgus Posted February 25, 2017 Share Posted February 25, 2017 (edited) Can someone tell me why I can't access webgui? All vm's and dockers working as expected, no problem accessing they. The problem appeared after installed delunge, I don't know if it can be related. Attached diagnostics (obtained on terminal ssh) Can I reboot from command line? Thankypu Gus unraid-media-diagnostics-20170225-2114.zip Edited February 25, 2017 by zzgus Quote Link to comment
Frank1940 Posted February 25, 2017 Share Posted February 25, 2017 You do have errors being reported in the libvirt.txt file in your logs folder of your Diagnostics file. It appears to be related to one of your VM's. Quote Link to comment
Frank1940 Posted February 25, 2017 Share Posted February 25, 2017 I did a search and it appears that the /sbin/poweroff and /sbin/reboot are the proper commands. Quote Link to comment
zzgus Posted February 25, 2017 Author Share Posted February 25, 2017 @Frank1940 exactly Frank. Solved rebooting my virtual machine. All appear to be well now!!!. How did you get those errors on my log file? What's the section to look at on those diagnostics files? Thankyou Gus Quote Link to comment
Frank1940 Posted February 25, 2017 Share Posted February 25, 2017 32 minutes ago, zzgus said: How did you get those errors on my log file? What's the section to look at on those diagnostics files? The Diagnostics file is a zipped file which contains many other folders and files inside of its container. You normally open it by double clicking on it. Then start down the tree of folders. In the second level down, you will see a folder named logs. Inside of that folder you will find various log files. (How many depending on your server configuration. Apparently, not everything ends up in the syslog!) One of those files in your case is the libvirt.txt file that I mentioned. You can open that file with virtually any test editor and see it. Don't be afraid to explorer those folders, you will find all kinds of information on the various settings that your server is using and the various configuration files. (Those configuration files are there for the benefit of folks who are trying to help solve problems!) Quote Link to comment
zzgus Posted February 25, 2017 Author Share Posted February 25, 2017 Yes I know the content of those zip files but my question was where to look and what to look. Too much information to search if you don't know what to look for !!! thankyou Gus Quote Link to comment
Frank1940 Posted February 26, 2017 Share Posted February 26, 2017 (edited) I am NOT a Linux Guru but what I do is search for " err" (note the space in front of the "e") in the files in the logs folder/directory in the Diagnostics file. That finds entries that have been tagged by the OS as having detected some type of error condition. If you go to 'Tools' >> 'System Log', you can uncheck the boxes at the top (like the one for "Text") and eliminate all of the entries that do not contain one of the other highlighted categories. (These 'Text' entries around an error entry can be useful after you have found the the error line.) Edited February 26, 2017 by Frank1940 1 Quote Link to comment
zzgus Posted February 26, 2017 Author Share Posted February 26, 2017 Thankyou @Frank1940 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.