I have installed and configured the syslog plugin, and have it listening on UDP 514, but I can't seem to see any data for any remote hosts that I have pointed at my cacti server.
I'm 99.9% sure I'm doing something wrong, which may include flat out misunderstanding syslog.
The remote devices I have connected so far are a networked thermostat (proliphix) and our UniFi WiFi controller.
When I search the rsyslogd log files for my UniFi controller I see tons of data ending in "in progres...", but nothing else.
When I search for my thermostat, I get nothing.
Is there a simple way to test syslog? Perhaps a command line utility I can run from a separate host somewhere and send a "hello world" log?
I have found a dozen remote hosts in my syslog list, but no actual logs are showing up, and I have no idea how those syslog messages are getting there (meaning I never configured them to connect to my cacti syslog server).
Having trouble receiving remote syslog commands.
Moderators: Developers, Moderators
-
- Posts: 10
- Joined: Thu Oct 03, 2013 12:50 pm
-
- Posts: 10
- Joined: Thu Oct 03, 2013 12:50 pm
Re: Having trouble receiving remote syslog commands.
I hate to have given up on google and posted only to find a good search string to find what I needed!
Here's what I did to see if remote messages were being received:
1. From a Windows Box attempted to use ncat.exe to send a UDP packet on port 514 with a message. it worked, but poorly because I didn't know what I was doing, so now I have the host "hi" with no other details.
2. From a linux box, used nc to do the same: nc -w0 -u 192.168.1.1 514 <<< "test from remote"
This resulted in the host test sending the message "from remote"...
I have much to learn about syslogging obviously, but at least I know the server is receiving messages.
Here's what I did to see if remote messages were being received:
1. From a Windows Box attempted to use ncat.exe to send a UDP packet on port 514 with a message. it worked, but poorly because I didn't know what I was doing, so now I have the host "hi" with no other details.
2. From a linux box, used nc to do the same: nc -w0 -u 192.168.1.1 514 <<< "test from remote"
This resulted in the host test sending the message "from remote"...
I have much to learn about syslogging obviously, but at least I know the server is receiving messages.
Re: Having trouble receiving remote syslog commands.
I also have this problem; I only see localhost syslog messages, but no remote hosts which are sending syslog data inbound...?
Anyone have any ideas why?
Anyone have any ideas why?
_________________
Lee
"knowledge breeds confidence, confidence breeds success"
Lee
"knowledge breeds confidence, confidence breeds success"
Who is online
Users browsing this forum: No registered users and 1 guest