Quote:
Originally Posted by
linuxadmin
mark,
The application runs is not a small one. it's a big application. And the server becomes very very slow as it used from morning to evening..
Thus in some servers tomcat / postgre or the Entire system itself reboots.
Sounds like you might have problem with Big app. here are the ways to check problems.
Code checks:
1. Check if app open lots of temp files or creates cache which is required to be cleared.
2. If it is a web based app. check if connection to DB is closed after usage. If database is slow or causing slowness to a page.
3. if you have any file called via n/w may be network is slow connecting the server at certain time as n/w might be busy.
4. Check if static pages also load slow if web based app.
5. Check your app logs for more errors
6. Check if you have any fork bomb etc
H/W and S/W check
Install something like MRTG or cacti etc to monitor:
1. Check if your DB is slowing down after certain queries
2. Check if your app server tomcat / weblogic is properly configured.
3. Check if /tmp and /var /usr/local/apachec etc etc where log files are written is having enough space.
4. Check lsof to see files open.
I usually try to blame this way
1. Hardware (check bad mem or disk or any n/w) etc
2. Developers.
3. DBA bad indexing/configurations
4. kiddy perl/shell scripts which cause problems.
5. unnecessary services.
if nothing else the SYS Admin, Data center...
last but not least .... my FATE
01-02-2012
