Collectd

Hi all
New system running smooth but collectd is not heres error
Ubuntu 20.04.4 LTS
graphs1090
tar1090
airspy_adsb
readsb (set net-only)
rpimonitor
pc 64bit
tried ubuntu 20 few options here

Restoring graphs1090 error on different architecture

Reading package lists… Done
Building dependency tree
Reading state information… Done
The following NEW packages will be installed
collectd
0 to upgrade, 1 to newly install, 0 to remove and 0 not to upgrade.
Need to get 0 B/21.2 kB of archives.
After this operation, 204 kB of additional disk space will be used.
Selecting previously unselected package collectd.
(Reading database … 229505 files and directories currently installed.)
Preparing to unpack …/collectd_5.9.2.g-1ubuntu5_amd64.deb …
Unpacking collectd (5.9.2.g-1ubuntu5) …
Setting up collectd (5.9.2.g-1ubuntu5) …
Job for collectd.service failed because the control process exited with error code.
See “systemctl status collectd.service” and “journalctl -xe” for details.
invoke-rc.d: initscript collectd, action “restart” failed.
● collectd.service - Statistics collection and monitoring daemon
Loaded: loaded (/lib/systemd/system/collectd.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/collectd.service.d
└─malarky.conf
Active: activating (auto-restart) (Result: exit-code) since Mon 2022-03-14 10:24:15 GMT; 4ms ago
Docs: man:collectd(1)
man:collectd.conf(5)
https://collectd.org
Process: 90238 ExecStartPre=/usr/sbin/collectd -t (code=exited, status=0/SUCCESS)
Process: 90239 ExecStartPre=/bin/bash /usr/share/graphs1090/readback.sh (code=exited, status=0/SUCCESS)
Process: 90252 ExecStartPre=/usr/sbin/collectd -t (code=exited, status=0/SUCCESS)
Process: 90253 ExecStart=/usr/sbin/collectd (code=exited, status=1/FAILURE)
Process: 90254 ExecStopPost=/bin/bash /usr/share/graphs1090/writeback.sh (code=exited, status=0/SUCCESS)
Main PID: 90253 (code=exited, status=1/FAILURE)
dpkg: error processing package collectd (–configure):
installed collectd package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
collectd
E: Sub-process /usr/bin/dpkg returned an error code (1)


latest del / reinstall

All done! Graphs available at http://192.168.0.12/graphs1090
It may take up to 10 minutes until the first data is displayed
john@john-H81M-S2H:~$ systemctl status collectd.service
● collectd.service - Statistics collection and monitoring daemon
Loaded: loaded (/lib/systemd/system/collectd.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/collectd.service.d
└─malarky.conf
Active: activating (auto-restart) (Result: exit-code) since Mon 2022-03-14 14:43:45 GMT; 6s ago
Docs: man:collectd(1)
man:collectd.conf(5)
https://collectd.org
Process: 218223 ExecStartPre=/usr/sbin/collectd -t (code=exited, status=0/SUCCESS)
Process: 218224 ExecStartPre=/bin/bash /usr/share/graphs1090/readback.sh (code=exited, status=0/SUCCESS)
Process: 218237 ExecStartPre=/usr/sbin/collectd -t (code=exited, status=0/SUCCESS)
Process: 218238 ExecStart=/usr/sbin/collectd (code=exited, status=1/FAILURE)
Process: 218239 ExecStopPost=/bin/bash /usr/share/graphs1090/writeback.sh (code=exited, status=0/SUCCESS)
Main PID: 218238 (code=exited, status=1/FAILURE)

What did the suggestion say? Please run these two commands (put sudo in front)

And please do us a favor formatting your logs posted here. Damn hard to read.

For this mark the text and press the “preformatting” icon on the toolbar:

My graphs1090 are nill

john@john-H81M-S2H:~$ sudo apt-get -y install collectd
Reading package lists... Done
Building dependency tree
Reading state information... Done
collectd is already the newest version (5.9.2.g-1ubuntu5).
0 to upgrade, 0 to newly install, 0 to remove and 3 not to upgrade.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up collectd (5.9.2.g-1ubuntu5) ...
Job for collectd.service failed because the control process exited with error code.
See "systemctl status collectd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript collectd, action "restart" failed.
● collectd.service - Statistics collection and monitoring daemon
     Loaded: loaded (/lib/systemd/system/collectd.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/collectd.service.d
             └─malarky.conf
     Active: activating (auto-restart) (Result: exit-code) since Mon 2022-03-14 14:57:02 GMT; 4ms ago
       Docs: man:collectd(1)
             man:collectd.conf(5)
             https://collectd.org
    Process: 226006 ExecStartPre=/usr/sbin/collectd -t (code=exited, status=0/SUCCESS)
    Process: 226007 ExecStartPre=/bin/bash /usr/share/graphs1090/readback.sh (code=exited, status=0/SUCCESS)
    Process: 226020 ExecStartPre=/usr/sbin/collectd -t (code=exited, status=0/SUCCESS)
    Process: 226021 ExecStart=/usr/sbin/collectd (code=exited, status=1/FAILURE)
    Process: 226022 ExecStopPost=/bin/bash /usr/share/graphs1090/writeback.sh (code=exited, status=0/SUCCESS)
   Main PID: 226021 (code=exited, status=1/FAILURE)
dpkg: error processing package collectd (--configure):
 installed collectd package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 collectd
E: Sub-process /usr/bin/dpkg returned an error code (1)

john@john-H81M-S2H:~$ sudo journalctl -xe
[sudo] password for john:
Mar 14 16:36:58 john-H81M-S2H collectd[273930]: Found a configuration for the `python' plugin, but the plugin isn't loaded or didn't register a conf>
Mar 14 16:36:58 john-H81M-S2H collectd[273930]: Plugin python failed to handle option ModulePath, return code: -1
Mar 14 16:36:58 john-H81M-S2H systemd[1]: collectd.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- An ExecStart= process belonging to unit collectd.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Mar 14 16:36:58 john-H81M-S2H collectd[273931]: writing DB from /run/collectd to disk
Mar 14 16:36:58 john-H81M-S2H systemd[1]: collectd.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit collectd.service has entered the 'failed' state with result 'exit-code'.
Mar 14 16:36:58 john-H81M-S2H systemd[1]: Failed to start Statistics collection and monitoring daemon.
-- Subject: A start job for unit collectd.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit collectd.service has finished with a failure.
--
-- The job identifier is 222393 and the job result is failed.
Mar 14 16:37:06 john-H81M-S2H sudo[273945]:     john : TTY=pts/0 ; PWD=/home/john ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Mar 14 16:37:06 john-H81M-S2H sudo[273945]: pam_unix(sudo:session): session opened for user root by john(uid=0)
lines 2663-2689/2689 (END)
Mar 14 16:36:58 john-H81M-S2H collectd[273930]: Found a configuration for the `python' plugin, but the plugin isn't loaded or didn't register a conf>
Mar 14 16:36:58 john-H81M-S2H collectd[273930]: Plugin python failed to handle option ModulePath, return code: -1
Mar 14 16:36:58 john-H81M-S2H systemd[1]: collectd.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- An ExecStart= process belonging to unit collectd.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Mar 14 16:36:58 john-H81M-S2H collectd[273931]: writing DB from /run/collectd to disk
Mar 14 16:36:58 john-H81M-S2H systemd[1]: collectd.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit collectd.service has entered the 'failed' state with result 'exit-code'.
Mar 14 16:36:58 john-H81M-S2H systemd[1]: Failed to start Statistics collection and monitoring daemon.
-- Subject: A start job for unit collectd.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit collectd.service has finished with a failure.
--
-- The job identifier is 222393 and the job result is failed.
Mar 14 16:37:06 john-H81M-S2H sudo[273945]:     john : TTY=pts/0 ; PWD=/home/john ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Mar 14 16:37:06 john-H81M-S2H sudo[273945]: pam_unix(sudo:session): session opened for user root by john(uid=0)

https://github.com/wiedehopf/graphs1090#ubuntu-20-fixes-symptom-collectd-errors-out-on-startup

Hi wiedehopf
i had already found that repair post (Ubuntu 20 fixes )
but nothing happend
i redone all today and same result
i can restart full install
that should do it
many thanks

john@john-H81M-S2H:~$ sudo apt update
[sudo] password for john:
Hit:1 http://gb.archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://gb.archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:3 http://gb.archive.ubuntu.com/ubuntu focal-backports InRelease
Hit:5 http://giteduberger.fr rpimonitor/ InRelease
Hit:6 http://security.ubuntu.com/ubuntu focal-security InRelease
Get:4 https://raw.githubusercontent.com/abcd567a/ubuntu/master ./ InRelease [2,1                   15 B]
Fetched 2,115 B in 0s (4,665 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up-to-date.
john@john-H81M-S2H:~$ sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up collectd (5.9.2.g-1ubuntu5) ...
Job for collectd.service failed because the control process exited with error co                   de.
See "systemctl status collectd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript collectd, action "restart" failed.
● collectd.service - Statistics collection and monitoring daemon
     Loaded: loaded (/lib/systemd/system/collectd.service; enabled; vendor prese                   t: enabled)
    Drop-In: /etc/systemd/system/collectd.service.d
             └─malarky.conf
     Active: activating (auto-restart) (Result: exit-code) since Tue 2022-03-15                    11:04:56 GMT; 4ms ago
       Docs: man:collectd(1)
             man:collectd.conf(5)
             https://collectd.org
    Process: 5195 ExecStartPre=/usr/sbin/collectd -t (code=exited, status=0/SUCC                   ESS)
    Process: 5196 ExecStartPre=/bin/bash /usr/share/graphs1090/readback.sh (code                   =exited, status=0/SUCCESS)
    Process: 5209 ExecStartPre=/usr/sbin/collectd -t (code=exited, status=0/SUCC                   ESS)
    Process: 5210 ExecStart=/usr/sbin/collectd (code=exited, status=1/FAILURE)
    Process: 5211 ExecStopPost=/bin/bash /usr/share/graphs1090/writeback.sh (cod                   e=exited, status=0/SUCCESS)
   Main PID: 5210 (code=exited, status=1/FAILURE)
dpkg: error processing package collectd (--configure):
 installed collectd package post-installation script subprocess returned error e                   xit status 1
Errors were encountered while processing:
 collectd
E: Sub-process /usr/bin/dpkg returned an error code (1)
john@john-H81M-S2H:~$ echo "LD_PRELOAD=/usr/lib/python3.8/config-3.8-x86_64-linux-gnu/libpython3.8.so" | sudo tee -a /etc/default/collectd
LD_PRELOAD=/usr/lib/python3.8/config-3.8-x86_64-linux-gnu/libpython3.8.so
john@john-H81M-S2H:~$ sudo echo "LD_PRELOAD=/usr/lib/python3.8/config-3.8-x86_64-linux-gnu/libpython3.8.so" | sudo tee -a /etc/default/collectd
LD_PRELOAD=/usr/lib/python3.8/config-3.8-x86_64-linux-gnu/libpython3.8.so
john@john-H81M-S2H:~$ sudo systemctl restart collectd
Job for collectd.service failed because the control process exited with error code.

use Ubuntu 21 or whatever …

I’m chicken so gone for Debian 11 :grinning:

Hi again
well right confused now
installed debain 11
all and working up untill a reboot just now
im now getting backend again not working

no graphs
it did display some time but failed after reboot
so weird

root@server:/home/john# systemctl status collectd.service
● collectd.service - Statistics collection and monitoring daemon
     Loaded: loaded (/lib/systemd/system/collectd.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/collectd.service.d
             └─malarky.conf
     Active: active (running) since Tue 2022-03-15 21:29:30 GMT; 5min ago
       Docs: man:collectd(1)
             man:collectd.conf(5)
             https://collectd.org
    Process: 599 ExecStartPre=/usr/sbin/collectd -t (code=exited, status=0/SUCCESS)
    Process: 614 ExecStartPre=/bin/bash /usr/share/graphs1090/readback.sh (code=exited, status=0/SUCCESS)
    Process: 725 ExecStartPre=/usr/sbin/collectd -t (code=exited, status=0/SUCCESS)
   Main PID: 726 (collectd)
      Tasks: 12 (limit: 19028)
     Memory: 59.5M
        CPU: 680ms
     CGroup: /system.slice/collectd.service
             └─726 /usr/sbin/collectd

Mar 15 21:29:30 server collectd[726]: plugin_load: plugin "irq" successfully loaded.
Mar 15 21:29:30 server collectd[726]: plugin_load: plugin "load" successfully loaded.
Mar 15 21:29:30 server collectd[726]: plugin_load: plugin "memory" successfully loaded.
Mar 15 21:29:30 server collectd[726]: plugin_load: plugin "processes" successfully loaded.
Mar 15 21:29:30 server collectd[726]: plugin_load: plugin "rrdtool" successfully loaded.
Mar 15 21:29:30 server collectd[726]: plugin_load: plugin "swap" successfully loaded.
Mar 15 21:29:30 server collectd[726]: plugin_load: plugin "users" successfully loaded.
Mar 15 21:29:30 server collectd[726]: Systemd detected, trying to signal readiness.
Mar 15 21:29:30 server systemd[1]: Started Statistics collection and monitoring daemon.
Mar 15 21:29:30 server collectd[726]: Initialization complete, entering read-loop.
root@server:/home/john# journalctl -xe
Mar 15 21:36:53 server airspy_adsb[496]: Push client connected to 127.0.0.1:30004 (beast)
Mar 15 21:36:53 server airspy_adsb[496]: Push client disconnected from 127.0.0.1:30004 (beast)
Mar 15 21:37:04 server systemd[1]: readsb.service: Scheduled restart job, restart counter is at 15.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit readsb.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Mar 15 21:37:04 server systemd[1]: Stopped readsb ADS-B receiver.
░░ Subject: A stop job for unit readsb.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit readsb.service has finished.
░░
░░ The job identifier is 2599 and the job result is done.
Mar 15 21:37:04 server systemd[1]: Started readsb ADS-B receiver.
░░ Subject: A start job for unit readsb.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit readsb.service has finished successfully.
░░
░░ The job identifier is 2599.
Mar 15 21:37:04 server readsb[5348]: readsb: Too many arguments
Mar 15 21:37:04 server readsb[5348]: Try `readsb --help' or `readsb --usage' for more information.
Mar 15 21:37:04 server readsb[5348]: Command line used:
Mar 15 21:37:04 server readsb[5348]: /usr/bin/readsb --net-only --write-json-every 1 --lat 52.24748 --max-range 500 --net --net-heartbeat 60 --net-ro-size 1>
Mar 15 21:37:04 server systemd[1]: readsb.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit readsb.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Mar 15 21:37:04 server systemd[1]: readsb.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit readsb.service has entered the 'failed' state with result 'exit-code'.
Mar 15 21:37:06 server airspy_adsb[496]: Push client connected to 127.0.0.1:30004 (beast)
Mar 15 21:37:06 server airspy_adsb[496]: Push client disconnected from 127.0.0.1:30004 (beast)

It is telling you there is a problem with your command line. Looks to me that you are missing a longitude.

Ive just noticed i got 2 conf 
readsb has lat / lon  
 readsb.airspyconf  has not got lat / lon ??
that cannot be right can it

deleted readsb.airspyconf

surprising what a pair of – can do

Thankyou for the nudge
blind looking to hard double checking still dont work
heres all sorted

root@server:/etc/default# systemctl status collectd.service
● collectd.service - Statistics collection and monitoring daemon
     Loaded: loaded (/lib/systemd/system/collectd.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/collectd.service.d
             └─malarky.conf
     Active: active (running) since Tue 2022-03-15 22:14:23 GMT; 4min 0s ago
       Docs: man:collectd(1)
             man:collectd.conf(5)
             https://collectd.org
    Process: 627 ExecStartPre=/usr/sbin/collectd -t (code=exited, status=0/SUCCESS)
    Process: 632 ExecStartPre=/bin/bash /usr/share/graphs1090/readback.sh (code=exited, status=0/SUCCES>
    Process: 739 ExecStartPre=/usr/sbin/collectd -t (code=exited, status=0/SUCCESS)
   Main PID: 740 (collectd)
      Tasks: 12 (limit: 19028)
     Memory: 54.1M
        CPU: 507ms
     CGroup: /system.slice/collectd.service
             └─740 /usr/sbin/collectd

Mar 15 22:14:23 server collectd[740]: plugin_load: plugin "irq" successfully loaded.
Mar 15 22:14:23 server collectd[740]: plugin_load: plugin "load" successfully loaded.
Mar 15 22:14:23 server collectd[740]: plugin_load: plugin "memory" successfully loaded.
Mar 15 22:14:23 server collectd[740]: plugin_load: plugin "processes" successfully loaded.
Mar 15 22:14:23 server collectd[740]: plugin_load: plugin "rrdtool" successfully loaded.
Mar 15 22:14:23 server collectd[740]: plugin_load: plugin "swap" successfully loaded.
Mar 15 22:14:23 server collectd[740]: plugin_load: plugin "users" successfully loaded.
Mar 15 22:14:23 server collectd[740]: Systemd detected, trying to signal readiness.
Mar 15 22:14:23 server collectd[740]: Initialization complete, entering read-loop.
Mar 15 22:14:23 server systemd[1]: Started Statistics collection and monitoring daemon.

[1]+  Stopped                 systemctl status collectd.service
root@server:/etc/default# journalctl -xe
Mar 15 22:16:54 server readsb[4107]: 30104: Beast TCP input port
Mar 15 22:16:59 server airspy_adsb[449]: Push client connected to 127.0.0.1:30004 (beast)
Mar 15 22:17:01 server CRON[4115]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=>
Mar 15 22:17:01 server CRON[4116]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Mar 15 22:17:01 server CRON[4115]: pam_unix(cron:session): session closed for user root
Mar 15 22:17:28 server sudo[4146]:  piaware : PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp >
Mar 15 22:17:28 server sudo[4146]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=>
Mar 15 22:17:28 server sudo[4146]: pam_unix(sudo:session): session closed for user root
Mar 15 22:17:28 server piaware[1171]: Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat>
Mar 15 22:17:28 server piaware[1171]: mlat-client(4148): fa-mlat-client 0.2.12 starting up
Mar 15 22:17:28 server piaware[1171]: mlat-client(4148): Using UDP transport to 206.253.84.196 port 100>
Mar 15 22:17:28 server piaware[1171]: mlat-client(4148): Listening for Beast-format results connection >
Mar 15 22:17:28 server piaware[1171]: mlat-client(4148): Listening for Extended Basestation-format resu>
Mar 15 22:17:28 server piaware[1171]: mlat-client(4148): Route MTU changed to 1500
Mar 15 22:17:28 server piaware[1171]: mlat-client(4148): Input connected to localhost:30005
Mar 15 22:17:28 server piaware[1171]: mlat-client(4148): Input format changed to BEAST, 12MHz clock
Mar 15 22:17:28 server sudo[4149]:  piaware : PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp >
Mar 15 22:17:28 server sudo[4149]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=>
Mar 15 22:17:28 server sudo[4149]: pam_unix(sudo:session): session closed for user root
Mar 15 22:17:28 server piaware[1171]: ADS-B data program 'readsb' is listening on port 30005, so far so>
Mar 15 22:17:28 server piaware[1171]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipa>
Mar 15 22:17:28 server piaware[1171]: Started faup1090 (pid 4151) to connect to readsb
Mar 15 22:17:29 server piaware[1171]: mlat-client(4148): Beast-format results connection with ::1:30104>
lines 2873-2895/2895 (END)
Mar 15 22:16:54 server readsb[4107]: 30104: Beast TCP input port
Mar 15 22:16:59 server airspy_adsb[449]: Push client connected to 127.0.0.1:30004 (beast)
Mar 15 22:17:01 server CRON[4115]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 15 22:17:01 server CRON[4116]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Mar 15 22:17:01 server CRON[4115]: pam_unix(cron:session): session closed for user root
Mar 15 22:17:28 server sudo[4146]:  piaware : PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Mar 15 22:17:28 server sudo[4146]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=998)
Mar 15 22:17:28 server sudo[4146]: pam_unix(sudo:session): session closed for user root
Mar 15 22:17:28 server piaware[1171]: Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect>
Mar 15 22:17:28 server piaware[1171]: mlat-client(4148): fa-mlat-client 0.2.12 starting up
Mar 15 22:17:28 server piaware[1171]: mlat-client(4148): Using UDP transport to 206.253.84.196 port 10085
Mar 15 22:17:28 server piaware[1171]: mlat-client(4148): Listening for Beast-format results connection on port 30105
Mar 15 22:17:28 server piaware[1171]: mlat-client(4148): Listening for Extended Basestation-format results connection on port >
Mar 15 22:17:28 server piaware[1171]: mlat-client(4148): Route MTU changed to 1500
Mar 15 22:17:28 server piaware[1171]: mlat-client(4148): Input connected to localhost:30005
Mar 15 22:17:28 server piaware[1171]: mlat-client(4148): Input format changed to BEAST, 12MHz clock
Mar 15 22:17:28 server sudo[4149]:  piaware : PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Mar 15 22:17:28 server sudo[4149]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=998)
Mar 15 22:17:28 server sudo[4149]: pam_unix(sudo:session): session closed for user root
Mar 15 22:17:28 server piaware[1171]: ADS-B data program 'readsb' is listening on port 30005, so far so good
Mar 15 22:17:28 server piaware[1171]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo->
Mar 15 22:17:28 server piaware[1171]: Started faup1090 (pid 4151) to connect to readsb
Mar 15 22:17:29 server piaware[1171]: mlat-client(4148): Beast-format results connection with ::1:30104: connection established
lines 2873-2895/2895 (END)

These two files are normal.

readsb.airspyconf is the backup the installation created and not in use
I would not delete it

Lat/Lon need to be entered either via command line as suggested in the wiedehopf installer readme or manually if you know where.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.