@Tom-Elliott You’re welcome. Here are the results after the last modifications you have uploaded. Seems like there are no more errors. Now I’m making the whole deployment to see the final partition sizes in Windows enviroment.

Thank you very much!
0_1489705889913_Captura de pantalla 2017-03-16 a las 23.09.10.png
0_1489705897537_Captura de pantalla 2017-03-16 a las 23.09.32.png

@Tom-Elliott Applied the fix and restarted and working perfect. Thank you very much!

@Tom-Elliott Thank you very much. Updated to RC14 and working perfect.

@Tom-Elliott So will you start including those? I don’t understand.

Sorry! It’s ok!
Agent was stopped for some reason. Now log seems ok.
Thanks a lot!

Thank you very match!

@Tom-Elliott Yep, that was my issue. I’ve updated to RC12 and from what testing that I have done, it seems that everything is working. I’m able to go from a 160GB to a 256GB and also 500GB drive and boot into Windows as well. The resizing seems to be correct as well.

The developers found this issue to why the log file grew so big (after almost a year of log file collection). The log file will now be capped at the log file maximum set by the fog configuration settings. This was just a fluke case that caused this file to grow to an abnormal size.

The fix / log file limiting code will be in 1.3.5RC11 when its released.

Those wanting to see the fix sooner than later please run:

wget -O /var/www/fog/lib/pages/reportmanagementpage.class.php https://raw.githubusercontent.com/FOGProject/fogproject/fee45cb8efe1d783f358589286f78c4cee82a5c5/packages/web/lib/pages/reportmanagementpage.class.php

So the reason the date selector was not being seen was because I am grabbing the minimal date.

Some entries, for this field, might have ‘0000-00-00 00:00:00’ as the date time stamp, which is invalid.

So the original way it worked, if the date was invalid (start time will always be earlier than end time) it would present “invalid”.

The updated method should work for this for all of you having this problem. I’m correcting this behaviour by adjusting the start date to 2 years before the current date.

Hopefully this is sufficient. The reason I don’t want to go back further is the amount of time it would take to generate the selector. (I’m not guessing the selector based on max end date any more. I’m just giving a date range based on the earliest time found and forward (as it’s not really a selector otherwise right?))

I’m also changing the way things are displayed a little bit.

Instead of showing logs of tasks that have either an invalid start OR end date, both start AND end must be invalid to no longer show. It may make some strange readings for things, but shouldn’t hurt anything otherwise.

This wasn’t a problem with key sequence or even double entries as originally thought (though that could still cause similar issues).

However it was found and is now fixed.

Fixed in working. Thank you.

@Tom-Elliott OK, I just downloaded the image to another computer, and it works. Thanks!

And there was much rejoicing.

If you expand each option on the Fog Settings page individually, the missing bits are not visible. Only Expand ALL shows the missing bits and only at the top of the list, not where you’d expect them to be.

@Tom-Elliott said:

@AndrewC I’m not seeing the problem, but I would imagine you are seeing this in particular with EFI style systems?

Yes. It was an issue with the particular test machine. Did not have a problem with any others BIOS or EFI. Worry not.

I’d bring this to your attention:

No more recursive calls in sanitize_items function.

This was pushed up for RC-5, while it doesn’t refer to the blank page for host creation, this is what the issue was referring to. The reason it didn’t implicitly call out the create new host is because it actually impacting many other elements.

Updating to RC-5 or higher will bring this “issue” to rest for you.

@FredG I’ve added more implicit checking to the working branch to prevent this type of error.

For what it’s worth, I’ve added checking for the variables so this shouldn’t be an issue anymore.

@Tom-Elliott

Hi tom That fixed the problem, Thanks for all your help!!