No lineup this morning!

An evolving, supported alternative to Rovi
Forum rules
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html
Post Reply
scottward01

Posts: 11
Joined: Mon Apr 20, 2020 10:54 am
Location:

HTPC Specs: Show details

No lineup this morning!

#1

Post by scottward01 » Sat Jun 06, 2020 11:47 am

EPG123 didn't complete its automatic update this morning, and when I launch it manually to take a look, there's no lineup in the GUI, although it logs into Schedules Direct no problem. Please help!

JRElliott

Posts: 1
Joined: Tue Apr 21, 2020 6:42 pm
Location:

HTPC Specs: Show details

#2

Post by JRElliott » Sat Jun 06, 2020 12:16 pm

Likewise here.

1.3.6.20 was working fine yesterday.

1.3.6.20 today:
[6/6/2020 4:40:05 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError

1.3.7.30 today:
[6/6/2020 7:07:41 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError

Excerpts from Trace:

Code: Select all

[6/5/2020 4:40:05 AM] ===============================================================================
[6/5/2020 4:40:05 AM]  Beginning epg123 update execution. version 1.3.6.20
[6/5/2020 4:40:05 AM] ===============================================================================
...
[6/5/2020 4:40:05 AM] [ INFO] epg123 is not up to date. Latest version is 1.3.7 and can be downloaded from http://epg123.garyan2.net.
[6/5/2020 4:40:06 AM] [ INFO] Successfully retrieved TMDb configurations.
[6/5/2020 4:40:06 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[6/5/2020 4:40:06 AM] Entering buildLineupServices() for 1 lineups.
[6/5/2020 4:40:06 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-02155.
[6/5/2020 4:40:06 AM] Exiting buildLineupServices(). SUCCESS.
[6/5/2020 4:40:06 AM] Entering getAllScheduleEntryMd5s() for 21 days on 64 stations.
[6/5/2020 4:40:07 AM] [ INFO] Successfully retrieved Md5s for  64 station's daily schedules. (0:00:00:00.6780725 /   121.141 KB)
[6/5/2020 4:40:08 AM] [ INFO] Successfully retrieved  64 station's daily schedules.          (0:00:00:00.6223395 /     2.630 MB)
[6/5/2020 4:40:09 AM] [ INFO] Found 709 cached daily schedules.
...

[6/6/2020 4:40:03 AM] ===============================================================================
[6/6/2020 4:40:03 AM]  Beginning epg123 update execution. version 1.3.6.20
[6/6/2020 4:40:03 AM] ===============================================================================
...
[6/6/2020 4:40:04 AM] [ INFO] epg123 is not up to date. Latest version is 1.3.7 and can be downloaded from http://epg123.garyan2.net.
[6/6/2020 4:40:04 AM] [ INFO] Successfully retrieved TMDb configurations.
[6/6/2020 4:40:04 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[6/6/2020 4:40:04 AM] Entering buildLineupServices() for 1 lineups.
[6/6/2020 4:40:05 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-02155.
[6/6/2020 4:40:05 AM] Exiting buildLineupServices(). SUCCESS.
[6/6/2020 4:40:05 AM] Entering getAllScheduleEntryMd5s() for 21 days on 64 stations.
[6/6/2020 4:40:05 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
[6/6/2020 4:40:05 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
[6/6/2020 4:40:05 AM] [ERROR] Failed to complete request. Exiting
...

6/6/2020 7:07:40 AM] ===============================================================================
[6/6/2020 7:07:40 AM]  Beginning epg123 update execution. version 1.3.7.30
[6/6/2020 7:07:40 AM] ===============================================================================
...
[6/6/2020 7:07:40 AM] [ INFO] system status: Online , message: No known issues.
[6/6/2020 7:07:41 AM] [ INFO] Successfully retrieved TMDb configurations.
[6/6/2020 7:07:41 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[6/6/2020 7:07:41 AM] Entering buildLineupServices() for 1 lineups.
[6/6/2020 7:07:41 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-02155.
[6/6/2020 7:07:41 AM] [ INFO] Kicking off background worker to download and process 53 station logos.
[6/6/2020 7:07:41 AM] Exiting buildLineupServices(). SUCCESS.
[6/6/2020 7:07:41 AM] Entering getAllScheduleEntryMd5s() for 21 days on 64 stations.
[6/6/2020 7:07:41 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
[6/6/2020 7:07:41 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
[6/6/2020 7:07:41 AM] [ERROR] Failed to complete request. Exiting
...

keitme

Posts: 2
Joined: Sat Jun 06, 2020 12:54 pm
Location:

HTPC Specs: Show details

#3

Post by keitme » Sat Jun 06, 2020 1:10 pm

looks like schedules direct is having an issue. A 500 error is a web server reporting an internal error.

I'm just getting a connection closed error report.

SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.

Mine normally updates at 3 am CDT. I did several retries this morning that failed.

lostgreycells

Posts: 61
Joined: Wed Jan 13, 2016 6:11 am
Location:

HTPC Specs: Show details

#4

Post by lostgreycells » Sat Jun 06, 2020 1:33 pm

Same here. Checked the Scheduled Direct Forum https://forums.schedulesdirect.org/ and no reports/announcements on the error

[6/6/2020 5:00:03 AM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[6/6/2020 5:00:03 AM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-WA46459-X.
[6/6/2020 5:00:03 AM] [ERROR] There are 0 stations queued for download from 1 subscribed lineups. Exiting.
[6/6/2020 5:00:03 AM] [ERROR] Check that lineups are 'INCLUDED' and stations are selected in the EPG123 GUI.
[6/6/2020 5:00:03 AM] [ERROR] Failed to create MXF file. Exiting.

[6/6/2020 5:00:34 AM] [ERROR] The MXF file imported is 24.00 hours old.

[6/6/2020 5:58:13 AM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[6/6/2020 5:58:13 AM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-WA46459-X.

scottward01

Posts: 11
Joined: Mon Apr 20, 2020 10:54 am
Location:

HTPC Specs: Show details

#5

Post by scottward01 » Sat Jun 06, 2020 3:40 pm

Seems to be working now, or at least I have a lineup now and I'm in the middle of a manual update!

keitme

Posts: 2
Joined: Sat Jun 06, 2020 12:54 pm
Location:

HTPC Specs: Show details

#6

Post by keitme » Sat Jun 06, 2020 7:26 pm

everything is working now. my 10 am cdt updating machine worked normally, and i ran an update on my 3am box manually with no issues.

kkingsto

Posts: 77
Joined: Fri Oct 20, 2017 8:36 pm
Location:

HTPC Specs: Show details

#7

Post by kkingsto » Mon Jun 15, 2020 11:22 am

Looks like it happened again this morning.

Opened EPG123 and no lineups.

Post Reply