Replies: 3 comments 7 replies
-
|
The SLF4J message is probably just a red herring. Time to look into indexer logs (configured in the |
Beta Was this translation helpful? Give feedback.
-
Hi vladak, thank you for answering and for the support. For some reason (probably a miss configuration) no logs are seem to be generated in the path described in the if I'm not wrong is configured as suggested in the documentation: https://github.com/oracle/opengrok/wiki/Debugging . If I check the processes running in the node when the indexer command is running I can see the following ouput: With this in mind, let me try to understand what is happening behind; If this is correct, I checked the PID 91135 and the temp files specified in the fileds:
and everything seems correct, the first one is a copy of the Please, if you need more information just let me know and I'll provide it. |
Beta Was this translation helpful? Give feedback.
-
|
The To sum this up, the |
Beta Was this translation helpful? Give feedback.
-
|
After restarting the docker container (customized self-made image) and executing the reindexing process again now some logs were generated, attaching here: I'm reindexing an AOSP project, but all I see are WARNING messages, not sure if this caused the process to fail. Many thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Although they are probably not fatal, the |
Beta Was this translation helpful? Give feedback.
-
|
For the record, this warning is displayed when |
Beta Was this translation helpful? Give feedback.
-
|
Also, this displays just a fragment of the indexer log. Normally the indexer log will end with a bunch of log messages like so: If the indexer fails for some reason, the cause should be clearly visible in the log, unless it was terminated externally (e.g. via the Linux OOM killer or such). |
Beta Was this translation helpful? Give feedback.
-
|
I have changed the reindexing command as you suggested in the comment, now the command looks like the following: Now it's generating the logs in the project directory under the logs path specified in the logging.properties (Thank you for the help here), but if I check it it doesn't tell me what the error or failure is, I even increased the logging level to FINE, this a snipped of the output: as you can see everything looks good, even the WARNINGS are not shown, only INFO and FINE messages, but suddenly it throws the error message at the end. Thank you |
Beta Was this translation helpful? Give feedback.
-
|
The message opengrok/tools/src/main/python/opengrok_tools/reindex_project.py Lines 151 to 152 in dcf1091 The return code reported there comes from which is what returns.The return code is In the Python
So the indexer process was killed by So to sum this up, either use a operating system that does not overcommit memory or tame the OOM killer. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @vladak , Thank you for you answer and support, you were absolutely right, it was an OOM issue all from the begging. Other change implemented was in the Thank you once again for all the support and help, I really appreciate it! |
Beta Was this translation helpful? Give feedback.
-
Hi everyone,
Not so long ago some of my projects started to face the following issue when performing the opengrok-reindex-project command.
Error Output:
I'm using the per project management structure, the command I'm running is:
Somehow I think the error is related to the #2130 issue, aka when the index finds a file that contains one immense term or when special characters are found. I'm saying this because before facing this issue I was facing the one specified in the #2130, but after implementing OPENGROK_ALL_NONWHITESPACE=on as an env. variable as suggested in the #2104 the old error apparently disappeared and this new error started showing.
I tried looking for this error in the community, but I didn't find a solution to my case.
I would appreciate all the help you could give me, thank you so much!
Opengrok version: 1.7.2
Tomcat version: 10.0.5
Git version: 2.17.1
Beta Was this translation helpful? Give feedback.
All reactions