search

ufal / lindat-kontext

An alternative web front-end for the Manatee corpus search engine
GNU General Public License v2.0
5 stars 1 forks source link

Unable to open database #202

Open Ansa211 opened 6 years ago

Ansa211 commented 6 years ago

These days, I am having strange access problems on kontext-dev, and now also on production.

Production: while this query works ok, applying a positive filter gives me "Access forbidden". It even does not list the "Last used corpus" that I've seen with similar errors (maybe on kontext-dev???). I am not logged in, so it may be that I should log in to apply a positive filter - but then clicking on it should be disabled.

kontext-staging/ansa: it seems to me that sometimes I get an error, or kontext-dev hangs in the middle of loading the concordances (the headers and background are there but the space for concordance lines is empty) and after a few minutes, the very same query works ok. I logged onto quest and found the following in /var/log/apache2/error.log:

[Mon Jun 11 22:09:50.068578 2018] [proxy:error] [pid 27417] (111)Connection refused: AH00957: HTTP: attempt to connect to 192.168.0.45:8097 (kontext-dev) failed
[Mon Jun 11 22:09:50.068635 2018] [proxy:error] [pid 27417] AH00959: ap_proxy_connect_backend disabling worker for (kontext-dev) for 60s
[Mon Jun 11 22:09:50.068659 2018] [proxy_http:error] [pid 27417] [client 195.113.20.155:38822] AH01114: HTTP: failed to make connection to backend: kontext-dev
Ansa211 commented 5 years ago

Update after updating production to new version: I have not experienced any problems of the reported kind yet, BUT both of the links above (as well as some other links in past bug reports) give me "unable to open database file". Removing the q~...& part from the address bar solves the issue, so I suppose the "database" in question is some hash table with past queries.