I see this with Ubuntu 16.04 (amd64), all up-to-date.
rsyslog 8.16.0-1ubuntu3
logrotate 3.8.7-2ubuntu2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/407862
Title:
Messages not being sent to system
** Tags added: amd64 i386 karmic saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/407862
Title:
Messages not being sent to system logs
To manage notifications about this bug go to:
https://bugs.
I see this with ubuntu 13.10, all up-to-date.
rsyslogd 5.8.11
logrotate 3.8.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/407862
Title:
Messages not being sent to system logs
To manage notificat
I can confirm this in Debian 6.0.7, default install, default daemon configs.
Logging just stops after couple of days. I gave a shot to an aptitude upgrade
but when I saw neither rsyslog/logrotate would not update I aborted it.
ii rsyslog 4.6.4-2
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/407862
Title:
Messages not being sent to system logs
To manage notifications about this bug go to:
https://bugs.launchpad.net/rs
I got this one too.
I was unable to SSH into the box, however it would respond to ping. I'd
describe this as freezing my box and it's resolution was a manual
restart of the VM.
Jun 25 06:36:04 tux rsyslogd: [origin software="rsyslogd"
swVersion="4.2.0" x-pid="733" x-info="http://www.rsyslog.com";
Hi,
I got this on my HP Envy 23 as last message in /var/log/syslog before a
complete freeze (keyboard, mouse and ping hangs)
May 21 23:28:02 neruda kernel: [ 901.308548] [drm:drm_mode_addfb], [FB:33]
May 21 23:28:02 neruda kernel: [ 901.308555] [drm:radeon_crtc_page_flip],
flip-ioctl() cur_fbo
I got this one 1 machine, Precise (32 bit) installed.
For me, it seems, that somebody used the machine as "Guest", did not
logged out and Firefox did an update, which lead to a total crash of the
system... (but this is juast a guess!)
Last messages in /var/log/syslog.1 where:
May 20 07:30:01 icaf
** Tags removed: karmic
** Tags added: lucid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/407862
Title:
Messages not being sent to system logs
To manage notifications about this bug go to:
https:/
logging is sent to /var/log/syslog not /var/log/messages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/407862
Title:
Messages not being sent to system logs
To manage notifications about this bug go
root@ms:~# tail -n 1 /var/log/messages
Oct 26 06:25:01 atlantic1 rsyslogd: [origin software="rsyslogd"
swVersion="4.6.4" x-pid="855" x-info="http://www.rsyslog.com";] rsyslogd was
HUPed, type 'lightweight'.
root@ms:~# uname -a
Linux ms 2.6.32-5-amd64 #1 SMP Sun May 6 04:00:17 UTC 2012 x86_64 GNU
Yesterday afternoon leaving with disconnecting usb drive.
When returned (after 8 'o clock) the system was unresponsive.
System restarted at 8:23
Sep 18 16:24:31 tahars kernel: [115887.494108] usb 1-7: USB disconnect, address
5
Sep 19 07:40:10 tahars kernel: [170826.226381] type=1505
audit(13480
Still broken in an up-to-date 10.04.4 LTS.
** Changed in: rsyslog (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/407862
Title:
Messages not being sent t
surfingalien, I'm getting the same issue on 3 of my servers as well.
Running 10.04LTS with latest updates. Have you found any fixes?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/407862
Title:
Mess
i'm making this discussion come up as i have the same problem as
described on 3 diferent machine all running ubuntu 10.04 (2 laptops and
1 server). if this is not so important for the laptop, it counts for my
server as i usually read the syslog to see if evrything works fine...
without a log file,
On 09/08/2011 11:28 AM, Barry Warsaw wrote:
> Now, here's a question: did you modify that line yourself, or did that come
> with the package? My Lucid system just has `create` on a line by itself, so
> I'm guessing you added that. If not, then is this machine updated from an
> earlier version of
On Sep 07, 2011, at 09:43 PM, Nikolaus Rath wrote:
>On 09/07/2011 02:16 PM, Barry Warsaw wrote:
>> At this point, what is the ownership and permissions on /var/log/syslog?
>
># ls -l /var/log/syslog
>-rw-rw-r-- 1 root adm 0 2011-09-07 10:11 /var/log/syslog
So the core problem here is that after
On 09/07/2011 02:16 PM, Barry Warsaw wrote:
>> [0] spitzer:~# logger testing
>> [0] spitzer:~# tail -2 /var/log/syslog
>> 10:08:48 beta AptDaemon: INFO: Shutdown was requested
>> Sep 7 10:09:42 spitzer root: testing
>> [0] spitzer:~# logrotate --force --verbose /etc/logrotate.conf
> [output delete
Thanks for the details Nikolaus; I want to get just a bit more
information.
On Sep 07, 2011, at 02:15 PM, Nikolaus Rath wrote:
>[0] spitzer:~# logger testing
>[0] spitzer:~# tail -2 /var/log/syslog
> 10:08:48 beta AptDaemon: INFO: Shutdown was requested
>Sep 7 10:09:42 spitzer root: testing
>[0]
** Changed in: rsyslog (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/407862
Title:
Messages not being sent to system logs
To manage notifications about this
[0] spitzer:~# logger testing
[0] spitzer:~# tail -2 /var/log/syslog
10:08:48 beta AptDaemon: INFO: Shutdown was requested
Sep 7 10:09:42 spitzer root: testing
[0] spitzer:~# logrotate --force --verbose /etc/logrotate.conf
reading config file /etc/logrotate.conf
compress_prog is now /bin/bzip2
Nikolaus, can you provide exact steps to reproduce the problem for you?
I have a fully up-to-date 10.04.3 LTS. /var/log/syslog is owned by
syslog:adm. Note that if your file does *not* have these ownerships,
you should `sudo chown syslog:adm /var/log/syslog` before you begin.
$ tail -f /var/log
I can confirm that the problem still exists in Ubuntu 10.04 LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/407862
Title:
Messages not being sent to system logs
To manage notifications about this
I can confirm that the problem still exists in Ubuntu 0.04 LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/407862
Title:
Messages not being sent to system logs
To manage notifications about this
FWIW, I tried various scenarios described here, including HUPing and
logrotate'ing in a fresh Oneiric install. I couldn't reproduce any of
the problems, namely that if /var/log/syslog has syslog:adm ownership,
it does so after the logrotate. Further, logger messages always go to
the new /var/log/
** Changed in: rsyslog (Ubuntu)
Assignee: (unassigned) => Barry Warsaw (barry)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/407862
Title:
Messages not being sent to system logs
To manage noti
seriously, I am a system administrator and I have this problem on my
server, is it possible that in 3 years we dont even have a workaround on
this?
what am I supposed to do? create a shell scripts that restarts all the
daemon logs AND mysql database each time they rotate or disable
logrotate allto
Launchpad has imported 7 comments from the remote bug at
http://bugzilla.adiscon.com/show_bug.cgi?id=150.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.la
>From my PoV, this is a problem that stems back to either the config
provided and/or other packages.
Ubuntu makes rsyslog drop privileges. That's fine, though has some
documented quirks until v6. Most importantly for this bug, files are
opened before dropping privs. Nevertheless, files are created
Ubuntu, you're doing just great.
First posted in 2009-08-02.
Today is 2011-09-09
3 years and the problem is still there, should we mark this is as a
feature maybe?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
is this still broken? any update from the maintainer?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/407862
Title:
Messages not being sent to system logs
To manage notifications about this bug go to
Same problem here with rsyslog 4.2.0-2ubuntu8 on ubuntu-server 10.10
(Dell PowerEdge R300)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/407862
Title:
Messages not being sent to system logs
--
ubu
This problem is still happening in fresh 11.04 installs. It makes
troubleshooting very difficult when I have no logs to consult.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/407862
Title:
Messages
** Changed in: rsyslog
Importance: Unknown => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/407862
Title:
Messages not being sent to system logs
--
ubuntu-bugs mailing list
ubuntu-bugs
Continuing problem confirmed for Ubuntu 10.10 64-Bit with latest updates on a
Dell OptiPlex 960, Intel Core 2 Duo E8600 (2x3.33GHz):
rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="841"
x-info="http://www.rsyslog.com";] rsyslogd was HUPed, type 'lightweight'.
--
Messages not bein
Unfortunately, the included fix (force changing ownership on start-up)
breaks logging of innd and running news-daily, as the logfiles should be
owned by news.news but are now forced to syslog.adm. The init.d script
from syslogd mentioned in https://bugs.launchpad.net/bugs/120085 uses
"syslogd-listf
Ubuntu 10.10 32-Bit on Athlon II X4
/var/log/messages :
...
Oct 19 19:18:16 desktop kernel: [ 20.290536] ADDRCONF(NETDEV_CHANGE): eth0:
link becomes ready
Oct 19 19:46:02 desktop rsyslogd: [origin software="rsyslogd" swVersion="4.2.0"
x-pid="977" x-info="http://www.rsyslog.com";] rsyslogd wa
r...@integre:/var/log# tail messages
Oct 10 06:45:53 integre rsyslogd: [origin software="rsyslogd" swVersion="4.2.0"
x-pid="807" x-info="http://www.rsyslog.com";] rsyslogd was HUPed, type
'lightweight'.
Oct 11 06:46:15 integre rsyslogd: [origin software="rsyslogd" swVersion="4.2.0"
x-pid="807" x
** Branch linked: lp:ubuntu/lucid/rsyslog
--
Messages not being sent to system logs
https://bugs.launchpad.net/bugs/407862
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
** Summary changed:
- [karmic] Messages not being sent to system logs
+ Messages not being sent to system logs
--
Messages not being sent to system logs
https://bugs.launchpad.net/bugs/407862
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
40 matches
Mail list logo
