This bug was fixed in the package ureadahead - 0.100.0-19.1
---
ureadahead (0.100.0-19.1) xenial; urgency=medium
* add -q parameter to stop ureadahead from logging thousands of
lines of noise (LP: #1579580)
-- Dan Streetman Wed, 10 Apr 2019 13:59:25
-0400
** Changed in:
ubuntu@fili:~$ dpkg -l |grep ureadahead
ii ureadahead0.100.0-19
amd64Read required files in advance
ubuntu@fili:~$ journalctl -b | grep ureadahead | wc -l
4051
(upgraded ureadhead version to -proposed, removed
** Description changed:
[impact]
ureadahead logs thousands of lines of useless noise on each boot.
[test case]
install bionic on physical hardware (ureadhead doesn't run under virt)
and check the boot logs:
- #journalctl -m | grep ureadahead | wc -l
+ #journalctl -b | grep
Hello Seth, or anyone else affected,
Accepted ureadahead into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/ureadahead/0.100.0-19.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package ureadahead - 0.100.0-21
---
ureadahead (0.100.0-21) bionic; urgency=medium
* add -q parameter to stop ureadahead from logging thousands of
lines of noise (LP: #1579580)
-- Dan Streetman Tue, 09 Apr 2019 17:01:18
-0400
** Changed in:
** Also affects: ureadahead (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: ureadahead (Ubuntu Xenial)
Status: New => In Progress
** Changed in: ureadahead (Ubuntu Xenial)
Importance: Undecided => Low
** Changed in: ureadahead (Ubuntu Xenial)
Assignee:
(note that /var/lib/ureadahead/pack file removed and then system
immediately rebooted before each verification test below)
ubuntu@fili:~$ dpkg -l |grep ureadahead
ii ureadahead0.100.0-20
amd64Read required files in advance
** Description changed:
[impact]
ureadahead logs thousands of lines of useless noise on each boot.
[test case]
install bionic on physical hardware (ureadhead doesn't run under virt)
and check the boot logs:
#journalctl -m | grep ureadahead | wc -l
30244
+
+
+
The version string pattern is very odd, but I guess it's OK given that
ureadahead was never published in Debian and the Ubuntu strings have
never contained "ubuntu" anyway. Similarly I'd prefer an additional "."
to indicate an SRU but the version numbering is so odd anyway it's not
clear how to do
Another regression possibility is that some user was relying (or will
rely) on the more verbose output and it'll no longer be there. For
example, are there more useful messages that will also be suppressed
with -q?
However, on balance I think this is worth doing regardless, as the spam
will make
marking upstream ureadahead as won't fix, since it was dropped from
Ubuntu starting in Cosmic.
** Description changed:
+ [impact]
+
+ ureadahead logs thousands of lines of useless noise on each boot.
+
+ [test case]
+
+ install bionic on physical hardware (ureadhead doesn't run under virt)
+
Work-around #3 solved the problem for me. Thanks!
https://askubuntu.com/a/840567 explains very well the question.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
https://bugs.launchpad.net/bugs/1579580
18.04 LTS 64 bit Server up-to-date
Having the same problem when rebooting ...
uname -a
Linux 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
@kkobashi: are you saying this is a wontfix for 18.04? Can't ureadahead
operate in quiet mode?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
https://bugs.launchpad.net/bugs/1579580
Title:
ureadahead
@Anders Hall
You can rid of it by:
systemctl stop ureadahead.service
systemctl disable ureadahead.service
apt-get purge ureadahead.service
Reboot
Check to see if it is running
systemctl status ureadhead.service
ps aux | grep ureadahead
It should be gone.
18.10 is coming out in a few weeks.
Also getting these messages (trying to find useful information in syslog
due to other issues, found these messages spamming).
NVme as well.
uname -a
Linux computer 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
#journalctl -m | grep ureadahead | wc
Did some testing. Installed Xubuntu 18.04 twice today on an NVme. In
both cases, ureadahead messages appeared all over the place in the
system log.
When I did this under Ubuntu 18.04 Desktop prior, I had over 250,000
lines of noise. This all works great on the first installation. But
after
I was checking for my own log messages I was writing and found this:
$ journalctl -b | grep eyesome | grep ureadahead
Oct 07 11:15:25 alien ureadahead[289]: ureadahead:acpi-lid-event-eyesome:
Ignored relative path
I found this bug report and ran the recommended check:
$ journalctl -b | grep
ureadahead has been already removed from cosmic. If you don't need it,
just remove the package.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
https://bugs.launchpad.net/bugs/1579580
Title:
Installed Ubuntu Desktop 18.0.4 a few days ago and noticed I am getting
large syslog files littered also with messages.
I have disabled this:
sudo systemctl disable ureadahead.service
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
ExecStart twice is what I meant (this is the way to replace the command
from the base definition instead of adding another command to the list,
see the systemd.unit man page for details.)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Why it contains ExecStart 2 times?
[Service]
ExecStart=
ExecStart=/sbin/ureadahead -q
Did you mean ExecStop?
[Service]
ExecStop=
ExecStart=/sbin/ureadahead -q
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in
Be aware the messages will come back next time you boot after
upgrading a package that touches something in /etc, which will trigger
another scan by ureadahead. Better is the workaround I gave back in
#9, but really what I recommend is just purge ureadahead. ureadahead
only ever can help the
Thanks, workaround in #19 seem to have removed (thousands of) these
messages.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
https://bugs.launchpad.net/bugs/1579580
Title:
ureadahead reports relative
I would just remove ureadahead using apt. It's just another canonical
project that nobody has looked at in years and not a priority. I see no
difference whatsoever without it and maybe you won't either.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
The same issue on Xubuntu 18.04.1: lots of ureadahead messages with
"Ignored relative path"
I solved it by instruction found here (in Russian language):
https://sysadmin.ru/articles/ubiraem-soobshheniya-ureadahead-ignored-
relative-path-v-syslog
1. run 'sudo ureadahead --force-trace --verbose /'
not foundation team but looking at the issue
a) Difference is much smaller but difference between memory and SSD is still
very large.
b) its only triggering a read/cache of files that would be read anyways. I have
quite a bit starting up on boot and if I'm reading correctly there are 2400
file
Foundations team, has anyone looked at ureadahead lately to make sure
that it still makes sense to include it?
(a) I suspect SSDs don't benefit much from it
(b) I suspect systems with spinning metal drives are also unlikely to have the
memory to cache all those files, nor the free IO cycles to
Insane amounts in /var/log/syslog
Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:usb: Ignored relative path
Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:devices: Ignored relative
path
Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:1-1.3:1.0: Ignored
relative path
Jun 10
Solution per comment #3 fixed the problem for me as well, ureadahead is
no longer spammy.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
https://bugs.launchpad.net/bugs/1579580
Title:
ureadahead
92454 entries here, Ubuntu 18.04, fresh installation.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
https://bugs.launchpad.net/bugs/1579580
Title:
ureadahead reports relative path errors in
3597 lines here on ubuntu 18.04 upgraded from 16.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
https://bugs.launchpad.net/bugs/1579580
Title:
ureadahead reports relative path errors in
Fresh install of UbuntuStudio 18.04, same issue:
# grep -i uread /var/log/syslog | grep -i "May 25 12:43" | wc -l
93742
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:sys: Ignored relative path
May 25 12:43:54 darkstar ureadahead[411]: ureadahead:class: Ignored relative
path
May 25
Hi,
I have this error on Ubuntu 18.04 after upgrading the system from 16.04.
>>> grep -i uread /var/log/syslog | grep -i "Apr 30 10" | wc -l
>>> 69482
and the boot time is very slow (it takes now ~ 2 minutes instead of ~7
seconds - as I had using the previous version of Ubuntu).
Here you can
Same on Ubuntu 17.10 with the latest updates and encrypted file system.
During boot the process stops at the Ubuntu label with the 5 dots and
does nothing else, but generates these messages.
Apr 17 19:54:33 L5280 sudo: pam_ecryptfs: pam_sm_authenticate: /home/user1 is
already mounted
Apr 17
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
https://bugs.launchpad.net/bugs/1579580
Title:
ureadahead reports relative path errors in journalctl output
Status in ureadahead
These messages were produced on my system after upgrading Lubuntu 17.10 to
18.04 beta.
One wants to hunt issues in syslog after upgrade, but one has to fight with
these obtrusive messages. :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
running 18.04.
saw a massiv syslog file and running grep -i uread /var/log/syslog.1|grep -i
"Feb 25 12" |wc -l:
> 63197
i dont think we need this to make syslog extra big for no reason.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Got this in a bionic live boot -
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1740378/+attachment/5028337/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
xb5i70, ureadahead gets a list of files accessed during boot using the
debugfs filesystem and the linux kernel's tracing mechanism. You can see
the sources at http://bazaar.launchpad.net/~canonical-
scott/ureadahead/trunk/view/head:/src/trace.c#L115 for the raw details.
Thanks
--
You received
I am using Ubuntu 16.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
https://bugs.launchpad.net/bugs/1579580
Title:
ureadahead reports relative path errors in journalctl output
Status in
Sorry if this is a stupid question, but what do you mean by 'every time it gets
a relative path from debugfs' ?
Is there a reason why its getting a relative path?
I sometimes get loads of ureadahead messages like this in logs straight
after random reboots but not always.
Like today, The problem
/sbin/ureadahead is writing out warnings every time it gets a relative
path from debugfs. This seems excessively wordy, but putting a -q on
the ExecStart in ureadahead.service would shut it up.
I did a systemd drop-in as a workaround by creating
** Changed in: ureadahead (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
https://bugs.launchpad.net/bugs/1579580
Title:
ureadahead reports relative path
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ureadahead (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
45 matches
Mail list logo
