New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenGrok home page not refreshing when index updated (NEW) #1286
Comments
Marking as stopper since it seems to be introduced by recent changes. |
I guess your repository is not public so I can not easily reproduce it...? That would really help. Have you read the flow in my comment in #1175? Does it apply to you? Can you please check the logs? Looking for some information:
|
hi Krystof, so to answer your questions.
fyi, the timestamp file is updated. index $ ls -l Let me know if there is any other info you need. |
According to what you wrote the problem is between these steps: Which means that the webapp doesn't get any configuration updates. (As you would notice the timestamp forced update is just 2 lines above). If you see If there is none of the error messages in 5., that means that the indexer successfully sent the configuration out. But it has never been received by the webapp. I don't know where to start, try to analyze:
|
something else I noticed.. so when I start up apache-tomcat I see this warning.. actually happens 3 times in a startup, which I did with a small test case.. 29-Nov-2016 11:01:56.980 SEVERE [localhost-startStop-1] org.opensolaris.opengrok.web.WebappListener.contextInitialized OpenGrok: Failed to start configuration listener thread 29-Nov-2016 11:01:57.433 SEVERE [localhost-startStop-1] org.opensolaris.opengrok.web.WebappListener.contextInitialized OpenGrok: Failed to start configuration listener thread 29-Nov-2016 11:01:57.882 SEVERE [localhost-startStop-1] org.opensolaris.opengrok.web.WebappListener.contextInitialized OpenGrok: Failed to start configuration listener thread Also, here is some info from the apache-tomcat conf/server.xml file
so not sure if there is anything here that could be amiss? |
This Possible cause:
$ lsof -i
|
Still not solving this. I have 2 versions running, but on 2 different ports, 8080, and 58080, but even if I only use one instance, I still get this error. So I guess I am still not sure what I am doing wrong. I will pose a couple of questions?
I cancel the current instance, and verify by making sure it isn't running. then every time I start up, I get the errors listed in previous runs.. eg. org.opensolaris.opengrok.configuration.RuntimeEnvironment.startConfigurationListenerThread I/O error when waiting for config: So not sure if this is related to my timestamp issue, or something I am just configuring wrong. last version of Opengrok I ran (where I didn't see this issue, is both 0.9, and 0.11.1) So anyone that help me figure out what to set would be lifesaver! :-) |
The scheme is like this for two instances: tomcat
The bind exception you got is there because the second instance would like to start the listener on port 2424 but it can't because it's already used by the first instance. Also the timestamp is not updated in the second instance because the message most probably goes to the first instance. Do not forget to kill all applications running on the 2424 port and restart tomcat after you make some changes. |
Thank you. I have gotten this to work! I didn't realize some of the new features of OpenGrok that I was never using before. :-D |
Caused by misconfiguration. Glad to hear this :) |
Hi, I noticed this issue with the new version of OpenGrok (0.13-rc4). This seems to be different from
#1175
When I create the index, everything seems to be created ok, and the data appears to be correct, except that the timestamp doesn't appear to update unless I bounce the index.
I am running on Linux Hardware, Redhat version 6.6
Using OpenGrok version 0.13-rc4
Universal CTAGS version 0.0.0
JAVA Version - 1.8.0_72
apache-tomcat version 8.5.4
Let me know if there is any other data you need. If you can figure out a fix quickly, that would be most appreciated. thanks.
The text was updated successfully, but these errors were encountered: