Sign of corrupted database

Product: OSCE 8.0, build 1189

A customer was having problem to load the login page of OSCE console. It's taking longer time than usual. Most of OSCE clients showed the offline icon. From the Task Manager of the server, performance for CPU and PF usage didn't indicate anything suspicious. Disabling the NIC, we were able to access the console with no problem. Mystery?? First round we collected the SIC log, capture the traffic using WireShark and running process using Process Explorer.

A tip from Trend that pattern file 4.995 may cause some OSCE server to be sluggish. This was not the case since customer was using 5.101 pattern file.

We received another suggestion from Trend, to look for *.tmp file in HTTPDB folder. If there was such file in that folder, it could indicate a corrupted database. Yes, we found one instance of .tmp file. We then resort to rebuilding the database.

Please read this for explanation.

That solved the problem. Case closed.