Solr Re-index url not working on production

[fouada]

Hi

I am using below url to fix one non searchable file's solr index on production server.

https://production-ip:8443/solr/admin/cores?action=REINDEX&nodeid=1788

But I am getting no response from above url.

Steps followed :

1) Copied the browser.p12 from   <INSTALLATION-DIR-ALFRESCO>\alf_data\keystore\ from production server to local system.

2) Imported the copied file in browser.

3) Executed the above url , but it gives no response and not re-index the file.

Is it ok , if I have copied the browser.p12 file from production to local system and then imported it in browser ?

If above steps is not correct , then is there any other process to make above url working?

Thanks,

Fouad

[jpotts]

Are you using solr or solr4? Your URL indicates solr, but if you are running on the latest stable version you are probably running solr4. If you are running solr4 your URL should be /solr4, not /solr.

If you go to https://production-ip:8443/solr/admin/cores do you get a response?

[fouada]

Thanks for Your Reply Jeff, I am using Alfresco 4.1 and it uses "Solr 1.4" .

It is executed successfully now but it didn't made the file searchable.

I had searched this file by using node browser selecting lucene as search type but no result came this made me think that may be its indexing is not done. But Re-indexing URL below have not made it searchable

https://production-ip:8443/solr/admin/cores?action=REINDEX&nodeid=4805

Please suggest how can i find root cause of some file being not searchable and solution to make them searchable.

Thanks in advance.

[ycoulon]

Hi,

Take a look a documentation at the documentation for version  4.1 : Solr monitoring and troubleshooting | Alfresco Documentation

Yann

[fouada]

Thanks Yann, But I have tried below URL

https://production-ip:8443/solr/admin/cores?action=REINDEX&nodeid=4805

Seeing this only Solr monitoring and troubleshooting | Alfresco Documentation

I dont think it is problem of solr index.

Thanks,

Fouad

[ycoulon]

That's why I gave this link.

For the 4.1 version, you don't have to use ssl.

Use the following ulr pattern:

http://localhost:8080/solr/admin/cores?action=REPORT&wt=xml

Regards

[fouada]

Hi Yann,

I have tried this above URL pattern and got below error

Secure Connection Failed

An error occurred during a connection to lit-vaaf-p001.gxsonline.net:8080. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG

    The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.

    Please contact the website owners to inform them of this problem.

Learn more…

Report errors like this to help Mozilla identify and block malicious sites

And this https://production-ip:8443/solr/admin/cores?action=REINDEX&nodeid=4805

return below xml in response

<response>

<lst name="responseHeader">

  <int name="status">0</int>

  <int name="QTime">0</int>

</lst>

</response>

Is there any other way or alternatives?

Thanks,

Fouad

[ycoulon]

Hi,

The return XML seems fine. The action seems to be executed without any errors. Maybe the issue is not with SolR.

Can you tell us a little more on the file ? Mimetype ? Upload path ?

How do you search that file ? Using live search ? Advanced Search ? Javascript ?

Regards

[fouada]

Hi Yann,

There are many files in the repository with same Mymetype and are searchable. I am searching this file using advance search.

and I have also tried to search it with node-browser using lucene as search type and it also didn't returned the file.

Thanks,

Fouad

[ycoulon]

Hi,

Ok, Is the node visible when browsing to the parent folder ?

Using the node browser have you try to search using the PATH syntax ?

For example for the nodes in documentlibrary of swsdp site the query look like :

PATH:"/app:company_home/st:sites/cm:swsdp/cm:documentLibrary/*"

You can retrieve the parent path using the node-browser.