SageService: why my bye bye?

[cat6man]

this has happened a couple of times this year, but this is the first time i've followed it up.

i tried my SageWeb interface, then SRE, but couldn't connect, so i went down into the basement and found SageService had stopped.

i see at least 2 problem here:

1) why did it stop?
out of the blue (at least to my eye) i get

Sun 3/28 4:08:54.258 [Thread-90@28ee2d] Sage.exit() called.

then after lots of things are killed and shut down, i get a very polite

Sun 3/28 4:08:56.635 [Thread-90@28ee2d] Bye-bye.

the log going back 10 minutes is attached

2) why didn't it re-start?
i have the re-start option checked for sageservice so why didn't windows or something start it up again? i was lucky i happened to log on and try to check in via web interface or i wouldn't have found the problem.

[Slugger]

Not sure why it shutdown to begin with, but it didn't auto restart because that output suggests that something requested a shutdown and a graceful shutdown was performed. Windows would only auto restart it if it crashed out, not on a clean shutdown.

[paulbeers]

You don't happen to have scheduled an automatic shutdown did you? What about Java updates, are they set to be automatically updated which might cause Sage to shutdown after install (this is completely a stab in the dark as I have no idea how Sage would handle an auto update to Java)?

[HelenWeathers]

Any hs_err_xxxxx (java generated) files in your SageTV\SageTV folder?

[cat6man]

Originally Posted by HelenWeathers

Any hs_err_xxxxx (java generated) files in your SageTV\SageTV folder?

no files even beginning with the letter 'h' in that folder.

i do have something that pops up about java updates but i ignore
them until it is convenient for me to update..........they don't get to run
automatically

(insert AHA!)
SageTV shut down gracefully due to a command of some sort that told it to?
now, i do have a script that runs nightly to move files from my default recording directory d: to an NAS.
it stops sageservice (a clue!), moves the files, then restarts sageservice.
this was a workaround for a bug where sage wasn't recognizing the files
that were move to the NAS and required a stop/re-start (support reproduced the problem and says the bug will be fixed in a future release, so i assume it will be in the next beta)

i conclude therefore the the stoppage is understood but the re-start is the part that occasionally fails...........any ideas?

[HelenWeathers]

How complex is your batch file?

Any branching based on errorlevel that might cause the branch to skip the net start sagetv command when an error occurs?

Just a thought.