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

Front end looses access to current running process #165

Open
LeonvanHeerden opened this issue Dec 30, 2024 · 8 comments
Open

Front end looses access to current running process #165

LeonvanHeerden opened this issue Dec 30, 2024 · 8 comments

Comments

@LeonvanHeerden
Copy link

Running Docker instance.
Access the front end and started a book conversion of an epub file.
The process started and I could see on the Docker systems the CPU is being used by the python process lined to this container.

Since this run for a long time, I let my PC sleep over night. This morning the page shows the progress encountered an error and the counter restarted.
I refreshed the page and now it just shows that that it is ready to start a new process.
I can see in the docker output that the processing is still going.

I have no way no way to see the progress on the web front end.

@clemcer
Copy link

clemcer commented Dec 30, 2024

You can see the progress in the docker logs. You could install something like dozzle to easily look at the logs of ebook2audiobook.
And you could mount the folders from inside the container where the files are being put to any folder on your system.

See here

In the /home/user/app/tmp folder you can see sentence and chapter files being created in real time and the final result will be put into /home/user/app/audiobooks

@ROBERT-MCDOWELL
Copy link
Collaborator

ROBERT-MCDOWELL commented Dec 30, 2024

are you using GUI or headless? are you using last git docker? if it's gradio it's the biggest issue with browsers pausing or stopping when the web page is in background. there is no way to rejoin with gradio a running server background process. the best way (and I'm working on it since days) is to find a way to kill the server process when the client disconnects, and resume it when refresh or back to the page. But the client must resubmit manually the conversion, then eb2ab will resume automatically from the last sentence converted (this is already developed).

@LeonvanHeerden
Copy link
Author

Hi,
Already checked that the chapters are still being created. Will wait for it to complete and then copy the files out. Will also attempt to use a link to my filesystem, so that the files are not stored in the container/volume and I can easier work with the files.

I used the docker-compose config as is.

@LeonvanHeerden
Copy link
Author

The process completed and I could find the completed book in /home/app/audiobooks/gui/host/web-56b647ac-b07b-4743-82fa-3159fc4e3c4d/

Once I then refreshed the Gui web interface, the book was listed in the Audio books dropdown list. and there is a download link there.

If i don't do anything on that webinterface the page gives an out of memory error. I don't know if the page is downloading the file in the background and causing the page to run out of memory.

@ROBERT-MCDOWELL
Copy link
Collaborator

I don't know if the page is downloading the file in the background

you can check from the terminal you run the docker (at least)

@janstadt
Copy link

This is also happening to me as well.

@wtfrules
Copy link

wtfrules commented Jan 2, 2025

Same here

@ROBERT-MCDOWELL
Copy link
Collaborator

this is a gradio limitation, not eb2ab fault. next update a refresh will tell you if a process is still running or not.
if not, it will resume from the last sentence converted, only and only if the user restart the process with the same ebook

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants