Very Computer

by Ni » Mon, 26 Aug 2002 13:40:05

in server side, I turn on the "-r" switch;

But I still can not see log information in server.

Any idea?

by **Thomas Phipp** » Mon, 26 Aug 2002 14:40:33

> in server side, I turn on the "-r" switch;

> But I still can not see log information in server.

> Any idea?

you did rember to restart both klogd and syslogd
right?

also do something that you know will generate a
log

--
Thomas Phipps
www.javatrix.net/whytewolf
Linux User #180408 LFS User #1791

by Ni » Tue, 27 Aug 2002 03:37:51

> > in server side, I turn on the "-r" switch;

> > But I still can not see log information in server.

> > Any idea?

> you did rember to restart both klogd and syslogd
> right?

> also do something that you know will generate a
> log

I restart both syslogd and klogd, and they work fine
for seperate machine.

And I try in client machine:
logger -u 514 -p authpriv.info "www"
it say: connect failed, not such file.

but I try in client machine
logger -p authpriv.info "www"
"www" will appear in log file. This try also work in server machine.

by **Ken DeRoch** » Tue, 27 Aug 2002 06:19:02

> in server side, I turn on the "-r" switch;

> But I still can not see log information in server.

> Any idea?

On the system that you want to send out it's syslog
messages, you will need to start syslogd with -h
option.

Ken

by Ni » Wed, 28 Aug 2002 14:14:47

> > in server side, I turn on the "-r" switch;

> > But I still can not see log information in server.

> > Any idea?

> On the system that you want to send out it's syslog
> messages, you will need to start syslogd with -h
> option.

In client side, I try syslog option "-m 0 -h" and
"-h", neither works.

In client side, I also try: logger -u 514 -p authpriv.info "bbb"
then it say: connect: no such file or directory. It seems
syslogd in client side can not use udp port 514 to send out
message.

by **Christiaan Otto** » Wed, 04 Sep 2002 22:53:22

syslogd -r should do...

From the man page:
*********************
-r This option will enable the facility to receive
message from the network using an internet domain
socket with the syslog service (see services(5)).
The default is to not receive any messages from the
network.

This option is introduced in version 1.3 of the
sysklogd package. Please note that the default
behavior is the opposite of how older versions
behave, so you might have to turn this on.
************************

in the /etc/syslog.conf file on the sending host, add this:

Maybe you forgot to let your firewall accept incoming udp packets for port
514?

> > > in server side, I turn on the "-r" switch;

> > > But I still can not see log information in server.

> > > Any idea?

> > On the system that you want to send out it's syslog
> > messages, you will need to start syslogd with -h
> > option.

> In client side, I try syslog option "-m 0 -h" and
> "-h", neither works.

> In client side, I also try: logger -u 514 -p authpriv.info "bbb"
> then it say: connect: no such file or directory. It seems
> syslogd in client side can not use udp port 514 to send out
> message.

by Ni » Thu, 05 Sep 2002 15:37:10

I found the problem, now it works ... I should also add -r in
/etc/sysconfig/syslog.

> syslogd -r should do...

> From the man page:
> *********************
> -r This option will enable the facility to receive
> message from the network using an internet domain
> socket with the syslog service (see services(5)).
> The default is to not receive any messages from the
> network.

> This option is introduced in version 1.3 of the
> sysklogd package. Please note that the default
> behavior is the opposite of how older versions
> behave, so you might have to turn this on.
> ************************

> in the /etc/syslog.conf file on the sending host, add this:

> Maybe you forgot to let your firewall accept incoming udp packets for port
> 514?

> > > > in server side, I turn on the "-r" switch;

> > > > But I still can not see log information in server.

> > > > Any idea?

> > > On the system that you want to send out it's syslog
> > > messages, you will need to start syslogd with -h
> > > option.

> > In client side, I try syslog option "-m 0 -h" and
> > "-h", neither works.

> > In client side, I also try: logger -u 514 -p authpriv.info "bbb"
> > then it say: connect: no such file or directory. It seems
> > syslogd in client side can not use udp port 514 to send out
> > message.

Very Computer

remote log with syslogd

remote log with syslogd

remote log with syslogd

remote log with syslogd

remote log with syslogd

remote log with syslogd

remote log with syslogd

remote log with syslogd