Could we have the web interface indicate that a storage node is correctly connected passwords match ect… maybe a green dot like the ping status when its added or listed in the all storage nodes list. A second indicator that all the images are in sync with the main repository.
Posts
-
Storage Nodesposted in Feature Request
-
RE: Is there going to be another official release?posted in General
I believe they are working to a final release under this code base before the switch away from mysql and php the only part left needing significant work is the new client which is advancing quickly.
-
RE: Let's make scripts!posted in FOG Problems
Where in the SVN is this being placed or is it not part of it then?
-
RE: Storage Node Setupposted in FOG Problems
The WEB interface won’t save a blank username and password it simply keeps the previous value and when I try to delete the node it goes to a blank screen form both the detail screen and the all nodes list.
-
RE: Storage Node Setupposted in FOG Problems
As seen here Ubuntu 12.04 SVN 3405. Where do I edit this to fix it and what account do I use an existing admin on the Ubuntu server or something in the fog installer.
[url=“/_imported_xf_attachments/1/1998_storage.png?:”]storage.png[/url]
-
Storage Node Setupposted in FOG Problems
I resetup my storage node that I had taken offline for troubleshooting when I upgraded to the latest SVN the username and password show as blank.
-
RE: Hash Check on Updateposted in Feature Request
Maybe adding a hash check to the troubleshooting script? Were we going to include the updated troubleshooting script in the utils folder for SVN.
-
RE: Legacy/New Client with FOG server swap-outposted in General
Most common issue seems to be the ad password not encrypting properly or copying properly during some upgrades.
-
RE: Hash Check on Updateposted in Feature Request
Getting the installer isn’t the issue, the issue is when the installer is run and it gets components and inits and some of the files fail to transfer we could use a more obvious error message and perhaps a prompt to try and fetch again or roll back any changes. I agree it is a nontrivial task but it would solve a reoccurring issue.
-
RE: PXE boot menu then black screenposted in FOG Problems
Really sounds like its timing out at one of the steps. I second the recommendation to go SVN.
-
RE: Nodes, Groups and Mirroring, oh my!posted in General
If your bandwidth between sites is adequate then you just need to set up the broadcast domain to all your vlans and it should work fine.
-
Hash Check on Updateposted in Feature Request
With the issues at source forge for an example could the SVN installer run a quick check at the beginning confirming that the get command was successful before updating the local install.
-
RE: Sysprep with out OOBEposted in Windows Problems
When you run the check out command what version did it say it found?
-
RE: Sysprep with out OOBEposted in Windows Problems
if it shows 1.2.0 you aren’t running the SVN version then if it was SVN your cloud logo would have a 4 digit number most likely 3374.
-
RE: Sysprep with out OOBEposted in Windows Problems
[SIZE=4][B][FONT=sans-serif][COLOR=#000000]Download the package[/COLOR][/FONT][/B][/SIZE]
[COLOR=#000000][FONT=monospace]cd ~
mkdir svn
cd svn
svn checkout [URL=‘https://svn.code.sf.net/p/freeghost/code/trunk’][COLOR=#3366bb]https://svn.code.sf.net/p/freeghost/code/trunk[/COLOR][/URL]
[/FONT][/COLOR]
[SIZE=4][B][FONT=sans-serif][COLOR=#000000]Install It![/COLOR][/FONT][/B][/SIZE][COLOR=#000000][FONT=monospace]cd ~/svn/trunk/bin
sudo ./installfog.sh[/FONT][/COLOR] -
RE: Sysprep with out OOBEposted in Windows Problems
This one if running Ubuntu
cd svn
sudo svn checkout [url]https://svn.code.sf.net/p/freeghost/code/trunk[/url]
Install It!
cd ~/svn/trunk/binsudo ./installfog.sh
-
RE: Sysprep with out OOBEposted in Windows Problems
I think you have an issue on the server side try this part of the wiki or maybe simply a reboot of the server.
[url]http://fogproject.org/wiki/index.php?title=Unable_to_connect_to_TFTP[/url]Fedora 20/21
status/enable/restart
systemctl status xinetd.service
systemctl enable xinetd.service
systemctl restart xinetd.serviceor more likley what Wayne posted
-
RE: Let's make scripts!posted in FOG Problems
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]