I'm running NCIDD fine on a Series 2 running 4.0.1b. When I start tivoncid it errors out. Here is the output just running and running verbose:
bash-2.02# tivoncid & [1] 336
bash-2.02# .//tivoncid: .//setpri: cannot execute binary file
invalid command name "0"
while executing
"0"
(procedure "displayLog" line 1)
invoked from within
"displayLog "Connecting to $Host:$Port""
(procedure "connectCID" line 15)
invoked from within
"connectCID $Host $Port"
(file ".//tivoncid" line 579)
This is a bug with the TiVo tivosh program. The "set Program ..." variable must be at the end of the ncid.conf file. NCID Version 0.67 will have the fix. For version 0.66, remove ncid.conf, or move the "set Program ..." line and its comment to the end of the file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried installing out2osd and running tivocid and got the same error. That was with version 0.66. I installed version 0.65 and ran tivocid and it is working fine.
Thanks,
Tony
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It seems there are two problems. The first is that tivoncid and tivocid looks for the command "setpri" to execute it. Your error message indicates the execute bit is not set or the binary file is corrupt. You need to make user the execute bit is on, and try to execute it directly.
The second problem needs more troubleshooting, but it could be that the tar file is corrupt or the ncid client is corrupt. You can install NCID version 0.66 and just run the ncid client from 0.65 if the ncid client from 0.66 is defective. That way you get the server fixes.
If you can do some testing and try out stuff for me, send me a email.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Did you reinstall NCID version 0.66 or just use the client from 0.65? I have had a report that using just the client from 0.65 works, and I have also have a report that removing the client configuration file, ncid.conf, alows the 0.66 ncid client to work. Could you try removing the client config file and post the results?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was having the same problem as toanders. I renamed the ncid.conf file as jlc suggested (effectively removing it) and that resolved the error. I start the client at the bash prompt with the command: /var/hack/bin/tivoncid &
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm running NCIDD fine on a Series 2 running 4.0.1b. When I start tivoncid it errors out. Here is the output just running and running verbose:
bash-2.02# tivoncid &
[1] 336
bash-2.02# .//tivoncid: .//setpri: cannot execute binary file
invalid command name "0"
while executing
"0"
(procedure "displayLog" line 1)
invoked from within
"displayLog "Connecting to $Host:$Port""
(procedure "connectCID" line 15)
invoked from within
"connectCID $Host $Port"
(file ".//tivoncid" line 579)
[1]+ Exit 1 tivoncid
bash-2.02# tivoncid -V
.//tivoncid: .//setpri: cannot execute binary file
Connecting to 127.0.0.1:3333
BGError: invalid command name "0"
I haven't modified any files, although I've looked at the config file. Am I doing something obviously wrong?
Thanks,
Tony
This is a bug with the TiVo tivosh program. The "set Program ..." variable must be at the end of the ncid.conf file. NCID Version 0.67 will have the fix. For version 0.66, remove ncid.conf, or move the "set Program ..." line and its comment to the end of the file.
I tried installing out2osd and running tivocid and got the same error. That was with version 0.66. I installed version 0.65 and ran tivocid and it is working fine.
Thanks,
Tony
It seems there are two problems. The first is that tivoncid and tivocid looks for the command "setpri" to execute it. Your error message indicates the execute bit is not set or the binary file is corrupt. You need to make user the execute bit is on, and try to execute it directly.
The second problem needs more troubleshooting, but it could be that the tar file is corrupt or the ncid client is corrupt. You can install NCID version 0.66 and just run the ncid client from 0.65 if the ncid client from 0.66 is defective. That way you get the server fixes.
If you can do some testing and try out stuff for me, send me a email.
I am getting same error as above EXCEPT when I run:
Super-TiVo# tivoncid -V
Connecting to 127.0.0.1:3333
127.0.0.1:3333 - error reading "sock11": connection refused
Connecting to 127.0.0.1:3333
127.0.0.1:3333 - error reading "sock11": connection refused
Connecting to 127.0.0.1:3333
127.0.0.1:3333 - error reading "sock11": connection refused
Connecting to 127.0.0.1:3333
127.0.0.1:3333 - error reading "sock11": connection refused
Connecting to 127.0.0.1:3333
127.0.0.1:3333 - error reading "sock11": connection refused
NCIDD runs fine, started when I upgraded to .66 - any thoughts?
john
and - going back to .65 works fine
Did you reinstall NCID version 0.66 or just use the client from 0.65? I have had a report that using just the client from 0.65 works, and I have also have a report that removing the client configuration file, ncid.conf, alows the 0.66 ncid client to work. Could you try removing the client config file and post the results?
I was having the same problem as toanders. I renamed the ncid.conf file as jlc suggested (effectively removing it) and that resolved the error. I start the client at the bash prompt with the command: /var/hack/bin/tivoncid &