My App Layering appliance under Monitoring and Storage both service show as "Needs Attention"

[Sergio Masone1709161115]

Im running 2409 appliance, Everythting seems to be working just fine post migration from older appliance (2403.3), however the message "Need Attention" is always there in the "Monitoring and Storage" section for the Layering and Management Service, however everything seems to work, so I do not know why it's complaining. Anyone else with this behavior? cannot find anything to explain this.

[Tyler]

We did see one case where the layering service lost connection to the database.  This was fixed by restarting the layering service with the command:

systemctl restart cams

Just rebooting the ELM should also do the trick if you would rather do that.

[Sergio Masone1709161115]

4 hours ago, Tyler said:

We did see one case where the layering service lost connection to the database.  This was fixed by restarting the layering service with the command:

systemctl restart cams

Just rebooting the ELM should also do the trick if you would rather do that.

Hi Tyler,
Unfortunately the message still persist after restarting the service.

[Tyler]

If you open a support case with the logs, we can take a look and figure out what is going on.

[Sergio Masone1709161115]

On 11/5/2024 at 9:23 AM, Tyler said:

If you open a support case with the logs, we can take a look and figure out what is going on.

I did open a case, level 1 are making me run this App Layering - Stuck Tasks or new tasks hang at "pending" or "stalled" despite my having no stuck tasks nor any symptoms relating to that article..

[Tyler]

What is the case number?

[Sergio Masone1709161115]

3 minutes ago, Tyler said:

What is the case number?

Hi
it is 83040905

[Sergio Masone1709161115]

Afte rebooting, the service was still marked as "needs Attention" then bout 10 min later it changed status to "running".. not sure what got it out of this state, reboot or the commands against the database..I will keep an eye on it.

it did clear over 41647 rows from the storedregisteredtasks
 

mysql> delete from WorkItemContext;
Query OK, 73 rows affected (0.00 sec)

mysql> update WorkItem Join WorkTicket on wtiWorkTicketId = wtId SET wtiState =                                                                                                                                                              'Canceled' WHERE wtiState not in('Complete', 'Failed', 'Canceled');
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0  Changed: 0  Warnings: 0

mysql> update WorkItem Set wtiUserActionPerformed = 0 Where wtiUserActionPerform                                                                                                                                                             ed != 0;
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0  Changed: 0  Warnings: 0

mysql> delete from StoredRegisteredTask;
Query OK, 41647 rows affected (2.26 sec)
 

[Tyler]

Hmm, interesting.  41,647 seems a lot for that table on a relatively new ELM.  The services will report that they need attention if CPU usage or memory usage gets too high.  On a reboot it isn't unusual for the CPU to working hard.  That could explain the 10 minutes of needs attention after reboot.

[Sergio Masone1709161115]

Its back to that again wth needs attention... this time tho im getting alerts of memory swapping.

 

Dear application layering administrator:

 

The following services MAY be experiencing health issues and MAY require attention:

 

* Layering Service since 11/15/2024 9:44:39 PM

** High swap memory usage

* Management Service since 11/15/2024 7:21:44 PM

** High swap memory usage

with the new appliance is there new memory recommendations for the new OS its using?

[Tyler]

No, 8 GB is still the recommendation.  What hypervisor is your appliance on?

[Sergio Masone1709161115]

3 hours ago, Tyler said:

No, 8 GB is still the recommendation.  What hypervisor is your appliance on?

Nutanix AHV