$ cat /etc/issue
Linux Mint 17.3 Rosa
$ uname -a
Linux R2D2 4.4.0-138-generic #164~14.04.1-Ubuntu SMP Fri Oct 5 08:56:16 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
Syslog contents showing error:
Oct 4 12:35:31 R2D2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4"
x-pid="13023"
k--andrey@kandrey:/tmp$ cat /etc/issue
Ubuntu 16.04.4 LTS \n \l
k--andrey@kandrey:/tmp$ uname -a
Linux kandrey.kitsoft.kiev.ua 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar
14 17:48:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Apr 27 12:12:41 kandrey rsyslogd-2039: Could not open output pipe
Wow, eight years and this is still a bug on Xenial. This is bordering on
incompetence
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
To manage
This is not fixed in Xenial, rsyslog.postinst will still install
50-default.conf, which is packaged to also include /dev/xconsole still.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
/dev/xconsole isn't created if it isn't there. If /dev/xconsole exists
it is not taken to output logs as given in
/etc/rsyslog.d/50-default.conf.
Creating /dev/xconsole and changing user:group doesn't help. service
rsyslog restart doesn't have access to this pipe. It doesn't matter if
apparmore
This has been fixed with:
rsyslog (8.14.0-2) unstable; urgency=medium
* Remove logging to /dev/xconsole from the default rsyslog configuration.
It is a rarely used feature and causes rsyslog to repeatedly retry if
there is noone reading from /dev/xconsole. Instead ship the
This is still present in the development branch for 16.04
Jan 19 17:53:23 ubuntu rsyslogd-2039: Could not open output pipe
'/dev/xconsole':: No such file or directory [v8.14.0 try
http://www.rsyslog.com/e/2039 ]
System information:
$ lsb_release -rd
Description:Ubuntu Xenial Xerus
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
To manage notifications about this bug go to:
** Tags added: x86-64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
To manage notifications about this bug go to:
Related? https://bugs.launchpad.net/hundredpapercuts/+bug/612900
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
To manage notifications about this
** Tags added: wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
To manage notifications about this bug go to:
** Tags removed: utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
To manage notifications about this bug go to:
** Tags removed: lucid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
To manage notifications about this bug go to:
Also 15.04:
---
Jul 5 16:00:16 Kermit rsyslogd-2039: Could no open output pipe
'/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
** Tags added: vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is still present in Ubuntu 14.04!
---
May 2 20:50:16 vstuaa-2 rsyslogd: [origin software=rsyslogd
swVersion=7.4.4 x-pid=20463 x-info=http://www.rsyslog.com;] start
May 2 20:50:16 vstuaa-2 rsyslogd: rsyslogd's groupid changed to 104
May 2 20:50:16 vstuaa-2 rsyslogd: rsyslogd's userid
** Tags added: i386 precise
** Tags added: lucid
** Tags added: utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
To manage notifications
the bug is still in Ubuntu 14.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
To manage notifications about this bug go to:
Vivid feedback (booted with systemd):
both /dev/console /dev/xconsole exist but with different settings:
- dev/console owned by root/root
- dev/xconsole owned by root/admin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
bug is still present on trusty. any progress on this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
To manage notifications about this bug
It simplifies software contents, bug fixing or development.
** Changed in: rsyslog (Ubuntu)
Importance: Undecided = High
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
** Changed in: hundredpapercuts
Status: New = Triaged
** Changed in: hundredpapercuts
Since the config for xconsole output in rsyslog has survived despite
broken for over 5 years now, I suggest removing that from the default
config will reduce confusion and clearly create no new problems. Those
wanting it have had to actively repair this for 5 years and shouldn't
have trouble
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
To manage notifications about this bug go to:
This issue still exists on Ubuntu 13.10. It was mentioned above that the
message in /var/log/syslog is just a warning, and can be ignored, but
note that the syslog actually speaks of an error:
Dec 9 04:14:00 rsyslogd-2039: Could not open output pipe '/dev/xconsole'
[try
Please disregard from comment #45. I had an unrelated issue which
produced the CONFIG ERROR in my syslog. Still get the Could not open
output pipe '/dev/xconsole' message though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
To manage notifications about this bug go to:
Having just encountered this on a copy of 12.04 Server running on a
virtual machine, I endorse Kenyon Ralph's approach in post 33 above. I
don't intend to run X on this machine, so it's easiest to comment out
the part at the end of /etc/rsyslog.d/50-default.conf that pipes some
output to
For what its worth, this bug is just a warning.
If you see these messages in /var/log/rsyslog, you can safely ignore them.
They are simply rsyslog saing that /dev/xconsole does not exist, and then going
on with life. This happens on perfectly functioning systems.
If your system crashes and
Scott,
There are two issues discussed in this bug:
1) rsyslog emits a Could no open output pipe '/dev/xconsole' warning
message message when it starts up, because /dev/xconsole doesn't exist.
2) after the daily log-rotation cron job, one's xconsole window suddenly
goes dead.
You are correct
Wait stop indie (alanlitster) on 2011-02-03: has the fix except the
mknod needs a masage.
sudo service rsyslog stop
sudo mknod -m 640 /dev/xconsole c 1 3
sudo chown syslog:adm /dev/xconsole
sudo service rsyslog start
Verify it is working with reload as well
sudo service rsyslog reload
sudo
On a box upgraded from 10.10 - 11.04 - 11.10, I also have this
problem, and it causes my machine to crash -- I have multiple entries in
my syslog in which this is the last message before my system crashes:
Feb 3 23:21:26 grickle-grass rsyslogd: [origin software=rsyslogd
swVersion=5.8.1
Sergio,
does it lead to freezing or its just a message in the syslog?
From: Sergio Callegari sergio.calleg...@gmail.com
To: stephen.cb...@yahoo.com
Sent: Saturday, December 10, 2011 8:49 AM
Subject: [Bug 459730] Re: rsyslog doesn't create /dev/xconsole
My
My oneiric also complaining at
rsyslogd-2039: Could no open output pipe '/dev/xconsole' [try
http://www.rsyslog.com/e/2039 ]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog
so, how can I find out what is causing my freezing? 11.10 unusable for 2 weeks
now.
there is no other message after that in the syslog.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
On 2011-12-06T17:55:34-, stephen bond 459...@bugs.launchpad.net wrote:
q on comment #33 from kralph:
which file exactly is that? I have 11.10 frozen and not usable for a week now
and nobody is answering my post in general help and I am not the only one.
and if the solution is known why
q on comment #33 from kralph:
which file exactly is that? I have 11.10 frozen and not usable for a week now
and nobody is answering my post in general help and I am not the only one.
and if the solution is known why isn't there an automatic patch or at least a
sticky as a known bug in general
Dec 6 00:41:58 hostname kernel: imklog 5.8.1, log source = /proc/kmsg started.
Dec 6 00:41:58 hostname rsyslogd: [origin software=rsyslogd
swVersion=5.8.1 x-pid=524 x-info=http://www.rsyslog.com;] start
Dec 6 00:41:58 hostname rsyslogd: rsyslogd's groupid changed to 103
Dec 6 00:41:58
Same problem in 10.04 64 bit.
I tried something: I added touch /dev/xconsole in /etc/gdm/Init/Default at
the beginning of the file.
It seems to solve the issue,
though I am not sure it is a good thing to proceed as well.
--
You received this bug notification because you are a member of
On 2011-12-01T09:20:27-, alligator...@free.fr 459...@bugs.launchpad.net
wrote:
Same problem in 10.04 64 bit.
I tried something: I added touch /dev/xconsole in
/etc/gdm/Init/Default at the beginning of the file.
It seems to solve the issue,
though I am not sure it is a good thing to
Steve Langasek suggested that perhaps this should be somewhere other
than /dev, since it isn't actually a device. /run/xconsole, perhaps?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
Same problem upgrading from 10.04 64bit to 11.10 64bit ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
To manage notifications about this
Same here, have this bug on a 11.10 64bit ubuntu box updated from 11.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
To manage notifications
I have this bug in oneric.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
To manage notifications about this bug go to:
Still exists.
Comment #4 is not true. There would be no bug reporti f it didn't complain,
right?
for me this not completely breaks rsyslog right away, instead it seems
to stop logging some time after launch.
Since there is also a fix in this launchpad (see the part about
Can confirm that the problem still exists on the 64bit version of 11.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
To manage notifications
I am getting this on 11.04 Beta2 x64 desktop immediately after boot into
clean install. Indie seems to have a good idea over what causes this,
just thought i would chip in and confirm it still is a problem in natty.
Apr 16 02:16:24 q kernel: imklog 4.6.4, log source = /proc/kmsg started.
Apr 16
I'm running Ubuntu 10.10 and the problem still exists - /dev/xconsole
doesn't exist.
If I manually create the node then restart rsyslog it works.
# mknod -m 640 /dev/xconsole
# chown root:adm /dev/xconsole
# restart rsyslog
However, if I reload rsyslog as is done from logrotate it no longer
rsyslogd-2039: Could no open output file '/dev/xconsole' [try
http://www.rsyslog.com/e/2039 ]
Ubuntu 10.10 32b.
How i help you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog
I have this bug on 10.10 Server, agree with #11 that this is serious.
Fixed it for now using the suggestion at comment #3, thanks inode77!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
Tax dollars hard at work it looks like.
** Attachment added: being spied on sucks
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/459730/+attachment/1759449/+files/look
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Following up with my #16 follow up, while my /lib/udev/devices trick works
for Ubuntu 10.04, it doesn't fully work for Kubuntu 10.04.
I still need to restart rsyslog shortly after logon.
What could be different between the two?
I believe that is the single problem to not closing this bug and
have installed a newest release but got a warning:
update-rc.d: warning: /etc/init.d/rsyslog missing LSB information
--
rsyslog doesn't create /dev/xconsole
https://bugs.launchpad.net/bugs/459730
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hola mi amigo has esta linea de comandos en la terminal y con esto se
resuelve saludos
/etc/init.d/rsyslog stop
/etc/init.d/rsyslog.dpkg-new stop
cd /usr/src
wget http://www.rsyslog.com/files/download/rsyslog/rsyslog-5.5.6.tar.gz
tar zxvf rsyslog-5.5.6.tar.gz.
cd rsyslog-5.5.6
./configure
make
In response to Neil, I think the problem is that rsyslog gets things
wrong on a *reload* but that on a *restart* it gets it right.
I've filed another bug, #61290, since its a separate issue.
David
--
rsyslog doesn't create /dev/xconsole
https://bugs.launchpad.net/bugs/459730
You received this
As a follow-up, in Lucid (10.04), the /lib/udev/devices fix works for
me. I don't have to restart rsyslog again.
--
rsyslog doesn't create /dev/xconsole
https://bugs.launchpad.net/bugs/459730
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/459730/comments/15
In response to Neil, I think the problem is that rsyslog gets things wrong on
a *reload* but that on a *restart* it gets it right.
I've filed another bug, #61290, since its a separate issue.
David
There is a typo
As per Nuno's suggestion, I created the entries in /lib/udev/devices but
also have the issues that xconsole ceases to output content when rsyslog
reloads as part of the daily cron. I am not clear on why this is though,
as the fix is -also- to restart rsyslog.
--
rsyslog doesn't create
Same thing here with up to date 10.04 amd64:
Jun 22 07:01:47 i7 kernel: imklog 4.2.0, log source = /proc/kmsg started.
Jun 22 07:01:47 i7 rsyslogd: [origin software=rsyslogd swVersion=4.2.0
x-pid=1009 x-info=http://www.rsyslog.com;] (re)start
Jun 22 07:01:47 i7 rsyslogd: rsyslogd's groupid
I'm seeing this on an upgraded Ubuntu server 9.10 to 10.04 server.
Whenever the nightly restart of rsyslogd happens, there is a chance it
will spin out of control.
--
rsyslog doesn't create /dev/xconsole
https://bugs.launchpad.net/bugs/459730
You received this bug notification because you are a
this bug is keeping ever and all logs on 3 of my computers from being
written... i'de say this is serious.
--
rsyslog doesn't create /dev/xconsole
https://bugs.launchpad.net/bugs/459730
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Mathias Gug wrote on 2010-04-01:
If /dev/xconsole doesn't exist rsyslog doesn't complain. So there is no real
need to comment the section in /dev/xconsole.
Not true:
May 16 09:58:56 ibis rsyslogd-2039: Could no open output file '/dev/xconsole'
[try http://www.rsyslog.com/e/2039 ]
I agree
I have exactly the same situation here as described by Dino99
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/459730/comments/6
on both Lucid server and desktop installs. Though I cannot comment on
previous versions - never bothered to check.
--
rsyslog doesn't create /dev/xconsole
Seeing it as well with fresh 10.04. I also have the problem (twice
today) of the display not coming up when booting, it changes (I assume)
to graphics mode shortly after the grub2 menu and my monitor goes in to
power saving. Trying Ctrl-Alt-F1 to go to text log-in had no effect, but
Ctrl-Alt-Del
Yes, I have the exact same message sequence as dino99 in a fresh install
of Ubuntu 10.04 official release:
Apr 30 08:06:57 Agrajag rsyslogd: [origin software=rsyslogd swVersion=4.2.0
x-pid=761 x-info=http://www.rsyslog.com;] (re)start
Apr 30 08:06:57 Agrajag rsyslogd: rsyslogd's groupid changed
situation on Lucid updated:
into syslog:
Apr 3 18:50:58 localhost kernel: imklog 4.2.0, log source = /proc/kmsg started.
Apr 3 18:50:58 localhost rsyslogd: [origin software=rsyslogd
swVersion=4.2.0 x-pid=986 x-info=http://www.rsyslog.com;] (re)start
Apr 3 18:50:58 localhost rsyslogd:
If /dev/xconsole doesn't exist rsyslog doesn't complain. So there is no
real need to comment the section in /dev/xconsole.
However rsyslog may need to be reloaded when the xconsole device is
created.
I'll unsubscribe the sponsor team for now since creating the xconsole
device in the upstart
I fixed this by adding xconsole to the /lib/udev/devices directory and
adjusting the permissions.
But I still have to restart rsyslog every day for xconsole to continue working,
because after the daily cron activities it ceases to work.
It seems to me the right fix would be:
1) Make the
I recently installed ubuntu 9.10 server headless.
If I'm not mistaken /dev/xconsole only makes sense if you intend to have a
running xserver.
So my propsition is to comment the snippet concerning xconsole
(/etc/rsyslog.d/50-default.conf).
#daemon.*;mail.*;\
# news.err;\
#
Shouldn't this be done in udev instead? A lot of init scripts used to do
this kind of thing, but I'm uncomfortable with this persisting into an
Upstart-based world - device creation does not really belong in Upstart
jobs.
--
rsyslog doesn't create /dev/xconsole
Here's a debdiff adding that bit back. Whoops.
** Attachment added: xconsole.debdiff
http://launchpadlibrarian.net/34404418/xconsole.debdiff
** Changed in: rsyslog (Ubuntu)
Status: New = Confirmed
--
rsyslog doesn't create /dev/xconsole
https://bugs.launchpad.net/bugs/459730
You
69 matches
Mail list logo
