09-08-2018
Maybe you need to change the logging level to get more information?
You should be able to get a more verbose logging level and then you can attempt to connect to the port and see the errors.
There is always a log file somewhere that can help you sort this out.
You just need to find the right log and the right logging level.
10 More Discussions You Might Find Interesting
1. AIX
Hi Guys,
i am trying to open a port in AIX.
but i am not able to get the command for this. AIX is not having the iptables file present.
So please any body can tell me how to open a port in AIX...
Thanks
sanju (2 Replies)
Discussion started by: sanju_d1231
2 Replies
2. IP Networking
Hi. I ran nmap on my server, and I get the following:
Starting Nmap 4.76 ( http://nmap.org ) at 2009-03-19 16:33 EDT
Interesting ports on -------- (-----):
Not shown: 997 closed ports
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
6881/tcp open bittorrent-tracker
The... (0 Replies)
Discussion started by: Rledley
0 Replies
3. Infrastructure Monitoring
I'm trying to register & start a service using SMF on Solaris 10. It's nsca, part of the Nagios monitoring system. I've got nsca running fine as a detached process, and can manually create passive checks via send_nsca. But when I try to run nsca as a daemon, I need some advice.
The nsca... (0 Replies)
Discussion started by: lyle
0 Replies
4. Web Development
Hi,
During Nagios install we added the following piece of config to apache httpd.conf file and it runs on the regular port 80, now if I want to run this on a different port then what needs to changed to make it run on lets say port 8080.
I tried adding Virtual servers but was getting... (1 Reply)
Discussion started by: jacki
1 Replies
5. Shell Programming and Scripting
Hope someone can help, I've been pulling my hair out with this one...
I've written a shell script that does a sanity check on our quite extensive Nagios configuration for anything that needs cleaning up but wouldn't make the Nagios daemon necessarily bork or complain.
One section of the script... (2 Replies)
Discussion started by: vinbob
2 Replies
6. AIX
Hi all,
I have problem while starting Oracle Listener on port 1001(I think it's well known ports).
It's error "Permission denied"
I can start it on port 1111 and no any service started on port 1001(netstat -an).
Can I start on this port ??, How ??
Thank you
aRm (5 Replies)
Discussion started by: arm_naja
5 Replies
7. Programming
Hi all, is it possible to use a different port number for daytime service. By default the port number of daytime service is 13, so what if I want to get the time from a different port number e.g say 9000 (or any other port).
I guess this would remain the same on the server side !... (2 Replies)
Discussion started by: manisum
2 Replies
8. IP Networking
i want to kill a tcp connection by killing its pid
with netstat -an i got the tcp ip connection on port 5914
but when i type ps -a or ps-e there is not such process running on port 5914
is it possible that because i do not log on with proper user account i can not see that process running? (30 Replies)
Discussion started by: alinamadchian
30 Replies
9. Solaris
Hello,
I have an unloaded T5140 machine and want to access the ILOM for the first time and subsequently the network port after that., and then load Solaris 10 the final January 2011 build.
The first part is what confuses me -the cabling.
I am coming from a Windows machine (w/appropriate... (5 Replies)
Discussion started by: joboy
5 Replies
10. AIX
Hello All,
I am new to Nagios. I have a requirement to monitor AIX 7.1 using Nagios xi, could any one guide me steps to go in right direction.
I know Nagios doesn't have precompiled agent and plugin for aix 7.1.
Appreciate your help (2 Replies)
Discussion started by: bsivavani
2 Replies
LEARN ABOUT OSF1
tntnet.properties
tntnet.properties(7) Tntnet users guide tntnet.properties(7)
NAME
tntnet.properties - configuration-file for tntnet (8)
DESCRIPTION
tntnet(8) uses cxxtools for logging and is configured in the configuration-file tntnet.properties.
Because cxxtools is a meta-logging-library, which can be compiled to use different logging-libraries, the content of tntnet.properties is
dependend of the underlying logging-library. Cxxtool has a built-in logging-library as default, which is documented here.
format
The format of tntnet.properties is line-based. A line consists of a variable-name followed by a equals-symbol and a value. Lines, which
does not follow this format and lines, which start with a hash (#), are ignored. It is recomended to prefix non-empty comments with a hash
to make clear, that it is a comment.
level
The logging-library has 5 levels for logging: fatal, error, warn, info and debug. Fatal has the highers priority and "debug" the lowest.
category
Each log-message has a category. Categories are hierarchical. Names of subcategories are devided by a dot.
log-message
Each log-message has a level and a category. If the level of the message is higher or equal to the level of the category, the message is
logged. To assign a level to a category put a line with the word "logger", a dot, the category, the symbol "=" and the category into tnt-
net.properties. Only the first letter of the value is checked and case is ignored, so e.g. info can be specified with INFO, info, I or
even ixxxx. If no level is specified for the current category, the upper category is checked. If nothing is found, the default level is
used. The default level is specified by the variable "rootLogger". If no rootLogger is specified, the level error is used.
destination
If nothing else is specified, log-messages are printed to standard-output. To redirect output to a file, specify the filename with the
variable file.
The cxxtools-logger can limit the size of the log-file by rolling log-files. If the limit is reached, the current file is renamed by
appending ".1" to it. If there is already a file with that name, this file is renamed to "*.2" and so on, until the maximum backupfile
limit is reached. The oldest file is deleted then. To specify the maximum file size, set the variable maxfilesize. The value specified
here can be postfixed with 'k' or 'M' to specify kBytes or MBytes. The maximum fileindex backed up is set with maxbackupindex.
Since writing the file can take some time, output can be buffered and written physically in regular intervals. The interval is specified
in milliseconds with the variable flushdelay. The logging-library starts a background-thread, which flushes the buffer regulary. This
improves logging-speed significantly. The problem is, that a background-thread is used, which consumes resources and if the program
crashes, the most recent log-messages might not be in the file.
Log-messages can be sent to another host in the network with udp. This is done by specifying a hostname and a port with the variable host.
The value must be a hostname, followed by a ':' and a port. Each log-message is sent in a single udp-message.
EXAMPLES
logging to standard-output:
rootLogger=INFO
logger.tntnet=WARN
logging to a file with rolling file and a background-flusher:
rootLogger=INFO
logger.tntnet=WARN
file=tntnet.log
maxfilesize=1MB
maxbackupindex=10
flulshdelay=100
logging to another host
rootLogger=INFO
logger.tntnet=WARN
host=pluto.tntnet.org:1234
AUTHOR
This manual page was written by Tommi Makitalo <tommi@tntnet.org>.
SEE ALSO
tntnet(8)
Tntnet 2006-08-13 tntnet.properties(7)