Compile the aprsc in Raspberry pi

[Francis LEE]

Dear all

I am tried to compile the aprsc on the raspberry pi platform for testing purpose. However, it prompt “aprsc: unrecognized service” when I enter:

sudo service aprsc start


Here is my steps to compile, and login as root.

1/ Install libevent2 :

wget https://github.com/downloads/libevent/libevent/libevent-2.0.21-stable.tar.gz
tar xzf libevent-2.0.21-stable.tar.gz
cd libevent-2.0.21-stable
./ configure
make
make install

NO Error prompt on libevent2 installation.


2/ Prepare the environment:

adduser --system --no-create-home --home /var/run/aprsc --shell /usr/sbin/nologin --group aprsc

However, it prompt no folder /var/run/aprsc, so I make it by myself:
mkdir /var/run/aprsc

and run the adduser script again, no warning prompt.


3/ Download & compiling the aprsc:

wget http://he.fi/aprsc/down/aprsc-latest.tar.gz
tar xvfz aprsc-latest.tar.gz
cd aprsc-2.0.1.g7a4bcfe

however, cannot run ./configure, so

cd src
./configure
make
make install

it seems some error found during make & make install

I refer some posts, they said compile to a dkpg package, but still unsuccessful.

Anyone can help ?

Thanks in advance.

[Heikki Hannikainen]

Hi,

On Thu, 21 Mar 2013, Francis LEE wrote:

> I am tried to compile the aprsc on the raspberry pi platform for testing
> purpose. However, it prompt “aprsc: unrecognized service” when I enter:

https://groups.google.com/d/msg/aprsc/6h3FARAytf4/OSLBaaJRHCUJ

> I refer some posts, they said compile to a dkpg package, but still unsuccessful.

Compile and install the dpkg, that works fine.

In src, ./configure, then make make-deb, and dpkg -i the resulting deb.

- Hessu

[Francis LEE]

Hi Heikki

While I proceed "make make-deb", there are some error prompted, and cannot create the package. Can you help ?

dpkg-buildpackage: source changed by aprsc maintainer <aprsc@ham>
dpkg-buildpackage: host architecture armhf
dpkg-source --before-build src
dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 4) lsb-release (>= 3)
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
dpkg-buildpackage: warning: (Use -d flag to override.)
make: *** [make-deb] Error 3

[Johan Hansson]

You need to install debhelper and lsb-release

apt-get update

apt-get install debhelper lsb-release

//SM0TSC

2013/3/21 Francis LEE <franci...@gmail.com>

--
You received this message because you are subscribed to the Google Groups "aprsc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aprsc+un...@googlegroups.com.
To post to this group, send email to ap...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/aprsc/-/bXS-TzhKWTYJ.
For more options, visit https://groups.google.com/groups/opt_out.

[Francis LEE]

Dear all

After I follow SM0TSC instruction, it seems work !

Million thanks yours help !

Br
Francis

Francis LEE於 2013年3月21日星期四UTC+8下午8時42分03秒寫道：

[Francis LEE]

Hi all

I cannot reach the aprsc http web by http://192.168.2.110:14501 (the IP address of raspberry pi), does any addition package request to install ?

I suspect the libevent2 download & compile not compatible with RPi, so I install others packge by "sudo apt-get install libevent-dev", but no help.

Tks in advance.

[9W2CEH - Bonar]

I've compile manually on Raspi and run ok. You have to download the libevent2 from main website and also compile manual. You have to tell aprsc where to get the libevent.a from libevent2. Just view the configure file on aprsc/src and look for libevent2. That's what I did.

Bonar
De 9W2CEH
http://aprs.myaprs.my:14501

--
You received this message because you are subscribed to the Google Groups "aprsc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aprsc+un...@googlegroups.com.
To post to this group, send email to ap...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msg/aprsc/-/GsQGN3S6BOEJ.

For more options, visit https://groups.google.com/groups/opt_out.

73, see ya..

[Heikki Hannikainen]

On the RPi, if you're running raspbian, I don't think it is necessary to
download and install libevent2 manually, since raspberry already comes
with libevent 2.0!

"sudo apt-get install libevent-dev" should be enough.

make make-deb probably fails spectacularly if you don't have the necessary
dependencies installed for building the http server.

Check your config file and log file for messages regarding the http
service. Depending on your config, it should have some messages like this:

hessu@rpi:/opt/aprsc/logs$ grep HTTP aprsc.log
2013/03/11 23:40:32.088598 aprsc[6915:4198c470] INFO: HTTP thread
starting...
2013/03/11 23:40:32.089357 aprsc[6915:4198c470] INFO: Binding HTTP upload
socket 85.188.1.32:8080
2013/03/11 23:40:32.090584 aprsc[6915:4198c470] INFO: Binding HTTP upload
socket 2001:67c:15c:1::32:8080
2013/03/11 23:40:32.091203 aprsc[6915:4198c470] INFO: Binding HTTP status
socket 85.188.1.32:14501
2013/03/11 23:40:32.091767 aprsc[6915:4198c470] INFO: Binding HTTP status
socket 2001:67c:15c:1::32:14501
2013/03/11 23:40:32.092321 aprsc[6915:4198c470] INFO: HTTP thread ready.


hessu@rpi:~$ dpkg -l|grep libev
ii libevent-2.0-5:armhf 2.0.19-stable-3
armhf Asynchronous event notification library
ii libevent-core-2.0-5:armhf 2.0.19-stable-3
armhf Asynchronous event notification library (core)
ii libevent-dev 2.0.19-stable-3
armhf Asynchronous event notification library (development files)
ii libevent-extra-2.0-5:armhf 2.0.19-stable-3
armhf Asynchronous event notification library (extra)
ii libevent-openssl-2.0-5:armhf 2.0.19-stable-3
armhf Asynchronous event notification library (openssl)
ii libevent-pthreads-2.0-5:armhf 2.0.19-stable-3
armhf Asynchronous event notification library (pthreads)

- Hessu

[Francis LEE]

Hi Hessu , Bonar & all

I still cannot access the status page by ipaddress:14501 .

I apt-get to install the libevent-dev, and I found the path of libevent.a is: "/usr/lib/arm-linux-gnueabihf/libevent.a"

so I modified the path of libevent.a to above path on the following 3 files, which under src sub-folder and contain default libevent.a path:
\src\rpm\aprsc.spec.in
\src\rpm\aprsc.spec
\src\debian\rules

After install the deb package, I serach again on the libevent.a, and found one more location which under aprsc folder:
/opt/aprsc/usr/lib/arm-linux-gnueabihf/libevent.a

I re-tried the procedure on a new flash image of Raspbian wheezy, manually download the libevent2 & from its web, and found it installation path is "/home/pi/libevent-2.0.21-stable/.libs/libevent.a".

Then modifed the paths of the 3 files to /home/pi/libevent-2.0.21-stable/.libs/libevent.a , but still no help. The path of the libevent.a under aprsc/usr/lib
is same as above one, so it may means the "/home/pi/libevent-2.0.21-stable/.libs/libevent.a " is no use.

I refer the log of HTTP , and cannot found any abnormal.

pi@raspberrypi /opt/aprsc/logs $ sudo grep HTTP aprsc.log
2013/04/04 15:49:20.353157 aprsc[2380:b5cfb470] INFO: HTTP thread starting...
2013/04/04 15:49:20.354050 aprsc[2380:b5cfb470] INFO: Binding HTTP upload socket 0.0.0.0:8080
2013/04/04 15:49:20.355154 aprsc[2380:b5cfb470] INFO: Binding HTTP status socket 0.0.0.0:14501
2013/04/04 15:49:20.355709 aprsc[2380:b5cfb470] INFO: HTTP thread ready.
2013/04/04 15:57:34.127350 aprsc[2486:b5d6e470] INFO: HTTP thread starting...
2013/04/04 15:57:34.128301 aprsc[2486:b5d6e470] INFO: Binding HTTP upload socket 192.168.2.108:8080
2013/04/04 15:57:34.129443 aprsc[2486:b5d6e470] INFO: Binding HTTP status socket 192.168.2.108:14501
2013/04/04 15:57:34.130014 aprsc[2486:b5d6e470] INFO: HTTP thread ready.
2013/04/04 15:57:58.346609 aprsc[2593:b5cf3470] INFO: HTTP thread starting...
2013/04/04 15:57:58.347481 aprsc[2593:b5cf3470] INFO: Binding HTTP upload socket 192.168.2.108:8080
2013/04/04 15:57:58.348666 aprsc[2593:b5cf3470] INFO: Binding HTTP status socket 192.168.2.108:14501
2013/04/04 15:57:58.349241 aprsc[2593:b5cf3470] INFO: HTTP thread ready.
2013/04/04 15:59:10.961546 aprsc[1994:b5d0f470] INFO: HTTP thread starting...
2013/04/04 15:59:10.962429 aprsc[1994:b5d0f470] INFO: Binding HTTP upload socket 192.168.2.108:8080
2013/04/04 15:59:10.963558 aprsc[1994:b5d0f470] INFO: Binding HTTP status socket 192.168.2.108:14501
2013/04/04 15:59:10.964149 aprsc[1994:b5d0f470] INFO: HTTP thread ready.
2013/04/04 16:18:45.508295 aprsc[2318:b5d92470] INFO: HTTP thread starting...
2013/04/04 16:18:45.509152 aprsc[2318:b5d92470] INFO: Binding HTTP upload socket 192.168.2.108:8080
2013/04/04 16:18:45.510341 aprsc[2318:b5d92470] INFO: Binding HTTP status socket 192.168.2.108:14501
2013/04/04 16:18:45.510930 aprsc[2318:b5d92470] INFO: HTTP thread ready.
2013/04/04 16:22:02.191584 aprsc[2008:b5d02470] INFO: HTTP thread starting...
2013/04/04 16:22:02.192475 aprsc[2008:b5d02470] INFO: Binding HTTP upload socket 0.0.0.0:8080
2013/04/04 16:22:02.193634 aprsc[2008:b5d02470] INFO: Binding HTTP status socket 0.0.0.0:14501
2013/04/04 16:22:02.194185 aprsc[2008:b5d02470] INFO: HTTP thread ready.

Any hits or additionl package request for the service ? Thanks in advance.

[Heikki Hannikainen]

Hi,

On Thu, 4 Apr 2013, Francis LEE wrote:

> I still cannot access the status page by ipaddress:14501 .

> I refer the log of HTTP , and cannot found any abnormal.
>
> pi@raspberrypi /opt/aprsc/logs $ sudo grep HTTP aprsc.log
> 2013/04/04 15:49:20.353157 aprsc[2380:b5cfb470] INFO: HTTP thread starting...
> 2013/04/04 15:49:20.354050 aprsc[2380:b5cfb470] INFO: Binding HTTP upload socket 0.0.0.0:8080
> 2013/04/04 15:49:20.355154 aprsc[2380:b5cfb470] INFO: Binding HTTP status socket 0.0.0.0:14501
> 2013/04/04 15:49:20.355709 aprsc[2380:b5cfb470] INFO: HTTP thread ready.

You have all the necessary packages installed. If some packages or
libraries were missing, the above lines would not appear at all. Also,
your aprsc.conf configuration is good, the HTTP server is configured and
running. So, libevent is fine.

Maybe you have some firewall blocking the ports?

What exactly is the error message you get when you try to access the
service? Connection refused? No route to host? Something else?

- Hessu

[9W2 CEH]

Hi Hessu, Lee & list..

For quick check, can you browse it using the Raspi browser itself?

If you can then might be firewall is blocking the port 14501..

just browse http://127.0.0.1:14501 or by using it's own IP http://192.168.2.108:14501

I can see you have 192.168.2.108:14501 and 0.0.0.0:14501 ...

I don't know if this in the same config or separate config..

supposed to just configure 0.0.0.0:14501

Bonar
De 9W2CEH
http://aprs.myaprs.my:14501

--
You received this message because you are subscribed to the Google Groups "aprsc" group.

To unsubscribe from this group and stop receiving emails from it, send an email to aprsc+unsubscribe@googlegroups.com.

To post to this group, send email to ap...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
--
9W2CEH,
73

[Francis LEE]

Hi Hessu , Bonar & all

Yes, I tried the RPI browse http://127.0.0.1:14501 & http://192.168.2.108:14501 on the X windows's browser,but fail. It prompt:
" the page 'http://127.0.0.1:14501 ' couldnot be loaded, Cannot connect to destination 127.0.0.1 ."

That's why I think does it also request some web server package for the web status page, such as apache or Nginx .

[9W2 CEH]

Aprsc doesn't need any other web engine... It's built in.
Can you removed all files at /opt/aprsc and then reinstall fresh one?
please copied over the "make install" output..
Maybe Hessu or anybody else have some idea on that output data..
Thanks...

Bonar
de 9W2CEH
http://aprs.myaprs.my:14501/

--
You received this message because you are subscribed to the Google Groups "aprsc" group.

To unsubscribe from this group and stop receiving emails from it, send an email to aprsc+un...@googlegroups.com.

To post to this group, send email to ap...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msg/aprsc/-/Bur6PSgblBIJ.

[Heikki Hannikainen]

It does not, the web server is built in. Trust me, I put it in there. If
you run some other web server on port 14501, aprsc's built-in server
cannot operate.

Let's try a few steps.

1) Could you try to get a more precise error message than the
"user-friendly" one. Run the following commands on the pi:

sudo apt-get install curl
curl -v http://127.0.0.1:14501/

like this:

hessu@jazz:~$> curl -v http://127.0.0.1:14501/
* About to connect() to 127.0.0.1 port 14501 (#0)
* Trying 127.0.0.1... Connection refused
* couldn't connect to host

The *real* error message is "Connection refused" in this case. What does
yours say? Please cut and paste the whole output!

2) Is aprsc running? Can you telnet / connect to port 14580?
"ps ax|grep aprsc" should display the aprsc process.

3) Do you have a firewall set up? Please run the following command and
cut-n-paste the output here:

sudo iptables -L -n -v

- Hessu

[Francis LEE]

Hi Hessu

1/
pi@raspberrypi ~ $ curl -v http://127.0.0.1:14501/

* About to connect() to 127.0.0.1 port 14501 (#0)
* Trying 127.0.0.1...

* Connection refused

* couldn't connect to host

* Closing connection #0
curl: (7) couldn't connect to host

==========================================

2/
pi@raspberrypi ~ $ ps ax|grep aprsc
2290 pts/0 S+ 0:00 grep --color=auto aprsc

==========================================

3/ There are no firewall policy setup on the raspberry pi
pi@raspberrypi ~ $ sudo iptables -L -n -v
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

==========================================

4/ For the telnet, I found that there are no telnet bundled on Raspbian Wheezy, so I install it by myself.

pi@raspberrypi ~ $ telnet 127.0.0.1:14580
telnet: could not resolve 127.0.0.1:14580/telnet: Name or service not known

Million thanks your help, I would like to know which Raspbian Wheezy version using ? I am using the latest release "2013-02-09-wheezy-raspbian". What I worry is the bundled package may alter to cause it not work.

[Heikki Hannikainen]

On Sat, 6 Apr 2013, Francis LEE wrote:

> 1/
> pi@raspberrypi ~ $ curl -v http://127.0.0.1:14501/
> * About to connect() to 127.0.0.1 port 14501 (#0)
> * Trying 127.0.0.1...
> * Connection refused

That means nothing is listening on port 14501

> 2/
> pi@raspberrypi ~ $ ps ax|grep aprsc
> 2290 pts/0 S+ 0:00 grep --color=auto aprsc

Hm, no aprsc process, aprsc is not running right now?

What happens if you run it, /etc/init.d/aprsc start ? Or /etc/init.d/aprsc
restart ?

> 3/ There are no firewall policy setup on the raspberry pi
> pi@raspberrypi ~ $ sudo iptables -L -n -v

Ok, good.

> 4/ For the telnet, I found that there are no telnet bundled on Raspbian Wheezy, so I install it by myself.
>
> pi@raspberrypi ~ $ telnet 127.0.0.1:14580
> telnet: could not resolve 127.0.0.1:14580/telnet: Name or service not known

For telnet you'll have to put a space between the IP address and port,
telnet 127.0.0.1 14580

> Million thanks your help, I would like to know which Raspbian Wheezy
> version using ? I am using the latest release
> "2013-02-09-wheezy-raspbian". What I worry is the bundled package may
> alter to cause it not work.

Latest. A small difference in Raspbian version is unlikely to have any
difference. aprsc is quite portable and runs unmodified on a very large
variety of very different systems, including OS X, Solaris, Windows, and
many different Linux systems.

- Hessu

[Francis LEE]

Hi Hessu & all

The aprsc seems activitied during boot up, please refer attached photo. I also use command "sudo service aprsc start" after bootup.

But the result of "ps ax|grep aprsc " same as last time.

for the command "/etc/init.d/aprsc start ", it seems the result is OK.
pi@raspberrypi ~ $ /etc/init.d/aprsc restart
[....] Testing aprsc configuration:: aprscaprsc: chroot(/opt/aprsc) failed: Oper ation not permitted
failed!
pi@raspberrypi ~ $ sudo /etc/init.d/aprsc restart
[ ok ] Testing aprsc configuration:: aprsc[....] Stopping APRS-IS server:: aprsc.
[ ok ] Preparing chroot for APRS-IS server:: aprsc chroot.
[ ok ] Starting APRS-IS server:: aprsc.
pi@raspberrypi ~ $


for the command " /etc/init.d/aprsc restart", it seems OK, too.
pi@raspberrypi ~ $ sudo /etc/init.d/aprsc restart
[ ok ] Testing aprsc configuration:: aprsc[....] Stopping APRS-IS server:: aprsc.
[ ok ] Preparing chroot for APRS-IS server:: aprsc chroot.
[ ok ] Starting APRS-IS server:: aprsc.


Telnet to 14580, it is connection refused

pi@raspberrypi ~ $ telnet 127.0.0.1 14580

Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused


It seems the package I complied got problem, I refer Bonar opinion, I use another SD card to re-do the installation and capture the result of 'make make-deb". I found a warning appears in the login.c. Compare result attached as a file "complie.txt".

# Add here commands to compile the package.
/usr/bin/make
make[2]: Entering directory `/home/pi/aprsc-2.0.1.g7a4bcfe/src'
gcc -Wall -g -O2 -Wall -Wstrict-prototypes -D_REENTRANT -c aprsc.c
gcc -Wall -g -O2 -Wall -Wstrict-prototypes -D_REENTRANT -c accept.c
gcc -Wall -g -O2 -Wall -Wstrict-prototypes -D_REENTRANT -c worker.c
gcc -Wall -g -O2 -Wall -Wstrict-prototypes -D_REENTRANT -c errno.c
gcc -Wall -g -O2 -Wall -Wstrict-prototypes -D_REENTRANT -c login.c
login.c: In function âlogin_handlerâ:
login.c:339:3: warning: implicit declaration of function âstrcasestrâ [-Wimplicit-function-declaration] <=======
gcc -Wall -g -O2 -Wall -Wstrict-prototypes -D_REENTRANT -c incoming.c
gcc -Wall -g -O2 -Wall -Wstrict-prototypes -D_REENTRANT -c dupecheck.c
gcc -Wall -g -O2 -Wall -Wstrict-prototypes -D_REENTRANT -c outgoing.c


Thanks you for yours help.

[Heikki Hannikainen]

Hi,

On Mon, 8 Apr 2013, Francis LEE wrote:

> The aprsc seems activitied during boot up, please refer attached photo. I also use command "sudo service aprsc start" after bootup.
>
> But the result of "ps ax|grep aprsc " same as last time.

Do a "tail -20 /opt/aprsc/aprsc.log" after reboot, see what are the last
messages there. Maybe it compiles about not listening on any IP addresses?

I'm guessing ipv6 module is missing, and your aprsc configuration uses
IPv6 Listen syntax (:: as local IP address).

I just released "official" RPi aprsc packages, you can switch to those
instead of building your own. The ipv6 hint in the previous email might
help.

> login.c: In function âlogin_handlerâ:
> login.c:339:3: warning: implicit declaration of function âstrcasestrâ [-Wimplicit-function-declaration] <=======

Just a warning, not relevant.

- Hessu

[Johan Hansson]

Try to use

make make-deb 

Instead that way you will get a deb package wich you install med dpkg -i package name and it will install all config files / init scripts etc correctly

//Johan - SM0TSC

2013/4/8 Francis LEE <franci...@gmail.com>

--
You received this message because you are subscribed to the Google Groups "aprsc" group.

To unsubscribe from this group and stop receiving emails from it, send an email to aprsc+un...@googlegroups.com.

To post to this group, send email to ap...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msg/aprsc/-/t9KVHHx_6poJ.

[Francis LEE]

Hi Hessu

pi@raspberrypi ~ $ sudo tail -20 /opt/aprsc/logs/aprsc.log

2013/04/08 08:41:00.934393 aprsc[2033:b5dc0470] INFO: Binding listening TCP socket: [::]:10152
2013/04/08 08:41:00.962004 aprsc[2033:b5dc0470] CRIT: socket(): Address family not supported by protocol

2013/04/08 08:41:00.962296 aprsc[2033:b5dc0470] CRIT: Failed to listen on any ports.

It seems the system listen to IPv6 only, not IPv4 that I using.

I really appreciate your help and release the wheezy (raspbian) package, I will try it soon.

Br
Francis

[Heikki Hannikainen]

On Mon, 8 Apr 2013, Francis LEE wrote:

> pi@raspberrypi ~ $ sudo tail -20 /opt/aprsc/logs/aprsc.log
>
> 2013/04/08 08:41:00.934393 aprsc[2033:b5dc0470] INFO: Binding listening TCP socket: [::]:10152
> 2013/04/08 08:41:00.962004 aprsc[2033:b5dc0470] CRIT: socket(): Address family not supported by protocol
>
> 2013/04/08 08:41:00.962296 aprsc[2033:b5dc0470] CRIT: Failed to listen on any ports.
>
> It seems the system listen to IPv6 only, not IPv4 that I using.

That's not quite true:

Listening to [::] on Linux will listen for connections on both IPv4 and
IPv6, thus it is a good default configuration for most setups.

It does require that your kernel contains IPv6 support. On raspbian it's
not loaded by default, so you'll need to "modprobe ipv6" and append ipv6
in /etc/modules to get it loaded at reboot.

- Hessu

[Francis LEE]

Hi Hessu

I follow your instruction on your next post to add the IPv6 module on the Raspberry Pi, and it work finally, thanks.