the story of blinking

[DIBU]

ok folks, here are the story...

yesterday in the morning i had set up my sage server new. i install the w2003 and run the normaly install. after all...(3 h) i run sage and see...all my mvp's are running and all shows are right...so i watch the recordings..after 4 h my mvp in the kittchen hangs...ok no problem..it is not the first time that i see that...hardreset...

but...

what this...no mvp will boot...all are blinking and pusching the sagetv bootscreen...why? is there an bug with pal here in germany?

after...

after 26 h...i have no mvp are working yet...all are blinking and no mvp will booting right...

i have switch all the things..java...new install sage..delete client folder..ect...

NOTHING...

the client on my laptop are working fine...

anybody here..there have a idee????

i hate this..it is not the first time that i have this problem with my mvp's but this is the first time..that all are blinking...

[DIBU]

i see now this in the web frontend

Connected Clients:
[/127.0.0.1:2403]

what this?

[omega]

Originally Posted by DIBU

i see now this in the web frontend

Connected Clients:
[/127.0.0.1:2403]

what this?

The 127.0.0.1:xxxx is the SageTV UI on your server system. Remember that when running in service mode, SageTV opens the local UI as if it were an instance of SageTVClient, and then connects to the service process over the localhost IP, 127.0.0.1.

The MVP(s) would show up in the Web Server by their MAC address(es), not as 127.0.0.1:xxxx connections, even though they are technically local connections from the server's point of view.

[nielm]

You are running sage as a service.
The sage user interface on the server machine functions as a 'client' (127.0.0.1 is the local IP address) to connect to the server.

For your MVP problem: have you checked that your firewall allows sagetvservice.exe to open ports? The MVPs require several ports to be open, and these are different to the PC-client ports.

[DIBU]

Originally Posted by nielm

You are running sage as a service.
The sage user interface on the server machine functions as a 'client' (127.0.0.1 is the local IP address) to connect to the server.

For your MVP problem: have you checked that your firewall allows sagetvservice.exe to open ports? The MVPs require several ports to be open, and these are different to the PC-client ports.

howdy, well but i have in my intranet no firewall..i watched sage with the new server...without problems...then in the middel of the show the mvp hangs...i boot the mvp new..and now i have blinking blue sagetv with black.. and this is not new...but it is new..that all my mvp have this blinking..

when i switch to the hauppauge-soft on the same server...without any changes (only i switch the sage service off) all my mvp's are working fine with this stup### software.

[blade]

Have you tried rebooting the server if so what about the router? I sometimes have odd network issues and end up having to restart my network.

[DIBU]

Originally Posted by blade

Have you tried rebooting the server if so what about the router? I sometimes have odd network issues and end up having to restart my network.

well i have rebootet my server (10x or more) and also my router...

i think that the mvp wil load the bin file and than comes the sage-screen and than comes a black screen and than comes the sage-screen and than comes the black screen...and and and and for ever?

[DIBU]

ok folks the story is not ending...

after one million hard resets on one of my mvp's (power off power on power off power on)...huch the mvp is booting..i see the sagetv gui.... hurray...


and now...the other mvps...booting...gui hurray....

but how long are the mvp are working..i will see an write here the challenge..

is this really the one and only version that i can relife the mvps to booting with sage?

ah ok i see..when i power off a mvp and wait 1 or more days without power...the mvp will not boot the sage it is blinking...after a lots of power off power on..the mvp boots sage...mhmm