Could not listen on UDP socket: address is in use.
*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
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.
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.
i don't undersatnd what your title has to do with the question... sounds like you need to configure the syslog server correctly and restart it. if you're getting that already in use message i'd assume that syslog is still running and you're trying to start another instance, which naturally isn't possible. not sure if it runs under bsd (no reason why not) but i would recommend syslog-ng for easier networked syslog reception. or even splunk to go to a whole new web 2.0 world of logging.
also openbsd is not linux... thread should shortly be moved to bsd forum.
Evidently, some other process is listening on that port. The first steps to solving your problem are to find out to which port the error refers, and which process is already listening, and then a determination can be made about a remedy. The tools lsof and/or netstat should allow you to locate the offending process. You will have to do a little sidebar research to determine which specific port is being referenced.
--- rod.
do 'lsof -i UDP:syslog'. It should show that syslogd is up and running correctly. You just need to tell your cisco stuff to send syslog info to your machine, choose a facility and point that facility to a logfile (in syslog.conf). If could be that you need to enable remote-logging, which is system-dependent I think (for debian it's in /etc/default/syslogd, don't know how to do it in bsd).
do 'lsof -i UDP:syslog'. It should show that syslogd is up and running correctly. You just need to tell your cisco stuff to send syslog info to your machine, choose a facility and point that facility to a logfile (in syslog.conf). If could be that you need to enable remote-logging, which is system-dependent I think (for debian it's in /etc/default/syslogd, don't know how to do it in bsd).
then maybe lsof is not installed. Try 'pgrep syslogd' or 'ps -A | grep syslogd' instead to verify that syslogd is running. The point is, that your problem is the configuration of syslogd, not the configuration of the network.
You are maybe irritated, that the udp lines in your output don't show the explicit 'LISTEN' but that's correct, it's not an error. udp does not know connection states such as listen or established, in fact it doesn't even use a connection. It's a fire-and-forget protocol, an application will send data and doesn't care if the receiver actually received them.
So you needn't (and can't) set udp ports to 'listen', all you need to do is configure syslogd.
then maybe lsof is not installed. Try 'pgrep syslogd' or 'ps -A | grep syslogd' instead to verify that syslogd is running. The point is, that your problem is the configuration of syslogd, not the configuration of the network.
You are maybe irritated, that the udp lines in your output don't show the explicit 'LISTEN' but that's correct, it's not an error. udp does not know connection states such as listen or established, in fact it doesn't even use a connection. It's a fire-and-forget protocol, an application will send data and doesn't care if the receiver actually received them.
So you needn't (and can't) set udp ports to 'listen', all you need to do is configure syslogd.
Almatic
Thanks for your professinals advice. This is what I get from ps -a | grep syslogd
you need to use capital A (ps -A, not ps -a). Probably that was your problem with lsof as well (capital UDP).
But I guess you have figured that out yourself in the meanwhile ...
you need to use capital A (ps -A, not ps -a). Probably that was your problem with lsof as well (capital UDP).
But I guess you have figured that out yourself in the meanwhile ...
I tried with -A. The result is not Found but "pgrep syslogd" is giving me this two numbers 13746 and 25622. Please explain this results
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.