@Ph3noM Fog doesn’t set a DB password - if fog sets up the DB on a new server, it’s left blank. The installer (at least in FOG 1.3.0 beta) asks you for a DB password just in case you set one in the back end. And of course if that’s the case (and 99% of the time it is) then the field in /opt/fog/.fogsettings would be blank as well.

How is DHCP setup in your network? Maybe this is dnsmasq ProxyDHCP and the new EliteBooks (EFI??) don’t like to talk to it?!? Just a random guess.

@Wayne-Workman Sorry Wayne ignore last re fog certificate. Issue was only on my laptop and has since been resolved.

I have not come across this issue since starting this thread (I did update FOG somewhere after the start of the thread which included updates for the binaries)

At worst it will ask me to enter the IP address which is a small price to pay for peace of mind.

So I guess this can be considered solved for now.

@GregorS
The problem is with your server. Notice the log lines

14.12.2015 12:53 Data::RSA ERROR: Certificate validation failed 14.12.2015 12:53 Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: The signature of the certificate cannot be verified. (NotSignatureValid) 14.12.2015 12:53 Middleware::Authentication ERROR: Could not authenticate 14.12.2015 12:53 Middleware::Authentication ERROR: Certificate is not from FOG CA

@Tom-Elliott would be able to help you debug why your server certs are incorrect.

@Tom-Elliott Looks like there was something wrong with yum. I did a basic yum clean all and that seemed to solve my issues with connecting to the mirrors. I’m progressing through the installation now. Thanks again for all of your help everyone!

@Tom-Elliott said:

@Mats-Nilsson said:

Problem solved. I installed a complementary Java Based Offline Proxy Server… [url]http://www.proxy-offline-browser.com/[/url]
(Java was bundled in Ubuntu) proxy ip 127.0.0.1 and port 8080 in Fog configuration and Firefox settings
I consider Fog to complex to be modified according to my wishes. It is clearly built to be online. To much work

Problem solved as stated.

However, your information is correct. I just wanted to know why the revival, are you having the issue?

I was having the issue, hence the reason I ended up on this page. I prefer the original method mentioned earlier in the page for an earlier version of fog without needing to download additional software. A question was raised regarding the newer version of fog, one to which an answer would have saved me some time. Upon finding the solution, I posted the results for anyone that comes upon this page to save time of their own. I honestly didn’t want to bring up a discussion, rather, just an FYI note for future viewers. The information I provided is valid and would be quite useless in a new thread.

@Wayne-Workman, @Kiweegie this should all be fixed now. Well a while ago but I’m just now updating lol.

As you all are probably well aware this should be fixed.

@Sebastian-Roth @george1421

Hi both, thanks for the pointer to log, that showed me issue. Had reinstalled from trunk and while fog password was ok per my records in the below locations I had like a complete rookie forgotten to reset password on the server itseld post upgrade… d’oh!

Storage Management > All Storage Nodes > Default Member > Management Password
Fog Configuration > Fog Settings > TFTP Server > FOG_TFTP_FTP_PASSWORD

cheers all
Kiweegie.

@Tom-Elliott He’s french, I’m helping him via the chat.

Never mind, apparently the guy that was told to make the changes only did it for one of our sites and not all seven. sorry for wasting your guys’ time.

This issue is resolved now.

@Wayne-Workman HI Wayne, thanks for this. I’ve upgraded to latest trunk and can confirm this now works as expected. Please mark call as resolved.

regards Kiweegie.

@Tom-Elliott Thanks - I updated after posting and it solved the issues, I’m on 5734 and all is working fine.

@Wayne-Workman you’re absolutely correct. 2094 is the svn rev at which we made the tag of 1.2.0. But if you’re pulling the tag instead of trunk, the rev will display the current rev of the repository, not the rev of the tagged released

Remoted in, and found that he is using a 32 bit OS. The value I was using to do the math was a function called intval which cannot do math beyond 32 bit scope (if the OS is 32 bit).

To fix, I just removed the intval function around the free/used space.

@arainero Thanks for reporting back so quickly! Great to hear that I was on the right track and this seams to be fixed for you. Please do not upgrade (run the installer again) yet as we are still waiting for others to report back if their (closely related) issues are fixed as well. Tom won’t update the init files till we hear back from them. So your issue would come back if you’d upgrade just now. Feel free to ask about upgrading here in this thread by the end of next week again. Hopefully we know more from the others by then and have updated the inits as well.

@JasonW said:

all used and unused space must be read by the FOG client.

Depends on the image type. Resizeable images resize the partitions first, so that only used space is captured.

When deploying an image, unused space is recognized in the image file and is much smaller than the size of the full hard drive. The compressed image is written to the FOG server very quickly.

Again, it depends on the image type. But generally image deployment is a lot faster than image capture.

Here’s a great article on the subject: https://wiki.fogproject.org/wiki/index.php/Image_Compression_Tests

@Sebastian-Roth said:

What on earth has subnetting to do with speed?

That’s what I thought. But if it’s fixed it’s fixed.

We have some Lenovos that are weird.

Pull the power cable and patch cable, hit the power button a few times, plug everything back up and auto-magically those weird ones start working…