Error, DVSwitch.ini file not found.. But it's right there?!
sigmazgfx@...
ls: DVSwitch.ini MMDVM_Bridge MMDVM_Bridge.ini dvswitch.sh
I am running the .sh in the folder with the entire support cast
Test with the full path: ++ parseIniFile /usr/local/dvswitch-2019-03-16/opt/MMDVM_Bridge/DVSwitch.ini DSTAR TXPort ++ python -
+ _MBTX=
parseIniFile "$DVSWITCH_INI" "$_MODE" "RXPort"
++ parseIniFile /usr/local/dvswitch-2019-03-16/opt/MMDVM_Bridge/DVSwitch.ini DSTAR RXPort
++ python -
+ _MBRX=
+ '[' '!' -z ']'
+ echo 'Error, DVSwitch.ini file not found'
Error, DVSwitch.ini file not found
+ _ERRORCODE=-1
exit $_ERRORCODE
+ exit -1
Test with the symlink: parseIniFile "$DVSWITCH_INI" "$_MODE" "TXPort"
++ parseIniFile /opt/MMDVM_Bridge/DVSwitch.ini DSTAR TXPort
++ python -
+ _MBTX=
parseIniFile "$DVSWITCH_INI" "$_MODE" "RXPort"
++ parseIniFile /opt/MMDVM_Bridge/DVSwitch.ini DSTAR RXPort
++ python -
+ _MBRX=
+ '[' '!' -z ']'
+ echo 'Error, DVSwitch.ini file not found'
Error, DVSwitch.ini file not found
+ _ERRORCODE=-1
exit $_ERRORCODE
+ exit -1
|
|
If you have dvswitch.sh MMDVM_Bridge.ini and DVSwitch.sh in the same
directory without any other symlinks what happens with ./dvswitch.sh
mode DSTAR?
toggle quoted messageShow quoted text
On 7/9/20 10:05 PM, w2jon@...
wrote:
This was put onto an ARCH 4.14.97 OS .Why Arch? it was a Crompton ASL payload and I wanted to enhance it with DVSwitch.
|
|
sigmazgfx@...
This was put onto an ARCH 4.14.97 OS .Why Arch? it was a Crompton ASL payload and I wanted to enhance it with DVSwitch.
It's been up running happily for some time now so I cant remember all that much about the build. All of the /opt Symbolic links are all pointing back to the respective sources but they are under the /usr/local/dvswitch-2019-3-16/opt/... I know it's not a standard deployment and I shouldn't expect any support but the question remains, Why does it not see the file when it is actually there. The script is just looking for a file at a location right? Even if I define the long path it still complanes.. Mind you I am no Linux guru.. I only know enough to cobble things together to get them to work. Clearly my last cobble has some flaws in it. But can we get around this? I'll take the lumps.. That's how we learn...other than my overall build, where did I go wrong?
|
|
There may be a symlink from /opt/MMDVM_Bridge/dvswitch.sh to
/opt/Analog_Bridge/dvswitch.sh But that's it.
toggle quoted messageShow quoted text
On 7/9/20 9:50 PM, w2jon@...
wrote:
|
|
Thell me about the symlink
toggle quoted messageShow quoted text
On 7/9/20 9:54 PM, w2jon@...
wrote:
sorry steve.. here is the last bit of the debug output
|
|
sigmazgfx@...
sorry steve.. here is the last bit of the debug output
getTLVPort
++ getTLVPort
++ getABInfoValue tlv rx_port
getABInfoFileName
+++ getABInfoFileName
+++ '[' -z '' ']'
ls -t /tmp/ABInfo_*.json 2>/dev/null | head -1
++++ ls -t /tmp/ABInfo_34001.json
++++ head -1
+++ declare _json_file=/tmp/ABInfo_34001.json
+++ echo /tmp/ABInfo_34001.json
++ declare _json_file=/tmp/ABInfo_34001.json
++ python -
+ TLV_PORT=30000
+ '[' -z 30000 ']'
+ case $1 in
+ setMode
+ '[' 0 -eq 0 ']'
getABInfoValue tlv ambe_mode
++ getABInfoValue tlv ambe_mode
getABInfoFileName
+++ getABInfoFileName
+++ '[' -z '' ']'
ls -t /tmp/ABInfo_*.json 2>/dev/null | head -1
++++ head -1
++++ ls -t /tmp/ABInfo_34001.json
+++ declare _json_file=/tmp/ABInfo_34001.json
+++ echo /tmp/ABInfo_34001.json
++ declare _json_file=/tmp/ABInfo_34001.json
++ python -
+ echo DMR
DMR
exit $_ERRORCODE
+ exit 0
|
|
This should not be.
toggle quoted messageShow quoted text
On 7/9/20 9:50 PM, w2jon@...
wrote:
Th one thing that IS of note is that the /opt/MMDVM_Bridge folder is a symbolic link to /usr/local/dvswitch/opt/MMDVM_Bridge as are all of the other folders under /opt
|
|
sigmazgfx@...
DMR
|
|
huh?
toggle quoted messageShow quoted text
On 7/9/20 9:50 PM, w2jon@...
wrote:
Th one thing that IS of note is that the /opt/MMDVM_Bridge folder is a symbolic link to /usr/local/dvswitch/opt/MMDVM_Bridge as are all of the other folders under /opt
|
|
What does /opt/MMDVM_Bridge/dvswitch.sh mode return?
toggle quoted messageShow quoted text
On 7/9/20 9:12 PM, w2jon@...
wrote:
Hey Guys/Gals,
|
|
Th one thing that IS of note is that the /opt/MMDVM_Bridge folder is a symbolic link to /usr/local/dvswitch/opt/MMDVM_Bridge as are all of the other folders under /opt
Also I can manually CAT the /opt/MMDVM_Bridge/DVSwitch.ini file from the Analog_Bridge folder from where the DVSwitch.sh scriptis run..
|
|
sigmazgfx@...
HAHA.. no its good.. You're going through it with me. I appreciate it
Every thing is root including the group owners
|
|
What about group ownership . I am no help. sorry
On 7/9/2020 9:40 PM, w2jon@...
wrote:
The path in the .sh script is set to DVSWITCH_INI=${DVSWITCH_INI:-"/opt/MMDVM_Bridge/DVSwitch.ini"}
|
|
sigmazgfx@...
The path in the .sh script is set to DVSWITCH_INI=${DVSWITCH_INI:-"/opt/MMDVM_Bridge/DVSwitch.ini"}
The file permissions are 755 and the owner is root.. but everything is root on this pi.
|
|
isn't there a place to set the path to the .ini file ? I'm not
using the newer software so I don't know.
On 7/9/2020 9:37 PM, w2jon@...
wrote:
Yes Mike, that's what I meant.. wait a min....I thought I put.....
|
|
sigmazgfx@...
Yes Mike, that's what I meant.. wait a min....I thought I put.....
Yeah, That's the subject of this thread right?
|
|
Are you sure you did not mean DVSwitch.ini 'not found' ? If so set path and check permissions and ownership of the .ini
file
On 7/9/2020 9:31 PM, w2jon@...
wrote:
Crazy... Still no worky..
|
|
Crazy... Still no worky.. ( ./Analog_Bridge/dvswitch.sh mode DSTAR )
parseIniFile "$DVSWITCH_INI" "$_MODE" "TXPort"
++ parseIniFile /opt/MMDVM_Bridge/DVSwitch.ini DSTAR TXPort
++ python -
+ _MBTX=
parseIniFile "$DVSWITCH_INI" "$_MODE" "RXPort"
++ parseIniFile /opt/MMDVM_Bridge/DVSwitch.ini DSTAR RXPort
++ python -
+ _MBRX=
+ '[' '!' -z ']'
+ echo 'Error, DVSwitch.ini file not found'
Error, DVSwitch.ini file not found
+ _ERRORCODE=-1
exit $_ERRORCODE
+ exit -1
|
|
typo ? perhaps try to back out of the current director of it and specify the path to it ./dir/sub/xxx.sh after that I am out of guesses.
On 7/9/2020 9:17 PM, w2jon@...
wrote:
|
|
Yep I'm root and the files are owned by root as well.\
all processes except for some started by systemd+ (none related to this) are running under root
|
|