-
-
Notifications
You must be signed in to change notification settings - Fork 402
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
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'parent_item.pick_reason_code' in 'field list' when trying to run in docker #2291
Comments
@ZobairQ Thanks for the ticket. Can you restart OpenBoxes and see if you get the same error? And if so, what version are you deploying? |
Hello and thank you for your reply. I am getting this everytime. I did try restarting 3 times and still the error is present. |
Ok, great. Thanks for the information. I'll test it out myself and get back to you. The issue might be resolving itself though. I think we may have a timing issue with the initial creation of the view. But the database migrations always execute the most up-to-date version of the view definitions at the end. So assuming the application actually starts, just go to the Stock Card page and see if the demand value is rendered (e.g. should be 0) without an error in the logs. |
@ZobairQ I just confirmed that the issue is a bug, but that OpenBoxes should continue executing database migrations until the system fixes itself. Can you let me know what you're seeing after this error? Does docker stop on the error? |
@jmiranda the container does not stop. However it seem running and i am getting |
@ZobairQ On a normal installation it seems to be pushing 30 minutes. On docker it can take longer depending on the amount of memory allocated to the Grails/Tomcat process. See this discussion for more details about docker slowness due to memory allocation. It shouldn't be stuck for an hour so you're probably ok to kill the process. Before starting back up you'll need to increase memory (as per the discourse link above) and remove the databasechangeloglock record in the database.
|
Hello again @jmiranda, |
Yay! So glad to hear. Don't hesitate to reach if you find any other issues. If you have general questions sign up and join the #development channel on slack (http:https://slack.openboxes.com/) or post a new topic on discourse (https://discuss.openboxes.com). Best of luck. |
The text was updated successfully, but these errors were encountered: