Re image problems

[tonys]

Don't know if I've got a problem or not!
Did a reimage yesterday, GS went ok, guide data has appeared, tivo wont let me set season passes etc as it's still indexing 12 hours later, is this normal?
Also, I noticed that the last daily call is noted as 'failed, service not available'
Again, will this sort itself out once the indexing is finished?
Finally, endpad isn't working ,also related to the indexing thing?

[tonys]

Hmmm, looks like something's wrong, just got home and checked, go into 'pick programmes to record' and it still says it's indexing data, 30 hours since GS! Going to force a daily call and then force an index, see if that clears it.

[tonys]

Went to force index, the forceindex.tcl file isn't in hack/bin! Anyone know where it is in the NZImage?

[tonys]

Message back from forced daily call: Service unavailable, tried again via Tivoweb, same problem. Anyone any ideas?

[DJC]

No this is not normal.

I imaged up a tivo last night, downloaded the image, installed, no problems at all.

No changes required from the stock 15 image to get it going.

Guide data appeared, indexing completed overnight. GS calls and daily calls are normal.

You might want to check for the usual, warped clock. touch /var/timestamps etc

My tivo has the relevant force indexes ...

[TiVo [p0] /hack/bin]# ls -l /hack/bin/force*
-rwxrwxr-x   1 0        0             433 Nov 20  2003 /hack/bin/force_index.tcl
lrwxrwxrwx   1 0        0              15 May 24  2005 /hack/bin/force_index30.tcl -> force_index.tcl
-rwxr-xr-x   1 0        0             248 Apr 18  2005 /hack/bin/forcedailycall.tcl

I just checked, same applies for the unit I just imaged.

[tonys]

Found them! Must have been a 'man look' as my wife describes it! Different layout than I'm used to seeing for some reason, had to scroll round to find them, bit like moving socks I suppose! Forced an index, see what that does...
No warped clock messages, timestamp is in /var, so that all looks ok
if the initial indexing failed for whatever reason, would that explain the failed daily calls? Still, at least the HDD hasn't got much on it if I have to reimage again!

[tonys]

Think I might have the solution, checked tclient.conf, which I haven't toched since installing the new image. Total of 4 'open' lines:

#dennis' emulator
126::66.23.218.193:80:::

#emu proxy problems (not exact wording, but something like)
127::127.0.0.1:8000:::

#nz legacy
126::210.48.107.133:80:::

#nz develop
128::210.48.107.133:8888:::

Surely there should only be one emulator line 'open' and it should be port 8000?

Which emulator does that mean I've set up against?

I think I feel a clear and delete all coming on! or maybe a complete reimage?

I say again, this config is as it appears from a straightforward install of the current NZ image

[DJC]

Yes, same as mine.

The only line that matters is the 127.

It uses emuproxy by default (127.0.0.1).

You need to ensure emuproxy is running.

[tonys]

ok, that's me lost!! How do I check that? Don't even know what it is!
As the 'Dennis' emulator line isn't hashed out, doesn't it mean that it tries there 1st?

[tonys]

Well ,it's suppossedly been indexing since 11.30 last night, no access to search by title etc, so I guess it's not finished (if it ever started!) looks like I'll have to reimage. Should I do a clear and delete all before reimaging? or does the reimage clear out all the old stuff anyway?
What is this emuproxy thing all about? Should it be running automatically after installing the NZ image?