If you could enable the debug log and trace files in emuProxyZA, this should enable us to determine where the problem lies.
First thing that needs to be done is to kill the running instance of emuProxyZA, this is done as follows:
Code:
ps ax (look for the emuProxyZA pid in the list returned)
kill pid (replace pid with the emuProxyZA pid from above e.g. kill 154)
You can now start emuProxyZA with the debug and trace files enabled as follows:
Code:
/hack/bin/emuProxyZA -ds /var/log/ -dc /var/log/ -d2 > /var/log/emuProxyZA.log 2>&1 &
Once done, you can initiate a daily call and wait until if fails.
Your TiVo's '/var/log/' directory should now contain a file named 'emuProxyZA.log', this is the debug log. There should also be a number of files named 'epXRequest.log' and 'epXResponse.log' (X being a number), these are the trace files of all the requests made by your TiVo and the responses received from the server. If you could zip up both the debug log as well as all the trace files and post them here, we may be able to determine where things are failing.
Bookmarks