Hi Ramon,
did you check:
* Robinhood log file for errors?
* are queries still running on the database?
We have also faced the situation, were Robinhood got stuck after a fullscan was
finished.
In our case, there were database errors reported in the Robinhood log file.
After killing all Robinhood processes, there was still running a database query
for days...
Next fullscan attempt also got stuck then.
In the end I had to kill the query on the database and also purge the database
to get a fullscan with exit.
I would recommand you also to run another fullscan to check if it exits after
completion.
Just to check, if you do not have the same error...
Regards,
Gabriele
________________________________________
From: Ramon Williamson <ramon.williamson...@gmail.com>
Sent: Thursday, February 11, 2021 22:04
To: robinhood-support@lists.sourceforge.net
Subject: [robinhood-support] Initial scan does not exit after first pass
I have been trying to get robinhood working on a CentOS 7 machine with Lustre
2.12.
When I run the initial scan of the filesystem, it completes in about 5 hours,
but the output continues hours afterward with no threads doing any scanning. I
have had to kill the process in order to get it to stop.
I have used robinhood for year on RHEL 6 and have not had this problem. Is
there something I need to so differently to get the desired behavior for the
"robinhood --scan --once" command?
Thanks for any suggestions.
Ramon Williamson
--
Time flies like an arrow, fruit flies like a banana.
-- Groucho Marx
_______________________________________________
robinhood-support mailing list
robinhood-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/robinhood-support
