SharkRF IP Connector Protocol Server

DO3DL
Posts: 7
Joined: Sat Oct 29, 2016 10:40 am

Re: SharkRF IP Connector Protocol Server

Post by DO3DL »

I give up for the moment. I rebuilt the Raspberry today and installed PHP 5.6. Unfortunately without success. The server works, but the dashboard still does not work. FYI: on my "old" server of 2016, it works fine. A colleague here from the forum should install the server and report...


DO3DL / Markus
W4INT
Posts: 7
Joined: Sat Dec 21, 2019 4:29 am
Location: Lewisville, NC

Re: SharkRF IP Connector Protocol Server

Post by W4INT »

I appear to have same error as others.. srf-ip-conn-srv.socket is not being created. I have ensured the directory is available (I manually created it) and that the app is running and pidof returns a PID.

Here is the error entry from Apache error log

[Mon Dec 23 07:56:32.849293 2019] [:error] [pid 3782] [client 45.36.142.83:51683] PHP Warning: stream_socket_client(): unable to connect to unix:///var/sharkrf/srf-ip-conn-srv.socket (No such file or directory) in /var/www/html/srf-ip-conn-srv/dashboard/api.php on line 11, referer: http://155.138.230.78/

Thx in advance!!

-Brad - W4INT
User avatar
HA2NON
SharkRF team
SharkRF team
Posts: 5580
Joined: Fri Mar 25, 2016 3:33 pm
Contact:

Re: SharkRF IP Connector Protocol Server

Post by HA2NON »

/var/sharkrf/srf-ip-conn-srv.socket is a path which usually can only be written by the root user. Make sure the running process has proper privileges for the path. It's best to use /tmp to create these temporary socket files.
Norbert Varga, HA2NON
SharkRF Team
W4INT
Posts: 7
Joined: Sat Dec 21, 2019 4:29 am
Location: Lewisville, NC

Re: SharkRF IP Connector Protocol Server

Post by W4INT »

Thanks for the reply. I created a directory in /tmp/sharkrf and restarted everything. Updated config.json and config.inc.php with negative results. The app still does not create the socket file 2nd to launching it.

maybe its how its being launched.

docker run -p 8001:8001 -p 65100:65100/udp ppicazo/srf-ip-conn-srv

Any idea where I can look next? could it be because I am using docker?

To note the server is working correctly just cannot get the GUI component to cooperate.

-Brad W4INT
User avatar
HA2NON
SharkRF team
SharkRF team
Posts: 5580
Joined: Fri Mar 25, 2016 3:33 pm
Contact:

Re: SharkRF IP Connector Protocol Server

Post by HA2NON »

Please try first without Docker. I can't help you with Docker right now as the colleague who knows Docker stuff is out of office until next year.
Norbert Varga, HA2NON
SharkRF Team
W4INT
Posts: 7
Joined: Sat Dec 21, 2019 4:29 am
Location: Lewisville, NC

Re: SharkRF IP Connector Protocol Server

Post by W4INT »

Will do.. Changing gears and trying to compile I get the below error that appears it cannot see the compiler that is installed.

I cannot figure out how to tell cmake where to find the compiler.

SRF_IP_CONN_PATH=/var/sharkrf/srf-ip-conn JSMN_PATH=/var/sharkrf/jsmn ./build-release.sh

-- The C compiler identification is GNU 6.3.0
-- The CXX compiler identification is unknown
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
CMake Error in CMakeLists.txt:
No CMAKE_CXX_COMPILER could be found.

Tell CMake where to find the compiler by setting either the environment
variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
to the compiler, or to the compiler name if it is in the PATH.

-- Configuring incomplete, errors occurred!
See also "/var/sharkrf/srf-ip-conn-srv/build/CMakeFiles/CMakeOutput.log".
See also "/var/sharkrf/srf-ip-conn-srv/build/CMakeFiles/CMakeError.log".
make: *** No targets specified and no makefile found. Stop.


>> I attempted to add the path to cmake in CMakeCache.txt then I get below when running compile command.

-- The CXX compiler identification is unknown
-- Check for working CXX compiler: /usr/bin/cmake
-- Check for working CXX compiler: /usr/bin/cmake -- broken

CMake Error at /usr/share/cmake-3.7/Modules/CMakeTestCXXCompiler.cmake:44 (message):
The C++compiler "/usr/bin/cmake" is not able to compile a simple test program.


Thanks for your assistance as I had prefer to run this without docker.

-Brad / W4INT
User avatar
HA2NON
SharkRF team
SharkRF team
Posts: 5580
Joined: Fri Mar 25, 2016 3:33 pm
Contact:

Re: SharkRF IP Connector Protocol Server

Post by HA2NON »

Please install g++.
Norbert Varga, HA2NON
SharkRF Team
W4INT
Posts: 7
Joined: Sat Dec 21, 2019 4:29 am
Location: Lewisville, NC

Re: SharkRF IP Connector Protocol Server

Post by W4INT »

g++ installed. Same error..

Is there anyone else out there that has been able to compile the app by only following the steps in the instructions? I have a strong feeling that their are steps missing. I work in IT and follow instructions well but this is very discouraging. If it matters I am trying to do this using Debian 9.

Thanks for any help or sympathy :)

-Brad W4INT
W4INT
Posts: 7
Joined: Sat Dec 21, 2019 4:29 am
Location: Lewisville, NC

Re: SharkRF IP Connector Protocol Server

Post by W4INT »

<BUMP> Anyone able to document the steps required to compile the server App in Linux?

My issues are that the compile process returns errors as apparently needs additional settings.

Thanks in advance.

-Brad W4INT
k9agr
Posts: 24
Joined: Sun Jun 10, 2018 8:59 pm

Re: SharkRF IP Connector Protocol Server

Post by k9agr »

On a fresh ubuntu 18.04 LTS system, I did the following set of commands, applying my system administration skills to know that I needed a build environment installed if I wanted to build things, then following the directions from https://github.com/sharkrf/srf-ip-conn-srv.

Code: Select all

sudo apt install build-essential cmake
mkdir /tmp/srf
cd /tmp/srf
git clone https://github.com/sharkrf/srf-ip-conn-srv
git clone https://github.com/sharkrf/srf-ip-conn
git clone https://github.com/zserge/jsmn
cd jsmn
git checkout 732d283ee9a2e5c34c52af0e044850576888ab09
cd ../srf-ip-conn-srv/build
SRF_IP_CONN_PATH=/tmp/srf/srf-ip-conn JSMN_PATH=/tmp/srf/jsmn ./build-release.sh
This compiled everything as expected. I used /tmp/srf to keep the paths short for this example, use your own judgement on where to build the software. I typically do that under /usr/local/src.

I hope this helps to point you in the right direction to figure out what is missing.

73 de K9AGR
Post Reply