Can anyone please let me know the procedure to do the solace integration with nagios monitoring tool.
I would like to know the step that how can be monitor solace appliance with nagios core
You can send the Solace Syslog messages to the Nagios server and do the filtration of alert at Nagios level for monitoring.
Please run the following commands on the solace appliance to log to your Nagios server.
solace> enable
solace# configure
solace(configure)# create syslog nagios
solace(configure/syslog)# facility command
solace(configure/syslog)# facility system
solace(configure/syslog)# facility event
solace(configure/syslog)# host 192.168.1.12 transport tcp
Host IP will be your destination IP, where you want syslog messages to go to.
Related
The gist of the issue is that I am trying to connect to a MSSQL Express Docker container, living on a RHEL 7 server from my local Windows 10 machine using Microsoft SQL Server Management Studio. It is successfully connecting to the RHEL 7 server IP address and port (1433), using the username/password that was created for the container. However, it is throwing out an error that, after countless hours scouring Google, people have referenced back to needing to enable TCP/IP. This is easy in the Windows GUI. Not so much in a Linux environment.
The error message from SSMS:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (Microsoft SQL Server, Error: 64) -> The specified network name is no longer available
I know how to do this in the Windows environment:
Run SQL Server Configuration Manager
Expand SQL Server Network Configuration
Select Properties for Protocols for MSSQLSERVER
Enable TCP/IP
I have also figured out how to use mssql-conf to modify various attributes in mssql.conf, which is where this change will take place. The issue is that I want to enable TCP/IP, but I am not seeing that option under the /opt/mssql/bin/mssql-conf list | more.
Any suggestions?
For reference, these are the parameters you can use with mssql-conf (the equivalent of SQL Server Configuration Manager on Linux).
control.alternatewritethrough Enable optimized write through flush for O_DSYN
C requests
control.hestacksize Host extension stack size in KB
control.stoponguestprocessfault Stops the process if any guest process reports
unhandled exception
control.writethrough Use O_DSYNC for file flag write through request
s
coredump.captureminiandfull Capture both mini and full core dumps
coredump.coredumptype Core dump type to capture: mini, miniplus, filt
ered, full
distributedtransaction.allowonlysecurerpccalls Configure secure only rpc calls for distributed
transactions
distributedtransaction.fallbacktounsecurerpcifnecessary Configure security only rpc calls for distribut
ed transactions
distributedtransaction.maxlogsize DTC log file size in MB. Default is 64MB
distributedtransaction.memorybuffersize Circular buffer size in which traces are stored
. This size is in MB and default is 10MB
distributedtransaction.servertcpport MSDTC rpc server port
distributedtransaction.trace_cm Traces in the connection manager
distributedtransaction.trace_contact Traces the contact pool and contacts
distributedtransaction.trace_gateway Traces Gateway source
distributedtransaction.trace_log Log tracing
distributedtransaction.trace_misc Traces that cannot be categorized into the othe
r categories
distributedtransaction.trace_proxy Traces that are generated in the MSDTC proxy
distributedtransaction.trace_svc Traces service and .exe file startup
distributedtransaction.trace_trace The trace infrastructure itself
distributedtransaction.trace_util Traces utility routines that are called from mu
ltiple locations
distributedtransaction.trace_xa XA Transaction Manager (XATM) tracing source
distributedtransaction.tracefilepath Folder in which trace files should be stored
distributedtransaction.turnoffrpcsecurity Enable or disable RPC security for distributed
transactions
filelocation.defaultbackupdir Default directory for backup files
filelocation.defaultdatadir Default directory for data files
filelocation.defaultdumpdir Default directory for crash dump files
filelocation.defaultlogdir Default directory for log files
filelocation.errorlogfile Error log file location
filelocation.masterdatafile Master database data file location
filelocation.masterlogfile Master database log file location
hadr.hadrenabled Allow SQL Server to use availability groups for
high availability and disaster recovery
language.lcid Locale identifier for SQL Server to use (e.g. 1
033 for US - English)
memory.memorylimitmb SQL Server memory limit (megabytes)
network.disablesssd Disable querying SSSD for AD account informatio
n and default to LDAP calls
network.enablekdcfromkrb5conf Enable looking up KDC information from krb5.con
f
network.forceencryption Force encryption of incoming client connections
network.forcesecureldap Force using LDAPS to contact domain controller
network.ipaddress IP address for incoming connections
network.kerberoskeytabfile Kerberos keytab file location
network.privilegedadaccount Privileged AD user to use for AD authentication
network.rpcport TCP port for Rpc endpoint mapper
network.tcpport TCP port for incoming connections
network.tlscert Path to certificate file for encrypting incomin
g client connections
network.tlsciphers TLS ciphers allowed for encrypted incoming clie
nt connections
network.tlskey Path to private key file for encrypting incomin
g client connections
network.tlsprotocols TLS protocol versions allowed for encrypted inc
oming client connections
sqlagent.databasemailprofile SQL Agent Database Mail profile name
sqlagent.enabled Enable or disable SQLAgent
sqlagent.errorlogfile SQL Agent log file path
sqlagent.errorlogginglevel SQL Agent logging level bitmask - 1=Errors, 2=W
arnings, 4=Info
telemetry.customerfeedback Telemetry status
telemetry.userrequestedlocalauditdirectory Directory for telemetry local audit cache
Also for reference, this is the only thing in the mssql.conf file. If something is there be default, I have no way of knowing it, because all I have to go off of is what's listed in this file:
[sqlagent] enabled = true
I have a remote customer machine that will not connect with either Remote Desktop or Radmin/Remote Administrator v3.5.2.1
The machine is a fresh build of Win10 Pro 20H2 on a Xeon.
It responds to PING, and DIR \\Computer\C$ and file copies to the same.
I can PSEXEC to the machine, run CMD.EXE /k without problem.
I do not yet have access to gpedit.msc but I doubt there is a GPO on a fresh standalone build.
The machine is a WORKGROUP member.
This is the logfile from a powershell script I wrote to audit the machine.
Info Windows Version 10.0.19042.0
Type Client operating system
Edition Windows 10 Pro
Product Windows(R) Operating System, OEM_DM channel
Status License Status = 1
Action Checking connected networks
Info Connected adapter ETHERNET 2
Action Checking firewall profiles
Info Domain is Disabled
Info Private is Disabled
Info Public is Disabled
Action Checking registry settings
Info fDenyTSConnections = 0 RDP is enabled
Info RDGClientTransport is not present
Info RDP Network Level Authentication is Disabled
Info SMB1 protocol is Enabled
Action Checking RDP services
Info Remote Desktop Services is Running
Info RDP UserMode Port Redirector is Running
Info DCOM Server Process Launcher is Running
Info RPC Endpoint Mapper is Running
Info Remote Procedure Call (RPC) is Running
Action Checking listening ports
Info RDP port 3389 is PID=5432 in process 'svchost'
Info RDP port 3389 state is Listening
Action Checking Trusted Hosts
Info Trusted Hosts value is '*'
There were two separate problems working here.
#1 - Win10 host does not like the Server 2003 5.x RDP client.
Version 6.0 is the last client for Server 2003, and this is acceptable to Win10.
RDP now connects to Win10 using the v6 client.
#2 - Xfinity has a security nanny operating by default.
When they determine a threat exists, they block all incoming traffic.
So far, their automated process refuses to unblock traffic, or disable the nanny.
I am trying to connect from a NoMachine client on a Windows 7 machine to an OpenSUSE machine. I can only connect via NX however I keep running into Error 138:Connection Timed out. I can connect via SSH on my Command prompt however Seem to be unable to connect via here. Does anyone know a solution - been doing this since morning with no light in sight!
Routers supporting UPnP or NAT-PMP are configured automatically to pass connections to NoMachine and all required information is displayed at initial screen (Welcome to NoMachine).
Routers not supporting UPnP or NAT-PMP and Firewalls have to be configured manually to pass traffic to port 4000 (NX protocol), 22 (SSH protocol on Linux/MacOSX) or (4022) (SSH protocol on Windows).
So, check the configuration first.
I have a similar issue setting up my ftp server.
There are a couple of possibilities why the connection was not established, but in my case, and perhaps yours, you must allow the service you're trying to execute in your firewall settings.
In my case I allowed the ftp port and some other specific port for tcp communication.
This (and the proper service, router, etc setup) allowed the communication to be established.
I have setup a nagios distributed monitoring system environment and i am able to send passive checks to Nagios server using send_nsca. When i look at the handshake between Nagios Client and Nagios Server, i see that Nagios Client is establishing a tcp connection to Nagios server whenever it has something to send and terminating the connection once the client is done sending the information. I want the tcp connection to stay up forever instead of terminating every time after data transfer is done. Could anyone please let me the know the process to make this happen?
You cannot do this without modifying the standard NSCA daemon. Normally, it will time out and that's why the NSCA client reestablishes the connection.
I've implemented send_nsca in both Perl and Ruby, and in both cases cannot make a persistent connection work.
A better solution, though, if you are using Nagios 3.x is to install the livestatus module (part of check_mk). This allows passive checks to be submitted, but supports a persistent connection and a whole lot more. We've moved to using this instead for many cases.
I'm trying to intercept application specific syslog log traffic from a custom UDP server in ubuntu. For testing purposes, I stopped the default syslogd daemon running in port 514 and configured a UDP server to listen to UDP traffic on port 514. I have faced the following questions in doing so:
The remote logging feature has to be enabled in /etc/default/syslogd file using SYSLOGD="-r". However, since I stopped the syslogd daemon and am running my own UDP server on port 514, is there any other way to enable remote logging (programmatically, etc.) without using syslog.conf file so that log traffic is sent to the port 514?
Is there a way to direct syslog log traffic to another port with the default port 514 (traffic must be sent to both ports)? If this is the case, I can easily run a custom UDP daemon in the second port and intercept log traffic.
Thanks.
You can't have two daemons listening on the same port. Set up your UDP test server (e.g. netcat) to listen on another port (e.g. 1514) and configure your ubuntu server to send logs to this port.