I think you are starting rsyslog w/ debugging in a way that isn't helping...
3769.538616155:7f8cf40f2740: exiting on signal 15
3769.538627625:7f8cf40f2740: Terminating input threads...
3769.538641082:7f8cf40f2740: request term via SIGTTIN for input thread
'imuxsock' 0xf1fed700
— Macro: int SIGTTIN
A process cannot read from the user's terminal while it is running as a
background job. When any process in a background job tries to read from the
terminal, all of the processes in the job are sent a SIGTTIN signal. The
default action for this signal is to stop the process. For more information
about how this interacts with the terminal driver, see Access to the
Terminal.
--
So there is still a chance I've read the debug output wrong but I suspect you
are using the service script to start rsyslog after adding debug flags
I personally do this to debug config errors:
rsyslogd -f /etc/rsyslog.conf -dn | tee /var/log/rsyslog.debug
if i'm debugging a crash I can typlically just scroll up a page and see what
broke, but having the log file is handy too.
This will run in the foreground until you stop it or it dies
Chip
On Tue, Dec 03, 2013 at 02:19:30PM -0600, Trent Creekmore wrote:
Well I did add something, if that could be contributing to the problem.
Other than that I have done nothing else.
Thank you
This one : : /etc/logrotate.d/asterisl containing:
------------------------------------------
/var/log/asterisk/messages /var/log/asterisk/*log /var/log/asterisk/full {
missingok
notifempty
sharedscripts
create 0640 asterisk asterisk
postrotate
/usr/sbin/asterisk -rx 'logger reload' > /dev/null 2> /dev/null
endscript
}
------------------------------------------
And this one : /etc/logrotate.d/freepbx containing:
------------------------------------------
/var/log/asterisk/freepbx_dbug /var/log/asterisk/freepbx_debug {
missingok
notifempty
sharedscripts
create 0640 asterisk asterisk
postrotate
/usr/sbin/asterisk -rx 'logger reload' > /dev/null 2> /dev/null
endscript
}
------------------------------------------
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Rainer Gerhards
Sent: Tuesday, December 03, 2013 1:57 PM
To: rsyslog-users
Subject: Re: [rsyslog] "exiting on signal 15"
Well, in essence rsyslog is told to terminate and so it does. Maybe a script
sending sigkill?
Sent from phone, thus brief.
Am 03.12.2013 19:59 schrieb "Trent Creekmore" <[email protected]>:
This on CentOS 64 using the provided repo which as version 5.8.10 and
on the rsyslog repo using version 7.4.6.
SELinux is not enabled and no modifications to the configuration file
has been done.
Not sure why this is happening.
I have put the debug output to pastebin using version 7.4.6:
http://pastebin.com/psnau6sY
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE
WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you
DON'T LIKE THAT.
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This
is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our
control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
--
------
**** Warning ****
This e-mail message, without warrant or warning, and despite US law as set
forth in the Foreign Intelligence Surveillance Act of 1978, may be subject
to monitoring by the United States National Security Agency and/or the
Department of Defense. Information contained in this message may be used
against any senders or recipients, now or in the future, in a public trial
or secret tribunal.
Please encrypt anything important.
PGP Key: http://wwwkeys.pgp.net:11371/pks/lookup?op=get&search=0x6CFA486D
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
