Posts made by Tom Elliott

That’s possible, though I don’t know why. If you still have the fog installer file (fog_0.32.tar.gz) run these commands to get tftpboot back:

[code]cd /opt
wget http://sourceforge.net/projects/freeghost/files/latest/download?source=files
tar -xzf fog_0.32.tar.gz
cd fog_0.32
cp -r packages/tftp /tftpboot
chown -R fog:root /tftpboot
cd /opt
rm -rf fog_0.32[/code]

That should give you back the tftpboot folder and apply the proper permissions. However, did you rerun the installer after getting NFS to work? If you didn’t your install may not be complete.

Check perms on /tftpboot. They should be fog:root recursive

Unfortunately no easy way.

The best method I could come up with is the get the system you need, deploy the partimage image from 0.32, then reupload the image thru 0.33

lanfeu,

Change your line:
[php]if ($Image->get(‘isMaster’))[/php]
to
[php]if ($StorageNode->get(‘isMaster’))[/php]

Otherwise, it’s never going to send the data to any of the servers because Image.class.php does not have an isMaster field.

no you set the password, and change it in the FOG GUI

lanfeu,

Does this work to all nodes in a setup without the isMaster? Or you’re only worried about the information getting sent to the masternode?

Check your username and password for the FOG_TFTP_FTP_USERNAME and FOG_TFTP_FTP_PASSWORD under: FOG Configuration (? Icon) FOG Settings

Make sure they are FOG User on the server, not the database user.

On the FOG Server, login as root:

type:
[code]passwd fog[/code]

Enter the password, then enter in the confirmation of the password.

Then Update these two settings and try setting up your upload task and try again.

I don’t know.

I don’t know specifics of your system and setup. What version of FOG are you running? Are you sure there’s actually an image? Did you upload the image, then test deploy?

Disable PXE BOOT temporarily from the BIOS Options. If it’s still boot looping like that, something else is wrong, like it can’t find a boot disk. (Maybe GRUB?)

So is 172.16.41.180 the Switch address, or the DHCP’d address (is this within range of your network?)

Is your FOG Server setup as a DHCP Server?

Do you guys have DHCP-Reservations? Is this/these box(es) not on DHCP Reservation and getting a totally redirected DHCP Server?

Can you try from a network cable that you know from a system you know works?

Those errors are telling you it can’t communicate with the server. This may be a bios issue on the client side, but at least this is a method of testing.

Is this the only system that has this problem or are other systems running into similar issues?

I don’t know for sure how to get them started, but I know that the Regular Active Tasks should NOT be displaying the multicast tasks.

It sounds to me you’re making a multicast task. Use that link on the task management page rather than the plain active tasks.

The file is actually in:
/opt/fog/service/common/lib/MulticastTask.class.php

I’m taking a look right now.

r1097 released.

Made minor change in wol.php to report if there’s an invalid mac address.
Updated TomElliott.config. It should include the bnx2 firmware during the build. It has other firmware’s as well but I’m more worried, at this point, of bnx2.

r1096 released.

Contains, hopefully, fix for Wake-On-LAN Functionality through the web host. Will test more tomorrow with it just to ensure all is working properly.

Contains new init.gz that has linux-firmware included and fixes the fog.capone file in the /bin/ of the init.gz file. I missed a back-tick and I’m sorry for that.

Shortly, after some testing, I’ll post the updated TomElliott.config file. It’s filesize, once all is said and done, is 6.5 MB. This should also include embedded bnx2/bnx2-mips-09-6.2.1b.fw in the kernel as well.

Your default file (that’s the name sorry) is located at:
/tftpboot/pxelinux.cfg/default

On the bottom line you should see:
[code]TIMEOUT 30[/code]
This means 3 seconds. Thirty seconds would be:
[code]TIMEOUT 300[/code]
I