git5572 - snapin log errors

[tian]

There seems to be a problem with snapin log:

• Getting the snapin log after selecting the start and end date the following appears:
  
  The snapins listed below this are displayed fine though (I just cut the screenshot there).

• exporting the csv works, but the “snapin run with” content has some display error (on the web interface and in the database the backslashes are displayed fine with just one between drive letter, folders and file):
  

• Trying to export the pdf the following page appears:
  

The snapins executed fine - return code was 0, state was 4.

The imaging log seems not to have these error and works fine (display web page, export csv and pdf).

[tian]

errors are still there in git5612 - from apache error log:

[Thu Dec 03 09:29:53.144110 2015] [:error] [pid 1458] [client MY_IP:55385] PHP Warning: mb_convert_encoding() expects parameter 1 to be string, object given in /var/www/html/fog/lib/db/mysql.class.php on line 152, referer: http://FOG_IP/fog/management/index.php?node=report&sub=snapin-log
[Thu Dec 03 09:29:53.148772 2015] [:error] [pid 1458] [client MY_IP:55385] PHP Warning: mb_convert_encoding() expects parameter 1 to be string, object given in /var/www/html/fog/lib/db/mysql.class.php on line 152, referer: http://FOG_IP/fog/management/index.php?node=report&sub=snapin-log

In the file “/var/log/php5-fpm.log” I just can see some of these messages:

NOTICE: configuration file /etc/php5/fpm/php-fpm.conf test is successfull

The number of warnings seems to be related to the number of snapin log entries returned for the selected date range.

Should I check/try anything else?

[Tom Elliott]

Confirmed and fixed in latest. Please update and thanks for reporting.

[tian]

@Tom-Elliott Thanks for the (partly) fix. The good news: I’m now on git5618 and the warning from the web page are gone now.

But the bad news: the other 2 bugs (backslashes in csv export and not be able to create pdf export) for the snapin log still exist.

[tian]

@Tom-Elliott Thanks for fixing the two other bugs also. I’m on git5662 now and it is working again.

And something other worth mentioning:
It is a great change that the state in the snapin log is now displayed as “complete” instead of “4” - this makes things more clear.