[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[EP-tech] [3.4.2] Wrong status of indexer on the admin site


This is an interesting issue.? When you go to the main Admin menu page 
under the System Tools tab what buttons are available for starting and 
stopping the indexer?? What drives whether the Admin status page stays 
Running, Stopped, etc. is the presence of the file:


and whether there is an indexer process running with the process ID 
stored in this file.? Also the presence of the file 
/usr/share/eprints/var/indexer.tick may affect the status you see.? At 
best guess? the indexer is running but under a different process ID to 
that in indexer.pid.? It should be noted that if your run something like:

ps aux | grep indexer

You would get two processes back (three if you include the "grep 
indexer" process in the command above).? The first is the parent process 
and this should have the process ID that is in indexer.pid and the 
second is a child process.? The latter is vulnerable to dying if the 
indexer task it is undertaking fails in certain ways.? The parent 
process should spawn a new child process if this happens.

Normally what I would do to clear things up is stop the indexer from the 
command line.? Then if any indexer processes are still running use the 
Unix kill command then kill these.? Then finally make sure that the 
/usr/share/eprints/var/indexer.pid and 
/usr/share/eprints/var/indexer.tick files are no longer present and 
delete if they are.? Then I would go back to the web interface to check 
the indexer's status (to ensure it is stopped) and hopefully then use 
the Admin page's "Start Indexer" button to restart the indexer.? This 
should get things back in a consistent state and hopefully the=is 
inconsistency will not re-occur.

Hope this helps.? Please let me know if this does not solve your problem.


David Newman

Subject:? [3.4.2] Wrong status of indexer on the admin site
From:? systems <systems at mdc-berlin.de>
Date: 27/01/2021, 07:28
To: <eprints-tech at ecs.soton.ac.uk>

Hi list,
I try to get eprints working on CentOS8.
As far it looks working, but the on the admin status page, the indexer 
is marked as stopped. But it runs and the task queue is empty.

systemctl tells, that it is running and
sudo -u eprints /usr/share/eprints/bin/indexer status
Indexer is running with PID 10960. Next index in 27 seconds

How will the status page check the state of the indexer?

for any hints.

*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&amp;data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cee3fc352e5254122cada08d8c2a7d504%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637473373370180401%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=DruZwRSeEu15jrGJZS%2Bg3X8Jr42brVjk%2Fy%2B%2BLRw2NJA%3D&amp;reserved=0
*** EPrints community wiki: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.eprints.org%2F&amp;data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cee3fc352e5254122cada08d8c2a7d504%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637473373370180401%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=Q67Uh6bhQLoKndwI3jYDja1z%2FTtm89fuYZHWetMx0qg%3D&amp;reserved=0

This email has been checked for viruses by AVG.