FOG Imaging Log Not Working
-
Server
- FOG Version: 1.3.4
- OS: Xubuntu 16.04
Just a FYI that the FOG Imaging Log is not working in 1.3.4
-
So the reason the date selector was not being seen was because I am grabbing the minimal date.
Some entries, for this field, might have ‘0000-00-00 00:00:00’ as the date time stamp, which is invalid.
So the original way it worked, if the date was invalid (start time will always be earlier than end time) it would present “invalid”.
The updated method should work for this for all of you having this problem. I’m correcting this behaviour by adjusting the start date to 2 years before the current date.
Hopefully this is sufficient. The reason I don’t want to go back further is the amount of time it would take to generate the selector. (I’m not guessing the selector based on max end date any more. I’m just giving a date range based on the earliest time found and forward (as it’s not really a selector otherwise right?))
I’m also changing the way things are displayed a little bit.
Instead of showing logs of tasks that have either an invalid start OR end date, both start AND end must be invalid to no longer show. It may make some strange readings for things, but shouldn’t hurt anything otherwise.
-
I’m on CentOS 7 fully updated, and I’m running FOG 1.3.4, my imaging log appears to be working fine. See below picture.
Do me a favor and check to see if there is anything in your imageingLog table or not with the below commands & sql.
mysql -D fog select * from imagingLog; quit
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
Daily Clean Installation Results:
https://fogtesting.fogproject.us/
FOG Reporting:
https://fog-external-reporting-results.fogproject.us/ -
This post is deleted! -
@Wayne-Workman Hi Wayne. I have the same issue but I can’t confirm that it’s since the update to 1.3.4
•FOG Version: 1.3.4
•OS: CentOS Linux release 7.2.1511 (Core)
Here the result of the command you ask for
Thanks for your help and time
-
@Wayne-Workman Yes there is (here are some that are in there)
| 923 | 1899 | 2017-01-18 14:20:58 | 2017-01-18 15:09:33 | Student 12-14-16 64bit | down | sballard | | 924 | 1900 | 2017-01-18 14:26:51 | 2017-01-18 15:09:59 | Student 12-14-16 64bit | down | dholifield | | 934 | 346 | 2017-01-18 15:14:09 | 2017-01-18 15:22:12 | Student 12-14-16 64bit | down | dholifield | | 935 | 1032 | 2017-01-25 10:55:47 | 2017-01-25 11:08:44 | Student 12-14-16 64bit | down | sballard | | 936 | 1014 | 2017-01-26 15:27:02 | 2017-01-26 15:31:19 | Student 11-11-16 | down | sballard | | 937 | 1701 | 2017-01-30 07:41:59 | 2017-01-30 07:59:08 | Student 12-14-16 64bit | down | fog | | 938 | 1701 | 2017-01-30 08:03:48 | 2017-01-30 08:10:43 | Student 11-11-16 | down | fog | | 939 | 1701 | 2017-01-30 11:47:37 | 2017-01-30 11:54:20 | Student 11-11-16 | down | sballard | | 940 | 2 | 2017-01-31 12:12:13 | 2017-01-31 12:22:04 | Student 12-14-16 64bit | down | sballard | | 942 | 3 | 2017-01-31 12:22:15 | 2017-01-31 13:27:20 | Student 12-14-16 64bit | down | sballard | +------+----------+---------------------+---------------------+----------------- -------+--------+-------------+ 783 rows in set (0.00 sec) -
I am seeing the same issue. The command returns a list of imaging but the web gui doesnt show the imaging log. I am on 1.3.4 on ubuntu server 14.04.
-
Those having issues, do you have any errors in your Apache logs?
Fedora/CentOS
tail /var/log/httpd/error_logDebian/Ubuntu
tail /var/log/apache2/error.log -
@cml Yes, I am seeing errors but im not sure it is related (pardon the typos as I typed over the errors - not sure how to copy from ubuntu server to here):
Uncaught Error: Call to a member function is Valid() on null in /var/www/fog/lib/client/registerclient.class.php:67\nStack trace: n#0 /var/www/fog/lib/fogpage.class.php(2701): RegisterClient->json()\n#1 /var/www/fog/lib/fog/fogpage.class.php(262): FOGPage->requestClientInfo()\n#2 /var/www/fog/lib/fog/processlogin.class.php(57): FOGPage->__construct('')\n#3[internal function]: ProcessLogin->__contruct()\n#4``` -
@cml said in FOG Imaging Log Not Working:
tail /var/log/apache2/error.log
[Wed Feb 01 11:22:54.142011 2017] [php7:warn] [pid 27640] [client 10.*.*.*:38236] PHP Warning: A non-numeric value encountered in /var/www/fog/lib/fog/inventory.class.php on line 95, referer: http://10.*.*.*/fog/management/index.php?node=report&sub=imaginglog -
@cml Hi.
I don’t know if it’s related but below are the last errors I found on the apache’s log . Thanks for your help[Wed Feb 01 09:31:34.483981 2017] [:error] [pid 1774] [client 172.*.*.*:51715] PHP Strict Standards: Only variables should be passed by reference in /var/www/html/fog/lib/pages/taskmanagementpage.class.php on line 224, referer: http://172.*.*.*/fog/management/index.php?node=task&sub=active -
@Nicolas-T Ok. I’ve a new clue (For my case). It seems that logs disapear in “FOG Imaging log” when the hosts are delete from de Host Management. Is it normal?
-
@Tom-Elliott could you look through this thread? I’m not sure where to go from here.
-
Any help on this would be great. I have still not got this figured out. Thanks
Raymond Bell
WiKi: https://wiki.fogproject.org/wiki/index.php/Main_Page -
@Raymond-Bell @Nicolas-T @coop90 In this posting, there’s a related bug fix:
https://news.fogproject.org/fog-1-3-5-rc-1/Also moving this to bugs as so many people have the issue.
Also cross-linking another thread about the same problem:
https://forums.fogproject.org/topic/9579/report-management-fog-imaging-log-no-results-found -
@Wayne-Workman I am on rc10 and still having this issue.
-
@coop90 I know why this is happening now.
Thinking of a way to fix.
This is simply you don’t even get the dates, correct?
-
So the reason the date selector was not being seen was because I am grabbing the minimal date.
Some entries, for this field, might have ‘0000-00-00 00:00:00’ as the date time stamp, which is invalid.
So the original way it worked, if the date was invalid (start time will always be earlier than end time) it would present “invalid”.
The updated method should work for this for all of you having this problem. I’m correcting this behaviour by adjusting the start date to 2 years before the current date.
Hopefully this is sufficient. The reason I don’t want to go back further is the amount of time it would take to generate the selector. (I’m not guessing the selector based on max end date any more. I’m just giving a date range based on the earliest time found and forward (as it’s not really a selector otherwise right?))
I’m also changing the way things are displayed a little bit.
Instead of showing logs of tasks that have either an invalid start OR end date, both start AND end must be invalid to no longer show. It may make some strange readings for things, but shouldn’t hurt anything otherwise.
