Posts made by seq-nate

seq-nate

Sweet thanks for the info.

seq-nate

So, with the Location plugin active the computers will only pull the image from the assigned storage node?

seq-nate

Here is my setup:
I currently have 12 geographically separate campuses, 1 Master server at my main campus and 11 storage nodes at the other campuses. All are running Debian 7 and FOG 1.2.0. On the FOG home page, it says that there are 120 free which I take that as if I start doing mass imaging the first 10 machines will pull from the storage node where I start the imaging and then start pulling from my other storage nodes?

If I understand this correctly, each of my campuses must have a storage group and the one storage node will be the only node in the group and the one node needs to be master. I initially set up the nodes this way and replication was not working between them so I set them back to one group and they all started talking again.

Can someone explain if my understanding is correct?

seq-nate

I know this is an old thread but it doesn’t look like it was answered. I found that I am having the same problem as TuxMeister getting a boot failure. Are there supposed to be other TFTP boot files inside the ISO folder and where do I find these files?

seq-nate

I noticed FOG 1.0.1 was posted so I ran the update and it booted initially but the kernel was not able to see my machine because of what I believe was an issue between the kernel and VirtualBox ([url]http://fogproject.org/forum/threads/virtualbox-4-2-16-and-kernel-3-11.6339/[/url]).

I remember I was using a vmware kernel on my old FOG server (running .32) so I copied the Kernel over to the new server and set the Host Kernel for my template machine and tried FOG again. It booted again and began to load the kernel but then froze. I rebooted, FOG booted again and began to load the kernel and got a little further and froze again. I decided to reboot again, because what the heck another reboot couldn’t hurt. This time… no go, I got the BOOT FAILURE message.

Update:
I changed the Kernel back to bzImage and was able to boot but it went back to searching for /dev/sda. I’m guessing now that the problem, once I get it booted, is getting a kernel that will work.

[url=“/_imported_xf_attachments/0/768_can’t see partitions-VBOX.png?:”]can’t see partitions-VBOX.png[/url]

seq-nate

I downloaded the latest FOG and the the first time I tried to upload from the VM it proceeded past where it was hanging up and appeared to be getting ready to upload. Partclone came up and flashed an error and then rebooted. After reboot, it went back to giving me boot errors. I kept rebooting hoping that it would proceed again so I could get the exact wording and after 8 tries it went through again. the wording is:

[CODE]Starting to clone device (/dev/sda1) to image (/tmp/pigz1)
Clone: open /dev/sda1 error[/CODE]

Then once again it rebooted.

My apache log came up with:
[CODE]tail: cannot open ‘/opt/fog//log/multicast.log’ for reading: No such file or directory
[Tue May 13 07:56:44 2014] [notice] caught SIGTERM, shutting down
[Tue May 13 07:56:45 2014] [notice] Apache/2.2.22 (Ubuntu) PHP/5.4.9-4ubuntu2.4 configured – resuming normal operations
[Tue May 13 07:57:26 2014] [error] [client 10.10.4.143] PHP Fatal error: Call to a member function get() on a non-object in /var/www/fog/lib/pages/DashboardPage.class.php on line 30, referer: http://10.10.7.244/fog/commons/schemaupdater/index.php?redir=1[/CODE]

I also checked config.php and confirmed that I had set the password.

[url=“/_imported_xf_attachments/0/760_boot-once.png?:”]boot-once.png[/url]

seq-nate

Thanks for the reply Tom,

The last FOG install was Friday (may 9th) from:
svn://svn.code.sf.net/p/freeghost/code/trunk
If there is was a newer update I will try updating my install.

I tried:
Kernel Issues: [url]http://fogproject.org/wiki/index.php/FAQ[/url]
No change.

The only thing in my apache logs is:
[CODE][Sun May 11 06:49:11 2014] [notice] Apache/2.2.22 (Ubuntu) PHP/5.4.9-4ubuntu2.4 configured – resuming normal operations
[/CODE]

Currently running:
FOG Version: 1.0.0
Ubuntu 13.04

seq-nate

I apologize now if there is a already a posting answering my question but I haven’t been able to find it.
I have been using fog .32, running dhcp, on a laptop so I can image on an isolated network, and making my image in Virtualbox and uploading perfectly. I am currently in the process of integrating a fog server into my network to eliminate a lot of the manual process of imaging.

What I am using in my new setup:
Ubuntu 12.04 server
Fog 1.0.0

I can can boot a normal workstation and register, schedule tasks, etc. When I try to boot the virtualbox (template machine) into FOG I get:

[CODE]Configuring (net0 00:50:56:37:df:20… Error 0x040ee119 (http://FATAL: INT18: BOOT FAILURE[/CODE]

Every once in a while (very rarely) it will boot to fog. I was able to register the VM but it will not upload the image.

Is there something I missed to allow a VM to work with FOG?

seq-nate

checked the log files but didn’t have a look at the wiki … Sorry, the Google wasn’t helping and I didn’t think to just go straight to the source (wiki).

seq-nate

I have been having some previous problems so to eliminate problems like virtual machine, subnet … I installed a fresh copy of Ubuntu 14.04 onto it’s own machine, made sure it was in my data subnet not management where I was playing. downloaded a fresh copy of fog .32 and started install. I had to change the interface from eth0 because Ubuntu wants to call my network interface p5p1 (and it won’t let me change it) I ran into a problem with udpcast failing but was able to resolve that by downloading the latest udpcast file. The fog installer then was able to complete the install with no errors. I then went to [url]http://10.10.7.244/fog/management[/url] and got
[SIZE=6][B]Not Found[/B][/SIZE]

The requested URL /fog/management/index.php was not found on this server.

Index.php is there and has the appropriate permissions. I am lost as to why this is not working.

seq-nate

When will .33 be available for upgrade?

seq-nate

Good to know. I did some searching around and it looks like the patch is available for .31 and will be in .33 but currently not in .32. Is that right?

seq-nate

After an experience I had yesterday, I don’t think a storage node is what I am wanting to use. I was pushing out an image to a machine and noticed that it was connecting to my storage node to try to pull the image (it errored out because the image still has not replicated.)

The problem I have with this is that my intent was to have a master node at my main school and a storage node at various campuses but what I found yesterday was that if I am imaging a machine at campus A it may pull an image from Campus B which would take up precious bandwidth.

Someone correct me if I am wrong but what I believe the storage nodes are most useful for is multi-casting and in my particular set-up it would be better to have individual master nodes at each campus and copy any new images manually to each campus.

seq-nate

Looking back over the posts still trying to understand what is needed. I looked at Lee’s post, troubleshooting connections between the two machines and realized something, there is no Mysql database on the node mysql-server does not install when installing a node.

seq-nate

I removed the bind address on both server and node, and both systems do not have a firewall. I checked mysql on the server and made sure the password was set. On node, mysql-server is not installed so there is no user to create or check.

I have set the node to try using root user, which I can log into the server from node with, and restarted FOGImageReplicator and Im still getting.

[CODE][02-27-14 7:32:54 pm] * Starting FOG Image Replicator Service
[02-27-14 7:32:59 pm] * [02-27-14 7:32:59 pm] Checking for new tasks every 600 seconds.
[02-27-14 7:32:59 pm] * [02-27-14 7:32:59 pm] Starting service loop.
[02-27-14 7:32:59 pm] [02-27-14 7:32:59 pm] Failed to connect to database server, will try again in next iteration.[/CODE]

seq-nate

Jaymes, I have completely reinstalled both my main FOG and the storage node and started from scratch. This did resolve a different issue with searching for hosts but did not resolve the issue of communication between my main and node.

seq-nate

Sorry for the delay in posting. Since my last post, I did something to my database and locked myself completely out. I purged everything and reloaded. My main fog server is running great (actually better, I had another unrelated issue that is now gone) and I just installed the storage node and followed step by step instructions on the web and got nothing. I retried the instructions to try to connect to the storage node through the main server

[CODE]first off - run the below command on your main server:
mysql -u fog fog -pPASSWORD_GIVEN_AFTER_INSTALLING_FOG_ON_THE_NODE -hIP_OF_NODE[/CODE]

and once again got

[CODE]ERROR 2003 (HY000): Can’t connect to MySQL server on ‘10.24.1.2’ (111)
[/CODE]

I commented out the bind-address line on my node and restarted with no change.

seq-nate

mysql -u fogstorage fog -pfs123456 -h10.24.1.2
ERROR 2003 (HY000): Can’t connect to MySQL server on ‘10.24.1.2’ (111)

seq-nate

So, I need to change the fog and mysql user’s password to match what? If I am changing the mysql fog user on the master node that would not allow me to connect to my web ui.

seq-nate

I can’t get past step one

I entered:

mysql -u fog fog -p <password from storage node> -h <IP of storage node>

and it didn’t go through

I then entered:

mysql -u fog fog -p --host=<IP of storage node>
Enter password: (entered <password from storage node> )
ERROR 2003 (HY000): Can’t connect to MySQL server on ‘<IP of storage node>’ (111)