loosing Messages via Modem (GPRS/UMTS) connection
Hi, I try to log to a remote Syslog Server via: destination logserver { tcp("log.mydomain.xyz" port(514) flush_lines(1) flush_timeout(10) keep-alive(yes) ); }; if I have a long period between the messages (e.g. 10 Minutes) the messsage is still logged to the local machine ( I write a second log to a local file) but no message reaches the server. all new messages are lost. if I restart the syslog deamon ill get messages again (but only new ones) I use Suse Linux 10.1 with syslog-ng (2.x) (client) I also compiled and tried 3.0.1 but git the same effect. any idea ? regards Jens-Peter C. Hillers
On Thu, 2009-03-12 at 00:32 +0100, Jens-Peter C. Hillers wrote:
Hi,
I try to log to a remote Syslog Server via:
destination logserver { tcp("log.mydomain.xyz" port(514) flush_lines(1) flush_timeout(10) keep-alive(yes) ); };
if I have a long period between the messages (e.g. 10 Minutes) the messsage is still logged to the local machine ( I write a second log to a local file) but no message reaches the server. all new messages are lost.
if I restart the syslog deamon ill get messages again (but only new ones)
I use Suse Linux 10.1 with syslog-ng (2.x) (client)
I also compiled and tried 3.0.1 but git the same effect.
any idea ?
did you enable flow control towards the TCP destination? what aboud dropped counters? it might be syslog-ng itself that drops messages, but there's always a reason why it does it. I don't see why it would be related to idle times, syslog-ng tries to keep the TCP connection alive at all times. -- Bazsi
Balazs Scheidler schrieb:
On Thu, 2009-03-12 at 00:32 +0100, Jens-Peter C. Hillers wrote:
Hi,
I try to log to a remote Syslog Server via:
destination logserver { tcp("log.mydomain.xyz" port(514) flush_lines(1) flush_timeout(10) keep-alive(yes) ); };
if I have a long period between the messages (e.g. 10 Minutes) the messsage is still logged to the local machine ( I write a second log to a local file) but no message reaches the server. all new messages are lost.
if I restart the syslog deamon ill get messages again (but only new ones)
I use Suse Linux 10.1 with syslog-ng (2.x) (client)
I also compiled and tried 3.0.1 but git the same effect.
any idea ?
did you enable flow control towards the TCP destination?
Hi, thanks I expected something at the destination to set flow control so I reread the Manual an come back with the results. regards jph
what aboud dropped counters? it might be syslog-ng itself that drops messages, but there's always a reason why it does it.
I don't see why it would be related to idle times, syslog-ng tries to keep the TCP connection alive at all times.
-- Mit freundlichen Grüßen Jens-Peter C. Hillers Sen. Developer ______________________________ *vendingControl* Telemedia GmbH & Co. KG Ernst-Litfaß-Str. 8 19246 Zarrentin / Germany tel +49 (0) 38851-326-18 fax +49 (0) 38851-326-15 hillers@vendingcontrol.de <mailto:hillers@vendingcontrol.de> www.vendingcontrol.de <http://www.vendingcontrol.de> AG Schwerin, HRA 2805, Geschäftsführer Frank Oliver Becker Komplementär: vendingcontrol Verwaltungsgesellschaft mbH Ernst-Litfaß-Str. 8, 19246 Zarrentin, AG Schwerin, HRB 9662 Geschäftsführer Frank Oliver Becker
participants (2)
-
Balazs Scheidler
-
Jens-Peter C. Hillers