Latest Development FOG
-
SVN 3141 released.
With this comes a minor schema update to enable the ability to have kernel debug parameter on or off. I’ve only tested it works on a download task, but taskings are dynamic so I know gui set tasks will operate properly. Will see about testing OS loads from the iPXE menu to see if they work, but I just wanted to give you all some knowledge.
FOG Configuration Page->FOG Settings->FOG Boot Settings->FOG_KERNEL_DEBUG is a checkbox that will enable/disable the kernel debugging argument and should show us more information on booting a system particularly if there’s an issue with it doing something. I can then provide better configurations to the kernels I build.
-
SVN 3142 installed.
[LIST]
[]Still unable to search for single system. Shows 75 systems rather than explicit system searched for.
[]List all images results in blank page.
[]After uploading an image to FOG, the image is no longer searchable. Image is still visible while viewing image list dropdown while editing a specific client.
[]Assigning a newly uploaded image to a system, does not keep changes. Image reverts to blank.
[/LIST]At this point we’re dead in the water and unable to image. If you would find it useful, I can connect you to my server so you may see issues and look for issues. Let me know.
-
This may not fix it but have you cleared your browser cache since upgrading.
-
Folks, I hate to say this but as I do, I am using the SVN builds on a live environment, Its a really bad thing to do unless your sure you have good backup’s and the ability to revert to an earlier version. as one thing is fixed for a revision something else may break. If you counting on a revision to fix all the problems you should probably wait for an official release. this is only for the development of the product. use in a live system can and often does result in some down time. to be expected.
-
Having said that, and as much as I agree, upgrading to the SVN several times from 1.2.0 became a necessity for us to address multiple issues we encountered in our environment.
We’re currently standardized on:
– svn: 3127
– Kernel: 3.18.5 x86_64 (manually downgraded)
– iPXE: 1.0.0+ (acc27)Of course new SVN are vetted in our dev environment before being pushed onto our live servers.
-
I agree the SVN updates are nice when it fixes and or addresses a current issue but for people who use FOG in a live environment it can be hectic when things dont always go right. I experiment in my live environment but I do have backups and ability to revert to a stable svn revision. sometime newer is not always better. Im kind of in a unique position as i have the ability to play a little and Fog is not always a daily requirement so down time is understood and creates a little job security.
-
It became necessary for us to move off stable to SVN to address issues encountered after migrating from .32 to 1.x. I’m thankful for the response we have received in debug and development. We realize that downtime is to be expected when running in the dev channel. Our situation would not allow us to continue on our current server without rebuild. At least this way, we can still keep going forward on the same system, and hopefully the ability to see the errors encountered on our system will provide insight into future fixes.
A big thanks to Tom for all the assistance thus far. -
I know exactly how you feel. only because i like to tinker do I experiment with my live system. I’m going to blow it out anyway and redo from a base of Linux Mint 17.1 Cinnamon x64. I like the interface more and i think its smoother. should play well based on Debian anyway.
future upgrade are better now too. direct upgrade path. so I’ll be tearing my ubuntu down and copying the files over to the new system. -
I’m currently on SVN 3149 and I’m unable to turn services on and off from the service configuration page. When I click the update button I’m just taken to a white screen. This is the apache error that I get:
[SIZE=13px][COLOR=#555555][Tue Mar 24 15:22:28.521929 2015] [:error] [pid 3131] [client 172.52.8.27:56499] PHP Fatal error: Call to a member function set() on a non-object in /var/www/fog/lib/pages/ServiceConfigurationPage.class.php on line 308, referer: [url]http://172.28.2.21/fog/management/index.php?node=service&sub=edit[/url][/COLOR][/SIZE]
-
3151 should be fixed.
Sorry about that.
-
3153 Release.
This should fix All Snapin Tasks as was reported a problem.
-
I’m currently on SVN 3153 and whenever I add a new host I get taken to a white screen. If I refresh the page and resend the data then the add host page comes back saying the host already exits. So it is still adding it but the initial creation just creates a white page instead of saying the host was added.
-
3154 hopefully fixes the white page on create new host you reported.
-
Thanks Tom that did take care of the issue. But now another odd issue has popped up. I’ve been able to add hosts to FOG without any issue. But now when I create a host I’m unable to find it in FOG at all. Listing all hosts does not show the host I created. If I look in the data base I see the host I created and that it is correctly tied to the MAC address for it. All of the settings in the database are correct with how my other hosts are but it won’t show in FOG. I’m not sure if these apache errors would reference it but these are the latest ones that I have.
[SIZE=13px][COLOR=#555555]PHP Fatal error: require_once(): Failed opening required ‘…/commons/base.inc.php’ (include_path=‘.:/usr/share/php:/usr/share/pear’) in /var/www/fog/service/servicemodule-active.php on line 2
[Wed Mar 25 12:30:09.649651 2015] [core:notice] [pid 11801] AH00051: child pid 14725 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Wed Mar 25 12:30:09.649678 2015] [core:notice] [pid 11801] AH00051: child pid 14727 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Wed Mar 25 12:33:32.725696 2015] [core:notice] [pid 11801] AH00051: child pid 16641 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Wed Mar 25 12:38:01.991290 2015] [:error] [pid 18225] [client 172.52.8.27:49931] PHP Warning: trim() expects parameter 1 to be string, array given in /var/www/fog/lib/fog/MACAddress.class.php on line 17, referer: [url]http://172.28.2.21/fog/management/index.php?node=host&sub=add[/url]
[Wed Mar 25 12:38:01.991382 2015] [:error] [pid 18225] [client 172.52.8.27:49931] PHP Warning: trim() expects parameter 1 to be string, array given in /var/www/fog/lib/fog/MACAddress.class.php on line 17, referer: [url]http://172.28.2.21/fog/management/index.php?node=host&sub=add[/url]
[Wed Mar 25 12:38:01.991405 2015] [:error] [pid 18225] [client 172.52.8.27:49931] PHP Warning: trim() expects parameter 1 to be string, array given in /var/www/fog/lib/fog/MACAddress.class.php on line 17, referer: [url]http://172.28.2.21/fog/management/index.php?node=host&sub=add[/url][/COLOR][/SIZE] -
3155 maybe fixes the error’s being reported. As to why they don’t appear in your host list I haven’t a clue. I’m not able to replicate that part of it.
-
That didn’t help unfortunately. I’m trying to give the host the name laptop test and then input a valid mac address. It does create the host, but if I navigate away from the host I’m unable to find it again from searching or looking at the entire host list.
Update: For some reason this only happening for a single laptop so I wonder if it just doesn’t like the mac address or something. This is isn’t a huge as an issue as I thought ti was.
-
I found another issue. I’m currently on SVN 3160 and I am unable to update MAC addresses for hosts. When ever I hit the update button it always reverts back to the previous MAC address. I have to go into the data manually and change the MAC address.
-
3162 Should address this, hopefully.
-
On svn 3162 I’m getting messages from machines with the new fog client that fog user service has stopped responding. The service will not allow itself to turn back on. This was working fine until this latest update.
-
anything in the c:\fog.log or c:\user<loggedinuser>\fog_user.log?
