Linux Trouble Starting Service

[Taddeusz]

I'm on the last Ubuntu LTS, 14.04 32-bit with Java 7. Mainly because SageTV won't build under the latest Ubuntu versions.

When I try to start the SageTV service it gets stuck on "Main is starting". The service seems to load ok but it won't complete the script. This is a problem when I install with dpkg. When I hit ctrl-c to break the script it puts dpkg in a locked state and messes things up.

Going to create a new Ubuntu 15.10 64-bit vm to test on to see if it has the same problem.

[stuckless]

try setting

export DEBIAN_FRONTEND=noninteractive

before running dpkg -i

I think the activation key request is causing issues.

The other thing is that we don't publish 32bit packages, so, if you are installing those, I'm assuming that you built them yourself?

[Taddeusz]

Originally Posted by stuckless

try setting

export DEBIAN_FRONTEND=noninteractive

before running dpkg -i

I think the activation key request is causing issues.

The other thing is that we don't publish 32bit packages, so, if you are installing those, I'm assuming that you built them yourself?

That didn't work. Yes, I'm building them myself.

[stuckless]

Originally Posted by Taddeusz

That didn't work. Yes, I'm building them myself.

I built a docker container the other day, and I know people are saying the "installer hangs", but I've never seen this myself

I even have 2 vagrant images that I use for testing as well, and I don't experience it there either.

Certainly there are times when you run dpkg -i that it will run post ininit scripts and start a service, etc, and it might appear as the command line went away, but pressing enter usually restores the command line. (I have seen this happen from time to time with other installs, but it's not blocked, it's just finished, and the console UI hasn't updated).

[Taddeusz]

Originally Posted by stuckless

I built a docker container the other day, and I know people are saying the "installer hangs", but I've never seen this myself

I even have 2 vagrant images that I use for testing as well, and I don't experience it there either.

Certainly there are times when you run dpkg -i that it will run post ininit scripts and start a service, etc, and it might appear as the command line went away, but pressing enter usually restores the command line. (I have seen this happen from time to time with other installs, but it's not blocked, it's just finished, and the console UI hasn't updated).

Sorry, I forgot to mention that it also happens when just starting the service by doing:

sudo service sagetv start

[stuckless]

Originally Posted by Taddeusz

Sorry, I forgot to mention that it also happens when just starting the service by doing:

sudo service sagetv start

not sure that is the right way for Ubuntu 14...

try

sudo /etc/init.d/sagetv start

SageTV doesn't use the newer service api.

SageTV starts in the background... and as I said, the cursor might not return immediately, but pressing enter, should get the curso back... i restart start like this every couple of weeks on my server.

If sagetv is already started (or if you don't know), then use

sudo /etc/init.d/sagetv restart

[EnterNoEscape]

I have seen it hang on Ubuntu 14.04, Fedora 22 and 23 when starting the service when I was using OpenJDK. I installed Oracle and that appeared to fix it. I've also seen when it returns you to the terminal, but not actually show the prompt. Pressing Enter always fixes that for me, but when it hangs, I can hit Ctrl-C and SageTV is definitely not running.

[Taddeusz]

Just tried doing this with Oracle Java 7 and it gives me the same problem.

[SageWizdom]

Did you use the script from this post?

http://forums.sagetv.com/forums/showthread.php?t=63026

This script is trying to do everything in a 64bit way. Not that I am only advocating for 64bit, but it may matter if you're on 32.

I would also offer that if you kill the script (at the install point where it gets stuck), I would encourage shutting down Sage (sudo service sagetv stop) and then re-running the script as it will attempt to validate what it has already done, and do the rest of the install.

If Sage isn't running at all... there may be a couple of problems.

A) if you used the script, you may now have multiple versions of Java installed
B) you may or may not have incorrect java paths set

Did you try running Sage manually?

/opt/sagetv/server/startsage

it should attempt to run, and should worst case give you a log file that might be more helpful (in the same directory).

[Taddeusz]

No, I don't use that install script. I have only HDHR tuners. I see no need to use OpenDCT.

Just to report. Since the latest available pre-built version is behind I used an Ubuntu 14.10 x64 vm to build the latest version. Then installed in an Ubuntu 15.10 x64 vm. It installs and runs fine without the same service starting issues as on 14.10. Not sure why the difference.

BTW, the error occurs during the startsage script. Since the output doesn't correspond with anything in the script I assume the output comes from the Sage.jar itself.

[Narflex]

If you post what the output is; I can tell you if it is coming from the Sage.jar file or not.

[Taddeusz]

Here is the output from startsage. Hitting ENTER at this point brings back the prompt. During installation hitting ENTER doesn't do anything.

jbean@sagetest32:/opt/sagetv/server$ sudo ./startsage
Changing to SageTV directory /opt/sagetv/server/.
jbean@sagetest32:/opt/sagetv/server$ Executing pre-scripts
Starting server mode
Main is starting

There's also a difference in the stopsage output that I noticed. It shows "." as it's waiting for it to stop. This doesn't happen on newer versions of Ubuntu.

jbean@sagetest32:/opt/sagetv/server$ sudo ./stopsage 
Changing to SageTV directory /opt/sagetv/server/.
.
.
.
.
.
.

[Narflex]

Those both look normal. If you turn on debug_logging; is there anything in sagetv_0.txt?