Symptom

Discovery task is stuck in notification while the AQ task is failed. Found that Discovery was already failed, notification task was still showing the discovery task running. ######### Discovery in progress. Jul 19 02:46:03 FMC ActionQueueScrape.pl[14788]: Tue Jul 19 02:46:03 2022 - ABBA - regCleanupOnDC END Jul 19 02:46:03 FMC ActionQueueScrape.pl[14788]: END TASK || e09cd7c6-070c-11ed-8206-f2dd727720d8 || Registration || Communication with FTD2 has been established, discovery in progress || 23 Jul 19 02:46:03 FMC ActionQueueScrape.pl[16128]: Added table event with table_id 37 Jul 19 02:46:03 FMC ActionQueueScrape.pl[16128]: Added table remediation_status with table_id 38 ######## RPC failed message that indicates that communication with FTD was there. Jul 19 02:46:07 FMC ActionQueueScrape.pl[16756]: RPC failed: Remote::SF::Synchronize::Transaction::requestRemote(d306b274-0709-11ed-928b-a33c7c60b3ed) Jul 19 02:46:07 FMC ActionQueueScrape.pl[16756]: RPC timed out at /usr/local/sf/lib/perl/5.10.1/SF/Synchronize/Transaction.pm line 454. Jul 19 02:46:07 FMC ActionQueueScrape.pl[16756]: Task failure (edeacc94-070c-11ed-836c-82ae5a3e8bf6) Sync CAPS to d306b274-0709-11ed-928b-a33c7c60b3ed : Error inserting remote task at /usr/local/sf/lib/perl/5.10.1/SF/Synchronize/Transaction.pm line 276. Jul 19 02:46:07 FMC ActionQueueScrape.pl[16549]: Task failure (ed963314-070c-11ed-836c-82ae5a3e8bf6) Push VDB : RPC timed out at /usr/local/sf/lib/perl/5.10.1/SF/ActionQueue.pm line 2553. ####### mdb.sfsnort> select status,category,hex(uuid),body from notification where status='7'; +--------+--------------------+----------------------------------+---------------------------------------------------------------+ | status | category | hex(uuid) | body | +--------+--------------------+----------------------------------+---------------------------------------------------------------+ | 7 | discovery:category | 931390C685C23538BF7569ABA1CB4F1E | {"arguments":{"host":"FTD2"},"property":"discovery:progress"} | +--------+--------------------+----------------------------------+---------------------------------------------------------------+ 1 row in set (0.000406 seconds)

Conditions

FMC running 6.6.5.2

Workaround

The notification can be manually cleared from the FMC either through omniquery delete, or by restarting tomcat with pmtool restartbyid Tomcat

Further Problem Description