My guess, as to the particular issue herein, is that php-mysql is not the correct file to be installed. Check the lib/ubuntu/config.sh file and change the references of php5-mysql to php-mysql
If you created the ubuntu VM without a swap partition, that would explain MySQL faltering (assuming it’s running out of memory). The mysql logs under /var/log/mysql will help more than my best guess though.
Yes this is very possible with fog. Fog even has the ability to function as the DHCP server. I don’t recommend using it as the DHCP server unless you intend to use fog off the main network or you plan to disable the DHCP server temporarily while you image.
If you have sites that you want to keep linked together and use the same images at your other site… You can also set up FOG as a storage node. This will allow you to have multiple servers in locations that can synchronize with your central server to get images for the networks they are attached to.
Wiping the system and installing Debian 7.5 allowed the FOG 33 1.0 SVN install to complete without incident.
Found where I needed to plug in the mysql password to get the database connecting, and have the schema installed so I can get in and get started with the program itself. I’ll test it out in the next couple of days and see what happens.
For whatever reason fog needs to be connected to the internet or you will get that error. since I have sonicwall doing dchp it doesn’t support option 66 with IP address only hostname.
Since I had to image using fog dhcp I removed the PC and server from the reset of the network… It didn’t like that.
Once it began copying the image I connected it back to the rest of the network with internet access and it didn’t have issues anymore.
Good post. I ran 0.32 under Debian 7.4 for a while. I did have to do the first three modifications, but I never ran into the ‘Unable to Mount NFS Volume’ issue.
That being said, after I switched to Fog 1.0.0 and did a clean install, I did not have to make any modifications to get it to work. So good news for Debian users as we move forward.
downloads of partimage format images are supported for backward compatibility, but all uploads are done in partclone format. partclone uploads can be sped up by reducing the compression level on the settings page.
// Proxy
if ($Proxy)
{
$ContextOptions[‘http’][‘proxy’] = ‘tcp://’ . $Proxy;
$ContextOptions[‘http’][‘request_fulluri’] = true;
}
This what line 3506 looks like in /var/www/fog/commons/functions.include.php
[quote=“falko, post: 26602, member: 48”]Just wanted to chime in and say I install windows 7 as default from disc (ie. 100mb partition + Second partition as OS) and for years I have always used [I][SIZE=12px]Windows 7 image that was "Single Partition (NTFS Only, Resizable). [/SIZE][/I]
[SIZE=12px]Never had an issue[/SIZE][/quote]
I’m also to guess that you were sysprepping/generalizing your images first?
I just wanted to add my findings to this thread. Ubuntu 14.10 fresh install, fully updated, downloaded Fog .33b via svn. I got this error repeatedly until I installed it from my user account and not the root account. So if you have enabled and are using the root user via being logged in, it can give this error. Took me WAY to long to figure it out. I don’t know why as I’m not a Linux user but that was my solution.
I was downloading and install ubuntu 14.04 after this i’ve installed Fog 1.0.0 on machine with intel core i7 and 32 gb everything was fine. When i put the server adres to connect on fog ex: XXXX/fog/management my pc is freezing the webpage also … i can’t do nothing, i was trying to connect on site online and offline… but no result only if i restart my computer… i can’t acces fog from http. And i don’t have on my ethernet when i want to deploy or upload on image on fog eth0 there… and no DCHP service on. I was read on wiki on forums on tutorials and i was installing correct ubuntu and also fog.
It’s other person who have the same problem? It’s a bug or im to stupid?
