So I solved the problem, and thought I’d let everyone know what it was since I’ve been on here for a couple of days now banging my head against a wall.

As it turns out, an ambitious young would-be network technician decided to go ahead and change what switch my office is on in the MDF down the hall. That switch hasn’t been used in forever since it was so unreliable. I can’t even ssh in to it. I put my office back in the appropriate switch and everything works just like it ought to.

As far as I can tell this has been my issue since square one, and I just wanted to come thank everyone for the help and input along the way to this Mad Hatter’s Tea Party of a solution (chaaaaaaange places!).

Thanks again!

This is a typical problem when uploading to FOG due to compression settings and hardware, If you want to see a slow upload, build your images in VMware and push them up.

If you would like faster upload speeds, adjust the settings in the web GUI. Personally, I upload mulitple images and I prefer if they don’t take up a mound of space. I will allow a slow upload to keep my blazing fast download. I only upload a few times a year, I download almost constantly.

Similar post from same user…
[url]http://fogproject.org/forum/threads/fog-1-1-1-with-proxydhcp-default-ipxe-connection-timed-out.10829/[/url]

Sorry, I had left out that part, its an isolated network, so the only machines on it are those waiting to receive the image, and the FOG server.
It is the same setup as our other FOG server, completely isolated.
We had tried it on a different network initially and found this problem, so we isolated that network but FOG didn’t like the switch, so we changed over to our switch which we know works.
Then came back to our Head Office and tested it again, and we had the same issues.

We do think it could be an issue with the network, but are not sure how to resolve this. The laptop has a Gigabit port, and its connecting to a Gigabit switch.
We are using a stock version of Ubuntu desktop 10.4.4, with a stock install of FOG. The only configuration I have made on the server was to set static IP for the lan connection.
Is there anyway to test it against the network? As proof of the network being the issue?

However the extra steps mentioned here [url]http://fogproject.org/forum/threads/database-update-failed-1-1-0-to-1-1-1.10809/#post-30630[/url] did fix the issue. Seems like /var/www/fog/lib/fog/Config.class.php had a randomly generated password in it for the database the same as /opt/fog/.fogsettings.

Okay,

I found and corrected this bug. It is up in svn at 1862. Thanks for reporting.

Read your other thread:
[url]http://fogproject.org/forum/threads/slow-uploading-image-using-fog-server-1-1-1.10849/[/url]

[quote=“madskillz23, post: 30596, member: 8206”]Check the config on the web interface in FOG Configuration > Web Server > FOG_WEB_HOST and see if that IP adress is correct.

Otherwise check through the config file in /var/www/fog/commons/config.php

Those are good places to start.[/quote]

Thanks!
Turns out its located at /tftpboot/default.ipxe

[quote=“NickConrad, post: 30590, member: 24656”]I’m sure not! I’ll check right now.[/quote]

You are right as always: 127.0.1.1

Hello to all the problem is not resolved, but I re-installed a vm apparently my OS 14.04 LTS server was not really advisable after the official doc

So I redid a vm:

OS: Ubuntu 12.04
FOG Version: 0.32

I managed without too much trouble to install FOG, I can go to the web interface. I recorded a machine (IP + MAC address). Then I started a task to upload the image to the server, it puts “the started task” but nothing happens and if I reload the page it says mssage following error: “Unable to start task”

ping works well between the FOG server and the client machien (ubuntu 14.04 LTS)

Do you have any ideas? ^ ^

Thank you again for your help

Hi Junkhacker,
this solution works. Thank you for your quick help on this.
greetings from germany.

Ahh that makes perfect sense, My apologies for my misunderstanding the group structure. I will use the groups to assign the images and AD settings to the hosts then just multicast the images, I was purely trying it as I had to test an image on a couple of machines and told the guy just to quick image them as I was busy doing something else 🙂

As always thanks for your speedy replies Tom and for the continued work you guys are doing , donation incoming 🙂

Robbie

As a quick update I have added this into the wiki “How-To-Guides”
[url]http://www.fogproject.org/wiki/index.php/Windows_Storage_Node[/url]

It is all in svn now. I don’t know if it will work, but hopefully…

Ahh No worries, if I suspect it is a bug I’ll post there sorry.
I wasn’t sure if it was something I did on the install.

Cheers,

I should have known that. Thanks it fixed that issue.

Because of potential dangers that could happen while in debug we’ve removed this as a standard selection model. There two methods to still get debug though. First is to schedule a task as simply debug. This is probably easiest. Second method is to enable hidden menu and choose which key sequence you want to get back to menu. At boot it will ask for this key sequence. After pressing that key sequence you will receive a login prompt. Type in a valid fog GUI login and pass and it will display the menu with debug as we are all so used to. Hope this helps.

Just an update: We found that if we pull the AC power and the Network cable. Then plug back in, all works fine.