-
Notifications
You must be signed in to change notification settings - Fork 44
Backup Errors & No "Stats" #419
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
Comments
Just tested it, backups are working fine |
Great...so I have 2 problems I guess. Thanks! |
Hi! I could recreate the database iissue by removing Did you replace the |
I just updated again with the new One note, I did have to change the port for redis in my docker compose file, I had another redis container on that port and it seemed to be causing some issues. I changed this to
1:M 14 Apr 2025 00:21:59.005 * Background saving started by pid 22 22:C 14 Apr 2025 00:21:59.488 * DB saved on disk 22:C 14 Apr 2025 00:21:59.489 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB 1:M 14 Apr 2025 00:21:59.507 * Background saving terminated with success In my webserver log I see this, which I assume means websockets is running correctly:
2025-04-14 00:13:13,304 INFO spawned: 'apache2' with pid 13 2025-04-14 00:13:13,305 INFO spawned: 'backup' with pid 14 2025-04-14 00:13:13,306 INFO spawned: 'horizon' with pid 15 2025-04-14 00:13:13,307 INFO spawned: 'websockets' with pid 16 2025-04-14 00:13:14,745 INFO success: apache2 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2025-04-14 00:13:14,745 INFO success: backup entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2025-04-14 00:13:14,745 INFO success: horizon entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2025-04-14 00:13:14,745 INFO success: websockets entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) |
It seems to be a websocket issue. From the logs:
|
@TheNomad11 Any luck fixing this? |
I have no idea, is it a nginx issue? Do you have the same error or any idea how to fix it @giuseppebaldi ? |
It looks like we have the same problem but potentially different causes, I don't know. I am not having the same websocket error you're having, in fact, I don't seem to have any errors in my container logs. I tried recreating the whole stack from scratch because I didn't have this problem when I first installed it, but immediately had the same issue. I've tried the new compose file and, like you, that didn't seem to have any effect. Not sure what to do next honestly. |
Yes, you should add
I don't think I use nginx or other revers proxy anywhere.
It is normal. 6001 port is used for websockets. It sends data to your browser without needing to refresh the pages. I think it is used at 2 places: loading data for chapters in an opened book, and importing a dictionary. You can test if it works the easiest if you try to import a larger dictionary. If you see the progress bar going, it is working. I have an idea what could have happened for both of you. Importing happens in the background, and the import jobs are stored in redis. If you start an import, but the redis server does not work, then the importing never starts. In this case if you fixed the redis server, it will be empty, but the chapters are still marked as "importing" in the database, and they are stuck. There is already a ticket for it: #404. If this is the case, and you can confirm that your redis server and websockets are working, you can fix this by changing chapter statuses in the database from This would only fix this very specific issue, where the chapters have the yellow/orange importing state next to them. On the images where chapters are not being imported, but still not getting their data streamed in I don't know what causes the issue, but it will be redis/websockets. |
After a reinstallation, I think it may have something to do with this, some sort of permission error in redis: My linguacafe directory has folder with different owners & groups. Some are owned by a "docker-user" I created and some are owned by user 999, they are all in group 999. I changed them all to 999:999 but I am not sure that fixed it, I still get hung up on importing new chapters. What's a better fix for this? What should the folder permissions be? |
Ok, I finally fixed this. I did a fresh install, after containers were created but not started yet I did |
I now get
Maybe I also need to make a clean installl EDIT: Same issue with new install, the errior messages disappeard though, maybe I should try another server or go back to v13 which worked fine... |
Are you using the default docker setup, or something custom? Can you please post your docker-compose.yml file? Sorry for the late responses, been busy last few weeks. |
Hi @simjanos-dev thanks and sorry for the trouble, you have enough things to do, and it might anyway boil down to my own stupidity.... I use the standard compose file, but maybe i messed something up, I also tried using an .env file without luck
Out of curiosity i sometimes used the .emv file
|
One note I would like to make: when accessing the application from the local ip and port the book/chapter stats show up just fine but when trying to access through a custom domain it shows the screen where it looks like the stats are constantly loading. No big deal but thought I would mention in case there's an easy fix to address that behavior (not sure why it would be different but it is). |
yeah, same for me @giuseppebaldi that means probably that's a reverse proxy issue. something must be changed related to websockets maybe? |
With help from Chatgpt I found the solution. If you use a nginx reverse proxy you have to add this in the server block:
and maybe also
restart nginx and problem solved (at least for stuff you will add and edit from now on)! |
Glad you got that fixed. I am not using nginx so your solution won't help me. I am just accessing through a cloudflare tunnel. I am seeing websocket errors in the browser console so I know that's the issue but I have no idea how to fix this via cloudflare. |
Not sure that it won't help you. The thing is that |
I was having this issue so I deleted the application and did a fresh install with new database, etc. Unfortunately, I am still having the exact same issues. When attempting to do a backup, I get an error: "An error has occurred while exporting your database."
On top of that, I am not seeing any statistics on book chapters (Total words, unique words, etc); I just get a perpetual "loading" animation across those fields.
I am not seeing any errors in horizon.log, below is from laravel.log:
The text was updated successfully, but these errors were encountered: