Re: Setting up a syslog server in a jail
On 30/01/2012 15:40, bsd wrote: I am still not able to get the log correctly sent to the specified jail… ?? Are you running syslogd in the host environment? If so, it's probably bound to INADDR_ANY and thus pre-empted your jailed syslog from binding to a network port. Try adding syslogd_flags=-ss in the host environment. That prevents syslogd from listening via a network port at all, although it will still happily log messages from the local machine. Use sockstat(1) to diagnose what addresses syslogd(8)s have bound to. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Setting up a syslog server in a jail
Le 30 janv. 2012 à 16:59, Matthew Seaman a écrit : On 30/01/2012 15:40, bsd wrote: I am still not able to get the log correctly sent to the specified jail… ?? Are you running syslogd in the host environment? Yes I am running it both in the host and jail environment. If so, it's probably bound to INADDR_ANY and thus pre-empted your jailed syslog from binding to a network port. Try adding syslogd_flags=-ss Ok, I have the following sockstat on the host environment : surf:root 17:09:02 ~ # sockstat | grep sysl root syslogd3176 4 dgram /var/run/log root syslogd3176 5 dgram /var/run/logpriv root syslogd3153 4 dgram /var/run/log root syslogd3153 5 dgram /var/run/logpriv root syslogd3153 6 udp4 1.2.3.6:514 *:* root syslogd2191 4 dgram /var/run/log root syslogd2191 5 dgram /var/run/logpriv root syslogd2191 6 udp4 1.2.3.5:514 *:* root syslogd1947 4 dgram /var/run/log root syslogd1947 5 dgram /var/run/logpriv root syslogd1947 6 dgram /var/run/log root syslogd1947 7 dgram /var/named/var/run/log root syslogd1947 8 udp4 1.2.3.4:514 *:* My syslog server is supposed to be on 1.2.3.6 In the jail environment I have : logjail# sockstat | grep syslo root syslogd3153 4 dgram /var/run/log root syslogd3153 5 dgram /var/run/logpriv root syslogd3153 6 udp4 1.2.3.6:514 *:* … But still no log from outside the jail… ? in the host environment. That prevents syslogd from listening via a network port at all, although it will still happily log messages from the local machine. Use sockstat(1) to diagnose what addresses syslogd(8)s have bound to. Thanks for your answers Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW –– - Grégory Bernard Director - --- www.osnet.eu --- -- Your provider of OpenSource appliances -- –– OSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetO ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Setting up a syslog server in a jail [SOLVED]
Le 30 janv. 2012 à 17:15, bsd a écrit : Le 30 janv. 2012 à 16:59, Matthew Seaman a écrit : On 30/01/2012 15:40, bsd wrote: I am still not able to get the log correctly sent to the specified jail… ?? Are you running syslogd in the host environment? Yes I am running it both in the host and jail environment. If so, it's probably bound to INADDR_ANY and thus pre-empted your jailed syslog from binding to a network port. Try adding syslogd_flags=-ss Ok, I have the following sockstat on the host environment : surf:root 17:09:02 ~ # sockstat | grep sysl root syslogd3176 4 dgram /var/run/log root syslogd3176 5 dgram /var/run/logpriv root syslogd3153 4 dgram /var/run/log root syslogd3153 5 dgram /var/run/logpriv root syslogd3153 6 udp4 1.2.3.6:514 *:* root syslogd2191 4 dgram /var/run/log root syslogd2191 5 dgram /var/run/logpriv root syslogd2191 6 udp4 1.2.3.5:514 *:* root syslogd1947 4 dgram /var/run/log root syslogd1947 5 dgram /var/run/logpriv root syslogd1947 6 dgram /var/run/log root syslogd1947 7 dgram /var/named/var/run/log root syslogd1947 8 udp4 1.2.3.4:514 *:* My syslog server is supposed to be on 1.2.3.6 In the jail environment I have : logjail# sockstat | grep syslo root syslogd3153 4 dgram /var/run/log root syslogd3153 5 dgram /var/run/logpriv root syslogd3153 6 udp4 1.2.3.6:514 *:* … But still no log from outside the jail… ? in the host environment. That prevents syslogd from listening via a network port at all, although it will still happily log messages from the local machine. Use sockstat(1) to diagnose what addresses syslogd(8)s have bound to. Thanks for your answers Problem was with the IP I was listening on. Was the wrong one. Found that using the debug option of syslog -d Very straight forward after debug was enable. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW –– - Grégory Bernard Director - --- www.osnet.eu --- -- Your provider of OpenSource appliances -- –– OSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetO ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org –– - Grégory Bernard Director - --- www.osnet.eu --- -- Your provider of OpenSource appliances -- –– OSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetO ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
