On 01/18/2014 04:30 AM, Rainer Gerhards wrote:
On Sat, Jan 18, 2014 at 12:44 AM, Assaf Gordon wrote:
Client side:
--
module(load="imuxsock" SysSock.Use="off")
module(load="omrelp")
input(type="imuxsock" Socket="/tmp/client.sock" CreatePath="on")
action(type="omrelp" target="1.2.3.4" port="2051
On Sat, Jan 18, 2014 at 12:44 AM, Assaf Gordon wrote:
> Hello David,
>
>
> On 01/17/2014 06:15 PM, David Lang wrote:
>
>> On Fri, 17 Jan 2014, Assaf Gordon wrote:
>>
>> BUT,
>>> If I understood the idea behind "RELP" correctly, the client-side
>>> "rsyslogd" should know and detect that those mes
Hello David,
On 01/17/2014 06:15 PM, David Lang wrote:
On Fri, 17 Jan 2014, Assaf Gordon wrote:
BUT,
If I understood the idea behind "RELP" correctly, the client-side
"rsyslogd" should know and detect that those messages were not ACK'd,
hence not delivered.
your understanding matches mine th
On Fri, 17 Jan 2014, Assaf Gordon wrote:
David,
Thank you for the detailed explanation. I think I'm in a simpler situation,
which does not require the additional protection you've listed.
On 01/17/2014 05:48 PM, David Lang wrote:
On Fri, 17 Jan 2014, Assaf Gordon wrote:
now, with all of th
David,
Thank you for the detailed explanation. I think I'm in a simpler
situation, which does not require the additional protection you've listed.
On 01/17/2014 05:48 PM, David Lang wrote:
On Fri, 17 Jan 2014, Assaf Gordon wrote:
now, with all of this said, let's get back to your situation a
On Fri, 17 Jan 2014, Assaf Gordon wrote:
Hello,
On 01/17/2014 04:35 PM, David Lang wrote:
RELP will prevent logs from being lost in transit, but if the log
arrived on the server, but was in the queue when rsyslog was killed, and
rsyslog didn't have time to write it out, you can still loose thi
On 01/17/2014 04:57 PM, Radu Gheorghe wrote:
I think the most probable cause is that the lost messages were in the
in-memory queue, which got wiped during restart. To fix that, you'd have to
make it disk-assisted and set queue.saveonshutdown to yes. I think you'll
find the details in those two li
Hello,
On 01/17/2014 04:35 PM, David Lang wrote:
RELP will prevent logs from being lost in transit, but if the log
arrived on the server, but was in the queue when rsyslog was killed, and
rsyslog didn't have time to write it out, you can still loose things.
how did you kill the rsyslog receiver
I think the most probable cause is that the lost messages were in the
in-memory queue, which got wiped during restart. To fix that, you'd have to
make it disk-assisted and set queue.saveonshutdown to yes. I think you'll
find the details in those two links:
http://www.rsyslog.com/doc/queues.html
ht
RELP will prevent logs from being lost in transit, but if the log arrived on the
server, but was in the queue when rsyslog was killed, and rsyslog didn't have
time to write it out, you can still loose things.
how did you kill the rsyslog receiver?
what does your config look like? (how much stu
Hello,
I've setup rsyslogd (version 7.5.8) with RELP and TLS on two machines
(one server, one client).
For testing purposes, I've sent repeated messages from the client to the
server, but killed and restarted the server during those messages.
The result is that I've lost some messages, despi
11 matches
Mail list logo
