Hi Shiv,
this is probably happening because of what we call a Defect Storm.
Now that you have eliminated the condition where the collector wasn't able to collect the defects, it is now processing all that he got (also the old one) and tries to aggregate them all at the same time.
You have 2 possibilities:
1. Wait until the collector calms down and is able to also age out old defects. The data retention settings will control this over time. But you will need to have space for the database in the meantime.
2. stop the collector and the TIM. Delete all defects on the TIM (Do not touch the statistics files themselves) that are in the out-queue. Clean up the collector directories (where it stores the defects to process) then restart the TIM and the collector.
Regards
Jörg
Original Message:
Sent: Jan 22, 2022 12:29 AM
From: Shiv Choudhary
Subject: Enterprise Manager cannot reach TIM
Hi Jorg,
We were facing error in one of our TIM server as the Worker XX folder under defects directory consuming lots of space . we have removed the files from the worker & noticed that our MOM is heavily loaded with defects data & the Database size is increasing at an alarming rate .
huge number of defects data started creating in DB and we are running out of space due to this. I have observed database size increase by 10GB in a day.
Please help me as i can't find any exact solution from Broadcom too . For this case 32989022 is also raised. PFB Screenshot for more clarity .
------------------------------
Shiv Choudhary
India
Original Message:
Sent: Jan 05, 2022 03:17 AM
From: Jörg Mertin
Subject: Enterprise Manager cannot reach TIM
Hi Shiv,
you have to go onto the TIM - and check (depending if you are running a plain TIM or a MTP) the mentioned directories for remaining files.
Maybe you want to du a "du - /etc/wily/cem/tim/data/out/defects" (or replace with correct directory) just to see how much data is inside first.
If you want, we can do WebEx to check it out together (Note that I am in Europe/Paris timezone). PM me to schedule it.
Original Message:
Sent: Jan 04, 2022 10:22 PM
From: Shiv Choudhary
Subject: Enterprise Manager cannot reach TIM
Hi Lynn,
I am also getting the same error and our entire 7 servers which include one MOM one agent collector, one TIM collector and four TIM servers are on physical environment.
why this error is coming in logs in CEM?
https://knowledge.broadcom.com/external/article/30192/em-unable-to-process-defects-seeing-http.html -
gone through this article too but unable to understand in point three where do we have to act, I mean out of seven servers where we need to troubleshoot
Shiv
------------------------------
Shiv Choudhary
Tata Consultancy Services
India
Original Message:
Sent: Nov 11, 2013 04:59 PM
From: Lynn Williams
Subject: Enterprise Manager cannot reach TIM
adan_85:
Hi Adan,
If this is only an intermittent problem it is likely to be a transient Network related problem rather than configuration related.
I have seen such intermittent errors reported (a few per day) when the EM and/or TIM are running under a virtual environment & there was no resolution aisde from just ignoring the messages.
If you think this may be more "sinister" and need a more extensive review please raise an issue with us.
Thanks,
Lynn
CA APM Support