"Failed service unavailable" message

[mikepy]

I have been away for a few days and on my return i have noticed that i have no tv guide data.
The last call status is today "Failed service unavailable"
I went to tivoweb and forced a daily call and almost immediately got the same message again.
I rebooted and tried again but no luck.
Obviously my network is working as i can access Tivoweb.

any ideas gratefully accepted :confused:

Mike

[petestrash]

I have split your post off the 'Wont let me access "Recorder & Phone Setup" ' thread as it didn't really have any relevance to that subject.

Having access to tivoweb only shows you have access to your TiVo, but does not test if your TiVo has access to the internet to download data.

You should run through the network troubleshooter.

Read from about half way down NetworkingHowto (http://minnie.tuhs.org/twiki/bin/view/Network/NetworkingHowto) starting at "Configuration and Diagnostics" and follow the tests and let us know the results.

Peter

[mikepy]

Route worked ok
I can ping the tivo ok
I couldn't ping the Tivo headquarters but then again it didnt work from the dos prompt either
Wget worked
and the dial prefix was ok too :confused:

one other thing i noticed.
I did a wget on emuproxy3 and somehow it ended up in the wrong directory so i got my ftp prog running on my pc to move it into the right directory.
( i dont know how to do it in linux)
But where as the FTP has been working fine. Now it aborts the connection?
i tried another ftp prog and that did the same.
Thanks
Mike

[petestrash]

Did you try pinging an IP address outside your house other than minnie ?

minnie won't respond to ping's, which is why 204.176.49.1 (tivo.com) is given in the document as a test IP for pinging from your TiVo.

Where did you wget emuproxy3 from? Did you try wgeting the suggested 'wget http://131.244.9.101/index.html', what happened.

Peter.

[mikepy]

I didnt ping minnie i pinged the US TIVO headquarters in California as suggested in the howto
the wget seemed to work as i got the same responses as it said i should

Mike

[petestrash]

Sorry, my bad I was reading multiple posts at the same time.

Yes you are right, TiVo doesn't respond to pings anymore. I have updated the twiki and given a google IP instead.

Ok, it looks like your TiVo can talk to the outside world ok.

So now we need to see why your not getting slices.

Do a daily call, then post your tclient or otclient log so we can see what is happening.

Peter

[mikepy]

I did the call and copied part of the tclient log from the time i iniated the call but it was over 15000 chars long and i couldn't post it.

Mike

[mikepy]

Oct 17 21:16:54 (none) comm[152]: CallService: Start err 0
Oct 17 21:16:54 (none) comm[152]: CAM_ID not found.
Oct 17 21:16:54 (none) comm[152]: CallStatusReporter: Phase: Dial, Status In Progress
Oct 17 21:16:54 (none) comm[152]: CallStatusReporter: sending message "CL|30"
Oct 17 21:16:54 (none) comm[152]: Backdoor code 4, enable calls via broadband
Oct 17 21:16:54 (none) comm[152]: Using Ethernet. Not starting modem/pppd.
Oct 17 21:16:54 (none) comm[152]: CallStatusReporter: Phase: Start_Auth, Status In Progress
Oct 17 21:16:54 (none) comm[152]: CallStatusReporter: sending message "ST|33"
Oct 17 21:16:54 (none) comm[152]: CommUtil: connection to host 127.0.0.1, port 8000, err 0x50005
Oct 17 21:16:54 (none) comm[152]: tmk tcp connect failed, reason = Operation now in progress
Oct 17 21:16:54 (none) comm[152]: drainGetPostQ: doXfer failed err=327685 (0x50005)
Oct 17 21:16:54 (none) comm[152]: NetAgent: drainPostQ failed, err = 0x50005
Oct 17 21:16:54 (none) comm[152]: CallService: NetAgent Process err 327685
Oct 17 21:16:54 (none) comm[152]: CallService: NetAgent failed, status 0x50005
Oct 17 21:16:54 (none) comm[152]: CallService: EndCall start
Oct 17 21:16:56 (none) comm[152]: CallStatusReporter: Turning off-hook LED off
Oct 17 21:16:56 (none) comm[152]: Recover private logs
Oct 17 21:16:56 (none) comm[152]: Opening old private log files
Oct 17 21:16:56 (none) comm[152]: Reverting private logs
Oct 17 21:16:56 (none) comm[152]: Cleanup: GetAddDiskBasedDirectories returned <70001> "0x70001"...skipping cleanup
Oct 17 21:16:56 (none) tcphonehome[152]: CallService return status 0x50005
Oct 17 21:16:56 (none) tcphonehome[152]: GetPostalCodeVersion - /PostalCode/07000 ServerVersion=26
Oct 17 21:16:56 (none) tcphonehome[152]: debug: sumServerVersion=26
Oct 17 21:16:56 (none) comm[152]: CallStatusReporter: Phase: Start_Auth, Status Failed
Oct 17 21:16:56 (none) comm[152]: CallStatusReporter: sending message "EX|14"
Oct 17 21:16:56 (none) tcphonehome[152]: TClient failed: EX|14
Oct 17 21:16:56 (none) tcphonehome[152]: Sending dialup event, subtype 8, msg EX|14
Oct 17 21:16:56 (none) tcphonehome[152]: setCallStatus called with: Failed state 0
Oct 17 21:16:56 (none) tcphonehome[152]: LastCallAttempt at 1129583777
Oct 17 21:16:56 (none) tcphonehome[152]: setting call status to: Failed
Oct 17 21:16:57 (none) tcphonehome[152]: setting call in progress to 0 (second successCount)
Oct 17 21:17:01 (none) tcphonehome[152]: Setting callActive to 0
Oct 17 21:17:01 (none) comm[152]: CallStatusReporter: sending data changed event 20
Oct 17 21:17:01 (none) tcphonehome[152]: destroying CommGlobals!
Oct 17 21:17:01 (none) tcphonehome[152]: pCommMempool empty
Oct 17 21:17:10 (none) tcphonehome[152]: Setting MCP PhoneHome action: ENABLED

[petestrash]

You can attach the log to your post. or just post the next 40 lines or so after
'(none) comm[150]: End Ident =================='

But, looking at the bit you posted it seems that the TiVo is stuck on trying to communicate, so it does not allow any further calls.

Only fix is to reboot, let the TiVo settle 10-15 minutes and then try another call.

Peter

[mikepy]

I have rebooted several times but i'll try again

thanks

Mike

[petestrash]

'tmk tcp connect failed, reason = Operation now in progress' generally means the TiVo is already trying to call.

This usually only occurs when a previous call was corrupted and the TiVo got stuck.

Make sure you wait 10-15 minutes after the reboot and then only try one call.

Peter.

[mikepy]

Didn't make any difference i'm afraid

mike

[petestrash]

Did you still get 'tmk tcp connect failed, reason = Operation now in progress' after 'CommUtil: connection to host 127.0.0.1, port'

Peter.

[mikepy]

Same error

[petestrash]

It's got me stumped then.

Each time I have seen a TiVo stuck on Communicating, a reboot has always cleared the problem. But while it's stuck you won't be able to make a successful call.

Beyond redoing GS i'm out of Idea's, sorry.

Peter.

[mikepy]

:eek:

I tried a full GS and at the bit where it connects to the database i got the "Failed Service unavailable" error so i had to pull the plug and do a hard reboot.

This hasn't got anything to do with the proxy problem i read about somewhere has it?

Mike

[mikepy]

I just tried to get my logs from the emulator by inpuuting my Tivo serial no and came up with a blank?

Mike

[petestrash]

I tried a full GS and at the bit where it connects to the database i got the "Failed Service unavailable" error so i had to pull the plug and do a hard reboot.

If this was last Thursday afternoon / early Friday morning then it would be because of the problems at the server. So if you try again now it should work fine.


This hasn't got anything to do with the proxy problem i read about somewhere has it?

Your current problem doesn't have anything to do with that problem. It was fixed last Friday morning. Your problem may have been caused by the proxy problem if you re-did GS while the server was unreachable. Currently your tivo is not even attempting to call-out, as it thinks there is already a call in progress.


I just tried to get my logs from the emulator by inpuuting my Tivo serial no and came up with a blank?

That would be right as you have not had a slice in the last week.

Peter.

[mikepy]

at the dialling Tivo i got "Failed service unavailable" again

had to do a hard reboot and noew it keeps coming up in maintenance mode so i hard reboot again and it loops endlessly :eek:

Looks like my Tivo is a deceased Tivo

Mike

[mikepy]

I accessed the tivo in maintenance mode using Tiviweb - altered the boot parameters and then reset them and rebooted.
So i got passed that one but i still cant get it to phone in and therefore i can't record anything and funnily i cant watch live tv either?

Mike

[Darren King]

but i still cant get it to phone in and therefore i can't record anything

You can still do manual recordings.


and funnily i cant watch live tv either?

What are your boot parameters? If it says NTSC instead of PAL then I wouldn't expect you to watch live TV as the TiVo will be looking for the wrong video standard.

[mikepy]

It is set to PAL -
i was assuming it was something to do with having no guide data.
but i've noticed that when i change channell on the TIVO although the Tivo screen tell me i've changed the Sat box doesnt change.

I've checked all the cables and even if i change the sat box channel with its own controller the tivo is not passing it through to the telly

I'm a right pain arent I!

Mike

[mikepy]

Putting my old UK hard drive back in-

I can now watch Live TV but of course it wont change channels as the codes are for my old UK sat box.

when I change channels should i see the led's on the infra red blaster light up at all?

Mike

[petestrash]

I'm a right pain arent I!

Yes :D , but more seriously you just seem to be unlucky.


when I change channels should i see the led's on the infra red blaster light up at all?

You should see a faint flicker from one of the LED's when you press keys on your remote, but you won't see the blaster light up when it re-sends it's code unless you use a digital still or video camera to look at it. the signal is infrared and not visible to the human eye.

It seems you have nothing to lose by reimaging your other HDD and starting over.

Peter

[mikepy]

Is I can't re-image at the moment as i haven't got access to my Main PC
I can't see how i can do it from my notebook.

Mike

[petestrash]

That makes things difficult, but not impossible.

I'm fairly sure the system on the installer supports USB, so you could use a USB external case for the HDD.

I'd also be happy to do it for you, as long as you cover the postage.

Peter.

[daggo]

when I change channels should i see the led's on the infra red blaster light up at all?


If you have video camera, doesn't matter how old it is, you should be able to see IR by looking in the viewfinder of the camera. Just aim the remote at the camera and look in the viewfinder. Easy.

Matt

[mikepy]

Hi Thanks Pete - I might take you up on that

but one more try :)

I got this log from Tivoweb info page -- any ideas what thats about?

INTERNAL SERVER ERROR
--cut here--
action_info '/' ''
Invalid /Schedule format: ''
while executing
"error "Invalid /Schedule format: '[lindex $schedlist 1]'""
("uplevel" body line 30)
invoked from within
"uplevel $body"
invoked from within
"transaction {uplevel $body}"
(procedure "RetryTransaction" line 5)
invoked from within
"RetryTransaction {
set state [db $db open "/State/MyWorld"]
set channel [dbobj $state get LastChannel]
set chnum [dbobj $c..."
(procedure "::action_info" line 15)
invoked from within
"::action_$action $chan $part $env"
("eval" body line 1)
invoked from within
"eval {::action_$action $chan $part $env}"
--cut here--

[petestrash]

Usually you see those messages on a fairly recently imaged TiVo, it normally goes away after 24-48 hours once the TiVo has settled down.

Peter.

[mikepy]

so no help then.
Oh well :(