Hi DFS,

Having exactly the same issue here. Version 0.32 worked for us, so we can rule out any network config issue. When we start the task it dies after 10 seconds. We’ve verified that the multicast services are running, etc…Have you found a fix?

Thanks…

Just so everyone’s aware I fix this bug in SVN in case anybody doesn’t want to delete their location stuff but still want a functional fog system

YYYYYYAAAAAAAAAAAAAYYYYYYYYYY!!!

IT WORKED! IT WORKED!

:D:D:D

I chainloaded PXE to iPXE using pxelinux.0, and now a client machine that is PXE booted resolves to the FOG menu!!

I am very happy!!

Now, what next???

Back to the WIKI/User Guide!

[quote=“Tom Elliott, post: 32679, member: 7271”]Cool
Boot into an upload-debug task.

Run
[code]fixparts /dev/sda[/code]

Hit the letter w, it should exit properly.

When back at terminal run:
[code]fog[/code][/quote]

Thanks Tom - Processed the image and all is good!

Thanks I’ll get all my current requests for Snapins using my work around deployed then I’ll try out the latest SVN version.

If scheduling a shutdown after completion of a donate task, the client reboots rather than shuts down. (fog 1.1.2 on ubuntu server 14.04)

Can anyone help me.

personally, i would recommend using a folder such as /var/www/html/ISO because this folder will not be touched in fog upgrades, but the /var/www/html/fog/service/ipxe/ folder will be moved

[quote=“Fhajad, post: 31428, member: 24675”]You’re not supposed to use pxelinux.0 anymore, you’re supposed to use [B][COLOR=#000000][FONT=sans-serif]undionly.kpxe[/FONT][/COLOR][/B][COLOR=#000000]. You’ll need to update that in your DHCP option settings.[/COLOR][/quote]

This just solved my issue.
Just upgraded from 0.32 to 1.1.2 and TFTP was all “no way Aieesha, I aint no doin dat!”

Changed the DHCP server options (that i had setup ages ago for .032) and BAMO AIEESHA…

Thats right, all you would need to change is “bootfile pxelinux.0” to “bootfile undionly.kpxe”.

As for which version I would recommend 1.2 personally, I switched our systems about a month ago and the changes have all been positive for me: I found the linux handling is vastly improved and iPXE seems much more flexible. The front page of the wiki ([url]http://fogproject.org/wiki/index.php/Main_Page[/url]) has a summary of some of the more important changes.

Incidentally when I put up my fog server I also thought I wouldn’t be using it a lot, but I ended up using it ways I wasn’t expecting (system rescue, “backing up” or migrating hardware), I leave it up all the time now 🙂

I re-uploaded the image as a Single Disk (NTFS Only). and now I can download the image to similar hardware.

I just verified that the .mntcheck exists in both of those directories, and I changed the permission on the images folder on the NAS (labeled fimages) with the following command:
[CODE]chmod -R 777 fimages[/CODE]
Still receiving the same error.

Hi,

[quote=“Tom Elliott, post: 32893, member: 7271”]Normal method of update is download the new file and extract and go to bin/ and rerun installfog.sh[/quote]

i downloaded svn 2040 did a installfog.sh rerun and after that i hang in this:
[IMG]http://i.imgur.com/RqUK3tg.png[/IMG]

the db schema updater page is just empty
[url]http://fogip/fog/management[/url] always redirects to aboves empty page.

EDIT:

Same issue after db drop an reinstall, hmm.

Regards X23

No, there is a “funny” bug once in a while I’m aware of, but don’t remember exactly when I fixed it. It should be fine in SVN though.

Hi,

why isn’t the project driving your recommendations? grrr 😉
i really want to have fog this time running well i tried a first run with 0.32 and was working hard on it but in the end it was useless for our business. This will be the second run i want fog so hardly for a nice automated backup of workstations.

Regards X23

Good luck!

I do not know any more how BOOT my ISO about the server FOG

sorry i didn’t make it very clear - this is what i meant, i’m using a port say :25280 but doing an internal rewrite (so u don’t have to specify port in web address) but ALL traffic fitting the pattern for fog gets directed to apache/fog box using the port:25280 and have no issues… with ur port-translation it seems the initial traffic i.e. /fog/ is going to apache but further traffic is not… try looking into apache config, also check logs they will give u a clue with what is wrong and whether apache is seeing the request. like tom said it is environment/routing issues not fog gui, fog gui doesn’t care what port it’s ur apache doing the listening 🙂 u could test the theory by getting apache to listen on 25280

junkhacker’s avatar is actually a live feed of his expression…

update

I’m noticing some bizarre activity troubleshooting this fog box, going to reinstall fog and post results.