Still in 2022 on fresh 18.04.5 updated to 18.04.6 Kubuntu 32-bit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/655831
Title:
update-apt-xapian-index bogs down system
To manage notifications about
Nope, the problem has not been fixed. Still there with Kubuntu 18.10.
** Changed in: apt-xapian-index (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/655831
Problem has been fixed long ago
** Changed in: apt-xapian-index (Ubuntu)
Status: Triaged => Invalid
** Changed in: apt-xapian-index
Status: New => Invalid
** Changed in: ac100
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Singtoh, I give many thanks for this fix. I have 4 cores (2 hyperthreads
each, so '8 cores'), so the high single-thread usage didn't bother me
too much... But the amount of time it took really frustrated me.
This goes from a 'leave Synaptic open for a while and do something else'
sort of thing,
Correction I didn't purge Synaptic and apt-xapian-index before. Now I
did and the crashes stopped.
The update-apt-xapian-index process is still heavy on resources but it
does work faster. It needs about one minute on my machine after
refreshing sources in Synaptic.
--
You received this bug
Installing a pure Debian package over Ubuntu one isn't a good advice.
Anyway I tried it and all it did was a crash fest for update-apt-xapian-
index process. It crashes for every single operation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hello All,
Just thought I would add a comment to this.
The apt-xapian-index has been driving me mad since installing Ubuntu 16.04,
being very slow rebuilding and it was rebuilding every time I opened Synaptic
taking a few minutes. I had a script that I found on ubuntu forum that would
rebuild
With actual commonly used cpu having multi cores, the index should be
rebuilt on at least 2 cores (or half the total cores number, to let the
others available for the other processes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is still a problem in 16.04 LTS.
This process uses 100% CPU for a long time and up to 500MB of RAM on my
machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/655831
Title:
** Tags removed: lucid vivid
** 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/655831
Title:
update-apt-xapian-index bogs down system
To manage notifications about this bug go
That issue is still disturbing when updating vivid archive; maybe it's
time to 'assign' a Debian/Ubuntu maintainer
** Tags added: vivid
** Tags removed: quantal raring saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I hit this problem while upgrading from Kubuntu 13.10 to 14.04. I have
an old laptop with 512 MiB RAM and the updating process crawled to a
halt.
I just created a fake package to get rid of apt-xapian-index without
having to edit system configuration files, see here:
On Xubuntu 14.04 (supposed to be light-weight), same problem, update-
apt-xapian-index is knocking down the system
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/655831
Title:
update-apt-xapi is so powerful that it can also block 14.04 users from
doing their job.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/655831
Title:
update-apt-xapian-index bogs down system
To
In KUbuntu 14.04 this bug is getting terrible. This process, update-apt-
xapi, tries to take about 400 M of memory, and given the minimum
cumulative KDE memory consumption of 1.5 G at idle, all my 2 G get
consumed, so I can run nothing more! This indexing process starts almost
each time when I
** Tags added: saucy trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/655831
Title:
update-apt-xapian-index bogs down system
To manage notifications about this bug go to:
Just ran into this issue (FWIW) today, on 13.10. Basically, if you
install a new distro, the first time you go to use it it drags to a
crawl thanks to something named update-apt-xapi in top using all of
one core. Very frustrating for users of fresh installs (i.e. new users
included). Could it be
For me, the apt-xapian-index cronjob used to crash a complete Xen domU
(Raring minimal install w/ linux-vm, 512 MiB RAM, 1 vcpu, 1 GiB swap) on
a weekly basis until I disabled the cronjob. Took me a while to find out
why the domU crashed in such a timely manner.
I do not have this problem on
Just had another look into my notes. The problem appeared for me after
upgrading from quantal to raring. I have also found bug 1152736 and bug
1185172 dealing with a potential kswapd regression in Kernel 3.8 and
might be related.
--
You received this bug notification because you are a member of
Still affecting Raring.
We've yet to receive an explanation of the rationale for this package
being installed by default (or even for its very existence). It's been
causing major usability problems for almost 3 years now. It's
unfathomable that it's installed on Ubuntu server VM images!
This
This bug affects Ubuntu 12.04 (Precise Pangolin). I noticed the CPU
hogging for several minutes. I did not notice any disk I/O slow down.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/655831
Title:
Just an idea: the case and environment Hontvári József Levente
(hontvari) mentioned on 2013-04-13 should be easy to recreate, and could
be used to track down the problem with this indexer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Max Polk has a good analysis. Partly to help google, I would add that on a
Quantal 64 bit server installed with Install a minimal virtual machine option
and 256 MB RAM, the command (simulating the cron job)
sudo /usr/sbin/update-apt-xapian-index -v -f
results in an additional 300 MB RAM usage
** Tags added: quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/655831
Title:
update-apt-xapian-index bogs down system
To manage notifications about this bug go to:
** Tags added: amd64 raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/655831
Title:
update-apt-xapian-index bogs down system
To manage notifications about this bug go to:
A weekly fatal unable to fork error message from /etc/cron.weekly/apt-
xapian-index on a server with 512MB memory with a web server and
database server running leads to this bug. That cron job calls /usr/sbin
/update-apt-xapian-index, which is a Python script that imports axi and
axi.indexer.
Thats what i get on RR i386, logged as gnome-classic:
Traceback (most recent call last):
File /usr/sbin/update-apt-xapian-index, line 97, in module
indexer.slave()
File /usr/lib/python2.7/dist-packages/axi/indexer.py, line 454, in slave
childProgress = ClientProgress(self.progress)
@marvin24: Thanks for the hint!
zcache seems not to be enabled in my system (but the head of dmesg can
be cut off).
Is there another way to tell whether zcache is enabled?
Still, even if it were enabled, I doubt that I wouldn't notice this
extra-heavyweight program.
** Also affects: ac100
dmesg cant be cut off in /var/log/dmesg, thats the file where your dmesg
output gets dumped to right after boot, just grep in there instead of
piping teh dmesg output to grep ...
zram is enabled by default in all ubuntu ac100 images cat /proc/swaps
should confirm this ...
--
You received this
Yes, I'm sure zram is enabled. I'm glad to know this.
But zcache is not mentioned anywhere in the logs. Has something gone
wrong? Must it have been enabled in the Ubuntu 12.04 for Toshiba ARM
that I've installed (from the wiki page)?
Where to learn how to enable it in a sensible way for this
I don't agree with the comment saying that it is not installed in Ubuntu
12.04 by default: I've installed Ubuntu 12.04 for Toshiba AC100 (ARM)
from the homepage of this project.
And I have this disaster in my system.
It shouldn't be installed by default, at least, for such weak machines
as the
Make sure zram and zcache are enabled, e.g. cat /proc/swaps and
dmesg|grep zcache. This may help in low memory situations.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/655831
Title:
The whole thing is getting ridiculous. The bug is two and a half years
old (that makes five (!) releases), there seems to be no benefit to it,
so what is the point of keeping this package?
I realise that this job is started with a very low ionice and nice value, and
it's *supposed* to not
The amount of memory it uses seems to depend on the number of packages
installed?
On my Precise netbook with 1GB ram it uses at least 150MB memory, which
pretty much always causes some swapping. Audio and video are completely
unresponsive for 5 minutes at a random time almost every day.
Sucks if
I think the simple workaround is to uninstall it if you don't need it:
sudo apt-get purge apt-xapian-index
Getting it to play more nicely could be difficult; it already uses both
nice and ionice from what I can see.
A default install of Lubuntu 12.04 (as of the 2012-03-23 daily build)
does
** Changed in: apt-xapian-index (Ubuntu)
Importance: Undecided = High
** Changed in: apt-xapian-index (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Lubuntu, on a 600 MHz Celeron with 128MB of RAM (!), this process really,
truly bogs the system down :-)
It uses 79MB of physical ram... which means the entire rest of the system is
swapped out.
It never completes.
--
You received this bug notification because you are a member of Ubuntu
Same problem here - using Ubuntu 11.10, kernel 3.0.0-15-generic.
Uses 100% of one core.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/655831
Title:
update-apt-xapian-index bogs down system
To
This bug is still extant on 11.10. Checked the anacron job and nice is
set to 19, but it still maxed out my dual-core E8400 and caused music
playback to stutter horrifically. That's a bit ridiculous for a
background maintenance job.
--
You received this bug notification because you are a member
I purged this package and found no problems with Synaptic or Software
Centre. However the update-apt-xapi process always used to cause my
(single core Intel Celeron) computer to run so slowly as to be unusable
(on Ubuntu 11.10).
I think this package should not be included in the default
Also happens on Ubuntu 11.10
This is especially painful when you have a single core machine and 1GB of RAM.
The CPU use is somehow tamed by nice, but not the memory use.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also happens on Ubuntu 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/655831
Title:
update-apt-xapian-index bogs down system
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 363695 ***
https://bugs.launchpad.net/bugs/363695
** This bug has been marked a duplicate of bug 363695
update-apt-xapian-index uses too much CPU
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** This bug is no longer a duplicate of bug 363695
update-apt-xapian-index uses too much CPU
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/655831
Title:
update-apt-xapian-index bogs down system
Same problem for my Ubuntu Server 11.10, fully updated micro instance
servers running in the Amazon cloud. When it happens I can neither SSH
into them, TeamSpeak server starts lagging immensely and my blog is no
longer connectable to. The problem I solved by removing the package, but
it is quite a
ubuntu 10.10, apt-xapian-index 0.39ubuntu1
This happened to me this morning.
i5 CPU, 4gig ram.But my computer was under heavy load already.
Completely froze for a few minutes, hard disk light on constantly.
It's probably allocating too much memory somewhere cause top says I've used
1.3gig
On my 2,9Ghz dualcore this generally doesn't cause problems, however,
I'm typing this message on a Pentium 3 laptop with lucid. 850Mhz, 384MB
RAM minus some for integrated video, which also ruins RAM performance.
You don't want update-apt-xapian-index on this machine.
Maybe it would be an idea to
Same problem here with Kubuntu 10.10, apt-xapian-index 0.39ubuntu1. On
my notebook with Celeron M 1,3 GHz processor RAM 512 MB shared (464
available for the system) this process takes up to 91% CPU and eats the
whole memory so that the system nearly freezes (takes up a a minute to
open kickoff
I do not understand the purpose of this piece of software.
It seems that when I found out about it and removed it, the only
functionality I lost was being able to quickly search using the
toolbar in Synaptic?
Surely that's not worth heating up my computer for.
I manage fairly well with Ctrl+F to
@Tormond: Actually the indexer (IMO) should work as a background job
using CPU (limited) when idle. Instead it takes control of the system
regardless of what is running. It causes issues with other applications,
creates a possible hardware issue, etc. I do however agree with your
last comment that
NoOp, if nothing else is running, you would want the indexer to use all
CPU available so that it finishes as soon as possible (before you want
to use the machine for instance). And full CPU makes the fan spin up for
a while, that is just healthy (although I admit I hate to hear the fan
spin up
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/655831/+attachment/1675388/+files/Dependencies.txt
--
update-apt-xapian-index bogs down system
https://bugs.launchpad.net/bugs/655831
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: apt-xapian-index (Ubuntu)
Status: New = Confirmed
--
update-apt-xapian-index bogs down system
https://bugs.launchpad.net/bugs/655831
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
$ sudo update-apt-xapian-index
On 10.04.1 32bit 2.4Ghz/1GiB:
from top:
32305 root 20 0 99.9m 83m 4636 R 84.9 8.3 1:06.20 update-apt-xapi
84.9% CPU - and I've seen it get as high as 99%. Fans kick in, system
respones slow during the update.
On a 10.10 64bit (updated as of
Yes, I think also that bug 131094 is responsible for this.
NoOp, note that when update-apt-xapian-index is run automatically, it is
launched with nice and ionice to be less intrusive, so benchmarking
with calling it directly is not correct. And high CPU usage is perfectly
normal if it runs alone.
It is the accumulation that is destroying the performance. Try playing
an intensive game when that process decides to kick in and all hell will
break loose with the computer.
What is the point of this Xapian index other than for the quick search
function of Synaptic? It seems EXTREMELY useless to
On 10/06/2010 01:24 PM, Tormod Volden wrote:
Yes, I think also that bug 131094 is responsible for this.
NoOp, note that when update-apt-xapian-index is run automatically, it is
launched with nice and ionice to be less intrusive, so benchmarking
with calling it directly is not correct. And
57 matches
Mail list logo
