[quote=“JustinGSEIWI, post: 27621, member: 23733”]Thank you for the reply.

I am following the directions to get fog 0.32 installed on Ubuntu 12 with this link.
[url]http://www.fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server[/url]

In step five, I am unable to edit the exports file. How do I do this? It is in use or write protected?

Justin[/quote]
[code]

sudo gedit /etc/exports[/code]

We have moved the nodes to the same VLAN as the Master and changed the storage location IP config to the Masters IP address. This seemed to resolve the issue for a little while. After the weekend we came back and were running a few more tests before we implemented this solution for our servers. When we tried to capture again it started uploading to the storage node again instead of the master. We are hoping to get this up and running for our summer imaging throughout our district. We will be imaging 4000-6000 new computers and roughly 10000 existing computers.

If anyone has any advice as to what we could test it would be greatly appreciated.

[quote=“Dageezah, post: 27644, member: 4267”]Hi All,

I keep getting :

esas2r: driver will not be loaded because no ATTO esas2r devices were found
i2c-parport-light: adapter type unspecified

whilst reading several posts, I understand it is safe to ignore, but I cannot find a fix - reason being when I get this message the computer pauses for about 4 minutes before proceeding… very annoying!

Using latest Fog 1.0.1 with latest Tom Elliot Kernal.

Any help would be good.

Thanks[/quote]

While annoying, I’m very sorry, you may need to look into building your own kernel. My kernels are very much generalized and contain a LOT of drivers in them. This is WHY it’s taking so long to load. Some systems take longer than others as well. I don’t know why. If it’s that “frustrating” of an issue, build your own kernels and only contain the driver set’s needed for your particular system.

14.04 still has issues and 13.10 will work about half the time after reboot

[url]http://fogproject.org/forum/threads/tftpd-hpa-not-starting-on-reboot.10560/[/url]

anyone got any ideas on this? kinda stuck and our old node with smaller disk is running out of space.

cheers

Aaron

I had this same issue on my last reinstall, and corrected it.

First, as WolfBane said, you must make sure if you set a MySQL password, you update your config.php file.

Other than that, the fix that worked for me for this issue was to stop and start the MySQL service. After that it works fine. Try running the following in Terminal:
[CODE]sudo service mysql stop
sudo service mysql start[/CODE]

If you go to the web interface after this, click next on the database schema update page, does it let you go on? If yes, then see my permanent fix for this solution [URL=‘http://fogproject.org/forum/threads/mysql-problem-what-am-i-doing-wrong.10515/#post-27515’]here[/URL].

Hope this works for you, let us know!

I solved the problem. For some reason the isc-dhcp-server was not running. This hadn’t happened before, but starting that and restarting tftpd-hpa fixed the DHCP issue.

This is for Ubuntu 12.04.04 with Fog 0.32

First and foremost, system.php is the file that always defined SPACE_DEFAULT_STORAGE, and at least with 0.32 and higher, has always been defined and located in commons/system.php.

Second, the SPACE_DEFAULT_STORAGE variable always returned based on that particular setting. This meant, if you had a storage node located at /data/somedir/images rather than /images, the only way to get the data to return was to either change this variable to the proper location on the fog server or create a symbolic link as /images on the system.

This same applied to other storage nodes. I fixed this issue by just performing a df on the systems proper directory thus limiting the reporting of the SPACE_DEFAULT_STORAGE unless it could not find information on the other nodes.

It didn’t moved, it never moved, just the means of obtaining the information changed.

is there an active or scheduled task for that host?
what version of fog are you running?

Could have been the kernel – but what I ended up doing was a clean install of 1.0.1 – and all is working well with the newer devices. Just have a few path issues to work out since I have the images folder on a separate drive.
Thanks.

I have updated the wiki to avoid further confusion. The 192.168.1.1 that you chose at the beginning of the install IS the ip you want to use, not 192.168.1.5.

Make sure to put
[QUOTE][FONT=monospace][COLOR=#000000]/fog/management[/COLOR][/FONT][/QUOTE]
after the ip or you will just get a “It works!” page from Apache(the web service).

the ghost boot image.

We used ghost and i discover fog, and we migrated. but we have 250 images to transfert (and fog don’t allow to make usb restauration key) and i need to load first in ghost to create image in fog after.

That did it. I did set a different mySQL password other than the default and I forgot to go back and change it in there.

Thanks so much.
Andrew

do you have a bluetooth device plugged in to this computer?

Okay, here’s my crude but functional workaround…

Since I figured the problem is that the mysql service was being locked out of a file it needed, and restarting the service completely fixes the issue, I changed my Ubuntu server to stop and start the mysql service after boot up. Fairly simple procedure, just do the following:

[CODE]sudo nano /etc/rc.local
[/CODE]

In this file, above “exit 0”, type “service mysql restart” (no quotes).

Ctrl X to exit, Y to save, Enter to save to same file.

From that point forward, every time your server reboots, it will automatically bring down and up the SQL service, solving the “Unable to connect to database” error.

Hope this helps someone out there, let me know if anything is unclear!

the kernel refers to a part of the fog system that is used for creating and deploying images. fog uses a 64bit kernel now, for hosts that support 64bit. this does not require any changes to the hosts being imaged.

unfortunately, the easiest way to do that would probably be directly in the database. fog database, hosts table, hostKernel column, i think
(i use phpMyAdmin for these kinds of tasks, but someone better at command line stuff could probably tell you how to do it with a single command)