This bug was fixed in the package rsyslog - 7.4.4-1ubuntu2.7
---
rsyslog (7.4.4-1ubuntu2.7) trusty; urgency=medium
* d/p/bugfix-plug-a-memleak-in-imuxsock.patch: Applied upstream patches
fixing abnormal timestamps in rsyslog when using cron. (LP: #1429427)
- Patch 1/2 : [7a2
I tested -proposed pkg and this symptom is fixed with it.
ii rsyslog 7.4.4-1ubuntu2.7 amd64..
Thanks.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Hello sgofferj, or anyone else affected,
Accepted rsyslog into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/rsyslog/7.4.4-1ubuntu2.7 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
Unsubscribing ~ubuntu-sponsors as there appears nothing left to sponsor.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429427
Title:
Unexplainable time jumps in CRON
To manage notifications about
[STS SPONSOR]
Thanks Seyeong for the quick patch rework to include the second upstream
commit.
The trusty debdiff has been uploaded in the Trusty upload queue, now
waiting for SRU verification team approval in order to start building in
trusty-proposed.
https://launchpad.net/ubuntu/trusty/+queue
right,
In my test, only 7a2e247 commit fixes this symptom.
but
I think be45099 is worth SRUing with 7a2e247 as commit's description
5a11a1d is quite far
uploaded debdiff for two patches.
Thanks
** Patch added: "lp1429427_trusty2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bu
[ STS SPONSOR REVIEW ]
@Seyeong,
According to your dediff you are only cherry-picking "7a2e247 bugfix:
plug a memleak in imuxsock".
This commit has been introduced upstream starting with
"v7.6.3-158-g7a2e247", thus it seems like this bug is only affecting
Trusty as you previously mentioned.
Acc
** Also affects: rsyslog (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: rsyslog (Ubuntu Trusty)
Assignee: (unassigned) => Seyeong Kim (xtrusia)
** Changed in: rsyslog (Ubuntu Trusty)
Importance: Undecided => Medium
** Tags added: sts-sru-needed
--
You receiv
** Patch added: "lp1429427_trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1429427/+attachment/4916080/+files/lp1429427_trusty.debdiff
** Description changed:
[Impact]
on Trusty
logging to syslog via cron causes timestamp abnormals after several
hours.
** Description changed:
+ [Impact]
+
+ on Trusty
+
+ logging to syslog via cron causes timestamp abnormals after several
+ hours.
+
+ [Test Case]
+
+ 1. run below first,
+ while true ; do logger "hello syslog" ; sleep 1; done
+
+ 2. register below script to crontab
+ for i in {1..100} ; do lo
I can confirm this bug still exists on ubuntu 14.04.4
It only seems to happen to CRON entries although the github bugreport
referenced in #14 confirms the problem is with rsyslog.
Supposedly setting '$RepeatedMsgReduction off' in /etc/rsyslog.conf should work
around this problem.
--
You receive
I've had some of the same time jumps in CRON's syslog entries, but where
I really noticed it was during roughly the same time-frame in my apache2
logs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/142
I found a matching bugreport on the rsyslog issuetracker at github. The
report is about ubuntu 14.04.1 too.
https://github.com/rsyslog/rsyslog/issues/315
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
I'm seeing the same behavior out of rsyslogd. It shows up most
frequently with CRON runs, but I've seen it on kernel syslog entries as
well.
I'm shipping my logs into ELK, and I was noticing that old indices kept
getting updated. When I dug into the issue, I saw that this was
happening on a rela
I don't get to anything meaningful before the weekend. Gosh, it's at
least 10 years since I last straced anything - have to read up on that
too.
Jup, I'm using rsyslog. I'll keep an eye on xconsole stuff but IIRC I
disabled that in rsyslogd.conf.
--
You received this bug notification because you
Hi Stefan,
yup yup, same here, only showing for cron related entries in syslog.
Also somewhat busy due to a noisy sogo/postfix/openchange/dovecot plus
all sorts of extra add-ons. Not nearly as noisy as a firewall logging of
course ;-)
Can you strace your cron pid for a bit, including forks and ho
Hi,
did you notice that I wrote that the time jumps ONLY affect CRON
entries? No other message shows them, even not the firewall log which
receives logs from a Cisco ASA in debug logging mode, so there's A LOT
of logs coming in on that channel.
-Stefan
--
You received this bug notification beca
root@mail1:~# apt-cache policy rsyslog
rsyslog:
Installed: 7.4.4-1ubuntu2.5
Candidate: 7.4.4-1ubuntu2.6
Version table:
7.4.4-1ubuntu2.6 0
990 http://nl.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
*** 7.4.4-1ubuntu2.5 0
100 /var/lib/dpkg/status
7.4
Gave it another 10 mins, this time checking the 'receiving' end, being
rsyslog in my case:
[pid 583] <... select resumed> ) = 1 (in [0])
[pid 583] recvmsg(0, {msg_name(0)=NULL, msg_iov(1)=[{"<86>Jun 9 10:01:01
CRON[4860]: pam_unix(cron:session): session opened for user sogo by (uid=0)",
I'm convinced this is more rsyslog related and not cron.
** Package changed: cron (Ubuntu) => rsyslog (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429427
Title:
Unexplainable time jumps
Figured I'd give it a quick google for this weirdness and stumbled upon
this report. Confirmed it, but then started doubting if it actually is
cron that's causing this weirdness. So I put a simple strace on my
freshly restarted cron with strace -f -p -s 1000 2>&1 | grep
'CRON\[' and left this run
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cron (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429427
Title:
Unexp
One of the mentioned network devices is a Firewall which logs verbosely,
i.e. there is a LOT of logs coming in from there and /var/log/firewall
does not show a single time jump.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Forgot: Restarting CRON does not solve the problem. Rebooting the system
does - as written, temporarily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429427
Title:
Unexplainable time jumps in CRON
Script used for monitoring:
#!/bin/bash
oldTime=$(date +%s)
oldPsOutput=$(ps faux)
while sleep 1
do
currentTime=$(date +%s)
currentPsOutput=$(ps faux)
if [ "$currentTime" -lt "$oldTime" ] # clock change detected?
then
(
echo '='
echo "$currentTime < $oldTime"
25 matches
Mail list logo
