aprsc problems on centos

[Erik Schott]

I have just migratedT2NL to a different server running Centos 7.
Although the installation went ok, and i used the previous config file, i cant get to the status page.

This is the status report:
[root@pa0esh iptables]# service aprsc status
● aprsc.service - LSB: start and stop aprsc
Loaded: loaded (/etc/rc.d/init.d/aprsc; bad; vendor preset: disabled)
Active: active (running) since Wed 2018-06-13 12:25:13 CEST; 4min 22s ago
Docs: man:systemd-sysv-generator(8)
Process: 2886 ExecStop=/etc/rc.d/init.d/aprsc stop (code=exited, status=0/SUCCESS)
Process: 2902 ExecStart=/etc/rc.d/init.d/aprsc start (code=exited, status=0/SUCCESS)
Main PID: 2913 (aprsc)
CGroup: /system.slice/aprsc.service
└─2913 /opt/aprsc/sbin/aprsc -u aprsc -t /opt/aprsc -f -e info -o file -r logs -c etc/aprsc.conf

Jun 13 12:25:13 pa0esh.com systemd[1]: Starting LSB: start and stop aprsc...
Jun 13 12:25:13 pa0esh.com aprsc[2902]: Preparing chroot for aprsc...
Jun 13 12:25:13 pa0esh.com aprsc[2902]: /bin/cp: cannot stat ‘/etc/gai.conf’: No such file or directory
Jun 13 12:25:13 pa0esh.com aprsc[2902]: Starting aprsc: [ OK ]
Jun 13 12:25:13 pa0esh.com systemd[1]: PID file /opt/aprsc/logs/aprsc.pid not readable (yet?) after start.
Jun 13 12:25:13 pa0esh.com systemd[1]: Started LSB: start and stop aprsc.


the server has ip 5.2.72.156, but pointing at 5.2.72.156:14501 gives no result.
Do I have to add a rule to iptables ?

the firewall is not running (yet)

Erik, PA0ESH

[Heikki Hannikainen]

Hi,

On Wed, 13 Jun 2018, Erik Schott wrote:

> I have just migratedT2NL to a different server running Centos 7.

I think CentOS 7 should run fine, I've made the build for it, and
supposedly perhaps even tested that it runs. :)

> Main PID: 2913 (aprsc)
> CGroup: /system.slice/aprsc.service
> └─2913 /opt/aprsc/sbin/aprsc -u aprsc -t /opt/aprsc -f -e info -o file -r logs -c etc/aprsc.conf
>
> Jun 13 12:25:13 pa0esh.com systemd[1]: Starting LSB: start and stop aprsc...
> Jun 13 12:25:13 pa0esh.com aprsc[2902]: Preparing chroot for aprsc...
> Jun 13 12:25:13 pa0esh.com aprsc[2902]: /bin/cp: cannot stat ‘/etc/gai.conf’: No such file or directory
> Jun 13 12:25:13 pa0esh.com aprsc[2902]: Starting aprsc: [ OK ]
> Jun 13 12:25:13 pa0esh.com systemd[1]: PID file /opt/aprsc/logs/aprsc.pid not readable (yet?) after start.
> Jun 13 12:25:13 pa0esh.com systemd[1]: Started LSB: start and stop aprsc.
>
> the server has ip 5.2.72.156, but pointing at 5.2.72.156:14501 gives no result.
> Do I have to add a rule to iptables ?
>
> the firewall is not running (yet)

If the firewall is running, rules need to be added in it's configuration
to allow the necessary ports.

You could check the basics:
- is the aprsc process running (ps ax|grep aprsc)
- if it is, is it listening on the correct ports:
sudo netstat -anp|grep aprsc
- in any case, /opt/aprsc/logs/aprsc.log should say what happened in the
startup; there should be ERRORs or CRITical or WARNing messages in there.

- Hessu

[Erik Schott]

Hello Hessu and thanks for the reply.
Carried out the basic tests and here is the output.
Can't see anything strange, but still no screen when connecting to 5.2.72.156:14501 because i'd like to see my status page.
Firewallld is not running - rules are in iptables.
Erik

Here is the output of the basics, and i can't see any warnings or so:

[erik@pa0esh ~]$ ps ax|grep aprsc
7821 ? Ssl 0:20 /opt/aprsc/sbin/aprsc -u aprsc -t /opt/aprsc -f -e info -o file -r logs -c /etc/aprsc.conf
9641 pts/0 R+ 0:00 grep --color=auto aprsc
[erik@pa0esh ~]$ sudo netstat -anp|grep aprsc
[sudo] wachtwoord voor erik:
tcp 0 0 5.2.72.156:59150 204.17.39.172:20152 ESTABLISHED 7821/aprsc
tcp6 0 0 :::14501 :::* LISTEN 7821/aprsc
tcp6 0 0 :::10152 :::* LISTEN 7821/aprsc
tcp6 0 0 :::8080 :::* LISTEN 7821/aprsc
tcp6 0 0 :::14580 :::* LISTEN 7821/aprsc
udp6 0 0 :::14580 :::* 7821/aprsc
udp6 0 0 :::8080 :::* 7821/aprsc
udp6 0 0 :::10152 :::* 7821/aprsc
unix 3 [ ] STREAM CONNECTED 35224 7821/aprsc
unix 3 [ ] STREAM CONNECTED 35184 7821/aprsc
unix 3 [ ] STREAM CONNECTED 35225 7821/aprsc
[erik@pa0esh ~]$ cat /opt/aprsc/logs/aprsc.log
cat: /opt/aprsc/logs/aprsc.log: Toegang geweigerd
[erik@pa0esh ~]$ sudo cat /opt/aprsc/logs/aprsc.log
2018/06/13 21:27:48.182040 aprsc[7821:7f7e93f23840] NOTICE: Starting up version 2.1.4-g408ed49, instance id yzc8urve ...
2018/06/13 21:27:48.183251 aprsc[7821:7f7e93f23840] INFO: After configuration FileLimit is 10000, MaxClients is 500, xpoll using epoll
2018/06/13 21:27:48.192332 aprsc[7821:7f7e93f23840] INFO: Initializing OpenSSL, built against OpenSSL 1.0.1e-fips 11 Feb 2013 ...
2018/06/13 21:27:48.194185 aprsc[7821:7f7e93df2700] INFO: Time thread starting: using clock_gettime
2018/06/13 21:27:48.197566 aprsc[7821:7f7e93dd1700] INFO: Accept thread starting...
2018/06/13 21:27:48.197711 aprsc[7821:7f7e93db0700] INFO: HTTP thread starting...
2018/06/13 21:27:48.197917 aprsc[7821:7f7e93dd1700] INFO: Binding listening UDP socket: [::]:8080
2018/06/13 21:27:48.197980 aprsc[7821:7f7e93dd1700] INFO: Binding listening UDP socket: [::]:10152
2018/06/13 21:27:48.198009 aprsc[7821:7f7e93dd1700] INFO: Binding listening TCP socket: [::]:10152
2018/06/13 21:27:48.198031 aprsc[7821:7f7e93dd1700] INFO: Binding listening UDP socket: [::]:14580
2018/06/13 21:27:48.198049 aprsc[7821:7f7e93dd1700] INFO: Binding listening TCP socket: [::]:14580
2018/06/13 21:27:48.198068 aprsc[7821:7f7e93dd1700] INFO: Accept thread ready.
2018/06/13 21:27:48.198080 aprsc[7821:7f7e93dd1700] INFO: Starting 2 worker threads (configured: 2)...
2018/06/13 21:27:48.198295 aprsc[7821:7f7e902ff700] INFO: Dupecheck thread ready.
2018/06/13 21:27:48.198355 aprsc[7821:7f7e93db0700] INFO: Language 0 installed: fi: web/strings-fi.json
2018/06/13 21:27:48.198363 aprsc[7821:7f7e93db0700] INFO: Language 1 installed: en: web/strings-en.json
2018/06/13 21:27:48.198409 aprsc[7821:7f7e902de700] INFO: Uplink thread applying new configuration...
2018/06/13 21:27:48.198428 aprsc[7821:7f7e902de700] INFO: Uplink thread configured.
2018/06/13 21:27:48.198434 aprsc[7821:7f7e93db0700] INFO: Binding HTTP upload socket :::8080
2018/06/13 21:27:48.198440 aprsc[7821:7f7e902de700] INFO: Uplink: 1 uplinks configured, 0 are connected, need to pick new
2018/06/13 21:27:48.198596 aprsc[7821:7f7e93db0700] INFO: Binding HTTP status socket :::14501
2018/06/13 21:27:48.198646 aprsc[7821:7f7e93db0700] INFO: HTTP thread ready.
2018/06/13 21:27:48.231933 aprsc[7821:7f7e902de700] INFO: Uplink hubs: Connecting to hub-rotate.aprs2.net:20152 ([2605:8e00:12:1::c]:20152) [link 0, addr 3/8]
2018/06/13 21:27:48.376041 aprsc[7821:7f7e902de700] INFO: Uplink hubs: [2605:8e00:12:1::c]:20152: Connection established on fd 17 using source address [2a04:52c0:101:198::c3b2]:49058
2018/06/13 21:27:48.376078 aprsc[7821:7f7e902de700] INFO: status: setting error flag no_uplink ttl 3600
2018/06/13 21:27:48.519686 aprsc[7821:7f7e93d8f700] INFO: Uplink TCP [2605:8e00:12:1::c]:20152 (hubs) closed after 0 s: EOF - remote end closed connection, tx/rx 0/0 bytes 0/0 pkts, dropped 0, fd 17, worker 0
2018/06/13 21:27:48.519793 aprsc[7821:7f7e93d8f700] INFO: [2605:8e00:12:1::c]:20152: Uplink [0] has been closed: EOF - remote end closed connection
2018/06/13 21:27:52.381058 aprsc[7821:7f7e902de700] INFO: Uplink: 1 uplinks configured, 0 are connected, need to pick new
2018/06/13 21:27:52.381842 aprsc[7821:7f7e902de700] INFO: Uplink hubs: Connecting to hub-rotate.aprs2.net:20152 (204.17.39.172:20152) [link 0, addr 7/8]
2018/06/13 21:27:52.520881 aprsc[7821:7f7e902de700] INFO: Uplink hubs: 204.17.39.172:20152: Connection established on fd 17 using source address 5.2.72.156:59150
2018/06/13 21:27:52.520924 aprsc[7821:7f7e902de700] INFO: status: setting error flag no_uplink ttl 3600
2018/06/13 21:27:52.673861 aprsc[7821:7f7e93d8f700] INFO: 204.17.39.172:20152: Uplink server software: # aprsc 2.1.4-g408ed49
2018/06/13 21:27:52.673919 aprsc[7821:7f7e93d8f700] INFO: 204.17.39.172:20152: Connected to server, logging in
2018/06/13 21:27:52.811936 aprsc[7821:7f7e93d8f700] INFO: 204.17.39.172:20152: Uplink server login response: # logresp T2NL verified, server T2HUB2
2018/06/13 21:27:52.811970 aprsc[7821:7f7e93d8f700] INFO: 204.17.39.172:20152: Uplink logged in to server T2HUB2
2018/06/13 21:27:56.527453 aprsc[7821:7f7e902de700] INFO: status: clearing error flag no_uplink
2018/06/13 22:12:58.422930 aprsc[7821:7f7e93d8f700] INFO: Client TCP 161.202.115.41:49942 (APRS2N-ET) closed after 1 s: EOF - remote end closed connection, tx/rx 69/47 bytes 0/0 pkts, dropped 0, fd 18, worker 0 app aprs2net-poll ver 2.0
2018/06/13 22:13:06.872616 aprsc[7821:7f7e93d6e700] INFO: Client TCP 198.137.202.78:60732 (APRS2N-ET) closed after 0 s: EOF - remote end closed connection, tx/rx 69/47 bytes 0/0 pkts, dropped 0, fd 19, worker 1 app aprs2net-poll ver 2.0
2018/06/13 22:16:34.493715 aprsc[7821:7f7e93d8f700] INFO: Client TCP 85.188.1.174:54996 (APRS2N-ET) closed after 30 s: Connection reset by peer, tx/rx 140/47 bytes 0/0 pkts, dropped 0, fd 18, worker 0 app aprs2net-poll ver 2.0
2018/06/13 22:18:06.636810 aprsc[7821:7f7e93d8f700] INFO: Client TCP 198.137.202.78:33214 (APRS2N-ET) closed after 0 s: EOF - remote end closed connection, tx/rx 69/47 bytes 0/0 pkts, dropped 0, fd 20, worker 0 app aprs2net-poll ver 2.0
2018/06/13 22:18:28.231848 aprsc[7821:7f7e93d6e700] INFO: Client TCP 161.202.115.41:50656 (APRS2N-ET) closed after 30 s: Connection reset by peer, tx/rx 140/47 bytes 0/0 pkts, dropped 0, fd 18, worker 1 app aprs2net-poll ver 2.0
[erik@pa0esh ~]$ ^C
[erik@pa0esh ~]$




Op woensdag 13 juni 2018 18:27:28 UTC+2 schreef Erik Schott:

[Heikki Hannikainen]

Hi,

iptables *is* the firewall.

If you have iptables rules, you have a firewall.

If aprsc is running and listening like that (listening sockets look good,
and the log is all happy), then probably your firewall (iptables) is
blocking port 14501 and you'll need to add an ALLOW rule there.

On Wed, 13 Jun 2018, Erik Schott wrote:

> --
> 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/msgid/aprsc/61ed2d99-0ce1-4308-bb09-8b0758ac5378%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

- Hessu

[Joe Bennett]

Just for fun, post the result of 'iptables -L'... That will help
understand if it is a firewall issue, at least an iptables/ netfilter
issue... If that shows no significance, do you have a firewall
northbound of your server that could be blocking the port(s)? Are you
forwarding the ports across any NAT instance?





-Joe
KA3NAM

> https://groups.google.com/d/msgid/aprsc/alpine.DEB.2.20.1806141135360.29079%40jazz.he.fi.

[Erik Schott]

Thanks Heikki and Joe, you set me on the right path. I took the easy way and changed iptables for firewalld and I am up and running. I had issues with the rules in iptables, due to my lack of knowledge and so i choose the easy way....
Thanks for the help
Erik, PA0ESH - T2NL

**** Nagios *****

Notification Type: RECOVERY

Service: APRS-IS
Host: T2NL
Address: 5.2.72.156
State: OK

Date/Time: Thu Jun 14 14:37:11 UTC 2018
Additional Info:
IS OK - aprsc 2.1.4-g408ed49

Op woensdag 13 juni 2018 18:27:28 UTC+2 schreef Erik Schott: