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 OPENSOLARIS
sasl_log_t
sasl_log_t(3SASL) Simple Authentication Security Layer Library Functions sasl_log_t(3SASL)
NAME
sasl_log_t - the SASL logging callback function
SYNOPSIS
cc [ flag ... ] file ... -lsasl [ library ... ]
#include <sasl/sasl.h>
int sasl_log_t(void *context, int level, const char *message);
DESCRIPTION
Use the sasl_log_t() function to log warning and error messages from the SASL library. syslog(3C) is used, unless another logging function
is specified.
PARAMETERS
context The logging context from the callback record.
level The logging level. Possible values for level include:
SASL_LOG_NONE Do not log anything.
SASL_LOG_ERR Log unusual errors. This is the default log level.
SASL_LOG_FAIL Log all authentication failures.
SASL_LOG_WARN Log non-fatal warnings.
SASL_LOG_NOTE Log non-fatal warnings (more verbose than SASL_LOG_WARN).
SASL_LOG_DEBUG Log non-fatal warnings (more verbose than SASL_LOG_NOTE).
SASL_LOG_TRACE Log traces of internal protocols.
SASL_LOG_PASS Log traces of internal protocols, including passwords.
message The message to log
RETURN VALUES
Like other SASL callback functions, sasl_log_t() returns an integer that corresponds to a SASL error code. See <sasl.h> for a complete list
of SASL error codes.
ERRORS
SASL_OK The call to sasl_log_t() was successful.
See sasl_errors(3SASL) for information on SASL error codes.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWlibsasl |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
|MT-Level |MT-Safe |
+-----------------------------+-----------------------------+
SEE ALSO
sasl_errors(3SASL), syslog(3C), attributes(5)
SunOS 5.11 27 Oct 2003 sasl_log_t(3SASL)