Hi,
I configured all my servers with to send all to a central server with
"*.* @192.168.0.10:2514" which works great.
For some test and proof-of-concepts, i'd like to have the syslog
messages also to a second logserver. However, adding "*.*
@192.168.0.22:514" on the central server 192.168.0
ion server to "unpack".
Unless of course your destination solution is some another system
which can't do this "unpacking".
On 01.04.2021 15:29, rsyslog--- via rsyslog wrote:
Hi,
I configured all my servers with to send all to a central server
with "*.* @1
We are getting an error when starting/restarting rsyslog on RHEL 7 "rsyslogd:
error starting up disk queue, using pure in-memory mode [v8.24.0-57.el7_9.3 try
http://www.rsyslog.com/e/2026 ]"
The system has the same config as another that is not getting the error and we
have disabled SELINUX, re
Hi there,
we've issued a TLS certificate from our internal standalone PKI and
configured it and the corresponding certificate chain to use syslog-TLS
with rsyslog.
Everything works fine so far. We receiving TLS encrypted syslog from
devices which are capable to send via encrypted syslog.
N
I am in the preliminary stages of creating a failover rsyslog.conf for all our
Redhat 6 and 7 clients (default rsyslogd 5.8.10 and 8.24.0), using this page
(and others) as a starting point, but I am unable to get the failover to work
on either version.
https://www.rsyslog.com/doc/master/tutorial
Given the below, I would like to put something in there it guard against
blocking if the disk queue fills up in the event of an extended outage where
the remote server can not be reached. Or if writing to disk is not working for
some reason.
I saw a suggestion to use $ActionQueueTimeoutEnqueue
Anyone have any insight on this? Maybe some things to look at? This
setup does not fail to the other server.
On Sun, May 20, 2018, at 12:40 PM, rsyslog--- via rsyslog wrote:
> I am in the preliminary stages of creating a failover rsyslog.conf for> all
> our Redhat 6 and 7 clients
; On Fri, May 25, 2018 at 1:35 PM, rsyslog--- via rsyslog
> wrote:
> > Anyone have any insight on this? Maybe some things to look at? This
> > setup does not fail to the other server.
> >
> > On Sun, May 20, 2018, at 12:40 PM, rsyslog--- via rsyslog wrote:
> >> I
I have the following setup that I want to use (on RH 6 and 7)to stop the
system from slowing and/or hitting performance issues if:
1. Remote TCP logs server is down or not present for a extended time
2. The disk queue happens to fill up and can no longer write to disk for some
reason ( $ActionQu
By the way, these are client systems.
On Tue, May 29, 2018, at 3:34 PM, rsyslog--- via rsyslog wrote:
> I have the following setup that I want to use (on RH 6 and 7)to stop
> the system from slowing and/or hitting performance issues if:
> 1. Remote TCP logs server is down or not pres
very
> confusing to understand.
>
> The current documentation should list the default values (the watermark
> functionality is disabled by default)
>
> David Lang
>
> On Tue, 29 May 2018, rsyslog--- via rsyslog wrote:
>
> > Date: Tue, 29 May 2018 15:34:54 -0600
I'm on the latest rsyslog in RHEL 7 (8.24.0-34.el7) with the following client
config that sends to a commercial syslog server:
Rsyslog.conf:
$ModLoad imuxsock
$ModLoad imjournal
$WorkDirectory /var/lib/rsyslog
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
$IncludeConfig /etc/rsyslog.
t; but I never
> use the old style syntax and cant say what the effects of that might be.
>
> Regards,
>
>
> On 4/5/19 11:13 AM, rsyslog--- via rsyslog wrote:
> > I'm on the latest rsyslog in RHEL 7 (8.24.0-34.el7) with the following
> > clien
ead and
> configure a
> ruleset for the imfile input and give it a queue (so that the input is
> not
> involving the main queue)
>
> David Lang
>
>
>
> > Regards,
> >
> >
> >
> > On 4/5/19 11:42 AM, rsyslog--- via rsyslog wrote:
> &g
:52 PM, Rainer Gerhards wrote:
> As I said:
> I guess it's useless to try to fix it with that version.
>
> Rainer
>
> Sent from phone, thus brief.
>
> rsyslog--- via rsyslog schrieb am Mi., 10.
> Apr. 2019, 20:38:
> > Update on this. Since we cha
uot;local4"
>ruleset="from_weblog")
>
>
> ruleset(name="from_weblog") {
>
>if ($msg contains ["ignore_this","ignore_that"]) then stop
>
> action(
> type="omfwd"
> name="send_to_remote"
&g
Hello,
When using TCP redirects (@@), is it possible to configure multiple
servers but only send to one only? (If that one fails, then try another
one from the list.)
How would I do this?
Thanks,
Marki
___
rsyslog mailing list
http://lists.adiscon.
Hello,
There are:
1) "Enter confirmation cookie" page issues
2) "Private Archives Authentication" not working either
I suspect that's because both pages are an https URL but the form
submission/action is http.
Probably there is a redirect in the background (http->https) that breaks
the trans
I have *rootsh* logging to syslog/rsyslog and I am seeing xterm/terminal
color codes in the logs. My rsyslog configuration has:
$EscapeControlCharactersOnReceive off
I have a template which applies *controlcharacters="drop"* to the /msg/
property.
This takes care of many control characters but
19 matches
Mail list logo
