We’re not using the new client yet I upgraded to SVN 3463 this morning which fixed the missing client issue.

Please examine this:
https://wiki.fogproject.org/wiki/index.php/Known_FOG_Bugs#The_Image_Resize_Bug

I think you may be affected.

Please examine this:
https://wiki.fogproject.org/wiki/index.php/Known_FOG_Bugs#The_Image_Resize_Bug

I think you’re affected.

@Tom Elliott : Many thanks for your answer.
Now, i will use my brain and think if multicast is really necessary …
In french, a proveb say : “Le mieux est l’ennemi du bien”.

In few days, i will discuss with my collegue of the situation and we will choose a good decision about that.

PS : Learn guitar is hard but it’s a very cool hobbie 🙂

Thanks Wayne!

Thanks for the starting place. I was just gonna experiment when I got home tonight.

If you’ve changed your IP address, there are a number of files you need to change.

/var/www/fog/lib/fog/Config.class.php use "grep -r <old fog server ip> /var/www/fog/lib/fog/ " and find any references you missed there /tftpboot/default.ipxe /etc/hosts /etc/dnsmasq.d/ltsp.conf /etc/network/interfaces

Full list is here

https://wiki.fogproject.org/wiki/index.php/Change_FOG_Server_IP_Address

@Seydoo said:

My problem is solve, due to a bad password (user fog on linux with not the same password than fog tftp user)
tanks to ch3i for his help

The problem was that you have a password policy that does not accept the password “password”.

Now in the WiKi under Troubleshoot FTP.

https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP#You_must_first_upload_an_image_to_create_a_download_task

Thank you Tom for pointing in the right direction. There was one more place that the password needed to be change.
The second location is under:
Storage Management >> DefaultMemeber >> Management Password.
After changing the password and submitting the changes; it seems that it is back online.

Thank you so much!!!

Awesome, thanks I am up and running again. Glad it wasn’t something I did.

Chatted and found out the problem.

This was a two part problem.

Problem number one.

Location Plugin was installed, but no entries were made. I don’t know yet if there’s a bug specifically in this, but there was a location association at one point in time. This lost its association but made it so the default location was not set. This is why the http:///fog/service/ipxe/bzImage was display.

Problem number two.

The FOG Configuration->FOG Settings->TFTP Server->FOG_TFTP_PXE_KERNEL setting was literally set to /bzImage instead of bzImage

Any of the files being stated should not have a beginning precursor as such.

Hopefully we’ve helped out and helped figure out other means to troubleshoot.

Found my problem, the cache of my browser had a problem.

Reset settings and everything is ok!

Also, don’t forget that most of the time the speed issues are either going to be hardware limits now or point at a problem with connectivity to the NFS server.

@Polii123 This is because document root is looking at /var/www/fog (so you can access by simply http://localhost/) and still see fog. However, the FOG_WEB_ROOT setting is not reflecting this. So essentially it’s looking for the link:

http://localhost/fog/status/hw.php in: /var/www/fog/fog/status which I’m going to guess doesn’t exist.

Thanks for the quick help. I will update.

@Polii123 said:

@ch3i said:

@Polii123 said:

But how did they come into my config.class.php file?

Maybe a ghost lol

F*****g ghots 😡 I think Tom has to code some ghostbusters, so things like that won’t happen again. 😂

3430 should not allow the brackets at all. I don’t know why it did it to begin with, but worse things have happened I suppose?

@Wayne-Workman said:

What version of FOG are you using? Look at the cloud in the top left. There will be a number in it.

Hi,

I think partclone use DD with bitlocker and save whole disk.

Regards,
Ch3i.

It’s very common on Ubuntu. Others on other systems have occasionally ran into the issue also. I know on Fedora Workstation 21 in Hyper-V, I had the issue. But with Fedora 21 Server in Hyper-V I don’t have the issue.

It’s just all about the timing, really.

And yes, that post you found is how you’d fix it.

And, there’s no reason to put up with having zero logs. Different systems experience different problems. For some, imaging doesn’t even work unless you make those services wait for a bit.

I think he was just confused about what you were saying, and was wanting clarification.