Open garethrees opened 4 years ago
I expect what's happened is that wvText
has been killed due to memory or timeout constraints but we haven't registered that in the parent process (see https://askubuntu.com/a/201308).
For now I've just killed the Xapian processes.
I've also marked the event for indexing, so we'll see if it happens again or whether it's just a one off.
e = InfoRequestEvent.find(7332184)
e.xapian_mark_needs_index
Will reopen if it gets stuck again.
This has happened again:
$ ps aux | grep "^foi\s" | grep -E "(xapian|defunct)"
foi 12202 0.0 0.0 4276 768 ? Ss 16:25 0:00 /bin/sh -c /usr/bin/env XAPIAN_MAX_CHANGESETS=10 run-with-lockfile -n /data/vhost/www.whatdotheyknow.com/change-xapian-database.lock "/data/vhost/www.whatdotheyknow.com/alaveteli/script/update-xapian-index verbose=true" >> /data/vhost/www.whatdotheyknow.com/alaveteli/log/update-xapian-index.log || echo "stalled?"
foi 12233 0.0 0.0 4164 680 ? S 16:25 0:00 run-with-lockfile -n /data/vhost/www.whatdotheyknow.com/change-xapian-database.lock /data/vhost/www.whatdotheyknow.com/alaveteli/script/update-xapian-index verbose=true
foi 12289 0.0 0.0 4276 712 ? S 16:25 0:00 sh -c /data/vhost/www.whatdotheyknow.com/alaveteli/script/update-xapian-index verbose=true
foi 12327 0.0 0.0 33612 3056 ? S 16:25 0:00 /bin/bash /data/vhost/www.whatdotheyknow.com/alaveteli/script/update-xapian-index verbose=true
foi 12362 99.7 0.2 668228 140932 ? Rl 16:25 74:18 /data/vhost/www.whatdotheyknow.com/alaveteli-2020-07-27T11-52-07/vendor/bundle/ruby/2.6.0/bin/rake --silent xapian:update_index verbose=true
foi 13050 0.0 0.0 0 0 ? Z 16:25 0:00 [wvText] <defunct>
Happened again (~08:00 – 10:00); killed.
update-xapian-index
has been stuck since midnight (9 hours).Looks like its a problem due to
[wvText] <defunct>
:The last event in the log is a response containing some word docs:
At the moment, both HTML extractions of the attachments are just blank: