Added by Bernd Müller about 9 years ago
Today I tried to bundle let’s encrypt ssl certificates and OP.
It worked. So I had a working + valid https.
But during that process I accidentally “configure”d OP instead of “reconfigur(e)”ing it.
So I guess that I updated OP to the latest version (though I still can see that 5.0.7 is displayed…maybe I have 5.10, maybe not)
Anyways! The main problem is now, that I cannot not see my work packages any more
When I click on work packages I can see that URLs are generated in that form:
<host>/projects/<name_of_project>/work_packages?query_props={%22f%22%3A[{%22v%22%3A2%2C%22n%22%3A%22type_id%22%2C%22o%22%3A%22%3D%22}]%2C%22t%22%3A%22updated_at%3Adesc%22}
The logs do not give me a clue:
, [2016-01-26T15:10:41.564677 #10762] WARN -- : hook registered W, [2016-01-26T15:53:44.935472 #14797] WARN -- : hook registered W, [2016-01-26T16:42:47.193565 #20397] WARN -- : hook registered W, [2016-01-26T17:11:14.226456 #22977] WARN -- : hook registered W, [2016-01-26T17:21:35.329868 #24253] WARN -- : hook registered
But in my browser I just see a while sheet.
Now what can I do? Any hint is appreciated
Replies (8)
Hey Bernd,
running
openproject(-ce) configure
should not update the application nor break it per se. It simply re-runs the installer using the configuration items persisted in/etc/openproject-ce/installer.dat
and should be idempotent and thus not break your app. An update is installed through your package manager, and runningconfigure
would only run new installer steps.Could you provide me with the following:
1. The content of installer.dat above (passwords redacted)
2. The output of the apache2 error log (
/var/log/apache2/error.log
)BTW: You can check the OpenProject version by running
sudo openproject run bundle exec rake version
.Best,
Oliver
Hi!
Thanks for your feedack. Would be great if we´d figure out what´s happening there:
installer.dat looks something like this:
the error.log contains this here….maybe this gives a hint:
Hmm….what makes me wonder, why is the openproject looking into /home/openproject? This location is the place where my “old” manual insallation was running. I change to the packaged installer as the manual setup cause some issue. I guess that I should setup the ENV to /opt/openproject. Not 100% sure show to…maybe you got a clue. But unfortunately I am not sure if this is really related to my issue, could be tough…
I have restarted the apache, this is shown after a restart, semms ok in my eyes:
The log within openproject says following
Does this make any sense to you?
Cheers!
Ah!
I guess that I got a little step further -> I guess my problem could be related to my old apache.conf that I created while using the manual installation, here is see
When I do a “ruby -v” I get
I should see 2.16, right?
Also i forgot to mention that my drop down boxes refuse to drop down. sigh
The packaged installation does not use packager, but uses unicorn. There should only be one
openproject.conf
site in apache2 that includes most of its configuration from/etc/openproject/addons/apache2/includes/{vhost,server}/*
.So I assume that you’re request is actually going to the old installation (or some weird state in between) which would explain why the log remains empty in the packaged installation.
The packaged installation always lives at
/opt/openproject
and does not require configuration regarding that path.Best,
Oliver
Hi!
Thx bro, for your support!!
You were very right, in apache.conf I had still old stuff that I forgot to disable.
Now I see following issue in apache´s error.log:
and in deed these .js were not generated in the /opt/openproject/public/assets/. Now how should create these.js?
Does that ring a bell, maybe?
Cheers!
That’s weird, since the package should contain all required assets.
You can still force a recompilation of assets with
sudo openproject run bundle exec rake assets:precompile
OP lives again. I simply rebooted the server and tata all back to normal. Lord! :-/