WebGrab+Plus

Quote from awiouy

Superb!
I will integrate your configurator to the LE addon this week-end

Looking forward to Primaeval's WebGrab+Plus Configurator (all options?) being merged into webgrabplus service, makes a lot of sense.

I believe that webgrabplus.start program we previously pointed too for when specific one-off runs of epg grab required (i.e. via primaeval configurator) becomes webgrabplus.run with webgrab+Plus v8.0.104 and later versions. (Is this a correct assumption, I have only looked at code contained in .start & .run files, have not physically tested )

I get this error message Failed to start transient timer unit: Unit webgrabplus.timer already exists.

Quote

Using username "root".
##############################################
# LibreELEC #
# LibreELEC – Just enough OS for KODI #
##############################################

LibreELEC (community) Version: 7.90.008
LibreELEC:~ # webgrabplus.start
Failed to start transient timer unit: Unit webgrabplus.timer already exists.
LibreELEC:~ #

Display More

Quote

Using username "root".
##############################################
# LibreELEC #
# LibreELEC – Just enough OS for KODI #
##############################################

LibreELEC (community) Version: 7.90.008
LibreELEC:~ # webgraplus.run
-sh: webgraplus.run: not found
LibreELEC:~ #

Display More

Have not seen sorry

Quote from awiouy

Hello Alister,

Can you describe the circumstances which produce this error?
Are you trying to run the service manually?
If so, you should use the command webgrabplus.run, not the command webgrabplus.start

awiouy, Please can you update 1st post in thread to reflect latest release features. (This will reduce user queries on changes/improvements to this truly excellent service add-on)

H'mmm. Today my log says that webgraplus ran at 10A.M. in configuration it is set to run at 2 A.M. and blanks for on-active. I think I may have rebooted around 10 this A.M.

I don't remember changing anything else.

It is 8.0.104

I just rebooted and it started running 300 seconds after.

how do we all keep mis-spelling webgrabplus? and why a p instead of a b? Don't know how many times I've done it.

donbrew with WebGrab+Plus Service (currently v8.0.104 for LE Krypton or v7.0.104 LE Jarvis) you need to ensure that you remove default 300 value from --on-active field
(To stop run of webgrabplus 300s (5Mins) after every device restart)

Otherwise at a set time (5 mins by default) after every reboot job will be run.

For a quick how-to modify settings introduced in vx.1.104 see my Screenshots in this post

The reason I rebooted last night was to test, the on-active field is empty.

To ensure I reset it it to default, then cleared it, then rebooted (I did remember to click OK).

I just checked the settings and rebooted. Webgrabplus started on reboot, no delay.

I wasn't watching the clock last night, so I assumed it started with a delay. I was wrong.

My systemctl output is the same as yours.

I have started with plain WebGrab+Plus, changed to Webgrabplus.servic, back to plain Webgrab+plus, then back to the service. I may have left something behind.

Doesn't matter much to me I just was reporting an odd behavior. Right now, the state of the addons I like (not to be mentioned here) makes the guide sort of a waste.

I re boot then immediately check the timestamp on the webgrab log via WinSCP.

Here is settings.xml:
<settings>
<setting id="wgp_on_act" value="" />
<setting id="wgp_on_cal" value="*-*-* 03:00:00" />
</settings>

There are no more crontabs

journalctl webgragplus
journalctl service.webgrabplus
systemctl status webgrabplus
systemctl statu service.webgrabplus

Those were when not running

here is while running with webgrabplus.run

journalctl webgrabplus
journalctl service
systemctl webgrabplus
systemctl service

Did you want them while running from reboot?

journal webgrabplus
journal service
systemctl webgrabplus
systemctl service