Announcement

Collapse
No announcement yet.

Two instances of FR24feed on the same linux box?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    I thought of another slightly different format of fr24feed ini file.

    Code:
    sudo nano /etc/fr24feed-1.ini

    Copy-paste following code in above file
    Code:
    CONFIG=" \
     --receiver=beast-tcp" \
     --fr24key=xxxxxxxxxxxxxxxx \
     --host=127.0.0.1:30005 \
     --bs=no \
     --raw=no \
     --logmode=1 \
     --logpath=/var/log/fr24-1 \
     --mlat=yes \
     --mlat-without-gps=yes \
     --use-http=yes \
     --http-timeout=20 "
    IMPORTANT:
    If you type the above code, make sure there is no blank space after back-slah \ .

    Better copy-paste from above instead of typing

    Code:
    [Unit] 
    Description=Flightradar24 Feeder 
    After=network-online.target 
    
    [Service] 
    Type=simple 
    Restart=always 
    LimitCORE=infinity 
    EnvironmentFile=/etc/fr24feed-1.ini 
    RuntimeDirectory=fr24feed 
    RuntimeDirectoryMode=0755 
    ExecStartPre=/bin/mkdir -p /var/log/fr24-1 
    ExecStartPre=/bin/chown fr24 /var/log/fr24-1 
    ExecStart=/usr/bin/fr24feed $CONFIG 
    User=fr24 
    PermissionsStartOnly=true 
    StandardOutput=null 
    
    [Install] 
    WantedBy=multi-user.target
    Last edited by abcd567; 2019-04-19, 05:50.

    Comment


    • #17
      @Khan
      @Oblivian

      By default fr24feed (arm & i386) serves status & settings page in browser at port 8754.

      If I want to change this to another port number, what is the process argument to be passed to fr24feed binary?

      As an example, dump1090 by default serves map in browser at port 8080. This can be customized to another port, for example 8787 by passing following process arguments to dump1090
      --net-http-port 8787

      Comment


      • #18
        From experience its hard coded. No way around

        Sent from my EML-L09 using Tapatalk
        Posts not to be taken as official support representation - Just a helpful uploader who tinkers

        Comment


        • #19
          Originally posted by Oblivian View Post
          From experience its hard coded. No way around
          Oh boy!

          Comment


          • #20
            I mean if someone does this he should be able to do the settings without the webinterface.
            No big loss imho.

            Anyway the number of people using this will likely be limited to the single digits.

            Also you should set the MLAT to no in your secondary feed:
            Code:
            MLAT="--mlat=no --mlat-without-gps=no"

            Comment


            • #21
              Finally, almost like Windows Feeder / RPi Feeder / Linux i386 .deb package setup...

              Found a way to make linux binary's configuration & setup almost like Windows Feeder / RPi Feeder / Linux i386 .deb package setup

              Note:
              The steps below are for Feeder-1.
              For Feeder-2, replace fr24feed-1 by fr24feed-2, and fr24-1 by fr24-2, wherever these occur in code below.

              STEP-1: Prepare config file "fr24feed.ini"
              Code:
              sudo touch /etc/fr24feed-1.ini
              sudo chmod a+rw /etc/fr24feed-1.ini
              sudo nano /etc/fr24feed-1.ini
              Copy-paste following into /etc/fr24feed-1.ini
              Code:
              receiver="beast-tcp"
              fr24key="xxxxxxxxxxxxxxxx"
              host="127.0.0.1:30005"
              
              bs="no"
              raw="no"
              logmode="1"
              logpath="/var/log/fr24-1"
              mpx="no"
              mlat="yes"
              mlat-without-gps="yes"
              use-http="yes"
              http-timeout="20"

              STEP-2: Prepare service file "fr24feed-1.service"
              Code:
              sudo nano /lib/systemd/system/fr24feed-1.service

              Copy-paste following into /lib/systemd/system/fr24feed-1.service
              Code:
              [Unit]
              Description=Flightradar24 Feeder
              After=network-online.target
              
              [Service]
              Type=simple
              Restart=always
              LimitCORE=infinity
              RuntimeDirectory=fr24feed
              RuntimeDirectoryMode=0755
              ExecStartPre=/bin/mkdir -p /var/log/fr24-1
              ExecStartPre=/bin/chown fr24 /var/log/fr24-1
              ExecStart=/usr/bin/fr24feed  --config-file=/etc/fr24feed-1.ini  
              User=fr24
              PermissionsStartOnly=true
              StandardOutput=null
              
              [Install]
              WantedBy=multi-user.target

              STEP-3: Enable service, and start fr24feed-1
              Code:
              sudo systemctl enable fr24feed-1
              sudo systemctl restart fr24feed-1

              STEP-4: Check status
              Code:
              abcd@debian:~$ sudo systemctl status fr24feed-1
              
              ● fr24feed-1.service - Flightradar24 Feeder
                 Loaded: loaded (/lib/systemd/system/fr24feed-1.service; enabled; vendor preset: enabled)
                 Active: active (running) since Fri 2019-04-19 17:34:42 EDT; 6s ago
                Process: 4345 ExecStartPre=/bin/chown fr24 /var/log/fr24-1 (code=exited, status=0/SUCCESS)
                Process: 4342 ExecStartPre=/bin/mkdir -p /var/log/fr24-1 (code=exited, status=0/SUCCESS)
               Main PID: 4348 (fr24feed)
                  Tasks: 9 (limit: 4915)
                 CGroup: /system.slice/fr24feed-1.service
                         └─4348 /usr/bin/fr24feed --config-file=/etc/fr24feed-1.ini
              
              Apr 19 17:34:42 debian systemd[1]: Starting Flightradar24 Feeder...
              Apr 19 17:34:42 debian systemd[1]: Started Flightradar24 Feeder.


              STEP-5: Check logs
              Scroll down to see full log
              Code:
              abcd@debian:~$ cat /var/log/fr24-1/fr24feed.log 
              
              2019-04-19 17:34:42 | [main][i]FR24 Feeder/Decoder
              2019-04-19 17:34:42 | [main][i]Version: 1.0.18-5/generic
              2019-04-19 17:34:42 | [main][i]Built on Mar  4 2016 16:26:55 (devel-d11ca48.git/Linux/x86_64)
              2019-04-19 17:34:42 | [main][i]Copyright 2012-2016 Flightradar24 AB
              2019-04-19 17:34:42 | [main][i]http://flightradar24.com
              2019-04-19 17:34:43 | [main][i]DNS mode: LIBC
              2019-04-19 17:34:43 | [main][i]Automatic updates are DISABLED
              2019-04-19 17:34:43 | [main][i]Reader thread started
              2019-04-19 17:34:43 | [main][i]MLAT data feed started
              2019-04-19 17:34:43 | [reader][i]Initializing reader
              2019-04-19 17:34:43 | [reader][i]Connecting to Beast receiver via (tcp://127.0.0.1:30005)
              2019-04-19 17:34:43 | [mlat][i]Waiting for MLAT configuration
              2019-04-19 17:34:43 | [master][i]Starting processing thread
              2019-04-19 17:34:43 | [e]bind function failed, errno: 98
              2019-04-19 17:34:43 | [httpd][d]Master thread terminated
              2019-04-19 17:34:43 | [reader][i]Connected to the receiver, configuring
              2019-04-19 17:34:43 | [reader][i]Configured, processing messages
              2019-04-19 17:34:43 | [reader][w]Setting new UTC offset: 0!
              2019-04-19 17:34:44 | [time][i]Synchronizing time via NTP
              2019-04-19 17:34:46 | [time][i]Time synchronized correctly, offset +0.0005 seconds
              2019-04-19 17:34:46 | [main][i]Feed Network client started
              2019-04-19 17:34:46 | [feed][i]Downloading configuration
              2019-04-19 17:34:47 | [feed][c]Interval: 5s
              2019-04-19 17:34:47 | [feed][c]Latitude: 43.xxxx
              2019-04-19 17:34:47 | [feed][c]Longitude: -79.xxxx
              2019-04-19 17:34:47 | [feed][c]GND: YES
              2019-04-19 17:34:47 | [feed][c]NonADSB: YES
              2019-04-19 17:34:47 | [feed][c]Timestamps: optional
              2019-04-19 17:34:47 | [feed][c]Max range AIR: 350.0nm
              2019-04-19 17:34:47 | [feed][c]Max range GND: 100.0nm
              2019-04-19 17:34:47 | [feed][i]defined 4 servers
              2019-04-19 17:34:47 | [feed][n]CYYZ52@185.218.24.22:8099/UDP
              2019-04-19 17:34:47 | [feed][n]connecting
              2019-04-19 17:34:47 | [stats][i]Stats thread started
              2019-04-19 17:34:47 | [feed][n]connected via UDP (fd 8)
              2019-04-19 17:34:47 | [feed][n]working
              2019-04-19 17:34:48 | [feed][i]sent 11, filtered 0 AC in 1 packet
              2019-04-19 17:34:48 | [mlat][i]MLAT configuration received, service ENABLED
              2019-04-19 17:34:48 | [mlat][i]Starting MLAT with preconfigured position: 43.xx,-79.xx,450.0
              2019-04-19 17:34:48 | [mlat][i]MLAT bandwidth reduction active, level 1
              2019-04-19 17:34:48 | [mlat][i]Configuring UDP connection udp://usa-2.fr24.com:19788
              2019-04-19 17:34:48 | [mlat][i]Registering MLAT station
              2019-04-19 17:34:48 | [mlat][i]Registering MLAT station: SUCCESS
              2019-04-19 17:34:53 | [feed][i]sent 26, filtered 0 AC in 1 packet
              2019-04-19 17:34:54 | [mlat][i]Received ADS-B time references AC:
              2019-04-19 17:34:54 | [mlat][i] A082AC
              2019-04-19 17:34:54 | [mlat][i] A2A7B5
              2019-04-19 17:34:54 | [mlat][i] A73E6D
              2019-04-19 17:34:54 | [mlat][i] A7C849
              2019-04-19 17:34:54 | [mlat][i] AADF08
              2019-04-19 17:34:54 | [mlat][i] ACB0B9
              2019-04-19 17:34:54 | [mlat][i] ADCD6D
              2019-04-19 17:34:54 | [mlat][i] C0193B
              2019-04-19 17:34:54 | [mlat][i] C0225E
              2019-04-19 17:34:54 | [mlat][i] C04D0A
              2019-04-19 17:34:54 | [mlat][i] C05F0E
              2019-04-19 17:34:54 | [mlat][i] C07F2F
              2019-04-19 17:34:54 | [mlat][i] C07F37
              2019-04-19 17:34:58 | [feed][i]sent 29, filtered 0 AC in 1 packet
              2019-04-19 17:35:03 | [feed][i]sent 36, filtered 0 AC in 1 packet
              2019-04-19 17:35:04 | [mlat][i]Pinging the server
              2019-04-19 17:35:04 | [mlat][i]Stats 92759/92759
              2019-04-19 17:35:08 | [feed][i]sent 34, filtered 0 AC in 1 packet
              2019-04-19 17:35:13 | [feed][i]sent 34, filtered 0 AC in 1 packet
              2019-04-19 17:35:18 | [feed][i]sent 29, filtered 0 AC in 1 packet
              2019-04-19 17:35:24 | [feed][i]sent 34, filtered 0 AC in 1 packet
              2019-04-19 17:35:29 | [feed][i]sent 32, filtered 0 AC in 1 packet
              2019-04-19 17:35:34 | [feed][i]sent 30, filtered 0 AC in 1 packet
              Last edited by abcd567; 2019-04-20, 21:53.

              Comment

              Working...
              X