Posts made by Tom Elliott

It’s because the /opt/fog/service/etc/config.php file is generated, from what I can tell, before the actual information is stored in place.

This message, in particular, means it’s not communicating with the FOG Server:
21/01/2014 13:34 FOG::SnapinClient at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
at System.Net.WebClient.DownloadString(Uri address)
at FOG.SnapinClient.startWatching()

For that machine, check the:

IF 32 BIT Windows 7
C:\Program Files\FOG\etc\config.ini

IF 64 BIT Windows 7
C:\Program Files (x86)\FOG\etc\config.ini

Check to verify the ipaddress is set correctly on the system that’s giving you issues.

If not, simply uninstall the FOG Client, and reinstall it (or just add the ipaddress in the appropriate field) making sure to set the fog server information on the system.

Partimage does not work with ext4 partitions at all. This is why you were seeing an issue. It does, however, work with ext3 partitions which was common place for a long time. It wouldn’t surprise me if what you’re referring to was ext3. The differences between partclone and partimage are great. The Pros far outweigh the cons to switch to Partclone, but one of the drawbacks is you have to specify the file system architecture in the partclone binary. This is why I was interested in what the output of blkid was.

I can use a grep command with awk to get each partitions type so that I can set the fstype for the partclone binary. Right now I haven’t the time as it will also require rebuilding the init.gz. I will try to get to this today, but I’ve got to mount a few WAPs thoughout my school district.

Log into the FOG Server as root and go to your installation folder.
Something like:
[code]cd /opt/fog_0.32[/code]

Then cd into the packages folder

[code]cd packages[/code]

Then run these commands:
[code]wget https://svn.code.sf.net/p/freeghost/code/trunk/packages/udpcast-20120424.tar.gz
rm -f udpcast-20071228.tar.gz
sed -i ‘s/udpcastout=“udpcast-20071228”/udpcastout=“udpcast-20120424”/’ …/lib/common/config.sh
sed -i ‘s/udpcastsrc=“…/packages/udpcast-20071228.tar.gz”/udpcastsrc=“…/packages/udpcast-20120424.tar.gz”/’ …/lib/common/config.sh
cd …/bin
./installfog.sh[/code]

EDIT: Fixed a typo in the command above

Yep. Give me a moment to provide the info.

And I thought this worked in 0.32.

Can you perform a compatibility check?

From the PXE Boot Menu, choose Client Information. Then a menu will come up, I think it’s option 4. Both network and hard-drive need to say pass.

My suspicion is it doesn’t recognize your hard drive. The errors you report seeing, aren’t usually indicative of the actual problem, though in your case the one that worries me is the hdparm, It feels like your hard-drive is not recognized though I may be wrong. I say this because you wouldn’t typically get to that phase in the menu if your network was incompatible.

The operation mode could be an issue, though I’ve included AHCI into the kernel, so it shouldn’t pose as much a threat and we use AHCI were I work without issue on FOG 0.32.

I may need to build a new kernel so your system will recognize the drivers.

What fog version are you running? FOG 0.32, FOG 0.33?

@rado,

I’ve already been working on that element, though it doesn’t truncate the command, rather just destroy’s the related associations and, once the associations for that task are all complete/canceled, sets the multicastSessions state field to (complete/canceled) respectively.

That said, I’m currently having trouble with it killing the udp-sender task if you kill the tasks. The multicast.log file shows the task starting, but if you kill the tasks (or kill the multicastSession related to those tasks) it doesn’t kill the task. That may be because I need to actually destroy the session that’s created versus trying to keep it stored in canceled though. So that’s easy to work out.

@fabritreno,
I haven’t added the “fixes” as you’ve recommended yet. Yesterday I was more focused on getting the multicastSessions working. They do work now, however if you update, you may have to perform a service FOGMulticastManager restart.

I don’t know what your many php statements are looking like.

@jbsclm
I’m not seeing a corresponding error, though I do see it repeatedly trying to get the imagelookup based on the key you’ve provided. One thing that makes me wonder, do you have image id AND a dmi key? This may be my fault, but If I’ve read the rewritten capone script (while rewriting of course) properly, it’s checking if either the dmi OR the imagelookup is set.

chad,

progress does get displayed now, on all imaging tasks.

I’ll try and post more formal HowTo to build the kernel using the TomElliott.config as there is an extra step involved now that I’m building firmware’s into the kernel.

Download my latest kernel from The local normal place and it already has that exact firmware loaded into the kernel.

Should be fixed here shortly, forgot to save the association.

r1128 released.

PXE, in and of itself, does not need to have DHCP Server installed.

You can install FOG without DHCP Server and have little to no issues.

Do you not want PXE because you can’t add Options to the DHCP Server or is there already a PXE Server?

I Understand that environments can be rather unforgiving, but I don’t think there’s any easy way to perform this methodology. Then again, I’ve never had to.

I figured out the issue. r1127 is released and should set the correct port now.

can you give me output of your apache2/httpd error log?

@jbsclm

can you update to the latest revision? r1126 and try again.

I want to make sure I get this right!

Are you creating a multicast task for the individual hosts? (One task per host)

Or are you creating a multicast task from the group? (One task to multiple hosts)

I haven’t implemented a code base to kill the original task/job/command and regenerate if the two individual tasks have the same image id.

Does this make sense?

I guess I don’t understand? Are the tasks going to different hosts on different ports from within the same tasking?

Also,

Instead of reinstalling the DB.

Just clear out the sessions and Assocs:

truncate table multicastSessions;
truncate table multicastSessionsAssoc;