Let's make scripts!
-
Hi,
You can create a single script for each version using uname like this :
[CODE]DISTRIB_NAME=($(uname -v | grep -w -o “Debian|Ubuntu|Redhat|Fedora”)) # add other redhat/debian basedif [ “$DISTRIB_NAME” == “Debian” ] || [ “$DISTRIB_NAME” == “Ubuntu” ] || [ “$DISTRIB_NAME” == “Other_Debian_Based” ]
then
your instructions here;
elif [ “$DISTRIB_NAME” == “Fedora” ] || [ “$DISTRIB_NAME” == “Redhat” ] || [ “$DISTRIB_NAME” == “Other_Redhat_Based” ]
then
your instructions here;
fi[/CODE]Regards,
Ch3i. -
Pulled code from the FOG installer scripts to come up with the combination. I left Arch commented out at the end of the script if anyone wants to give a go at it. If not I can after testing completes next week.
[url=“/_imported_xf_attachments/1/1891_FogScript.zip?:”]FogScript.zip[/url]
-
[quote=“cml, post: 45691, member: 28688”]cml[/quote]
Thank you for the logic, it’s exactly what was needed![quote=“ch3i, post: 45671, member: 2513”]Ch3i.[/quote]
Thanks for taking the time to convert the commands to Debian, and putting together all the code.I’ve made a few small changes - mostly to simplify things a bit more.
I’ve changed the output path to whatever directory it’s run from.
I also changed the Fedora output from “Fedora21Fog.txt” to just “FedoraFog.txt”
I changed the name of the file to simply “troubleshoot.sh” for simplicity and obviousness.It works beautifully on Fedora 21.
If anyone can think of anything else that should be included in the checks, suggestions are welcome.
If someone can test the Debian portions to see if they work on Ubuntu, that’d be great because Ubuntu is the most used distro for FOG.
And, as we can, get people to continue adding to the script for other distros of Linux.Before you know it, we will have a one-stop-shop for information collection to aid in troubleshooting - be it here on the forums, or to help people with a starting place so they can help themselves.
The latest script is attached.
[B]OSs covered so far:[/B]
Fedora 20/21
Debian[url=“/_imported_xf_attachments/1/1902_troubleshoot.zip?:”]troubleshoot.zip[/url]
-
Few changes.
Ubuntu had to be run with sudo, so added a root check to the beginning of the file.
Ubuntu also has UFW as a firewall, added a check for that.
Changed the Debian/Ubuntu version check to ‘lsb_release -a’ to get more information.
Pointed the log file to a variable that is $Distro-Fog.txt
The script now overwrites the log if ran again.Script and Debian/Ubuntu logs attached.
[url=“/_imported_xf_attachments/1/1907_troubleshoot.zip?:”]troubleshoot.zip[/url]
-
Tom helped with a command to convert the output file to windows-friendly text. I’ve added this at the very bottom of the script.
Latest and greatest is attached.
[url=“/_imported_xf_attachments/1/1910_troubleshoot.zip?:”]troubleshoot.zip[/url]
-
Here’s a more refined version. This particular should work on CentOS/Redhat (in general e.g. 5,6,7) and Fedora.
It also prints that the file is complete and where it can be located.
[url=“/_imported_xf_attachments/1/1911_troubleshoot.zip?:”]troubleshoot.zip[/url]
-
Here’s slightly more refined. Log items are somewhat nice now (more informative). Theres also a lot more checking.
-
Now that’s awesome. This is going to be a major help for troubleshooting!
-
Can we sticky this and add to the wikki.
-
When I ran the latest version in this thread I got the following output in terminal.
./troubleshoot.sh: line 19: [: : integer expression expected
rpcbind: unrecognized service
nfs: unrecognized service
iptables: unrecognized service
Usage FOGMulticastManager {start|stop|restart}
Usage FOGSnapinReplicator {start|stop|restart}
Usage FOGImageReplicator {start|stop|restart}
Usage FOGScheduler {start|stop|restart}
Script Completed Wed May 6 16:10:25 CDT 2015
Your logfile can be found in /home/jhales/test/FOGtroubleshoot.log[url=“/_imported_xf_attachments/1/1977_FOGtroubleshoot.log.txt?:”]FOGtroubleshoot.log.txt[/url]
-
[quote=“Tom Elliott, post: 46119, member: 7271”]Here’s slightly more refined. Log items are somewhat nice now (more informative). Theres also a lot more checking.[/quote]
Hi,
Is it possible to had it in the web interface ?
Regards,
Ch3i. -
[quote=“Joseph Hales, post: 46929, member: 18131”]When I ran the latest version in this thread I got the following output in terminal.
./troubleshoot.sh: line 19: [: : integer expression expected
rpcbind: unrecognized service
nfs: unrecognized service
iptables: unrecognized service
Usage FOGMulticastManager {start|stop|restart}
Usage FOGSnapinReplicator {start|stop|restart}
Usage FOGImageReplicator {start|stop|restart}
Usage FOGScheduler {start|stop|restart}
Script Completed Wed May 6 16:10:25 CDT 2015
Your logfile can be found in /home/jhales/test/FOGtroubleshoot.log[/quote]Hi,
For the status of FOG services I have submit modifications here : [url]http://fogproject.org/forum/threads/add-the-status-of-fog-services-in-the-command-service.12912/[/url]
Regards,
Ch3i. -
I will work on integrating these.
Tom, is the latest and greatest the last thing you’ve posted?
-
Probably?
-
Where in the SVN is this being placed or is it not part of it then?
-
I haven’t coded or tested it for all the specifications of different os’s so it’s not part of it yet…
-
Can we get attachments working? I can’t grab the latest script.
-
This post is deleted! -
[troubleshoot.zip](uploading 100%)
I added a function to add the revision number.
-
@cml Nice, can you upload a copy?
