Storage Group Activity data displaying wrong information
-
When you updated your FOG server, what version did you update from and to?
-
Updated 1.5.7 to 1.5.9-RC1
-
@xburnerx00 I would think there are some old task states in the DB. Let’s try to figure it out. Go to your FOG server console and run the following commands/queries. First get the DB settings and use those credentials to log into the database to run a few queries:
shell> grep DATABASE_ /var/www/html/fog/lib/fog/config.class.php ... shell> mysql -u fogmaster -p fog Password: ... mysql> SELECT * FROM tasks WHERE taskStateID IN ( 0, 1, 2, 3 ); ... mysql> SELECT * FROM multicastSessions WHERE msState IN ( 0, 1, 2, 3 ); ... mysql> quitPost all output here except your credentials.
-
MariaDB [fog]> SELECT * FROM tasks WHERE taskStateID IN ( 0, 1, 2, 3 ); +--------+----------------------------+---------------------+---------------------+------------+-------------+-------------+-------------+--------------+-----------+------------------------+------------+------------+----------+-----------------+-------------------+----------------+-----------------+---------------+----------------+-----------------+-----------------+------------------+---------+---------------+--------------+ | taskID | taskName | taskCreateTime | taskCheckIn | taskHostID | taskImageID | taskStateID | taskIsDebug | taskCreateBy | taskForce | taskScheduledStartTime | taskTypeID | taskPCT | taskBPM | taskTimeElapsed | taskTimeRemaining | taskDataCopied | taskPercentText | taskDataTotal | taskNFSGroupID | taskNFSMemberID | taskNFSFailures | taskLastMemberID | taskWOL | taskPassreset | taskShutdown | +--------+----------------------------+---------------------+---------------------+------------+-------------+-------------+-------------+--------------+-----------+------------------------+------------+------------+----------+-----------------+-------------------+----------------+-----------------+---------------+----------------+-----------------+-----------------+------------------+---------+---------------+--------------+ | 756 | AutoRegTask - IS-STU-SL-03 | 2020-03-14 13:15:35 | 2020-03-14 13:28:02 | 515 | 32 | 1 | 0 | fog | 0 | 0000-00-00 00:00:00 | 1 | 0000000000 | | | | | | | 1 | 1 | | 0 | 0 | | | | 905 | Deploy Task - HS-103-SD-17 | 2020-05-13 12:30:18 | 0000-00-00 00:00:00 | 401 | 33 | 1 | 0 | fog | 0 | 0000-00-00 00:00:00 | 1 | 0000000000 | | | | | | | 1 | 1 | | 0 | 0 | | | | 754 | Deploy Task - IS-STU-SL-16 | 2020-03-14 13:08:01 | 2020-03-14 13:12:05 | 513 | 32 | 3 | 0 | fog | 0 | 0000-00-00 00:00:00 | 1 | 0000000014 | 4.20GB | 00:00:50 | 00:05:04 | 3.264 GiB | 14.12 | 23.680 GiB | 1 | 1 | | 0 | 0 | | | | 771 | AutoRegTask - IS-STU-SL-21 | 2020-03-14 16:05:24 | 2020-03-14 16:07:06 | 529 | 32 | 3 | 0 | fog | 0 | 0000-00-00 00:00:00 | 1 | 0000000074 | 1.85GB | 00:00:11 | 00:00:03 | 415.80 MiB | 74.05 | 529.00 MiB | 1 | 1 | | 0 | 0 | | | | 777 | AutoRegTask - IS-STU-SL-18 | 2020-03-14 16:27:08 | 2020-03-14 16:28:24 | 532 | 32 | 3 | 0 | fog | 0 | 0000-00-00 00:00:00 | 1 | 0000000061 | 25.17MB | 00:00:55 | 00:00:35 | 23.26 MiB | 60.50 | 100.00 MiB | 1 | 1 | | 0 | 0 | | | | 908 | AutoRegTask - HS-104-SD-13 | 2020-05-13 12:49:04 | 2020-05-13 12:50:03 | 584 | 13 | 3 | 0 | fog | 0 | 0000-00-00 00:00:00 | 1 | 0000000000 | | | | | | | 1 | 1 | | 0 | 0 | | | +--------+----------------------------+---------------------+---------------------+------------+-------------+-------------+-------------+--------------+-----------+------------------------+------------+------------+----------+-----------------+-------------------+----------------+-----------------+---------------+----------------+-----------------+-----------------+------------------+---------+---------------+--------------+ 6 rows in set (0.00 sec) Hard to see for me, but I see tasks that were set back in March 14, 2020 and May 15, 2020. MariaDB [fog]> SELECT * FROM multicastSessions WHERE msState IN ( 0, 1, 2, 3 ); Empty set (0.00 sec)I’ve never done Multicast sessions so I would think this should be empty.
-
@xburnerx00 If you are certain you have no tasks needed to be run right, can you run:
UPDATE tasks SET taskStateID = 4 WHERE taskID IN ('756','905','754','771','777','908');You should then have a cleaned up dashboard.
Thank you,
-
@Tom-Elliott said in Storage Group Activity data displaying wrong information:
UPDATE tasks SET taskStateID = 4 WHERE taskID IN (‘756’,‘905’,‘754’,‘771’,‘777’,‘908’);
Yes, thank you, that worked.
Any idea on what may have caused this, and how to avoid in the future?
-
@xburnerx00 Would you please run the following two queries to see if all of the hosts and images referenced still exist.
SELECT * FROM hosts WHERE hostID IN ( 515, 401, 513, 529, 532, 584 );and
SELECT * FROM images WHERE imageID IN ( 32, 33, 13 ); -
MariaDB [fog]> SELECT * FROM hosts WHERE hostID IN ( 515, 401, 513, 529, 532, 584 ); Empty set (0.00 sec) MariaDB [fog]> SELECT * FROM images WHERE imageID IN ( 32, 33, 13 ); +---------+--------------------+-----------+------------------+--------------+----------------+---------------------+---------------+---------------+----------------------------------------------------------------------------------------------------+-------------+----------------------+-----------+-------------+---------------------+---------------+--------------+----------------+-----------------+ | imageID | imageName | imageDesc | imagePath | imageProtect | imageMagnetUri | imageDateTime | imageCreateBy | imageBuilding | imageSize | imageTypeID | imagePartitionTypeID | imageOSID | imageFormat | imageLastDeploy | imageCompress | imageEnabled | imageReplicate | imageServerSize | +---------+--------------------+-----------+------------------+--------------+----------------+---------------------+---------------+---------------+----------------------------------------------------------------------------------------------------+-------------+----------------------+-----------+-------------+---------------------+---------------+--------------+----------------+-----------------+ | 13 | DellOP3050 | | DellOP3050 | 0 | | 2019-07-17 15:31:36 | fog | 0 | 524283904.000000:204800.000000:104857600.000000:16777216.000000:9948450.000000:40748851200.000000: | 1 | 1 | 9 | 0 | 2020-05-11 12:54:12 | 6 | 1 | 1 | 19663157396 | | 32 | Dell Latitude 3189 | | DellLatitude3189 | 0 | | 2020-03-14 09:27:01 | fog | 0 | 554692608.000000:104857600.000000:16777216.000000:25425911808.000000: | 1 | 1 | 9 | 0 | 2020-03-14 11:52:34 | 6 | 1 | 1 | 14588521696 | | 33 | HP 400 G1 | | HP400G1 | 0 | | 2020-05-13 07:39:14 | fog | 0 | 554692608.000000:104857600.000000:16777216.000000:8306813.000000:34024706048.000000: | 1 | 1 | 9 | 5 | 2020-05-13 08:05:09 | 6 | 1 | 1 | 16054171954 | +---------+--------------------+-----------+------------------+--------------+----------------+---------------------+---------------+---------------+----------------------------------------------------------------------------------------------------+-------------+----------------------+-----------+-------------+---------------------+---------------+--------------+----------------+-----------------+ 3 rows in set (0.00 sec) -
@xburnerx00 Looks to me like the Hosts that were in the task were deleted at some point?
So, if what I’m gathering makes sense:
Auto-reg tasks were created (maybe by quick reg for these hosts.), but then the hosts were deleted. When those hosts were deleted, the tasks were not removed.
This would explain why the tasked showed in the “queue” but not on the tasks list (as the hosts didn’t exist).
-
Yes, the Dell Latitude 3189 are laptops that do not have internet ports and we had to use USB adapters. At that time, the version of FOG didn’t like same MACs for multiple machines. So the way I got around that was deleting the hosts since it was tied to a MAC from a USB and I was more concerned with just getting them imaged. I guess I deleted them prematurely. Unless I just overlooked something completely and did something wrong.
As for the deploy task ones, I’m not sure why they were stuck in there. They may have been ones that seemed to be giving me imaging problems and I turned off the machine before canceling it in the task menu.
-
S Sebastian Roth referenced this topic on
