syslog purge

Answered Question
Sep 17th, 2008

the last 2 weeks my syslog records default purge job failed. I got error log "[ Wed Sep 17 10:28:26 PDT 2008 ],ERROR,[main],Drop table failed:ASA Error -210: User 'DBA' has the row in 'SYSLOG_20080722' locked 8405 42W18

[ Wed Sep 17 10:28:27 PDT 2008 ],ERROR,[main],Failed to purge syslogs

[ Wed Sep 17 10:28:27 PDT 2008 ],ERROR,[main],Purge not successful. there is no duplicate job, and I don't know why it's lock. the rmeng.db size is close to 2gb. is that cause a problem. restarting dmgtd can help? thanks in advance.

I have this problem too.
0 votes
Correct Answer by Joe Clarke about 8 years 2 months ago

Something was holding a lock on this table. Since this table is from August, that lock is most likely stale. If there are no other syslog purge jobs scheduled or running, SyslogAnalyzer is a likely suspect. A restart of the SyslogAnalyzer alone may free this lock up. However, if it is Tomcat holding it, then you would need to restart dmgtd.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Joe Clarke Wed, 09/17/2008 - 10:32

Something was holding a lock on this table. Since this table is from August, that lock is most likely stale. If there are no other syslog purge jobs scheduled or running, SyslogAnalyzer is a likely suspect. A restart of the SyslogAnalyzer alone may free this lock up. However, if it is Tomcat holding it, then you would need to restart dmgtd.

eliaspaulos Wed, 09/17/2008 - 13:06

thank you J. stop and restart SyslogAnalyzer solve the problem. appreciated your help!!!

Actions

This Discussion