Latest Development FOG

David Herrington

Well I was working on something else and messed things up even more… lol?

I’m not using this in production, just seeing what I can mess up and testing

Anyways I just left the database alone, I didn’t touch anything at all when updating
But before running the 1.2 installer while on 2556 none of my images would show in the list and if I tried to create another one they wouldn’t show up either

Hosts show up and I can create new ones on 2556 if that matters at all

At the end of the apache error log there’s several PHP warnings
[QUOTE]PHP Warning: in_array() expects parameter 2 to be array, null given in /var/www/fog/lib/pages/ImageManagementPage.class.php on line 351, referer: [url]http://127.0.0.1/fog/management/index.php?node=image&sub=edit&id=4[/url][/QUOTE]

There’s also this warning
[QUOTE]PHP Warning: MySQL::sqlerror(): Couldn’t fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 180, referer: [url]http://127.0.0.1/fog/commons/schemaupdater/index.php?redir=1[/url][/QUOTE]

I’m not too worried about fixing this, like I said, it’s a test machine but thought I’d bring it up just in case

Tom Elliott

SVN 2559 released.

Hopefully this will have better handling of memory by freeing up the memory used by the database connection. This connection cannot be freed from the MySQL class otherwise you’ll only ever get the first returned set whether using store_result or use_result. I don’t think it’ll help but quite possibly?

Hopefully this fixes any/all of the pressing issues (e.g. Image definition creation, installation on Ubuntu/Debian, reports blank page, etc…)

I’m not expecting any miracles but maybe, just maybe I’m heading in the right direction?

Also, A few things to note incase I missed things and figure it’d be nice to just know about in general.

) This is probably the largest pressing item: memory_limit in php.ini does not need to be adjusted any more, nor’ will it work with FOG any longer. I’ve made a new value setting in FOG Configuration->FOG Settings->General Settings called FOG_MEMORY_LIMIT. Set your value here, I’ve defaulted it to 128 as is the default php starts out with. Anything non-numeric or lower than this number will be reset to 128.
) Snapin’s now have group-group relationships as do images. This means images and snapins can be replicated across groups as well as their relevant group’s nodes. Does this mean there’s no bugs? Probably not, but feel it’s good to know about.
) Hidden menu now has it’s own timeout setting separate from the regular timeout. Also, when hidden menu is in use, the timeout on the regular options is set to 0 which should mean it just waits for you to make a selection. It’s quite possible I need to change this though as I believe --timeout 0 will just boot right to the first item rather than wait indefinitely. Will need people to test this for me if possible.
) You can now email imaging tasks as they complete. It, right now, is only valid for Unicast imaging, or anything that hits the Post_Stage3.php file on completion. However, it should work. Settings for this are found in FOG Configuration->FOG Settings->FOG Email Settings. They should be rather self explanatory.

Tom Elliott

SVN 2563 released.

Hopefully made some more progress in the never ending quest for fixing the large result set returned issue we’ve been seeing, though I’m not expecting much. It appears to give a pretty good overall performance improvement on the GUI side though so just maybe?

Also add’s a new get request to get the snapin args of snapins for post download scripts in the snapcheck.php file.

Ray Zuchowski

Tom,

Im running 2570 and just did a unicast to one client and the image completes but at the end it says sending to database and I get this.

Continuously scrolling and in task manager in the gui it says imaging still in progress.

Adam Taylor

Ditto on Ray’s post. using 2571.

Tom Elliott

can you try 2574?

Adam Taylor

Just pushed an image…

It’s still doing the same thing with the *…we also see that it is not updateing the progress bar of the task and the task doesn’t even look like it thinks its running…

Tom Elliott

What’s in the apache error logs?

Justin P

Same as above, error.log:

10.132.57.100 - my PC
10.132.61.251 - Netbook (Trying to deploy image to)
10.132.59.71 - Netbook (Trying to deploy image to)

[code][Wed Nov 05 12:34:34 2014] [error] [client 10.132.61.251] PHP Fatal error: Can’t use method return value in write context in /var/www/fog/service/Post_Stage3.php on line 79
[Wed Nov 05 12:35:40 2014] [error] [client 10.132.57.100] File does not exist: /var/www/fog/management/css/images/ui-bg_flat_75_ffffff_40x100.png, referer: http://10.132.57.26/fog/management/css/jquery-ui.css
[Wed Nov 05 12:35:40 2014] [error] [client 10.132.57.100] File does not exist: /var/www/fog/management/css/images/ui-bg_glass_75_e6e6e6_1x400.png, referer: http://10.132.57.26/fog/management/css/jquery-ui.css
[Wed Nov 05 12:35:40 2014] [error] [client 10.132.57.100] File does not exist: /var/www/fog/management/css/images/ui-bg_highlight-soft_75_cccccc_1x100.png, referer: http://10.132.57.26/fog/management/css/jquery-ui.css
[Wed Nov 05 12:36:48 2014] [error] [client 10.132.59.71] PHP Fatal error: Can’t use method return value in write context in /var/www/fog/service/Post_Stage3.php on line 79
[Wed Nov 05 12:36:48 2014] [error] [client 10.132.59.71] PHP Fatal error: Can’t use method return value in write context in /var/www/fog/service/Post_Stage3.php on line 79
[/code]

Tom Elliott

So all of you having issues are trying to use the email functionality?

Tom Elliott

I’ve tried changing the way that setting is looked at. 2576 release to try fixing the issue you’re seeing.

Fernando Gietz

Now, with revision 2578, I can not access to dashboard. I have problems with the browsers:
“[SIZE=13px][FONT=Helvetica][COLOR=#a0a0a0]Error Code: ERR_CONTENT_DECODING_FAILED[/COLOR][/FONT][/SIZE]”

Fernando Gietz

If I change the php.ini config:
zlib.output_compression = On
I can access but appears a php error:
[SIZE=13px][FONT=Ubuntu][COLOR=#555555]/var/www/html/fog/lib/db/MySQL.class.php on line 74 Warning: mysqli::select_db(): Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php on line 74 Warning: ob_start(): output handler ‘ob_gzhandler’ conflicts with ‘zlib output compression’ in /var/www/html/fog/management/index.php on line 42[/COLOR][/FONT][/SIZE]

Lee Rowlett

turn off Display_Errors also

Fernando Gietz

Now works fine. But, the compression is necessary? Until now was not necessary

Tom Elliott

The compression isn’t necessary but is used to try limiting the bandwidth usage on your network.

Adam Taylor

Here is my apache error log when sending my last image:

[CODE][Tue Nov 04 17:14:25 2014] [error] [client 10.96.14.226] PHP Warning: array_key_exists() expects parameter 2 to be array, null given in /var/www/html/fog/lib/db/MySQL.class.php on line 164
[Tue Nov 04 17:14:25 2014] [error] [client 10.96.14.226] PHP Warning: mysqli::mysqli(): (HY000/2002): Can’t connect to local MySQL server through socket ‘/var/lib/mysql/mysql.sock’ (2) in /var/www/html/fog/lib/db/MySQL.class.php on line 69
[Tue Nov 04 17:14:25 2014] [error] [client 10.96.14.226] PHP Warning: mysqli::query(): Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php on line 102
[Tue Nov 04 17:14:25 2014] [error] [client 10.96.14.226] PHP Warning: MySQL::query(): Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php on line 103
[Tue Nov 04 17:14:25 2014] [error] [client 10.96.14.226] PHP Warning: array_key_exists() expects parameter 2 to be array, null given in /var/www/html/fog/lib/db/MySQL.class.php on line 164
[Tue Nov 04 17:14:25 2014] [error] [client 10.96.14.226] PHP Warning: mysqli::escape_string(): Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php on line 262
[/CODE]

I also have a load of other SQL errors from many other clients…all like the above but in slightly different orders.

Tom Elliott

2579 should fix the array_key_exists errors, though there shouldn’t really be any issues as their just warnings.

Adam Taylor

We are trying that svn trunk now. On a note…the * issue does not happen on upload…only downloads does it happen.

On one other note. This line is repeating ALOT (~5-10 a second) in apache when just sitting at the dashboard doing nothing.

[CODE][Wed Nov 05 09:22:33 2014] [error] [client 10.16.0.153] PHP Warning: mysqli::select_db(): Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php on line 74, referer: http://ulm-fog.ulm.edu/fog/management/index.php[/CODE]

I know it’s just a warning in PHP…but man it fills the logs up quick. Also, anything you do on the web interface (and links clicked, etc…) also shows up as the “line 74” error.

Ray Zuchowski

The issue with the
*
*
*
*
Is linked to email feature being turned on. My guess is its trying to communicate back to the server and if the smtp settings aren’t configured its just hanging. Some where in the script going to have to probably have a timeout if the email fails to send and then close out the session. Running 2579 with email feature now off and have no issues.

Ray Z

Latest Development FOG

235

11.6k

17.1k

154.6k