Skip to content
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

Error 500 On Fresh Install Of 1.3 #1117

Closed
acmeraptor opened this issue Sep 18, 2019 · 5 comments
Closed

Error 500 On Fresh Install Of 1.3 #1117

acmeraptor opened this issue Sep 18, 2019 · 5 comments

Comments

@acmeraptor
Copy link

Describe the bug
Minor/documentation. There appears to be new files/paths created between the documented step of changing file ownership/permissions and the console installation.
kimai-1.3-error.log

To Reproduce
Steps to reproduce the behavior:

  1. chown -R :www-data .
    chmod -R g+r .
    chmod -R g+rw var/
  2. (In .env file) DATABASE_URL=mysql://user:[email protected]:3306/database
  3. bin/console kimai:install -n

Additional context
Re-running the ownership/permission changes following the install step clears the error.

@kevinpapst
Copy link
Member

Hm, that shouldn't happen. Actually the caches should be pre-filled before you open the page the first time. I'll give it a try and see if anything changed.
Thanks for posting!

@acmeraptor
Copy link
Author

acmeraptor commented Sep 18, 2019

I didn't dive into the whole tree structure, but I saw that (mypath)/kimai2/var/cache/prod had somehow reverted from :www-data to :mygroup following the install step. I just ran the recursive chown/chmods to fix it again.
This is a test VM so I tried several times going back and forth between 1.2 and 1.3, it only happens on 1.3 for some reason. Hope this helps!

@kevinpapst
Copy link
Member

Can't remember when I added the change to the documentation, introducing the kimai:install command. But I guess that the updated documentation should do the trick:
https://www.kimai.org/documentation/installation.html#recommended-setup

The permission change is not necessary before the install command, as all is done by the same user.

@kevinpapst
Copy link
Member

kevinpapst commented Sep 18, 2019

What I want to say is: I changed the order: first install, then change permissions.
I hope that this will fix all issues.

Thanks for posting, yes it helps! That was important feedback and it will likely help to prevent a lot of questions by less experienced bash users ;-)

@lock
Copy link

lock bot commented Nov 17, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. If you use Kimai on a daily basis, please consider donating to support further development of Kimai.

@lock lock bot locked and limited conversation to collaborators Nov 17, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants