06-03-2002 05:39 AM - edited 03-08-2019 10:49 PM
The table opened fine when I first created the alarm view. I came back in after the weekend and now I can't get into it. Is there somewhere that lists what these error numbers are so I can troubleshoot anything else that comes up.
06-03-2002 07:20 AM
You can first open a Dos Cmd window, then go to /path/to/Cisco IDS Event Viewer/MySQL/bin directory and type 'perror ERROR_NUMBER'. For exampe, type following:
perror 145
It will show you what error number '145' means.
Basically, the table was crashed. MySQL table may gets crashed only if the user hard reboots the machine(turned the power off or windows crashed etc.) when the mysql server is doing insertion data into that table. You can fix the problem by following the steps in IEV configure notes. Please refer to trouble shooting section - 'Unable to Save Events to MySQL Database'. I have also cut-paste the trouble shooting steps as below:
******************************************************************************
You can correct the problem by closing the IDS Event Viewer and then stopping the MySQL service and deleting the corrupt files. To stop the MySQL service, select Start > Settings > Control Panel > Services > MySQL, and then click Stop. Next, delete the following files from the mysql\data\alarmDB directory:
event_realtime_table.frm
event_realtime_table.MYI
event_realtime_table.MYD
Finally, restart the Cisco IDS Event Viewer service. The Cisco IDS Event Viewer should now be able to properly store realtime events.
******************************************************************************
Notice the mysql\data\alarmDB directory is under your box's /path/to/Cisco IDS Event Viewer/ directory.
Jie
06-03-2002 07:49 AM
Thanks for the help. I was able to bring it back up.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide