-
-
Notifications
You must be signed in to change notification settings - Fork 27
EPG Mapping error #153
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
I see a couple things going on: first, it looks like the DB is locked, which you might be able to fix with the latest for the Playlist and EPG you're mapping, whats the channel count for each? And are they from your provider, or is the EPG a non-provider EPG (e.g. playlist and epg are from different sources)? I can increase the timeout to start, but not sure how much it will take. When it timed out, what percentage was the mapping? |
The EPG has 2167 channels. The playlist with the error has 12936 channels. The channels are from provider, they just started offering epg data, but it is horrible. I use IPTVBoss for the EPG data. As for how far along it was, im not sure. The page shows 100% with status "Failed". Will the progress stop where it failed? EDIT: |
Hey, I'm also having this same issue and it's also stuck at 2%, EPG is from my provider. |
I am facing same issue. EPG mapping is stuck at 2%. 194534 channels and 11757 EPG from same provider. I moved to dev branch with Postgres. |
My EPG mapping is also stuck at 2% during processing. I've tried resetting the queues, but it remains stuck. Reprocessing is not possible — the only available option is to delete it. The log files do not show any errors or warnings, but the Queue Manager displays the following:
I'm currently running the dev version in combination with the built-in PostgreSQL database. |
It's looking like timeout, the mapping is just taking too long. I'll see if I can split things up so processing goes more quickly. |
Uh oh!
There was an error while loading. Please reload this page.
Here is message as in log. If you require something else let me know. Version 0.5.8
The text was updated successfully, but these errors were encountered: