Closed miguel-negrao closed 11 months ago
@gdicristofaro I think you might be the right person to look at this one. Thanks.
Hi @miguel-negrao , could you please also include the logs in ~/snap/autopsy/common/.autopsy/dev/var/log/
for the files: autopsy.log.0
, messages.log
, solr.log.stdout
, and solr.log.stderr
?
I'm getting the following behaviour:
If I delete all files in ~/snap/autopsy/common/.autopsy/dev/var/log/
I no longer get an error now when creating a new case. No ideia if it is related or not, could just be coincidence.
If I try to open an old case, I still get the same error. See the files you requested in this gist.
What seems to happen is that If I open an old case Solr fails, and from then on if I create a new case it also fails to start solr. But If I close autopsy and open again and create a new case then solr starts ok. It doesn't seem to be related to deleting the log files. It could just be random also...
Hello again @miguel-negrao ,
I'm not seeing anything readily apparent. Did you happen to have a solr.log.stdout
file by any chance? I'll try to circle back to this soon to see if I can debug, but my initial thoughts are these:
ps aux | grep solr
.solr.log.stderr
, I see a usage error, which makes me think that the autopsy solr startup or stop script are somehow providing illegal arguments. If there is a solr.log.stdout
, that would be helpful in this situation.Every file in "~/snap/autopsy/common/.autopsy/" has the correct permissions "miguel:miguel" which is my username. All files of the autopsy case also have the same owner (miguel:miguel).
There are no solr instances left running, ps aux | grep solr
gives nothing.
The content of solr.log.stdout
is:
Sending stop command to Solr running on port 23232 ... waiting up to 180 seconds to allow Jetty process 382234 to stop gracefully.
[|] [/] [-] [\]
Hi @miguel-negrao , would you be willing to share the case at /home/miguel/tmp/test_autopsy21_2
? When did you make that case by the way if you happen to remember? Short of that or in addition, could you share:
/home/miguel/tmp/test_autopsy21_2/SolrCore.properties
~/snap/autopsy/common/.autopsy/dev/solr/logs
~/snap/autopsy/common/.autopsy/dev/solr4/logs
if you have anyHi @gdicristofaro, I've sent you the case in a zip file to your gmail.
Hi @miguel-negrao ,
I believe the issue is that the older cases likely use Solr 4. You should be able to verify this by looking in SolrCore.properties
and you should see something like: <SolrVersion>4</SolrVersion>
. Autopsy moved on to Solr 8 a few years ago. I think what is happening is that when Autopsy opens the older cases, it has issues running Solr 4 when we are now running with Solr 8. Then, when you go to open a new case, Solr had issues starting up previously and the new case also fails.
Here are some workarounds:
SolrCore.properties
. This will cause Autopsy to generate a new SolrCore.properties
file using Solr 8. If you need to do any text indexing (i.e. ad hoc searches), you will first need to rerun Keyword Search on the images in the old case to re-index the case in Solr 8. You can do this by right clicking on the image in the tree, going to 'Run Ingest Modules', and selecting 'Keyword Search' with the 'Add text to Solr index' selected.
Hi, indeed the case I was using for testing was using solr4. I've tested again with an old case but with solr 8 and everything works fine. I suggest that perhaps you could check SolrCore.properties
at startup and display a warning saying that this case uses solr4 and ask weather to update to solr4 invalidating the keyword search (deleting the SolrCore.properties
file), or close the case.
Hi
I run Debian 12, and installed Autopsy 4.21 from github via snap. I've enabled all connections for the snap using the command line suggested in the readme:
When creating a new case or opening an old one, in almost 90% of the times (but not 100%) I get an error related to solr:
The only time when I don't get the error is when creating a new case in a specific directory in a specif volume, which is quite misterious.