Question for the Avamar experts. We have recently performed a 6.0 to 6.1 upgrade. While prepping for the upgrade, we mistakenly staged the software to the root filesystem on the utility node, filling it up. We deleted the files and freed the space, but about 40,000 events were generated in the Avamar event logs. Attempts to load the list of events in the "Administration | Event Management" view never completes, and I'm unable to select all the events and acknowledge them to get them out of the way. Is there any way to run a command from the utility node to either acknowledge all the events or delete them from the system?
I believe you should be able to accomplish this using mccli. I personally have never tried it but my interpretation is the following command syntax should acknowledge ALL events.
>>> mccli event ack --all=true
There are numerous filters to be more specific as shown in the detailed syntax help screen shown below.
mccli event
syntax: mccli event :
: Address of MCS
: MCS Password
: MCS port
: MCS profile key
: MCS User Name
: Normalize output for byte and date/time values
: Output in XML format
:
ack: Acknowledge an event < ==================== Here is specific syntax available for acknowledging events
: Acknowledge events after date (format: YYYY-MM-DD HH:mm:ss)
: Acknowledge all events
: Acknowledge events before date (format: YYYY-MM-DD HH:mm:ss)
This is the part of the process that’s hanging. When attempting to launch the Event Management screen, the large number of events causes the screen to hang. I never get to the list of events, and as such can’t select all and acknowledge all. It may eventually work given enough time, but I’ve let it run for several hours with no progress. Am hoping there’s a way to remove these events without using the GUI.
--after=STRING - Acknowledges events after a date. STRING must be in the format of: YYYY-MM-DD HH:mm:ss where YYYY is the four-digit year, MM is the two-digit calendar month, DD is the two-digit day of the month, and HH:mm:ss is a timestamp.
--all=BOOLEAN(false) - Acknowledges all events.
--before=STRING - Acknowledges events before a date. STRING must be in the format of: YYYY-MM-DD HH:mm:ss where YYYY is the four-digit year, MM is the two-digit calendar month,
DD is the two-digit day of the month, and HH:mm:ss is a timestamp.
--category=STRING - Specifies the category of the events to acknowledge. STRING must be one of the following:
• APPLICATION
• SECURITY
• SYSTEM
• USER
--domain=STRING - Specifies the domain of the events to acknowledge.
--exclude=STRING - Comma-separated list of event codes to exclude from acknowledgement. The comma-separated list cannot contain spaces. The --include and --exclude options are mutually exclusive.
--id=INTEGER - Unique identifier of the event to acknowledge.
--include=STRING - Comma-separated list of event codes to include for acknowledgement. The comma-separated list cannot contain spaces.
The --include and --exclude options are mutually exclusive.
--range=STRING - Specifies a range of event IDs for the events to acknowledge. STRING must be in the format of: ID-1:ID-2 where ID-1 and ID-2 are the lower and upper limits of the range, respectively.
--severity=STRING - Specifies the severity of the events to acknowledge. STRING must be one of the following:
• NODE
• NODE_FATAL
• OK
• PROCESS
• PROCESS_FATAL
• SYSTEM_FATAL
• USER
• USER_FATAL
--source=STRING - Specifies a source storage location for the events to acknowledge, either:
• avamar
• dd
If you specify avamar, then the command acknowledges events for the Avamar server. If you specify dd, then the command acknowledges events for all configured Data Domain systems.
--type=STRING - Specifies the type of event to acknowledge. STRING must be one of the following:
mradamk
215 Posts
5570
0
Posted November 20th, 2013 04:00
I believe you should be able to accomplish this using mccli. I personally have never tried it but my interpretation is the following command syntax should acknowledge ALL events.
>>> mccli event ack --all=true
There are numerous filters to be more specific as shown in the detailed syntax help screen shown below.
mccli event
syntax: mccli event :
: Address of MCS
: MCS Password
: MCS port
: MCS profile key
: MCS User Name
: Normalize output for byte and date/time values
: Output in XML format
:
ack: Acknowledge an event < ==================== Here is specific syntax available for acknowledging events
: Acknowledge events after date (format: YYYY-MM-DD HH:mm:ss)
: Acknowledge all events
: Acknowledge events before date (format: YYYY-MM-DD HH:mm:ss)
: Event category (SYSTEM | APPLICATION | USER | SECURITY )
: Event domain
: Comma-separated list of event codes to exclude
: Unique event identifier
: Comma-separated list of event codes to include
: Event identifier range (format: id:id)
: Event severity (OK | USER | PROCESS | NODE | USER_FATAL | PROCESS_FATAL | NODE_FATAL | SYSTEM_FATAL)
: Event source ( Avamar | DD )
: Event type (DEBUG | AUDIT | INFORMATION | WARNING | ERROR | INTERNAL)
get-info: Get general information on an event
<--code=Integer>: Event code to lookup
: Include event description in output
: Include remedy in output
: Include event summary in output
publish: Publish an event
: Event data attribute.
<--code=Integer>: Event code to publish
: Event summary message.
: Product calling mccli: MCGUI, MCCLI, END_USER, WEB_RESTORE, EM, EMS, NONE, TEST, MCS, SNMP_SUB_AGENT, SCC, DTLT
: Event data value.
show: Show event occurrence details
: Show events after date (format: YYYY-MM-DD HH:mm:ss)
: Show events before date (format: YYYY-MM-DD HH:mm:ss)
: Event category (SYSTEM | APPLICATION | USER | SECURITY )
: Event domain
: Comma-separated list of event codes to exclude
: Unique event identifier
: Comma-separated list of event codes to include
: Event severity (OK | USER | PROCESS | NODE | USER_FATAL | PROCESS_FATAL | NODE_FATAL | SYSTEM_FATAL)
: Event source ( Avamar | DD )
: Event type (DEBUG | AUDIT | INFORMATION | WARNING | ERROR | INTERNAL). Multiple --type options are acceptable.
: Show only unacknowledged events