Autocompress waiting for ?

[bnh]

.autocompress files are being created ok, but nothing is getting compressed anymore.... they are just piling up in the job list with a "Waiting" status. Default compression is enabled and auto-compression is enabled.

This was working admirably up until, i think, it was when i had to restart the sage service a week or so ago. I'm guessing SageTVTranscoder was running when the server was restarted, and something is telling Sage to wait for that incomplete auto-compression to finish before it starts another one. So i thought i could delete all the .autocompress files, and then turn on/turn off each of the favorites' autocompress setting, but thought i would ask here first if that approach made sense???

SageMC settings:
-----------------
SageTVserver 6.5.7.201
SageMC STV 6.3.8a
SageMC.jar 6.3.8
Sageutils.jar 2.2

compression related SageMC settings in Sage.properties:
------------------------------------------------------
sagemc/auto_compress_last_run=1233622587696
sagemc/auto_compression=true
sagemc/compression_dir=
sagemc/use_standard_compression=true

[evilpenguin]

Originally Posted by bnh

.autocompress files are being created ok, but nothing is getting compressed anymore.... they are just piling up in the job list with a "Waiting" status. Default compression is enabled and auto-compression is enabled.

This was working admirably up until, i think, it was when i had to restart the sage service a week or so ago. I'm guessing SageTVTranscoder was running when the server was restarted, and something is telling Sage to wait for that incomplete auto-compression to finish before it starts another one. So i thought i could delete all the .autocompress files, and then turn on/turn off each of the favorites' autocompress setting, but thought i would ask here first if that approach made sense???

SageMC settings:
-----------------
SageTVserver 6.5.7.201
SageMC STV 6.3.8a
SageMC.jar 6.3.8
Sageutils.jar 2.2

compression related SageMC settings in Sage.properties:
------------------------------------------------------
sagemc/auto_compress_last_run=1233622587696
sagemc/auto_compression=true
sagemc/compression_dir=
sagemc/use_standard_compression=true

For every autocompress file that gets created you should see a job added to Sage's compress Queue. Are they being added bug Sage isn't processing them or are they not being added to the queue at all?

[bnh]

Originally Posted by evilpenguin

For every autocompress file that gets created you should see a job added to Sage's compress Queue. Are they being added bug Sage isn't processing them or are they not being added to the queue at all?

they are being added to the list, but SageTVtranscoder.exe never runs.

[evilpenguin]

Can you manually schedule a compression and have it work?

[bnh]

I just manually sent a series favorite with autocompress disabled to Compress, but it all it did was add just it to the bottom of the job list. i don't see the SageTVtranscoder running in TaskManager.

[evilpenguin]

There's a lot of stuff at work here, lets try and rule the simple things out.

First of all, switch the latest default STV, schedule a compression and see if it works.

[bnh]

i got one scheduled, and happened to see SageTVTranscoder.exe flash by in the TaskManager list. So it at least it appears it is getting triggered.

I suspected some kind of permissions issue and took a look at the WinXP logs, and found a whole slew of errors in the System log:

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{BC866CF2-5486-41F7-B46B-9AA49CF3EBB1}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19). This security permission can be modified using the Component Services administrative tool.

The CLSID referenced is a "NvAppFilterSvr Class". The SageService is running under an admin account, not the local account.

[evilpenguin]

Try running it not as a server and seeing if that helps.

[bnh]

eesh.. that may take awhile... to find a time when i can avoid a WAF recording conflict. Your theory is that the account/perms that the transcoder is running under now, would be different if run via the client as opposed to the SageTVService?

I would gladly reset the recording directories to remove all permission conflict possibilities, like enable Guest or Everyone, but alas the OS is WinXP home, and don't know how to do that like one can in WinXP Pro, nevertheless the Guest account has been enabled for some time (shhh).

Does the above error seem relevant to this issue? or is it a symptom of another unrelated problem? The only change i've made recently is to reformat the cluster size (64k) of one of the new recording drives, but there was nothing in the recording directory at the time. There are some recordings there now though, so the sage core can use it no prob.

I'll see if there is a lull in the recording schedule sometime this week and turn off the service and try scheduling a manual compress then.

thanks for your help.

[bnh]

Well lo and behold this was a perfect time to bring down Sage as a service, and thusly, the Transcoder is now running!!!!

So what does this mean?

[gplasky]

Instead of running the service under localsystem

to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19). This security permission can be modified using the Component Services administrative tool

Have the service log in as a user in the Adminsitration group and that user MUST have a psasword. You can change it in services or the SageTV Service Control app.

Gerry

[bnh]

I can see both SageTVService and SageTVTranscoder running on my own login which is an administrator account. Not sure how to set the SageTranscoder to run under a specific account, but now that i look again the SageTVService Control application is running now under my own administrative account without me telling it to restart.

it's almost like i somehow started two sageservice processes and stopping the SageUI, allowed the former to go ahead ?? is that possible?

[bnh]

83 jobs queued. 2 converted thus far. eeesh. at least it's running.

thank you evilpenguin!

[evilpenguin]

Glad I could point you in the right direction. Just wish we could have figured out what caused the log jam in the first place.

[bnh]

yup. agreed and thank you.

just to be clear for the WAF tomorrow (and if this happens again):

Since SageTVService.exe and SageTVTranscoder.exe are both running right now, all normally scheduled activities within SageMC are good to go, right?