There was an issue with storage nodes in the release of 1.2.0. Would you mind upgrading to trunk and then look into the replication logs to verify that your nodes are replicating correctly. (NOTE: ALL instances of Fog should be on the same version. No if ands, or buts about it. This means nodes versions must match server version)
[url]http://fogproject.org/wiki/index.php?title=Upgrade_to_trunk[/url]
A opção está em suas opções de servidor DHCP. Se você configuração DHCP no servidor de nevoeiro que voc vai precisar alterar dhcp.conf. Se você estiver usando outro servidor dhcp impliment então você vai precisar para mudar isso no servidor particular.
The option is in your dhcp server options. If you setup dchp on the fog server you will need to change dhcp.conf. If you are using another server to impliment dhcp then you will need to change it on that particular server.
You got your numbers mixed up.
This past summer I had a fog server running 0.32 and moved to 0.33 and there were so many changes that it was really best to just start over. As Jaymes said that’s the best thing. To save your images, you can download them on to the appropriate machines, check them over for issues, and then upload them when you have built the new server.
This should also help you out. If you wish to do a direct upgrade.
[url]http://fogproject.org/wiki/index.php/Upgrade_to_1.x.x[/url]
[LIST=1]
[]When fog installed did you use a password for the database?
[]Can you login to the database using username root? --> mysql -u root fog
[]If yes to question 1, can you login to the database using --> mysql -u root -p <password you entered> fog
[]Do you have any errors in your mysql log?
[]Are there any errors on your screen when trying to login to the database?
[]What does show up when you go to your fog server URL? (picture required)
[*]Can you give use your apache error log file? (file upload required)
[/LIST]
Pictures and/or video work wonders!
Can you give us the example of your image folder path/name for future reference of this issue?
Do you have to use multicast? You can still create a unicast task (Download) using the group and deploy. Multicast is just a particular method of deployment.
This is a re-occurrence.
[url]http://fogproject.org/forum/threads/error-cant-evaluate-_crs-12311.11894/[/url]
Try some of the trouble shooting in these posts. It may have something to do with your drive and the way it is formatted.
[LIST]
[]Newest revision is 2868. Please make sure you update then be sure that all old multicast tasks are killed. Then start a new task.
[][url]http://fogproject.org/wiki/index.php/Multicasting[/url]
[*]I don’t use multicasting but I will help muddle through it.
[/LIST]
To kill multicast tasks:
[CODE]sudo service FOGMulticastManager stop
sudo killall udp-sender
sudo killall udp-sender
sudo killall udp-sender
sudo service FOGMulticastManager start[/CODE]
After changing the values in .fogsettings you will need to re-run the installer. This will re-push the settings that you have there. Just changing the values in .fogsettings will not affect anything.
Please also post your install log. Located /var/log/foginstall.log
FYI
HP Compaq 6715s and HP Compaq 6715b is on the list as working for .032 but not confirmed for 1.x.x. HP Compaq 6735b is however tested and working with 1.x.x.x. Also confirm that you have the most up-to-date BIOS on these devices.
This shows that STP is enabled by default. It’s surprising that you got to the “[B]Fatal Error: Failed to mount NFS Volume”[/B]
Was this during a upload/download or does this occur before the FOG Menu appears?
[SIZE=13px][FONT=arial][COLOR=#262626]this should be kind of simple in theory. prompt user for ip address and give them a choice for the kpxe file they want and boot to network with this information. basically remove the dchp out of the equation.[/COLOR][/FONT][/SIZE]
[quote=“TonyB.2871, post: 40274, member: 26980”]To answer your questions in order…
I am not entirely certain what you are speaking of in regards to the trunk, more specifically the version
[/quote]
[url]http://www.fogproject.org/wiki/index.php/Upgrade_to_trunk[/url]
Do you see the FOG MENU?
Verify your DHCP options.
Verify your network switch settings are correct. If STP is enabled you will need to read this wiki. [url]http://fogproject.org/wiki/index.php/IPXE[/url]. If you recently changed a switch this could easily cause an issue. When in doubt pull the fog server out of your network and create a small private network for testing. Try using an un-managed switch.
I’m just throwing this out there but could you update to trunk. May issues have been corrected since June. If you have a trunk version please verify that you have at least r2836.
Video would be nice.
Same thing happens on Lenovo R500’s and Lenovo R61’s. Changed AHCI to compatibility. Its a known issue and its related directly with the hardware and BIOS. This will affect any install of Windows, ghosting, Acronis True Image and FOG. Sorry but not a FOG issue.
I would assume the edits to apache has effected your system.
An easy way to redirect xxx.xxx.xxx.xxx to your xxx.xxx.xxx.xxx/fog/management is to edit/create the index.php file in /var/www/
I have this in the file:
[CODE]
<?php header(‘Location: ./fog/index.php’);?>
[/CODE]
this will redirect to /fog/index.php which points to /fog/management/index.php taking you directly where you need to go.
Np. This step specifically will let you know if your tftp, firewall, and rights are correct. If this fails then it could be one of these causing your issue.
[SIZE=4][B][FONT=sans-serif][COLOR=#000000]0.33 and 1.x.x[/COLOR][/FONT][/B][/SIZE]
[LIST]
[]From your FOG server test out tftp
[/LIST]
[COLOR=#000000][FONT=monospace]tftp -v X.X.X.X -c get undionly.kpxe
[/FONT][/COLOR]
[LIST]
[]From a Windows PC run at the cmd prompt: ([URL=‘http://fogproject.org/wiki/index.php/Windows_TFTP’][COLOR=#0b0080]Windows TFTP[/COLOR][/URL] Service must be Installed first)
[/LIST]
[COLOR=#000000][FONT=monospace] tftp x.x.x.x get undionly.kpxe[/FONT][/COLOR]
Could you attempt some troubleshooting? [url]http://fogproject.org/wiki/index.php/Tftp_timeout…#Other_Troubleshooting[/url]