Latest Development FOG
-
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.
-
Ditto on Ray’s post. using 2571.
-
can you try 2574?
-
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…
-
What’s in the apache error logs?
-
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] -
So all of you having issues are trying to use the email functionality?
-
I’ve tried changing the way that setting is looked at. 2576 release to try fixing the issue you’re seeing.
-
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]” -
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] -
turn off Display_Errors also
-
Now works fine. But, the compression is necessary? Until now was not necessary
-
The compression isn’t necessary but is used to try limiting the bandwidth usage on your network.
-
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.
-
2579 should fix the array_key_exists errors, though there shouldn’t really be any issues as their just warnings.
-
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.
-
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
-
[S]Unfortunally…we do not have email turned on (FOG_EMAIL ACTION) is unchecked.[/S]
Now that the right test is done…Yes, it now works without the * all the time. This is with the 2579 checkout.
Sorry about that!
-
SVN 2580 released.
With this comes, hopefully, more fixes for multicast session joining. Also allows you, the users, to specify which tasks you want to show up as Used tasks on the dashboard and on taskings during checkin. This is simply a field in General Settings and is a comma separated field. Meaning, 1,15,17 will only deal with download tasks.
This also should fix issues with the capone plugin not allowing the format of the image to come through to image in partimage/partclone.
-
SVN 2598 released.
With this comes a couple new introductions. First is Replication Bandwidth is now setup and in place. The idea of this is to limit bandwidth usage between nodes. You limit by Kbps just like regular bandwidth limitations usually operate. Basically the intent is to keep your network links unsaturated if we can help it.
Also, comes an attempt at multiple node replication at the same time. So if your Group has nodes a,b,c in different sites, rather than wait for the first node to complete, it should start replicating to all three nodes. The bandwidth limitations will work in a fashion to limit the total rate of the sending node bandwidth is set. Meaning, if Group 1 has nodes a,b,c,d with d as the master. If node d’s limit is set and starts sending, it will limit all the transfers to the limit set on d. However, if d’s bandwidth is not set, it will use the limits individually set on a,b, and/or c, to transfer to those nodes.
This, I think leaves the best bandwidth optimization as needed. Is it perfect? Probably not, but it’s a test and something I think people could find extremely useful.
