User Tracker not working
-
Server
- FOG Version: 1.3.0-RC-36
- OS: Debian 7
Client
- Service Version: 0.11.7
- OS: Windows 7
Description
Hi
I never used the User Tracker before but today I looked at the login history and not a single host has an entry. I then checked the log on one host but i couldn’t find any errors.
------------------------------------------------------------------------------ ----------------------------------UserTracker--------------------------------- ------------------------------------------------------------------------------ 16.12.2016 11:57 Client-Info Client Version: 0.11.7 16.12.2016 11:57 Client-Info Client OS: Windows 16.12.2016 11:57 Client-Info Server Version: 1.3.0-RC-36 16.12.2016 11:57 Middleware::Response Success ------------------------------------------------------------------------------ 16.12.2016 11:57 Service Sleeping for 138 seconds 16.12.2016 11:59 Middleware::Communication URL: http://fogagh01/fog/management/index.php?sub=requestClientInfo&configure&newService&json 16.12.2016 11:59 Middleware::Response Success 16.12.2016 11:59 Middleware::Communication URL: http://fogagh01/fog/management/index.php?sub=requestClientInfo&mac=54:EE:75:3E:0C:DA||00:00:00:00:00:00:00:E0&newService&json 16.12.2016 11:59 Middleware::Response Success 16.12.2016 11:59 Middleware::Communication URL: http://fogagh01/fog/service/getversion.php?clientver&newService&json 16.12.2016 11:59 Middleware::Communication URL: http://fogagh01/fog/service/getversion.php?newService&json 16.12.2016 11:59 Service Creating user agent cache 16.12.2016 11:59 Middleware::Response Invalid time 16.12.2016 11:59 Middleware::Response No Printers 16.12.2016 11:59 Middleware::Response Module is disabled globally on the FOG server ------------------------------------------------------------------------------ ---------------------------------ClientUpdater-------------------------------- ------------------------------------------------------------------------------ 16.12.2016 11:59 Client-Info Client Version: 0.11.7 16.12.2016 11:59 Client-Info Client OS: Windows 16.12.2016 11:59 Client-Info Server Version: 1.3.0-RC-36 16.12.2016 11:59 Middleware::Response Success ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ ----------------------------------TaskReboot---------------------------------- ------------------------------------------------------------------------------ 16.12.2016 11:59 Client-Info Client Version: 0.11.7 16.12.2016 11:59 Client-Info Client OS: Windows 16.12.2016 11:59 Client-Info Server Version: 1.3.0-RC-36 16.12.2016 11:59 Middleware::Response Success ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ --------------------------------HostnameChanger------------------------------- ------------------------------------------------------------------------------ 16.12.2016 11:59 Client-Info Client Version: 0.11.7 16.12.2016 11:59 Client-Info Client OS: Windows 16.12.2016 11:59 Client-Info Server Version: 1.3.0-RC-36 16.12.2016 11:59 Middleware::Response Success 16.12.2016 11:59 HostnameChanger Checking Hostname 16.12.2016 11:59 HostnameChanger Hostname is correct ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ ---------------------------------SnapinClient--------------------------------- ------------------------------------------------------------------------------ 16.12.2016 11:59 Client-Info Client Version: 0.11.7 16.12.2016 11:59 Client-Info Client OS: Windows 16.12.2016 11:59 Client-Info Server Version: 1.3.0-RC-36 16.12.2016 11:59 Middleware::Response No snapins ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ --------------------------------PrinterManager-------------------------------- ------------------------------------------------------------------------------ 16.12.2016 11:59 Client-Info Client Version: 0.11.7 16.12.2016 11:59 Client-Info Client OS: Windows 16.12.2016 11:59 Client-Info Server Version: 1.3.0-RC-36 16.12.2016 11:59 Middleware::Response No Printers 16.12.2016 11:59 PrinterManager Getting installed printers ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ --------------------------------PowerManagement------------------------------- ------------------------------------------------------------------------------ 16.12.2016 11:59 Client-Info Client Version: 0.11.7 16.12.2016 11:59 Client-Info Client OS: Windows 16.12.2016 11:59 Client-Info Server Version: 1.3.0-RC-36 16.12.2016 11:59 Middleware::Response Success 16.12.2016 11:59 PowerManagement Calculating tasks to unschedule 16.12.2016 11:59 PowerManagement Calculating tasks to schedule ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ ----------------------------------UserTracker--------------------------------- ------------------------------------------------------------------------------ 16.12.2016 11:59 Client-Info Client Version: 0.11.7 16.12.2016 11:59 Client-Info Client OS: Windows 16.12.2016 11:59 Client-Info Server Version: 1.3.0-RC-36 16.12.2016 11:59 Middleware::Response Success -----------------------------------------------------```
-
-
Check your apache error logs, also I’m pinging @Tom-Elliott.
-
@Wayne-Workman Pinging me for what?
-
Apache error doesn’t show anything
-
@Polii123 Just to verify if the db really has no user tracking data in it, try to select the data manually.
mysql -D fog select * from userTracking; quit
-
@Wayne-Workman I think user tracking module is globally disabled which would be why it’s not creating entries. I ran through some pretty heavy tests. While I did see some, issues in reporting on logout, it did track logins. Sometimes logout worked others it didn’t
I don’t think it is server related as if I recall correctly the logout return is kind of a “beat the clock” thing. -
@Tom-Elliott Logout is not “beat the clock”. User tracker’s code has not changed since sometime around 0.10.0.
-
ERROR 144 (HY000): Table ‘./fog/userTracking’ is marked as crashed and last (automatic?) repair failed
Seems to be the issue, how can I fix that?
-
-
Thanks! It’s working now.
-
@Tom-Elliott This would have worked too: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Repair_broken_database