Latest Development FOG
-
Bill, in case you just installed php5-mcrypt, make sure apache is restarted.
Second thing to check is if mcrypt is actually loaded so for example in php5/apache2/conf.d does it mention to load mcrypt? Else load explicitly in your php.ini with extension=mcrypt.so or so, just to be sure.
-
You could also, if on ubuntu/debian, just run:
[code]sudo a2enmod mcrypt[/code]
-
Running that command Tom
Returns this --> sudo a2enmod mcrypt
ERROR: Module mcrypt does not exist!Modifying the php file adding extension=mcrypt.so appears to have given me the ability to save settings again.
[COLOR=#3366ff]Line 278 in file --> return $this->link->real_escape_string(strip_tags($data));[/COLOR]
[COLOR=#993300]I still see this error in the SQL line 278. this is a paste from the apache log file.[/COLOR]
[Thu Mar 19 07:02:32.262527 2015] [:error] [pid 4247] [client 172.31.178.79:56675] PHP Warning: mysqli::real_escape_string(): Couldn’t fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 278
[Thu Mar 19 07:02:32.262538 2015] [:error] [pid 4247] [client 172.31.178.79:56675] PHP Warning: mysqli::real_escape_string(): Couldn’t fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 278
[Thu Mar 19 07:02:32.262741 2015] [:error] [pid 4247] [client 172.31.178.79:56675] PHP Warning: mysqli::real_escape_string(): Couldn’t fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 278
[Thu Mar 19 07:02:32.262751 2015] [:error] [pid 4247] [client 172.31.178.79:56675] PHP Warning: mysqli::real_escape_string(): Couldn’t fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 278
[Thu Mar 19 07:02:32.262958 2015] [:error] [pid 4247] [client 172.31.178.79:56675] PHP Warning: mysqli::real_escape_string(): Couldn’t fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 278
[Thu Mar 19 07:02:32.262969 2015] [:error] [pid 4247] [client 172.31.178.79:56675] PHP Warning: mysqli::real_escape_string(): Couldn’t fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 278 -
I’m sory about that.
a2enmod is for Apache modules.
php5enmod is for php (mcrypt is a php function)
[code]sudo php5enmod mcrypt[/code]
-
ok updated to latest svn, 3123 lost all screens- im trying that command, rebooting and will update as it restarts.
If this still breaks the screens (can log in to fog but then all other screens dont display) I’ll back to svn 3122
Rebooted and no screens display other then the inital log on screen but i can click on log out and it will go back to initial log on screen.
no biggie. just an fyi. -
Ok current update - After adding the extension=mcrypt.so to the php file and also running the php5 command tom provided i am able to see all options and make needed changes.
I then did the SVN update and that when I lost all the option screens it allowed me to log in but then no other screen except for main screen would show up. I rebooted the system still no joy. I did run the command --> Sudo svn up -r 3122
allowed to update, and then run the installer. this has brought me back top 3122 and all is functional again.If you would like my log file for apache then let me know, I’ll post a little of the log in my next post for review.
-
Just the relevant parts. When you upgrade to 3123 and get the “white” screen, tail the log and give me that. It’s much more likely to show the relevant issue you’re seeing. Also, do you have plugins enabled/installed?
-
As far as plugins yes I have them enabled / Installed as I want to experiment with them.
I’ll look for the section where with ver 3123 was not opening the pages.Hope this is what you were looking for if not I’ll send in my entire log file.
PHP Warning: Module ‘mcrypt’ already loaded in Unknown on line 0
[Thu Mar 19 09:20:33.122027 2015] [mpm_prefork:notice] [pid 10579] AH00163: Apache/2.4.10 (Ubuntu) PHP/5.5.12-2ubuntu4.3 configured – resuming normal operations
[Thu Mar 19 09:20:33.122107 2015] [core:notice] [pid 10579] AH00094: Command line: ‘/usr/sbin/apache2’
mkdir: cannot create directory ‘/var/www/html/fog//management/other/ssl/’: File exists
[Thu Mar 19 09:26:50.685365 2015] [core:notice] [pid 10579] AH00051: child pid 10988 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Thu Mar 19 09:34:19.398974 2015] [:error] [pid 11210] [client 172.31.179.192:62153] PHP Warning: require_once(…/commons/base.inc.php): failed to open stream: No such file or directory in /var/www/fog/service/servicemodule-active.php on line 2
[Thu Mar 19 09:34:19.399000 2015] [:error] [pid 11210] [client 172.31.179.192:62153] 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
[Thu Mar 19 09:34:22.414912 2015] [:error] [pid 11166] [client 172.31.179.192:62154] PHP Warning: require_once(…/commons/base.inc.php): failed to open stream: No such file or directory in /var/www/fog/service/servicemodule-active.php on line 2
[Thu Mar 19 09:34:22.414944 2015] [:error] [pid 11166] [client 172.31.179.192:62154] 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
[Thu Mar 19 09:34:50.271903 2015] [core:notice] [pid 10579] AH00051: child pid 11166 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Thu Mar 19 09:37:14.497270 2015] [core:notice] [pid 10579] AH00051: child pid 13276 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Thu Mar 19 09:37:21.505580 2015] [core:notice] [pid 10579] AH00051: child pid 13294 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Thu Mar 19 09:50:44.506872 2015] [core:notice] [pid 10579] AH00051: child pid 13830 exit signal Segmentation fault (11), possible coredump in /etc/apache2 -
here is the log file complete.
Obviously change name back to error.log
[url=“/_imported_xf_attachments/1/1796_error.log.txt?:”]error.log.txt[/url]
-
SVN 3134 installed. When doing a host search, it narrows it down to 76 hosts, rather than giving me the exact system I am searching for. I have 451 hosts on this FOG instance.
[ATTACH]1800[/ATTACH]
[url=“/_imported_xf_attachments/1/1800_76hosts.png?:”]76hosts.png[/url]
-
I wanted to give everyone a heads up.
SVN 3138 released. With this release comes many more things. Specifically the Beta FOG Client is available now and is downloadable from the FOG GUI as normal. There are two links. One for Legacy and one for New. Hopefully this is self explanatory.
If you’re downloading right now, some things may not work properly as sourceforge is currently experiencing one of their many issues as normal (GRRRRRR). At anyrate, it also fixes an issue I didn’t see in snapins. Hopefully all works. As Jbob describes, please post a new bug report specific to the FOG Client bugs, and try to be as descriptive as possible.
Thank you and I hope you all enjoy,
-
Ok tom, Imaging issue I’m getting input/output error trying to image. seems all the interfaces are functional but the pxe boot to image the pc is failing.
log attached. -->[Tue Mar 24 08:04:00.751179 2015] [:error] [pid 8619] [client 172.31.179.2:50889] PHP Warning: mysqli::query(): Couldn’t fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 120
[Tue Mar 24 08:04:00.951181 2015] [mpm_prefork:notice] [pid 8558] AH00169: caught SIGTERM, shutting down
PHP Warning: Module ‘mcrypt’ already loaded in Unknown on line 0
[Tue Mar 24 08:07:14.265121 2015] [mpm_prefork:notice] [pid 4210] AH00163: Apache/2.4.10 (Ubuntu) PHP/5.5.12-2ubuntu4.3 configured – resuming normal operations
[Tue Mar 24 08:07:14.265204 2015] [core:notice] [pid 4210] AH00094: Command line: ‘/usr/sbin/apache2’
[Tue Mar 24 08:07:21.359352 2015] [core:notice] [pid 4210] AH00051: child pid 4445 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Tue Mar 24 08:07:44.828885 2015] [:error] [pid 4456] [client 172.31.178.231:42614] PHP Fatal error: Call to a member function get() on a non-object in /var/www/fog/lib/fog/BootMenu.class.php on line 781
[Tue Mar 24 08:08:37.821067 2015] [:error] [pid 4409] [client 172.31.178.231:44913] PHP Fatal error: Call to a member function get() on a non-object in /var/www/fog/lib/fog/BootMenu.class.php on line 781
[Tue Mar 24 08:09:24.958872 2015] [:error] [pid 4473] [client 172.31.179.0:40638] PHP Strict Standards: Only variables should be passed by reference in /var/www/fog/service/auto.register.php on line 90
[Tue Mar 24 08:09:24.958914 2015] [:error] [pid 4473] [client 172.31.179.0:40638] PHP Warning: array_reverse() expects parameter 1 to be array, string given in /var/www/fog/service/auto.register.php on line 90
[Tue Mar 24 08:10:13.893310 2015] [:error] [pid 4473] [client 172.31.179.0:27800] PHP Fatal error: Call to a member function get() on a non-object in /var/www/fog/lib/fog/BootMenu.class.php on line 781
[Tue Mar 24 08:11:21.515578 2015] [:error] [pid 4516] [client 172.31.178.231:55201] PHP Fatal error: Call to a member function get() on a non-object in /var/www/fog/lib/fog/BootMenu.class.php on line 781 -
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.
