On 09/24/2013 09:22 AM, Alberto Cortón wrote: > Hi, > > I have found the same behaviour when I use lots of both configuration > and input files, the SIGUSR1 signal seems to be ignored (I'm not > starting sec from rsyslog but from the shell) > > Regards,
hi Alberto, this problem is probably related to the new signal handling model of Perl, as described in the mailing list post from the end of 2012: http://sourceforge.net/mailarchive/forum.php?thread_name=201212032345.qB3NjcZI025233%40mx1.cs.umb.edu&forum_name=simple-evcorr-users John pointed out this problem, and during testing I found that signals might indeed get accidentally lost. That can happen to SIGINT if you send several of them from one command line, in order to increase logging verbosity by more than one level. However, the rsyslog scenario is much different, since in this gets nothing whatsoever gets delivered (apart from the KILL signal which takes down the process). kind regards, risto > > El 24/09/13 01:22, David Lang escribió: >> On Thu, 19 Sep 2013, David Lang wrote: >> >>> On Thu, 19 Sep 2013, Risto Vaarandi wrote: >>> >>>> On 09/19/2013 06:16 AM, David Lang wrote: >>>>> I've started running SEC from rsyslog via omprog and it's running, but >>>>> when it >>>>> tries to write the dumpfile, nothing happens. >>>>> >>>>> I did a cut-n-paste of the command line (as shown in ps) and ran it from >>>>> the >>>>> command line and from there it does create the dump file. the dump files >>>>> are set >>>>> to be written to /var/tmp >>>>> >>>>> I don't know if the problem is with rsyslog, SEC, or RHEL 6.x >>>>> >>>>> so I figured I'd crosspost to both lists to see if anyone had an idea :-) >>>>> >>>>> David Lang >>>> Does the dumpfile already exist in /var/tmp? If so, it is not overwritten >>>> for security reasons. Also, for troubleshooting I'd recommend to use the >>>> --log=<logfile> option, in order to get a log message about why writing was >>>> unsuccessful. >>> no, the dumpfiles do not already exist. I'll enable logfile and do more >>> checking, thanks. >> enabling the log file shows ongoing activity, but it does not show anything >> when >> the USR1 is sent to the pid. >> >> David Lang >> >> ------------------------------------------------------------------------------ >> October Webinars: Code for Performance >> Free Intel webinars can help you accelerate application performance. >> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from >> the latest Intel processors and coprocessors. See abstracts and register > >> http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk >> _______________________________________________ >> Simple-evcorr-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users >> > ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ Simple-evcorr-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users
