New repos are not marked as indexed in webapp

[anvesh-k99]

Hi,

i tried adding a new repo to opengrok and it got indexed successfully but it is not available in the UI. When checked the index logs found as below.

Could not notify the webapp that project xxx: indexed=true, history=true was indexed

I am using opengrok version 1.13.25. Can someone please help to fix the issue.

[vladak]

A project will become visible in the webapp if the webapp knows about it and it is marked as indexed. This is what the API call made by indexer at the end of successful indexing does.

How do you run the indexer exactly ? Is the webapp actually running during the indexing ? If yes, what is in the webapp logs ?

[vladak]

Do the webapp logs indicate new configuration is set into place when the indexer completes ?

[anvesh-k99]

Do you mean in the logs of the indexer. I do not see anything as such

[vladak]

No, I mean the webapp logs. For example in Tomcat there is usually a log file called catalina.out. In my testing with brand new projects not known to the webapp, at the end of the indexing (with -U) the webapp logs look like this:

16-Jun-2025 12:14:59.363 INFO [OpenGrok-api_task-configuration-517] org.opengrok.indexer.util.Statistics.logIt Done invalidating repositories (3 valid, 3 working) (took 409 ms)
16-Jun-2025 12:14:59.363 INFO [OpenGrok-api_task-configuration-517] org.opengrok.indexer.configuration.RuntimeEnvironment.applyConfig Configuration updated
16-Jun-2025 12:14:59.363 INFO [OpenGrok-api_task-configuration-517] org.opengrok.indexer.configuration.RuntimeEnvironment.maybeRefreshIndexSearchers refreshing searcher managers
16-Jun-2025 12:14:59.364 INFO [OpenGrok-api_task-configuration-517] org.opengrok.indexer.util.Statistics.logIt Done refreshing searcher managers (took 0 ms)
16-Jun-2025 12:14:59.364 INFO [OpenGrok-api_task-configuration-517] org.opengrok.indexer.configuration.WatchDogService.stop Watchdog stopped
16-Jun-2025 12:14:59.364 WARNING [OpenGrok-api_task-configuration-517] org.opengrok.indexer.framework.PluginFramework.reload Plugin directory '/private/var/opengrok/data/../plugins' not found or not readable: All requests allowed.
16-Jun-2025 12:14:59.364 INFO [OpenGrok-api_task-configuration-517] org.opengrok.indexer.configuration.RuntimeEnvironment.applyConfig Done applying configuration

This effectively tells the webapp to recognize the new project and given it has the indexed flag set to true, it will become available in the UI (and REST API as well).

[vladak]

You can check that the webapp posseses knowledge about particular project by using the REST API e.g. as follows:

$ curl -s http://localhost:8080/opengrok_web_war/api/v1/projects | jq
[
  "foo",
  "mercurial",
  "Lucene"
]

Then the indexed flag of the project can be checked using another API call:

$ curl -s http://localhost:8080/opengrok_web_war/api/v1/projects/foo/property/indexed 
true

Of course, in your case you will have to change the URL to match the location of your webapp.

[vladak]

Another piece of information that might shed some light on this is whether the webapp displays the new project in the UI after the server is restarted or the webapp redeployed. And whether the project and related repositories are actually present in the configuration.xml file written by the indexer.