Latest Development FOG
-
Right! It’s all working now!
-
[quote=“YuYo, post: 43152, member: 3300”]
What’s in 3073 that is not in 3072?
[/quote]all changes are documented in the SVN [url]http://sourceforge.net/p/freeghost/code/HEAD/log/?path=[/url]
-
So,
There’s a chance that I might be setting up FOG for my school district using the location plugin.
What’s the current recommended FOG revision ?
I want a solid version with as few known problems as possible.
I was considering using 2920 or 2922 because I’ve had zero serious issues with it so far, and it’s all I’ve used as of yet.
Also, I have to at least use 2920 because of the custom multicast address changes and Fedora support that it implemented.
-
I’d say 3078 should be good.
Not only does it have a “stable” working base now, but it’s also got all the work we put in. It also adds improvements for performance and a couple of new features you may like.
-
Hi Tom,
Using the latest SVN I can’t get into the fog configuration page. All i get in chrome is Version: 3091 and in IE it just errors out and doesn’t display.
Happy to troubleshoot in any way I can but will need guidance.
Shane
UPDATE**
Downloaded Latest SVN (Version 3100) and all is good again.
-
Probably good to open a new thread for this and post your apache error logs (see Tom Elliot’s signature). I guess you’ve tried clearing browser caches??
-
Okay,
3101 released.
This comes with a huge change. First the kernels are now 3.19.1. This done for you for those of you on SVN, but upgrading to 3.19.1 may prove problematic across the board for those on other versions of FOG where the kernel and init’s are NOT downloaded for you, though I’m not 100% sure. The init’s are now updated per our discussion on the Bug Reports about nic registering and what not. The methods that are used are updated to reflect properly as well. Hopefully you all will enjoy as it took a lot of hard work between collaborating (Thank you Uncle Frank and cspence for the help there).
It also has a lot of changes in how things operate. While I don’t know if things are truly Async, it’s as close as I think we can get until I figure out how to pass things in multiples and getting the returns back in the proper order. From what I can tell though, it feels very fast and may help those on isolated networks. It also, properly, attempts the mysqlnd installation and implementation so we can do async mysql queries using the mysqlnd drivers as many suggest. While again I doubt the queries are truly asyncronous due to there only ever being a single thread for the event to occur and our own mysql/php implementations are in their very nature a locking type of system, but it does seem to be a bit of an improvement.
Hopefully you all enjoy.
-
I just updated to 3110 and the web gui will not load for me anymore. It just spins in a constant loading cycle. I can’t even log into it anymore since the page never comes up.
-
James,
What did you update from?
-
I updated from 3101.
-
Can you try in a different browser?
-
I tried downgrading to 3109 and I had the same issue, but when I downgraded further to 3102 the FOG GUI comes up fine. I’ll try each new iteration and let you know when the issue started on which revision.
-
FOG works fine for until SVN 3109. Then I can’t load the web page anymore. All the previous revisions do not have this issue.
-
Can you do me a favor?
Run this command:
[code]wget -O /var/www/fog/lib/fog/FOGURLRequests.class.php http://sourceforge.net/p/freeghost/code/3108/tree/trunk/packages/web/lib/fog/FOGURLRequests.class.php?format=raw[/code]
Does the interface now load?
-
Also, that might break it worse, but it’s worth a shot.
Can you also see what’s in the apache error logs?
-
Should I run that command from certain folder, such as /trunk or /trunk/bin?
-
It doesn’t matter,
The command is implicitly telling it which file to use and copy over.
-
That didn’t seem to help. My apache error log has multiple lines of:
PHP Fatal error: Call to a member function isValid() on a non-object in /var/www/fog/service/servicemodule-active.php on line 11 -
That’s okay.
3111 should fix the issues and still maintain access to the interface.
-
Yep, 3111 fixed it. Thank you Tom.
