error with schedules direct

As info.txt says Open the SchedulesDirect.com.ini file and look for the next line and change the credentials to yours.
url_index.headers {credentials=ENTER_USERNAME,ENTER_PASSWORD}
This are meant to be credentials from schedule direct not webgrab credentials.

what u did was correct by disabling the perdomat line.
it's just a example as a username,password.
did you check your wg config directory,new channel lists are created there.
if the channel list is sucessfully created copy the ones u want epg for to your wg config.

Try to set timeout to 80 in your config

are your lineups new or old existing ones.
see the first msg on their site from dec/2023.
https://www.schedulesdirect.org/
the ini uses SD-DD not SD-JSON.

whatever you did after you created the channel list broke something.
the ini uses the same url(request) for epg data and channel list creation.
so if channel list creation worked then so should epg grabbing as the exact same request is made for both.

did u edit anything in the run.net.sh file?

also another thing to consider..
maybe webgrab was still running from the previous day?
if u had many channels for sd in you config and a time-out of 80.
each channel x 4 retries = 320 secs per channel or 5min 20 secs.
if you had 200 sd channels...200 x 5min 20 secs = 1066 minutes.
add with the time it takes for other channels in you wg config you getting close to a day...1440 minutes.

if wg is still running from the previous day and tries to run again,a error like this could happen.
the reason is when wg runs it opens the wg config file,it stays open until wg completes.
if its opened from a previous run and it tries to run again it will error as the second process cant open the file as its already in use.

check and see if its still running in task manager
it shows as a .NET Host
if its there kill it and try running wg again.

upload your wg config and sd ini in a zip.
remove your license info from you wg config.
remove sd login info from ini.

u didnt disable the channel list creation.
add a * to the beginning of the lines between
** @auto_xml_channel_start
and
** @auto_xml_channel_end

fyi with newer webgrab u dont have to enable this manually(remove the *)
u can leave it disabled
just use update c in wg config to create a channel list.

if still the same error i am guessing its a dotnet and PATH issue.
do you know where dotnet was installed?
if you dont you will need to find its install directory.
example i installed it in /opt/dotnet,inside this directory you will find the dotnet binary file.
no idea how u installed dotnet but i did it manually.
next edit the run.net.sh file
look for this
# check if dotnet can be found

which dotnet >/dev/null 2>&1 || { echo >&2 "DotNet required, but it's not installed."; quit 1; }

before the which dotnet line add
export PATH=/path/to/dotnet/folder:$PATH
for me it would be
export PATH=/opt/dotnet:$PATH

try running wg manually in terminal,i assume your .wg++ folder is in /home/username?
/usr/share/dotnet/dotnet "/home/username/.wg++/bin.net/WebGrab+Plus.dll" "/home/username/.wg++"
replace username with your actual username

i really dont think this is the problem as webgrab starts,its when it gets to the 1st schedulesdirect channel it crashes.
it could be the way you edited the files,what editor do you use?

since ur in a VM.
how much ram does it have avail?
i see your requesting `15 days epg(timespan 14 in wg config)
try it with a timespan setting of 0(1 day)

depending on how many channels are in your linups this can be a huge amount of data.
sd returns data for all channels in your linups,not just for the channels in your wg config.
wg laters sorts the data for each channel you want epg for.

i'm think this is your problem as when you made your channel list the instructions were to set timespan to 0 and it worked.
if it works with timespan 0 reduce the number of days your grabbing to a minimum or add more ram to your VM.

if i remember right the older V3.x wg version that used mono whout output a error indicating out of memory.
no idea what dotnet outputs,you'd be the first to have it run out of memory...if thats the problem.

well least finally know where the problem was.

btw thks
i also run a vm on my server for some media stuff.
had 2gb ram assigned and figured it should be lots.
just checked it and under 500mb avail.
i doubled avail ram to 4gb.

i run everything seen plus a few other things.
as u can see lots avail ram now.

your already a donator so you have done enough.
enjoy webgrab.
buy yourself a cold beer.
thanks

do u mean different ini than schedulesdirect by other stations?
far as debugging goes there nothing dotnet has available to output additional info.
one of the other guys who has a sd account will have to look into this.
i had one years ago but its expired.

give this file a try.
i bought a sd account to test,was only 9 dollars for 2 mths.
i use a time-out of 30.
when i first tested file i was getting timeout and retries grabbing 14 days(timespan of 13).
i made a few changes
1. added compression.this wasnt avail years ago(when ini was made) but newer webgrab can now download and decompress compressed(gzip) data.
this made the biggest improvement for a site like this that downloads alot of data.
2. change maxdays=14,was 16.
3. fix credits(actor,director,ect)

as u can see from the log its pretty fast.
2 channels 14 days epg in 22 secs.

edit:
i found another bug where the end date was incorrectly calculated.
ini was only grabbing one day epg regardless of timespan setting.
i fixed this but now since its really grabbing alot of data(really 14 days instead of 1) it requires a very high time-out setting.i had increase it to 60 in my case.
if your only using sd then you can just set it higher in your wg config.
if you also using other ini then a high timeout is most likely not needed.i always use 30 in wg config settings.
with that said wg has a channel grouping option when u can set custom setting like time-out,proxy,ect for a group of channels.
on the downloads page their are documented configuration files available.
its all explained in the wg config one.see screenshot for a example that i used to set a higher time-out just for sd channels.
course this slowed grabbing alot as each channel gets 14 days of epg.
also a screenshot of top while its running.
as u can see its using some cpu and memory..

Edit:
files updated July 15/2024
more improvements

add credentials only modification.

error downloading page: An error occurred while sending the request.
to me this indicates a typo maybe changing the credentials,check it again.

i dont know why your having so many issues.
i updated files above with some more improvements.
nothing i changed was broken,there's just better ways to do things since this ini was made.
have you ever uploaded a full wg log file? i didnt notice one above.
upload one please.
also what linux distro are u running in VM?
i changed my lineup today to a usa one and no issues with the espn channels.
i assume your using a high enough time out?

i dont run wg in VM.
but i do run it in a chroot environment.

regarding tracing why the process was killed.
you could try a few suggestions here..
https://stackoverflow.com/questions/726690/what-killed-my-process-and-why

one suggestion i liked what this.
dmesg -T| grep -E -i -B100 'killed process'

double post.

linux distro?

i really cant see why your having so many issues.
i run ubuntu 22.04,as u know its debian based.
did u read the link in the post above?
have u tried increasing ram just to test?

i ran a test to get a idea of how much data was being downloaded.
for 7 days it hit 400mb and was still climbing.
i killed it as it was hitting 75% cpu and 90% ram usage.
it slowed my laptop down big time,its running a i7 quad with 16gb ram.
you also need to remember that wg has to process this huge amount of data in ram also.
sd requires huge resources.
i would keep number of days grabbed to the minimum.

imho if i were you i wouldnt use it.
tvguide.com.ini(international folder) gets the same data(uses gracenote also).
open ini and read remarks for channel list creation.
if differs from sd in that it downloads a single channel epg at a time.
uses much less resources.

docker is known for this,your hardware id most likely changed.
you can do a forced hardware update with h(like u use f for force license update) on your license line in wg config.