Revisting NextCom R5000-HD and Having Issues

[checkbin99]

I have a Linux server running NextPVR 6 and a few years ago had it configured to work with my NextCom R50000-HD network encoder and DISH network.  I ad to switched to FIOS and have not used the R5000 and am now trying to set it up again.  The R500 is working perfectly writing to a QNAP network NFS share.  However when acccessing the R5000 from my NextPVR Linux server, the R5000 appears to b writing to the share but it is actually creating a zero byte file.   The file is readable and writeable by owner, group, and everyone else (666 permissions).  If from the command line as the NextPVR user (currently called sagetv I run the command:
    python3 r5000.py START R5ooo-HD 150   /R5000_Recordings/todays_test-on-the-r5000.  The opendct.sh file is called by an extra.xml file and the opendct calls an opendct.py script provided by Martin a few years ago.

The file todays_test-on-the-r5000 is created fine and has watchable video.

My opendct.sh file is as follows:
nextname=//R5000_Recordings//$2.ts

openname=\\R5000_Recordings/$2.ts

#example translations
#nextname=/media/recordings/$2.ts
#openname=\\172.16.3.105\Recordings\$2.ts
#openname=K:\$2.ts

opendct=/var/opt/nextpvr/scripts/opendct.py

python3 $opendct STOP "$2"
python3 $opendct START "$2" $1 "$openname"
python3 $opendct GET_SIZE "$2"
ffmpeg -re -i "$nextname" -f mpegts -codec copy -v panic -
#ffmpeg -re -i "$nextname" -f mpegts -codec copy -
#ffmpeg -re -i "$nextname" -f mpegts -codec copy -y /dev/null
python3 $opendct STOP "$2"
rm "$nextname"

I've been beating my head against the wall on this for days now to no avail.  Frustrating since it was working the last time I used it bad sadly don't have all the config files from when it was.  Since it still works in SageTV it seems like I'm missing something simple, but I can't wrap my head around it.  Can anyone point me in the right direction on this.

-Bil

[mvallevand]

I would start be writing some test python and see if python runs in the PreStartup.sh script. python might not work as the nextpvr user

Martin

[checkbin99]

Thanks Martin. But wouldn't the fact that the command " python3 r5000.py START R5ooo-HD 150 /R5000_Recordings/todays-test-on-the-r5000" records a file perfectly on the same share prove that python is working as expected?

[mvallevand]

That doesn't look like a file nextpvr would create. I don't know how python is installed on your machine bur running as user nextpvr will be completely different from any other user account, that is why you want to test.

Martin