How would you run a script when the Docker starts?

[wayner]

I wouldn't mind rebooting my extenders when my Docker restarts. How do I initiate a script when the Docker starts. I think in linux this is done in something like an rc.d file - is there something similar when a docker starts?

[stuckless]

if /opt/sagetv/server/sagetv-user-script.sh exists it will be run immediately before the SageTV starts.

[wayner]

Great, thanks. Does this script have to terminate before Sage starts or is the Sage start done in parallel? What I am looking at doing is running a script that restarts my extenders and have them autoconnect to Sage. But Sage will have to be up and running in order for that to happen.

[Fuzzy]

sage's startup will not continue until the script is done.

That said, if you start up the extender while the server is unavailable, it send a wake-up packet and wait for the server to become available, and once it is, it will connected to it, so you should be able to reboot your extender in the startup script, and once sage is up, the extender will connect.

[stuckless]

Originally Posted by wayner

Great, thanks. Does this script have to terminate before Sage starts or is the Sage start done in parallel? What I am looking at doing is running a script that restarts my extenders and have them autoconnect to Sage. But Sage will have to be up and running in order for that to happen.

It's a script, so "as is" it will block, but in linux, your script can simply start a background process if you call another command/script and end it will &

so if this script called...

do-my-long.task.sh

then it would block.. but if it called

do-my-long-task.sh &

Then it would return immediately and "do-my-long-task.sh" would continuing running.

[SomeWhatLost]

just curious, my extenders seem to reboot automatically when the docker is restarted... even the ones that were not on or in use at the time I need to wander by and turn them off afterwards...
I thought that was their normal behavior?

[EnterNoEscape]

Originally Posted by SomeWhatLost

just curious, my extenders seem to reboot automatically when the docker is restarted... even the ones that were not on or in use at the time I need to wander by and turn them off afterwards...
I thought that was their normal behavior?

I believe the SageTCPServer plugin would do this.

[wayner]

Originally Posted by EnterNoEscape

I believe the SageTCPServer plugin would do this.

I think you are right. I used to use that but it had a bug where it would only store the IP or MAC addresses of 10 miniclients. Any more and it would cause issues. So if you happened to use Placeshifter on a PC once then it would take up a slot, unless you went and cleaned out the list in the sage.properties file.

I think the other option for me may be SJQ as I think you can kick off jobs for when Sage starts up, in addition to Recording Started, Recording Stopped, Cron jobs, etc.

[SomeWhatLost]

Originally Posted by EnterNoEscape

I believe the SageTCPServer plugin would do this.

you are probably correct I do use the SageTCPServer plugin to talk to my CQC HA server...
so it is not just a default sage thing after all?

I did not know about the 10 client limit though... that may be problematic at some point in the future...
in my case that would mostly be because of Stuckless and his incredibly cool mini client... I just cant help but load it up on every android device I come across...
someone leaves their phone unlocked, they get a mini client installed...
that is just the way it is...
can't be helped...
I blame stuckless..

[wayner]

I can't find specific mention of the ten device limit in the thread but I remember hearing it from Fonceur - it might have been in a PM. I believe the limit was because it reserved a port for each miniclient and they didn't consider that some of the miniclients may be transient - in the past I would often use Placeshifter to connect to a server to try something out but never use Placeshifter on that computer again. There is less reason not to do this today as, as was mentioned, there are clients for mobile devices, and there is no licensing requirement for Placeshifter.

It would be nice if this limit could be eliminated but I don't think anyone if maintaining SageTCPServer anymore.

edit - And no, it is definitely not part of the core of SageTV, but maybe it should be?

[stuckless]

Originally Posted by SomeWhatLost

you are probably correct I do use the SageTCPServer plugin to talk to my CQC HA server...
so it is not just a default sage thing after all?

I did not know about the 10 client limit though... that may be problematic at some point in the future...
in my case that would mostly be because of Stuckless and his incredibly cool mini client... I just cant help but load it up on every android device I come across...
someone leaves their phone unlocked, they get a mini client installed...
that is just the way it is...
can't be helped...
I blame stuckless..

That's aweseome

[wayner]

And I hope you have a large JVM heap size and lots of upload bandwidth to deal with all of those miniclients.

[SomeWhatLost]

Originally Posted by wayner

And I hope you have a large JVM heap size and lots of upload bandwidth to deal with all of those miniclients.

local network only...

and yes, I set JVM heap to like 4 gig or something... and for some reason (could be my imagination?) Docker Sage does not seem to use it up as quickly as windows did...

[wayner]

Originally Posted by SomeWhatLost

local network only...

and yes, I set JVM heap to like 4 gig or something... and for some reason (could be my imagination?) Docker Sage does not seem to use it up as quickly as windows did...

It wouldn't surprise me if there is a memory leak in Windows as occasionally I will get JVM heap issues with only a couple of extenders attached, especially if there have been many other extenders attached, and then detached, since the last reboot. Maybe those memory leaks don't occur in Linux.

[Taddeusz]

Originally Posted by wayner

It wouldn't surprise me if there is a memory leak in Windows as occasionally I will get JVM heap issues with only a couple of extenders attached, especially if there have been many other extenders attached, and then detached, since the last reboot. Maybe those memory leaks don't occur in Linux.

When I started messing with SageTV on Linux I immediately noticed that it seemed to use significantly less memory than in Windows. Not sure why that would be?

[EnterNoEscape]

Originally Posted by Taddeusz

When I started messing with SageTV on Linux I immediately noticed that it seemed to use significantly less memory than in Windows. Not sure why that would be?

My best guess would be that V4L is a much lighter protocol to work with over BDA. There's also some differences in how some of the native code is compiled for Linux vs Windows that would contribute to the overall memory footprint.

[wayner]

Originally Posted by stuckless

if /opt/sagetv/server/sagetv-user-script.sh exists it will be run immediately before the SageTV starts.

One further question on this - will this script also be run whenever the SageTV service (if that is still the right term in unRAID) restarts, such as when a Plugin forces a restart?

[Fuzzy]

No, this is run only when the startup is done when the container loads.

[wayner]

So any suggestions on how to do this - I want to ensure that some of my extenders are connected and if you do a restart of the Sage service then the extender will lose the connection.

I thought that it was possible to use SJQ to start a task when SageTV starts but it turns out that isn't the case, as you can only attach tasks to: RecordingStarted, RecordingStopped, SystemMessagePosted, or MediaFileImported. Would it be possibel to have a SystemMessage generated whenever SageTV starts?

[Fuzzy]

Originally Posted by wayner

So any suggestions on how to do this - I want to ensure that some of my extenders are connected and if you do a restart of the Sage service then the extender will lose the connection.

I thought that it was possible to use SJQ to start a task when SageTV starts but it turns out that isn't the case, as you can only attach tasks to: RecordingStarted, RecordingStopped, SystemMessagePosted, or MediaFileImported. Would it be possibel to have a SystemMessage generated whenever SageTV starts?

This would best be done by a separate plugin. Sure a system message COULD be generated on a restart, but if the only purpose of that message is to be able to force SJQ into doing a task on startup, then it'd be better to just make a simpler plugin that will just do what you are looking for. Plugins have an init function that is run on startup, and this capability could be built in there.