AirNav RadarBox and RadarBox24.com > AirNav RadarBox and RadarBox24.com Discussion

Install rbfeeder and mlat-client on Raspberry Pi OS BOOKWORM

<< < (2/2)

Runway 31:
Did you re-boot your Pi after instalation

Alan

abcd567:
@Aviator56

Please do NOT edit file /etc/default/mlat-client. It may not work properly if you edit it.

The mlat-client is NOT supposed to start automatically. It is started by rbfeeder when the rbfeeder starts.

To restore default configuration of mlat-client, please issue following commands:

sudo apt purge mlat-client 

sudo rm /etc/default/mlat-client   

sudo apt install mlat-client   

sudo reboot   

After reboot, check status

--- Code: ---sudo systemctl status rbfeeder  | sed 's/ / /'

--- End code ---

In output of above command, look at this portion of output. The presence of mlat-client in this line shows mlat is working ok.:

     CGroup: /system.slice/rbfeeder.service
             ├─105976 /usr/bin/rbfeeder
             └─105985 /usr/bin/python3 /usr/bin/mlat-client --input-type dump1090 --input-connect 127.0.0.1:32457 --server mlat1.rb24.com:40900 --lat 43.5xxx --lon -79.6xxx --alt 1xx --user EXTRPI000008 --results beast,connect,127.0.0.1:32004
 

.
           

Aviator56:
Thanks, ro the helpful response, here's the output from the rbfeeder status report:-
@RPiRB24:~ $ sudo systemctl status rbfeeder  | sed 's/ / /'
● rbfeeder.service - RBFeeder Service
     Loaded: loaded (/lib/systemd/system/rbfeeder.service; enabled; preset: enabled)
     Active: active (running) since Mon 2024-04-29 16:14:40 BST; 2min 32s ago
    Process: 753 ExecStartPre=/bin/mkdir /var/run/rbfeeder (code=exited, status=0/SUCCESS)
    Process: 760 ExecStartPre=/bin/chown rbfeeder:rbfeeder /var/run/rbfeeder (code=exited, status=0/SUCCESS)
    Process: 762 ExecStartPre=/bin/touch /var/log/rbfeeder.log (code=exited, status=0/SUCCESS)
    Process: 767 ExecStartPre=/bin/chown rbfeeder:rbfeeder /var/log/rbfeeder.log (code=exited, status=0/SUCCESS)
    Process: 771 ExecStartPre=/bin/chown rbfeeder:rbfeeder /etc/rbfeeder.ini (code=exited, status=0/SUCCESS)
    Process: 779 ExecStartPre=/bin/setfacl -m u:www-data:rwx /etc/rbfeeder.ini (code=exited, status=0/SUCCESS)
   Main PID: 788 (rbfeeder)
      Tasks: 9 (limit: 763)
        CPU: 3.830s
     CGroup: /system.slice/rbfeeder.service
             └─788 /usr/bin/rbfeeder

No Mlat running indication.

Output from MLAT-client status:-

@RPiRB24:~ $ sudo systemctl status mlat-client
● mlat-client.service - LSB: Multilateration client
     Loaded: loaded (/etc/init.d/mlat-client; generated)
     Active: active (exited) since Mon 2024-04-29 16:14:30 BST; 7min ago
       Docs: man:systemd-sysv-generator(8)
    Process: 439 ExecStart=/etc/init.d/mlat-client start (code=exited, status=0/SUCCESS)
        CPU: 128ms

Apr 29 16:14:29 RPiRB24 systemd[1]: Starting mlat-client.service - LSB: Multilateration client...
Apr 29 16:14:30 RPiRB24 mlat-client[439]: Not starting mlat-client daemon, disabled via /etc/default/mlat-client ... (warning).
Apr 29 16:14:30 RPiRB24 systemd[1]: Started mlat-client.service - LSB: Multilateration client.


regards

Nigel

abcd567:
@Aviator56
Please do following. Issue commands in the order these are listed.

1. Delete mlat-client's config file
2. Purge mlat-client,
3. Clean apt cache (to remove corrupted mlat-client package so that the corrupted package is not reused for fresh install by the apt install command given below)
4. Reinstall mlat-client.
5. Reboot
6. Check status

sudo rm /etc/default/mlat-client 

sudo apt purge mlat-client 

sudo apt clean

sudo apt install mlat-client 

sudo reboot 

sudo systemctl status rbfeeder 


.

Navigation

[0] Message Index

[*] Previous page