-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Error in uwsgi script #194
Comments
On Tue Jan 14, 2025 at 4:01 PM CET, Agata Savary wrote:
When starting the FLAT docker container, we also have the following errors in logs:
`Running migrations:`
` No migrations to apply.`
`chown: cannot access 'dbparseme': No such file or directory`
`chmod: cannot access 'dbparseme': No such file or directory`
You can ignore these if you have a MySQL database, it's not a problem.
I'll apply a small fix to suppress these needless warnings.
`Starting FLAT via uwsgi...`
I'm not sure if it comes with FLAT or if it originates from our custom configuration.
We do have a dbparseme database:
***@***.***:~/mysql_data$ sudo ls dbparseme/`
`auth_group.frm auth_permission.ibd auth_user_user_permissions.frm django_content_type.frm`
`...`
Ok, but this is served via MySQL, FLAT/foliadocserve doesn't need direct
file access here, so this is fine.
I would be grateful for any hint...
Access to the database is working right? All starts fine? The log doesn't really indicate a
problem either.
|
Thank you. |
When starting the FLAT docker container, we also have the following errors in logs:
Running migrations:
No migrations to apply.
chown: cannot access 'dbparseme': No such file or directory
chmod: cannot access 'dbparseme': No such file or directory
Starting FLAT via uwsgi...
I'm not sure if it comes with FLAT or if it originates from our custom configuration.
We do have a dbparseme database:
parseme@parseme:~/mysql_data$ sudo ls dbparseme/
auth_group.frm auth_permission.ibd auth_user_user_permissions.frm django_content_type.frm
...
I would be grateful for any hint...
The text was updated successfully, but these errors were encountered: