-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
"/startup.sh: line 57: [: =: unary operator expected" when "SESSION_DRIVER" is not defined #9705
Comments
Why would |
It has a fallback / default defined in session.php so there is technically no need to define it. |
derdeagle
added a commit
to derdeagle/snipe-it
that referenced
this issue
Jun 12, 2021
If SESSION_DRIVER is not defined it leads to a syntax error.
11 tasks
snipe
added a commit
that referenced
this issue
Jun 23, 2021
Fixes #9705: Prevent syntax error in startup.sh
PetriAsi
pushed a commit
to PetriAsi/snipe-it
that referenced
this issue
Jul 15, 2021
If SESSION_DRIVER is not defined it leads to a syntax error.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please confirm you have done the following before posting your bug report:
Describe the bug
I am running Snipe-IT version 5.1.6 in docker via the official images and I noticed the following message during startup of the container.
Jun 12 11:36:19 SERVER_FQDN docker-compose[3318935]: snipeit_1 | /startup.sh: line 57: [: =: unary operator expected
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should be cought.
Screenshots
Server (please complete the following information):
Desktop (please complete the following information):
Smartphone (please complete the following information):
Error Messages
/startup.sh: line 57: [: =: unary operator expected
Additional context
Add any other context about the problem here.
Please do not post an issue without answering the related questions above. If you have opened a different issue and already answered these questions, answer them again, once for every ticket. It will be next to impossible for us to help you.
The text was updated successfully, but these errors were encountered: