Bug 998117
| Summary: | Queue seems no longer work | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Harald Reindl <h.reindl> |
| Component: | rsyslog | Assignee: | Tomas Heinrich <theinric> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 18 | CC: | h.reindl, lkundrak, mah.darade, pvrabec, theinric |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-02-05 22:17:50 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
you can see that also here - Modify/Change from the day of F18 upgrade forget "Access" -> noatime mounted [root@arrakis:~]$ stat /var/spool/rsyslog/ File: '/var/spool/rsyslog/' Size: 4096 Blocks: 8 IO Block: 4096 directory Device: 841h/2113d Inode: 15 Links: 2 Access: (1777/drwxrwxrwt) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2009-07-15 02:18:33.301000652 +0200 Modify: 2013-08-03 14:17:01.190949426 +0200 Change: 2013-08-03 14:17:01.190949426 +0200 As a workaround, would it be possible to run rsyslog on the host with mysql, log to the db locally and use relp[1] as the transport mechanism? [1] http://www.rsyslog.com/doc/imrelp.html not really - we speak about more than 20 machines and syslog for mail and other events are going to different hosts as well as on webservers and do not like rsyslog open any network socket itself even from localhost This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Could you retest and potentially switch to f19+? the first line of my bugreport was "this affects also F19" i am using that rsyslog configuration on any machine and as you can see all of them touched /var/spool/rsyslog/ the last time on 2013-08-03, the same on my test-vm with F20 _________________________________________________________________ [root@srv-rhsoft:~]$ stat /var/spool/rsyslog/ File: '/var/spool/rsyslog/' Size: 4096 Blocks: 8 IO Block: 4096 directory Device: 901h/2305d Inode: 1439084 Links: 2 Access: (1777/drwxrwxrwt) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2011-06-20 18:12:04.402595429 +0200 Modify: 2013-08-03 11:08:12.513851097 +0200 Change: 2013-08-03 11:08:12.513851097 +0200 Birth: - [root@srv-rhsoft:~]$ cat /etc/redhat-release Fedora release 19 (Schrödinger’s Cat) _________________________________________________________________ [root@testserver:~]$ stat /var/spool/rsyslog/ File: '/var/spool/rsyslog/' Size: 4096 Blocks: 8 IO Block: 4096 directory Device: 811h/2065d Inode: 254557 Links: 2 Access: (1777/drwxrwxrwt) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2009-12-30 23:19:32.000000000 +0100 Modify: 2013-08-03 12:34:17.886226197 +0200 Change: 2013-08-03 12:34:17.886226197 +0200 Birth: - [root@testserver:~]$ cat /etc/redhat-release Fedora release 20 (Heisenbug) BTW: https://bugzilla.redhat.com/show_bug.cgi?id=812617 in case of rsyslog-mysql still is a problem and "TimeoutSec=2" prevents from going crazy in case of production servers hanging around at reboot while the same systemd-unit with "TimeoutSec=2" on machine snot using rsyslog-mysql not ends in "entered failed state" due "systemctl restart rsyslog.service" (In reply to Harald Reindl from comment #6) > the first line of my bugreport was "this affects also F19" There was no package version specified. Could you get 'rpm -q rsyslog systemd' ? > i am using that rsyslog configuration on any machine and as > you can see all of them touched /var/spool/rsyslog/ the > last time on 2013-08-03, the same on my test-vm with F20 There isn't supposed to be a '/var/spool/rsyslog/' on recent f19, f20, rawhide. The current workdir in the updated config file is /var/lib/rsyslog. I understand that you have a custom config, but is the selinux policy aligned as well? There's a huge difference between the old v5 and the new v7 packages. The switch happend in the f18/f19 timeframe, so could you make sure you have the current packages and an updated configuration? you can in my case assume always the latest one available, selinux is *not* enabled here because there are too many customzied service-layouts for all sort of network services for old / deprecated settings there are usually always warnings due start of rsyslogd, hence i have no idea why this does not work any longer reliable Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
this affects also F19 i can't say for sure when this started, but with the configuration below if i do not specify "After=network.service" early boot messages forwarded by journald are completly missing in the database hence this way any messages get lost if the remote server is rebootet and the whole mysql logging becomes unrelieable rsyslog of F17 did work as expected - short ago we upgraded from F17 to F18 on production servers and from this moment it was pretty clear that most informations around boot are lost compared to the last F17 reboot ____________________ template(name="stdSQLformat" type="string" option.sql="on" string="insert into SystemEvents (DeviceReportedTime, FromHost, Message, SysLogTag) values ('%timereported:::date-mysql%', '%HOSTNAME%', '%msg%', '%syslogtag%')" ) $WorkDirectory /var/spool/rsyslog # default location for work (spool) files $ActionQueueType LinkedList # use asynchronous processing $ActionQueueFileName dbq # set file name, also enables disk mode $ActionResumeRetryCount -1 # infinite retries on insert failure *.info;mail.none;authpriv.none;cron.none action(type="ommysql" server="192.168.196.1" serverport="3306" db="****" uid="****" pwd="****" template="stdSQLformat") mail.* action(type="ommysql" server="192.168.196.1" serverport="3307" db="****" uid="****" pwd="****" template="stdSQLformat")