09-17-2016
One of the more important things of Tomcat Monitoring is to keep an eye on the memory usage. The solution for most Tomcat/Java Server Problems is...
More Memory!
Some say there's only one better thing than more memory for a Tomcat Server:
Even more Memory!
And for the monitoring part: I suggest you to have a more broader look at your problem. When you have a certain message "...bla...broken pipe...", then you may know it already "Ah this one again" or you dig into your system until you figure out the root cause of the problem. What helps a lot in discovering the reasons are system performance data.
- Tomcat Java Memory Usage over time
- System RAM Usage over time
- IO-Usage and Filesystem growth over time
- CPU-Usage
- Load
- Network(Bandwidth+Errors)
- Clock-synchronisation and drift(Very important!)
If you have those data, you'll discover from a look at those graphs what is normal for your system at what is not and above all: you'll discover all sort of changes before a critical state is reached. You'll learn what the impact of certain technical changes is, when you see the data coming in after that.
I suggest you to have a look at some monitoring system. As I assume you work in some type of company, there's probably already a monitoring system installed. I would expect most monitoring systems to be flexible enough to add your specific own checks there or use the features already available there. If no monitoring system is available to use, I recommend monit as an easy one ore check_mk as a more powerful approach - the latter needs to be on a separate best dedicated system(vps is enough). (Maybe there's a better solution for solaris available, but I do not know that).
There are some checks available for Tomcat/Java and check_mk. The client(=your tomcat server) part consists of a bash script most of the times. Sometimes, so chances are good that they just work at your server. Look here:
Catalog of check plugins
And of course that one you're after(log file pattern matching) may be an import issue too. Most monitoring applications do have such features available.
Last edited by stomp; 09-17-2016 at 05:08 PM..
10 More Discussions You Might Find Interesting
1. Solaris
How can I make analysis for catalina.out (2 Replies)
Discussion started by: Burhan
2 Replies
2. Shell Programming and Scripting
I have Tomcat installed on a Unix box and I need to start it remotely from another Unix box.
Tomcat is started using a script. When this script is run locally everything is fine. When I run the same script from remote box, tomcat starts but the command running the script does not terminate.:(
... (2 Replies)
Discussion started by: shrgh
2 Replies
3. Shell Programming and Scripting
Hi, I am a nbee to Unix, I have used following script to check my tomcat is running or not and restart if it down. but actually it restart my tomcat each time running even my tomcat still running fine:
Script that can run a check and perform an action if the check fails
... (1 Reply)
Discussion started by: quyennd
1 Replies
4. Shell Programming and Scripting
Hello Everyone,.
I am a novice with shell scripting and have written some minor shell scripts to copy files and such that. Now I have a requirement to write a shell script to go check if Tomcat running in the same server is up or not, if not then run the Tomcat startup script. Then put this... (4 Replies)
Discussion started by: bhaire
4 Replies
5. Shell Programming and Scripting
Hello Forum,
I have prepared script to monitor the tomcat status. Following is the script which will monitor tomcat instance.I need little modifcation in the script. My script will grep for java,the output of grep command will analyze by if condition under for loop and will
send following echo... (7 Replies)
Discussion started by: coolguyamy
7 Replies
6. Shell Programming and Scripting
Hello everyone,
I have a small expect script as follows;
#!/usr/bin/expect -f
set force_conservative 0 ;# set to 1 to force conservative mode even if
;# script wasn't run conservatively originally
if {$force_conservative} {
set send_slow {1 .1}
proc send {ignore arg}... (1 Reply)
Discussion started by: randeel
1 Replies
7. Shell Programming and Scripting
i have a problem with the code I created (see below).
a. when I logged in as root and su to tomcat, i can execute all options. when I press X, it will exit properly.
b. when I logged in directly as user1, I can execute also all options. if I press X i will logout automatically to putty.... (2 Replies)
Discussion started by: lhareigh890
2 Replies
8. Solaris
Hi,
We have upgrade tomcat from 5.0.20 to 7.0.33 and made changes to server.xml file according to newer version.. how ever the upgrade went fine and now i am unable to deploy application remotely.. it is giving 403 access denied error.. we have seperate appbase directory mentioned in server.xml..... (0 Replies)
Discussion started by: phani4u
0 Replies
9. Shell Programming and Scripting
Hello Forum,
I have prepared script to monitor the tomcat status.
Following is the script which will monitor tomcat instance.
I need little modifcation in the script.
My script will grep for process,
the output of grep command will analyze by if condition under for loop and will send... (2 Replies)
Discussion started by: ooilinlove
2 Replies
10. UNIX for Advanced & Expert Users
Hi all,
on our application server we have the following script that monitor the status of the website, my problem here is that i have edite the retries from 3 to 5,
and the timewait to 120 second,
so the script should check 5 times every 2 minutes, and if the fifth check fails it must restart... (0 Replies)
Discussion started by: charli1
0 Replies
LEARN ABOUT SUSE
sensors-detect
SENSORS-DETECT(8) System Manager's Manual SENSORS-DETECT(8)
NAME
sensors-detect - detect hardware monitoring chips
SYNOPSIS
sensors-detect
DESCRIPTION
sensors-detect is an interactive program that will walk you through the process of scanning your system for various hardware monitoring
chips, or sensors, supported by libsensors(3), or more generally by the lm_sensors tool suite.
sensors-detect will look for the following devices, in order:
o Sensors embedded in CPUs, south bridges and memory controllers.
o Sensors embedded in Super I/O chips.
o Hardware monitoring chips accessed through ISA I/O ports.
o Hardware monitoring chips reachable over the SMBus or more generally any I2C bus on your system.
As the last two detection steps can cause trouble on some systems, they are normally not attempted if the second detection step led to the
discovery of a Super I/O chip with complete hardware monitoring features. However, the user is always free to ask for all detection steps
if so is his/her wish. This can be useful if a given system has more than one hardware monitoring chip. Some vendors are known to do this,
most notably Asus and Tyan.
WARNING
sensors-detect needs to access the hardware for most of the chip detections. By definition, it doesn't know which chips are there before
it manages to identify them. This means that it can access chips in a way these chips do not like, causing problems ranging from SMBus
lockup to permanent hardware damage (a rare case, thankfully.)
The authors made their best to make the detection as safe as possible, and it turns out to work just fine in most cases, however it is
impossible to guarantee that sensors-detect will not lock or kill a specific system. So, as a rule of thumb, you should not run sensors-
detect on production servers, and you should not run sensors-detect if can't afford replacing a random part of your system. Also, it is
recommended to not force a detection step which would have been skipped by default, unless you know what you are doing.
SEE ALSO
sensors(1), libsensors(3)
AUTHOR
Frodo Looijaard and Jean Delvare
lm-sensors 3 December 2008 SENSORS-DETECT(8)