Re: [rsyslog] omprog loses messages (?)

Dear David, Joan and Mariusz: Thank you a lot for your quick replies! My fault: thanks to your hints I quickly found that had forgotten the loop for reading from STDIN and rsyslog kept re-spawning the script: this looked as dropped messages. Had sleepless night, sorry. Thanks a lot for your time an

Re: [rsyslog] omprog loses messages (?)

On 23.03.2025 10:02, Alexey Rudenko-Desnyak via rsyslog wrote: BINARY. Binary /tmp/test.php simply adds stdin input to "out.log" line by line: === #!/usr/bin/php Wait a second. Is it your php code? It is supposed to read a single line from the input, write it to the file and then exit. So omp

Re: [rsyslog] omprog loses messages (?)

I don't know PHP much, but just to rule out a possible buffering issue with your script (either when reading from stdin, or when writing to the file), I would suggest trying with a simple bash script instead, something like this: https://github.com/rsyslog/rsyslog/blob/master/tests%2Ftestsuites%2F

Re: [rsyslog] omprog loses messages (?)

Alexey Rudenko-Desnyak wrote: Unfortunately, I was hasty in my conclusion. I see the same problem even with the latest stable version rsyslogd 8.2502.0 (aka 2025.02) and updated omprog.so. omprog still loses messages. :( How this could happen?.. do you have impstats data for the timeframe whe

Re: [rsyslog] omprog loses messages (?)

Unfortunately, I was hasty in my conclusion. I see the same problem even with the latest stable version rsyslogd 8.2502.0 (aka 2025.02) and updated omprog.so. omprog still loses messages. :( How this could happen?.. вс, 23 мар. 2025 г. в 06:38, David Lang : > Alexey Rudenko-Desnyak wrote: > > >

Re: [rsyslog] omprog loses messages (?)

Thanks a lot, David, for the quick reply! This solved the problem: === add-apt-repository ppa:adiscon/v8-stable apt update apt install rsyslog rsyslogd -v rsyslogd 8.2502.0 (aka 2025.02) === вс, 23 мар. 2025 г. в 06:38, David Lang : > Alexey Rudenko-Desnyak wrote: > > > > > VERSION. I have the l

Re: [rsyslog] omprog loses messages (?)

Alexey Rudenko-Desnyak wrote: VERSION. I have the latest version of rsyslog installed on Ubuntu: === rsyslogd -v rsyslogd 8.2112.0 (aka 2021.12) compiled with: PLATFORM: x86_64-pc-linux-gnu === that is from the end of 2021. If you cannot upgrade to a newer community version, you will have t

[rsyslog] omprog loses messages (?)

VERSION. I have the latest version of rsyslog installed on Ubuntu: === rsyslogd -v rsyslogd 8.2112.0 (aka 2021.12) compiled with: PLATFORM: x86_64-pc-linux-gnu === CONFIG. Config is minimal: === local5.info action( type="omprog" binary="/tmp/test.php" ) General configuration file contains only d

Re: [rsyslog] omprog

al working hours should be discussed with me prior to booking. From: rsyslog on behalf of Mårten Persson via rsyslog Sent: Saturday, January 11, 2025 11:03 PM To: rsyslog@lists.adiscon.com Cc: Mårten Persson Subject: Re: [rsyslog] omprog CAUTION: The Sender is

Re: [rsyslog] omprog

Sorry, forgot to mention the distro Ubuntu 24.04.1 LTS (GNU/Linux 6.8.0-51-generic x86_64) So, no selinux ass far as I know Regards /Mårten On Sat, 2025-01-11 at 11:15 +0100, Mårten Persson via rsyslog wrote: > Hello everybody, > > I updated my distro and after that omprog lacks rights...

Re: [rsyslog] omprog

nt Cheers, Mike From: rsyslog on behalf of Mårten Persson via rsyslog Sent: Saturday, January 11, 2025 9:15 PM To: rsyslog@lists.adiscon.com Cc: Mårten Persson Subject: [rsyslog] omprog CAUTION: The Sender is located Outside The Organization. Do not click links or open attach

Re: [rsyslog] omprog

You haven’t mentioned the distro but this sounds like an SELinux issue... > On 11 Jan 2025, at 12:15, Mårten Persson via rsyslog > wrote: > > Hello everybody, > > I updated my distro and after that omprog lacks rights... > The config and the scripts have been working flawlessly for a long time

[rsyslog] omprog

Hello everybody, I updated my distro and after that omprog lacks rights... The config and the scripts have been working flawlessly for a long time :-) The error message: rsyslogd: omprog: failed to execute program '/usr/local/bin/fanvil.sh': Permission denied The file with permissions: -rwxr-xr

Re: [rsyslog] omprog : error 2119

along these lines: #!/bin/sh while IFS= read -r string; do echo -n "32790 EVT22: Start PLC now!" >> "/tmp/fuse/control/logevt/alarm" done exit 0 may not be 100% correct, taken from: https://unix.stackexchange.com/questions/433066/bash-succinct-way-to-loop-over-lines-from-stdin-or-command-line

Re: [rsyslog] omprog : error 2119

Thanks for the reply, but I'm not sure I understood what I needed to do. How to keep the script active? The script only needs to write text once per event. What should I do after writing the text to the file? Regards Drasko Am 17.06.2022 um 09:11 schrieb Rainer Gerhards: your script (rsyse

Re: [rsyslog] omprog : error 2119

your script (rsysevent32790.sh) does not work properly. It needs to keep active and not terminate by itself. Instead, once started, it needs top read stdin until EOF is reached. Rsyslog warns about the unexpected abnormal termination. That was probably introduced in some version. HTH Rainer El v

Re: [rsyslog] omprog : error 2119

That's right, after the reset there is no warning on the first "Start PLC now!" but after the second ... a warning/ error 2119 appears. On the second attempt, the function write  fails with errno=EPIPE.    written = write(pChildCtx->fdPipeOut, ((char*)szMsg) + offset, len - offset);     

Re: [rsyslog] omprog : error 2119

I forgot to mention: also attach your rsyslog configuration please. On Thu, Jun 16, 2022, 19:55 Joan Sala wrote: > The warning message simply indicates that rsyslog has detected that the > program (.rsysevent32790.sh) has exited. > > The way omprog is intended to be used is as follows: it launch

Re: [rsyslog] omprog : error 2119

The warning message simply indicates that rsyslog has detected that the program (.rsysevent32790.sh) has exited. The way omprog is intended to be used is as follows: it launches the program attaching a pipe to its stdin, the program should continuously read lines (logs) from the pipe, until the pi

[rsyslog] omprog : error 2119

Hi, In the embeded system we use rsyslog 8.2010.(but the same si in 8.2204) Is it possible to prevent the cause of the following warnings?  rsyslogd: omprog: program '/tmp/.rsysevent32790.sh' (pid 29661) terminated; will be restarted [v8.2204.1 try https://www.rsyslog.com/e/2119 ] rsyslogd: a

Re: [rsyslog] omprog as non root user

Create a totally separate instance of rsyslog running as a non-root user. In this case, when the omprog application is called it executes as the same non-root user such that su is not necessary. Then simply have the root instance forward the applicable events to the standalone instance on the

[rsyslog] omprog as non root user

Hi, Our client is adamant that they do not want applications running as the root user. The rsyslogd process is not a problem because it comes as a daemon process and is packaged as part of the OS install. However, when they see the omprog program running, it's flagged as an issue. Is there a si

Re: [rsyslog] omprog script left running after rsyslog stopped

> On 2020-06-04 20:00, John Chivian via rsyslog wrote: From the documentation page... [omprog] Executes the configured program and feeds log messages to that binary via stdin. The binary is free to do whatever it wants with the supplied data. If the program terminates, it is re-started. If rsys

Re: [rsyslog] omprog script left running after rsyslog stopped

From the documentation page... [omprog] Executes the configured program and feeds log messages to that binary via stdin. The binary is free to do whatever it wants with the supplied data. If the program terminates, it is re-started. If rsyslog terminates, the program’s stdin will see EOF. The

[rsyslog] omprog script left running after rsyslog stopped

Hello, I am using omprog to send mail logs to my script: mail.* action(type="omprog" name="blacklist" binary="/usr/local/sbin/blacklist.py" template="long-iso") It works well, but I have noticed that when I stop rsyslog, the script is not terminated, but continues running. I can see the process

Re: [rsyslog] omprog only working when rsyslogd started with '-n'

> I will try to reproduce the problem using the testbench (not sure when > though, don't count on a quick response...). AFAIK the testbench always > launches rsyslog in non-daemon mode. Rainer, is there an easy way to run > the testbench in daemon mode? Not really - we would need full control over

Re: [rsyslog] omprog only working when rsyslogd started with '-n'

(when starting rsyslog in daemon > mode) Or sometimes works? > > Also I would recommend opening a github issue. (Even if it's not a bug in > rsyslog/omprog, the resolution could be useful to other users having the > same problem.) Attaching a debug log could also be useful. >

Re: [rsyslog] omprog only working when rsyslogd started with '-n'

aemon mode) Or sometimes works? Also I would recommend opening a github issue. (Even if it's not a bug in rsyslog/omprog, the resolution could be useful to other users having the same problem.) Attaching a debug log could also be useful. Regarding this: > I have tried adding 'outp

Re: [rsyslog] omprog only working when rsyslogd started with '-n'

Rainer, Thank you for the response. I agree that it sounds like a system problem, not necessarily syslogd or omprog. This is an embedded system and doesn't have any selinux. I have disabled all cgroup functionality as well. Debug logging, etc. hasn't provided any clues. Given that it is the ro

Re: [rsyslog] omprog only working when rsyslogd started with '-n'

This sounds like a problem with SELinux or a similar hardening system. HTH Rainer El lun., 13 abr. 2020 a las 4:20, Derek Dresser via rsyslog () escribió: > > Hello, > > I am troubleshooting an issue on a Yocto based distribution with sending > logs > to a python program '/usr/bin/logoutput' via

[rsyslog] omprog only working when rsyslogd started with '-n'

Hello, I am troubleshooting an issue on a Yocto based distribution with sending logs to a python program '/usr/bin/logoutput' via omprog. If rsyslogd is started by init script, or by me (as root) on the command line, I get the following errors. apr 12 21:35:02.865327 RSYSLO action 'action-1-omp

Re: [rsyslog] omprog: Using action.output as stderr for debuging

It should not wait for the program to finalize. Probably you are writing the messages to stderr without flushing. Try flushing stderr after each message. On Sat, Feb 1, 2020, 14:28 Eudald Valcàrcel via rsyslog < rsyslog@lists.adiscon.com> wrote: > Nevermind, it was waiting for the program to fina

Re: [rsyslog] omprog: Using action.output as stderr for debuging

Nevermind, it was waiting for the program to finalize in order to write all the messages to the output file. Thanks and sorry. Eudald El sáb., 1 feb. 2020 a las 14:18, Eudald Valcàrcel (< reaven.galaeind...@gmail.com>) escribió: > Hello! > I'm trying to understand why some logs are missed by my

[rsyslog] omprog: Using action.output as stderr for debuging

Hello! I'm trying to understand why some logs are missed by my plugin, and I thought that writing something from my plugin to stderr would help me. I've configured the omprog to have an output file, and my plugin writes: *sys.stderr.write("test")* for each message it receives (along with the "OK"

Re: [rsyslog] [omprog] Plugin multithreading

Hello Rainer, First of all, thanks for your answer! I've been trying something simple to understand why setting the parameter queue.workerThreadMinimumMessages leaded me to some logs not being parsed by my script. I created a flooding script to fill the syslog with lots of different messages and,

Re: [rsyslog] [omprog] Plugin multithreading

an artificial delay does not play well with the design. It spawns new workers based on how full the queue is. Have a look here and read at least the section on "Worker Thread Pools": https://www.rsyslog.com/doc/v8-stable/concepts/queues.html This guide unfortunately is not yet updated to current

Re: [rsyslog] [omprog] Plugin multithreading

How can I find out the amount of work needed? Maybe I'm approaching this wrong, but adding delays of 10 seconds in the plugin don't trigger more instances when I generate 50 consecutive random logs, resulting in an overall delay of 500 seconds for the processing of the last log. Thank you! Eudald

Re: [rsyslog] [omprog] Plugin multithreading

El jue., 9 ene. 2020 a las 1:32, Eudald Valcàrcel via rsyslog () escribió: > > hello John, > My current setup has queue.workerThreads set at 20, but whenever I check > processes or I add some testing delays it shows only one process being > executed. That indicates there is not sufficient work to

Re: [rsyslog] [omprog] Plugin multithreading

hello John, My current setup has queue.workerThreads set at 20, but whenever I check processes or I add some testing delays it shows only one process being executed. Thanks, Eudald On Thu, Jan 9, 2020, 01:24 John Chivian via rsyslog < rsyslog@lists.adiscon.com> wrote: > From the documentation..

Re: [rsyslog] [omprog] Plugin multithreading

From the documentation... "By default, the omprog action will start an instance (process) of the external program *per worker thread.* (the maximum number of worker threads can be specified with the queue.workerThreads

[rsyslog] [omprog] Plugin multithreading

Hello! I've a kind of slow python plugin being fed from rsyslog. I'm using omprog, but I'd like to be able to launch another instance of the plugin if the current one is in use. The problem is that by using sys.stdin.readline() and feeding it through omprog with a template ending in "\n" the plugin

Re: [rsyslog] omprog and transactions

> 2. It appears that it's possible to enable useTransactions without > enabling confirmMessages.  If you do that, do you still need to confirm > the COMMIT TRANSACTION message or not? No you don't. For more details, please see: https://github.com/rsyslog/rsyslog/blob/master/plugins/external/INT

Re: [rsyslog] Omprog module does not execute every time

Hello, try the following: /home/pi/telldusUpdate2.sh #!/bin/bash # read stdin while read input do echo "Script was executed" >> /var/log/telldus.log echo $input >> /var/log/telldus.log done Regards, Ansgar Am 10.10.2019 um 21:40 schrieb Rasmus Hollin via rsyslog: Hi I have a Raspberry

[rsyslog] Omprog module does not execute every time

Hi I have a Raspberry PI 3B+ with Raspbian GNU/Linux 10 (buster) on which I intend to recieve syslog messages twith a specified format and update an MySQL database based on the data sent in the logpost. So far I have been able to setup Rsyslog (v 8.1901.0-1) to filter these messages and with O

Re: [rsyslog] omprog and transactions

On 17/09/2019 00:51, David Lang wrote: be careful with mindequeuebatchsize, it adds delays which may be trivial at high log volumes, but could bite you at low traffic volumes I'm happy with (say) 500ms-1s of delay under low volumes. ___ rsyslog mail

Re: [rsyslog] omprog and transactions

Note: the last major omprog refcotring was done by https://github.com/jsiwrk - I suggest to create a github issues for the questions and mention @jsiwrk - he has agreed to take care of the module. Rainer El mar., 17 sept. 2019 a las 1:50, David Lang via rsyslog () escribió: > > On Mon, 16 Sep 201

Re: [rsyslog] omprog and transactions

be careful with mindequeuebatchsize, it adds delays which may be trivial at high log volumes, but could bite you at low traffic volumes David Lang ___ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/profess

Re: [rsyslog] omprog and transactions

On Mon, 16 Sep 2019, Brian Candler via rsyslog wrote: 1.  I have been unable to get batching to work. batching only happens under load, the worker thread goes to fetch messages from the queue and says 'give me the first messages, up to batch_size, if there is only one message in the queue at

Re: [rsyslog] omprog and transactions

On 16/09/2019 11:25, Brian Candler wrote: I found queue parameters , so I thought perhaps I could add   queue.type="LinkedList"   queue.minDequeueBatchSize="50" to my action(...) settings - but if I submit two messages i

[rsyslog] omprog and transactions

I am writing an omprog module, and I have a couple of questions about omprog with transactions: https://www.rsyslog.com/doc/v8-stable/configuration/modules/omprog.html#usetransactions I am using rsyslog 8.32.0-1ubuntu4 under Ubuntu 18.04. 1.  I have been unable to get batching to work. I don'

Re: [rsyslog] Omprog parameter evaluation issue

probably too late for this discussion, but may be helpful for others searching for the same problem: https://www.slideshare.net/rainergerhards1/external-plugins Rainer El mar., 3 sept. 2019 a las 23:49, Eudald Valcàrcel via rsyslog () escribió: > > Alright, got it. > Sorry for messing with stdin

Re: [rsyslog] Omprog parameter evaluation issue

Alright, got it. Sorry for messing with stdin and argument definitions. Thank you very much John, Eudald El mar., 3 sept. 2019 a las 16:31, John Chivian via rsyslog (< rsyslog@lists.adiscon.com>) escribió: > Your definition of "binary=" contains no command line arguments to > test.py. Therefore

Re: [rsyslog] Omprog parameter evaluation issue

Your definition of "binary=" contains no command line arguments to test.py.  Therefore your test.py, which reports the command line arguments, correctly states that there are none. Command line arguments are by definition passed on the command line, they are *not* received on stdin.  The progr

Re: [rsyslog] Omprog parameter evaluation issue

Then, based on what you say, shouldn't my script read the line: 337392BED58 name@email.extension 1567171349 sent ? I add again below the samples I'm using, but I believe my test.py should receive the line parsed by the template ( 337392BED58 name@email.extension 1567171349 sent ) and this line shou

Re: [rsyslog] Omprog parameter evaluation issue

Yes, each line of output from the template is passed as a line of input to stdin of the program. The program should read a line, process it as desired, and repeat until it receives an EOF from rsyslog. The program must exit on EOF. It might help if you think of the rsyslog template ouput as a

Re: [rsyslog] Omprog parameter evaluation issue

John, I'm trying to understand that but I don't. I create a log: logger -p mail.info -t "postfix/smtp[150]" "337392BED58: to=, relay=someaddress:25, delay=1.1, delays=0.1/0.02/0.43/0.52, dsn=2.0.0, status=sent (250 2.0.0 OK 1567163956 2si4574209wmn.22)" Which goes through my template and becomes:

Re: [rsyslog] Omprog parameter evaluation issue

The executable specified in omprog does not receive the message on the command line as arguments.  It must read stdin (repeatedly) and receives one message from rsyslog per read. See https://www.rsyslog.com/doc/v8-stable/configuration/modules/omprog.html Regards, On 8/30/19 5:22 PM, Eudald V

[rsyslog] Omprog parameter evaluation issue

Hello! Sent it before but I'm not sure if it's been posted :/ I'm trying to use omprog to send the template parsed log to a script. Unfortunately it doesn't seem to evaluate any parameter given. I've tested my template with omfile and from input: logger -p mail.info -t "postfix/smtp[150]" "337392

[rsyslog] Omprog parameter evaluation issue

Hello! I'm trying to use omprog to send the template parsed log to a script. Unfortunately it doesn't seem to evaluate any parameter given. I've tested my template with omfile and from input: logger -p mail.info -t "postfix/smtp[150]" "337392BED58: to=, relay=someaddress:25, delay=1.1, delays=0.1/

Re: [rsyslog] omprog binary file search path

it) David Lang On Tue, 28 May 2019, Daniel Granat via rsyslog wrote: Date: Tue, 28 May 2019 22:25:47 +0200 From: Daniel Granat via rsyslog To: Florian Riedl via rsyslog , daniel.gra...@op.pl Cc: Daniel Granat Subject: [rsyslog] omprog binary file search path Hi, I can see in documentation

[rsyslog] omprog binary file search path

Hi, I can see in documentation of omprog module 'binary' parameter that it must be passed full path of the external program to execute. I'd like to know if there is any possibility to use only program name which will be searched in $PATH? Best regards, Daniel Granat _

[rsyslog] omprog binary file search path

Hi, I can see in documentation of omprog module 'binary' parameter that it must be passed full path of the external program to execute. I'd like to know if there is any possibility to use only program name which will be searched in $PATH? ⁣Best regards, Daniel Granat​ _

Re: [rsyslog] omprog queue

David Lang Sent: Friday, March 25, 2016 7:04 PM To: rsyslog-users Subject: Re: [rsyslog] omprog queue On Fri, 25 Mar 2016, Elisabeth Kemper wrote: > Hi all, > > I have following question: > In my configuration I have defined: > > module(load="omprog") > ruleset(name=&q

Re: [rsyslog] omprog queue

On Fri, 25 Mar 2016, Elisabeth Kemper wrote: Hi all, I have following question: In my configuration I have defined: module(load="omprog") ruleset(name="iscsi_repair"){ action(name="iscsi_repair" type="omprog" binary="/usr/bin/iscsi-supervision-handler" template="RSYSLOG_Tr

[rsyslog] omprog queue

Hi all, I have following question: In my configuration I have defined: module(load="omprog") ruleset(name="iscsi_repair"){ action(name="iscsi_repair" type="omprog" binary="/usr/bin/iscsi-supervision-handler" template="RSYSLOG_TraditionalFileFormat") } # Rules for matching

Re: [rsyslog] omprog 'loosing' children

2015-04-22 10:20 GMT+02:00 David Lang : > On Wed, 22 Apr 2015, Rainer Gerhards wrote: > >> 2015-04-22 2:24 GMT+02:00 David Lang : >>> >>> On Tue, 21 Apr 2015, David Lang wrote: >>> I have the following in my config: action(type="omprog" name="sec-heartbeat" binary="/usr/bin/sec

Re: [rsyslog] omprog 'loosing' children

On Wed, 22 Apr 2015, Rainer Gerhards wrote: 2015-04-22 2:24 GMT+02:00 David Lang : On Tue, 21 Apr 2015, David Lang wrote: I have the following in my config: action(type="omprog" name="sec-heartbeat" binary="/usr/bin/sec --conf=/etc/sec/missing-logs --intevents --intcontexts --dump=/tmp/dumpf

Re: [rsyslog] omprog 'loosing' children

2015-04-22 2:24 GMT+02:00 David Lang : > On Tue, 21 Apr 2015, David Lang wrote: > >> I have the following in my config: >> >> action(type="omprog" name="sec-heartbeat" binary="/usr/bin/sec >> --conf=/etc/sec/missing-logs --intevents --intcontexts >> --dump=/tmp/dumpfile.missing-logs --input -" temp

Re: [rsyslog] omprog 'loosing' children

On Tue, 21 Apr 2015, David Lang wrote: I have the following in my config: action(type="omprog" name="sec-heartbeat" binary="/usr/bin/sec --conf=/etc/sec/missing-logs --intevents --intcontexts --dump=/tmp/dumpfile.missing-logs --input -" template="manual") I rotate logs via a script that doe

[rsyslog] omprog 'loosing' children

I have the following in my config: action(type="omprog" name="sec-heartbeat" binary="/usr/bin/sec --conf=/etc/sec/missing-logs --intevents --intcontexts --dump=/tmp/dumpfile.missing-logs --input -" template="manual") I rotate logs via a script that does a mv of the files and pkill -HUP rsys

Re: [rsyslog] omprog should forward signals to the binary

I didn't mange to extend the implemenation quickly enough. So today's release will see the limited set of signals, in 8.10.0 I'll change that to the full set. Just so that you know. Rainer 2015-03-31 22:11 GMT+02:00 David Lang : > On Tue, 31 Mar 2015, Rainer Gerhards wrote: > >> 2015-03-31 12:27

Re: [rsyslog] omprog should forward signals to the binary

On Tue, 31 Mar 2015, Rainer Gerhards wrote: 2015-03-31 12:27 GMT+02:00 Rainer Gerhards : 2015-03-31 1:25 GMT+02:00 David Lang : On Wed, 25 Mar 2015, Rainer Gerhards wrote: 2015-03-25 12:06 GMT+01:00 Rainer Gerhards : 2015-03-25 11:49 GMT+01:00 Rainer Gerhards : 2015-03-24 23:22 GMT+01:00

Re: [rsyslog] omprog should forward signals to the binary

2015-03-31 12:27 GMT+02:00 Rainer Gerhards : > 2015-03-31 1:25 GMT+02:00 David Lang : >> On Wed, 25 Mar 2015, Rainer Gerhards wrote: >> >>> 2015-03-25 12:06 GMT+01:00 Rainer Gerhards : 2015-03-25 11:49 GMT+01:00 Rainer Gerhards : > > 2015-03-24 23:22 GMT+01:00 David Lang : >>

Re: [rsyslog] omprog should forward signals to the binary

2015-03-31 1:25 GMT+02:00 David Lang : > On Wed, 25 Mar 2015, Rainer Gerhards wrote: > >> 2015-03-25 12:06 GMT+01:00 Rainer Gerhards : >>> >>> 2015-03-25 11:49 GMT+01:00 Rainer Gerhards : 2015-03-24 23:22 GMT+01:00 David Lang : > > when rsyslog gets hupped (closing it's outputs),

Re: [rsyslog] omprog should forward signals to the binary

On Wed, 25 Mar 2015, Rainer Gerhards wrote: 2015-03-25 12:06 GMT+01:00 Rainer Gerhards : 2015-03-25 11:49 GMT+01:00 Rainer Gerhards : 2015-03-24 23:22 GMT+01:00 David Lang : when rsyslog gets hupped (closing it's outputs), omprog currently does nothing, so programs that it's running keep writ

Re: [rsyslog] omprog should forward signals to the binary

2015-03-25 12:06 GMT+01:00 Rainer Gerhards : > 2015-03-25 11:49 GMT+01:00 Rainer Gerhards : >> 2015-03-24 23:22 GMT+01:00 David Lang : >>> when rsyslog gets hupped (closing it's outputs), omprog currently does >>> nothing, so programs that it's running keep writing to anything they have >>> open. >

Re: [rsyslog] omprog should forward signals to the binary

2015-03-25 11:49 GMT+01:00 Rainer Gerhards : > 2015-03-24 23:22 GMT+01:00 David Lang : >> when rsyslog gets hupped (closing it's outputs), omprog currently does >> nothing, so programs that it's running keep writing to anything they have >> open. >> >> there should be an option so that when rsyslog

Re: [rsyslog] omprog should forward signals to the binary

2015-03-24 23:22 GMT+01:00 David Lang : > when rsyslog gets hupped (closing it's outputs), omprog currently does > nothing, so programs that it's running keep writing to anything they have > open. > > there should be an option so that when rsyslog is sent a hup, it sends a hup > to the binaries it'

[rsyslog] omprog should forward signals to the binary

when rsyslog gets hupped (closing it's outputs), omprog currently does nothing, so programs that it's running keep writing to anything they have open. there should be an option so that when rsyslog is sent a hup, it sends a hup to the binaries it's managing via omprog. It may also be worth ha

Re: [rsyslog] OMPROG Problem

On Wed, Jun 18, 2014 at 2:09 PM, masoom alam wrote: > omprog module is not working for us. > > we are adding the following code in our rsyslog.conf > > module(load="omprog") > if $rawmsg contains "something" then action(type="omprog" > binary="/opt/test.sh") > > > test.sh contains simple echo mes

[rsyslog] OMPROG Problem

omprog module is not working for us. we are adding the following code in our rsyslog.conf module(load="omprog") if $rawmsg contains "something" then action(type="omprog" binary="/opt/test.sh") test.sh contains simple echo message. Regards ___ rsyslo

Re: [rsyslog] omprog now on v7

> -Original Message- > From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog- > boun...@lists.adiscon.com] On Behalf Of Rainer Gerhards > Sent: Thursday, June 27, 2013 9:01 AM > To: rsyslog-users > Subject: Re: [rsyslog] omprog now on v7 > > On Thu, Jun 27, 201

Re: [rsyslog] omprog now on v7

On Thu, Jun 27, 2013 at 9:01 AM, Orangepeel Beef wrote: > I'm running > rsyslogd 7.4.1, compiled with: > FEATURE_REGEXP: Yes > FEATURE_LARGEFILE: No > GSSAPI Kerberos 5 support: Yes > FEATURE_DEBUG (debug build, slow code): No > 32bit Atomic operations supported: Yes > 64bit Atomic operations supp

Re: [rsyslog] omprog now on v7

I'm running rsyslogd 7.4.1, compiled with: FEATURE_REGEXP: Yes FEATURE_LARGEFILE: No GSSAPI Kerberos 5 support: Yes FEATURE_DEBUG (debug build, slow code): No 32bit Atomic operations supported: Yes 64bit Atomic operations supported: Yes Runtime Instrumentation (slow code): No uuid support: Yes fro

Re: [rsyslog] omprog now on v7

On Thu, Jun 27, 2013 at 8:55 AM, Orangepeel Beef wrote: > That seems to have done the trick. Is the version that allows parameters > in the devel ubuntu package yet? > > I think Andre has not yet re-build the packages, but should happen today. Watch ML for annoucement. Rainer > > On Wed, Jun 26

Re: [rsyslog] omprog now on v7

per the page mentioned below http://www.rsyslog.com/doc/omprog.html the new style format should work action(type="omprog" binary="/pathto/omprog.py --parm1=\"value 1\" --parm2=value2" template="RSYSLOG_TraditionalFileFormat") David Lang On Wed, 26 Jun 2013, Orangepeel

Re: [rsyslog] omprog now on v7

That seems to have done the trick. Is the version that allows parameters in the devel ubuntu package yet? On Wed, Jun 26, 2013 at 10:23 PM, Rainer Gerhards wrote: > On Thu, Jun 27, 2013 at 5:23 AM, Orangepeel Beef > wrote: > > > So I got rsyslogv7 installed finally and working, the re_match fil

Re: [rsyslog] omprog now on v7

On Thu, Jun 27, 2013 at 5:23 AM, Orangepeel Beef wrote: > So I got rsyslogv7 installed finally and working, the re_match filters are > working, but it does not seem that the omprog script ever actually executes > even though it receives a child pid, it immediately dies. No output ever > makes it t

[rsyslog] omprog now on v7

So I got rsyslogv7 installed finally and working, the re_match filters are working, but it does not seem that the omprog script ever actually executes even though it receives a child pid, it immediately dies. No output ever makes it to logs. I even tried a script that just echo'd text to a file in

Re: [rsyslog] omprog module problem on ubuntu

Hello David, I'm on Ubuntu 12.04 x86_64, with rsyslog 5.8.6. The following works: # cat /etc/rsyslog.conf $ModLoad imuxsock # provides support for local system logging $ModLoad imklog # provides kernel logging support (previously done by rklogd)i $ModLoad omprog $actionomprogbinary /local/logte

Re: [rsyslog] omprog module problem on ubuntu

I did everything like you said but It still doesn't work, maybe my rule is not good *.* :omprog:;RSYSLOG_TraditionalFileFormat I really want to make it work, to say the truth, what I need is rsyslog to post the log to a URL, I want to consume the logs using a http webserver, can this be done, any

Re: [rsyslog] omprog module problem on ubuntu

Hello and welcome :) Try replacing the first line of the script: #/bin/bash with a proper shebang (http://en.wikipedia.org/wiki/Shebang_%28Unix%29): #!/bin/bash Then make sure it's executable: chmod +x /opt/logtest.sh And then put only the script there, as I'm not sure omprog supports parame

[rsyslog] omprog module problem on ubuntu

I am not an Linux expert, I want to have rsyslog report to a bash script I consoled the website of rsyslog and here is my /etc/rsyslog.conf and the bash script http://pastebin.com/69D8kfVw, I can't get this to work, the test.out file is not getting written, I feel like this is a permissions issue o

Re: [rsyslog] OMPROG data not being received

> -Original Message- > From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog- > boun...@lists.adiscon.com] On Behalf Of da...@lang.hm > Sent: Thursday, February 10, 2011 6:14 PM > To: rsyslog-users > Subject: Re: [rsyslog] OMPROG data not being received > >

Re: [rsyslog] OMPROG data not being received

Sent: Thursday, February 10, 2011 4:51 PM To: rsyslog-users Subject: Re: [rsyslog] OMPROG data not being received Hi, Thanks that is fixed, by adding "\n" to the end of my template it now flushes to the script straight away. Thanks Mark On 10 February 2011 15:27, Mark Olliver wrote: I

Re: [rsyslog] OMPROG data not being received

> -Original Message- > From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog- > boun...@lists.adiscon.com] On Behalf Of Mark Olliver > Sent: Thursday, February 10, 2011 4:51 PM > To: rsyslog-users > Subject: Re: [rsyslog] OMPROG data not being received > > Hi, >

Re: [rsyslog] OMPROG data not being received

Hi, Thanks that is fixed, by adding "\n" to the end of my template it now flushes to the script straight away. Thanks Mark On 10 February 2011 15:27, Mark Olliver wrote: > I think my script is actually waiting on an end of file rather than > end of line terminator, > > If that makes a differen

Re: [rsyslog] OMPROG data not being received

I think my script is actually waiting on an end of file rather than end of line terminator, If that makes a difference ? Mark ___ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com

Re: [rsyslog] OMPROG data not being received

level = "OK" alert( level, phone, message ) end end while !ARGF.eof? join_message( argv, ARGF.readline) end On 10 February 2011 14:49, Rainer Gerhards wrote: > ahhh... I see the message. Does your application wait for a NL character? I > am asking, because you

Re: [rsyslog] OMPROG data not being received

February 10, 2011 3:49 PM > To: rsyslog-users > Subject: Re: [rsyslog] OMPROG data not being received > > thanks for the log. But please have a look at it: search for omprog. > You'll > see that the data is written to the pipe. I have no idea why the OS > doesn't

  1   2   >