Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
09-07-2007, 03:04 PM
|
#1
|
LQ Newbie
Registered: Sep 2007
Posts: 10
Rep:
|
syslog-ng is not logging
This is basically what I have in the config file:
source s_network{
tcp(ip(0.0.0.0) port(514));
udp(ip(0.0.0.0) port(514));
unix-stream("/dev/log");
};
destination d_network { file("/var/log/network.log"); };
log {source(s_network); destination(d_network); };
All I want right now is to just get it logging syslog messages from the network. I know it's reciving them, because I can see them when I run tcpdump.
I also know I've got it somewhat right, because it does seem to be logging messages from unix-stream. What am I doing wrong/missing?
|
|
|
09-07-2007, 03:29 PM
|
#2
|
Moderator
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417
|
a firewall would be the thing that would block this traffic... do you have one on the machine itself? you'll still see the packets hit the box, but nothign more. definitely try the tcp connectivity not the udp as udp is connectionless, so for udp syslog if it's dropped or accepted the network will look the same. can you telnet to port 514 from a client? that'll test the tcp completely, and you can even stick your own message directly in by typing it yourself.
|
|
|
09-07-2007, 03:43 PM
|
#3
|
LQ Newbie
Registered: Sep 2007
Posts: 10
Original Poster
Rep:
|
haha, why didn't i think of that... i suppose it could be a firewall...
I can't telnet to port 514, so I guess something is blocking it... now to find out what
(this is on fedora 7 btw)
|
|
|
09-08-2007, 01:39 PM
|
#4
|
LQ Newbie
Registered: Sep 2007
Posts: 10
Original Poster
Rep:
|
hmm, well, I think I allowed for syslog messages to come through in iptables, but either I didn't do it right, or it didn't work.
I tried this... iptables -A INPUT -p tcp --sport 1024:65535 --dport 514 --j ACCEPT
Any other ides?
|
|
|
09-08-2007, 02:13 PM
|
#5
|
Moderator
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417
|
well just try temporarily disabling the firewall before you worry about specific iptables rules... i wouldn't bother about defining a source port range myself btw.
|
|
|
All times are GMT -5. The time now is 05:59 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|