Updating Broadcastify Pi Image

IcomIcR20

Member
Premium Subscriber
Joined
Jun 16, 2014
Messages
856
I am also running into some issues with the new image. I am trying to get Trunk-recorder running on the new image so that I can use two Airspy SDRs instead of one. When performing some preliminary testing with the same config.json file that worked correctly with the previous image, I immediately received some error messages when attempting to start Trunk-recorder.

At least part of the issue seemed to be that the trunk recorder folder is named "tr," rather than the expected "trunk-recorder." After changing that, I get the following message:
Starting trunk-recorder...
â trunk-recorder.service - BCFY Trunk Recorder Service
Loaded: loaded (/etc/systemd/system/trunk-recorder.service; disabled; preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2024-12-25 19:11:44 CST; 2s ago
Process: 2856 ExecStart=/bin/sh -c /home/pi/bcfy/trunk-recorder/recorder --config=/home/pi/bcfy/configs/trunk-recorder/config.json >> /home/pi/bcfy/logs/trunk-recorder.log 2>&1 (code=exited, status=127)
Main PID: 2856 (code=exited, status=127)
CPU: 5ms

Dec 25 19:11:44 bcfy-89de68a0 systemd[1]: trunk-recorder.service: Main process exited, code=exited, status=127/n/a
Dec 25 19:11:44 bcfy-89de68a0 systemd[1]: trunk-recorder.service: Failed with result 'exit-code'.
Press [Enter] to return to the main menu...
The Trunk-recorder log file states:
/bin/sh: 1: /home/pi/bcfy/trunk-recorder/recorder: not found
However, that file does exist at that location.

Like I said, this is a fresh, otherwise untouched install. Any words of wisdom regarding how to proceed would be much appreciated as I am not super knowledgeable about such things.
 
Last edited:

blantonl

Founder and CEO
Staff member
Super Moderator
Joined
Dec 9, 2000
Messages
11,273
Location
San Antonio, Whitefish, New Orleans
I am also running into some issues with the new image. I am trying to get Trunk-recorder running on the new image so that I can use two Airspy SDRs instead of one. When performing some preliminary testing with the same config.json file that worked correctly with the previous image, I immediately received some error messages when attempting to start Trunk-recorder.

At least part of the issue seemed to be that the trunk recorder folder is named "tr," rather than the expected "trunk-recorder." After changing that, I get the following message:

The Trunk-recorder log file states:

However, that file does exist at that location.

Like I said, this is a fresh, otherwise untouched install. Any words of wisdom regarding how to proceed would be much appreciated as I am not super knowledgeable about such things.
Can you post your config.json so I can have a look? Remove any API keys from it.

I think I know what the problem is - I might need to update the service definition. I'll get it fixed after the new year and I'll update this thread.
 

flippinfleck

Member
Joined
Jan 19, 2009
Messages
26
Location
worcester county
For starters, after writing the image I am unable to update due to a lack of free space.

Perhaps the documentation should include something about expanding to utilize the whole SD?
 

Attachments

  • Screenshot from 2024-12-25 20-11-45.png
    Screenshot from 2024-12-25 20-11-45.png
    114.1 KB · Views: 5

IcomIcR20

Member
Premium Subscriber
Joined
Jun 16, 2014
Messages
856
Can you post your config.json so I can have a look? Remove any API keys from it.

I think I know what the problem is - I might need to update the service definition. I'll get it fixed after the new year and I'll update this thread.
I tested a few different variations, but this is one basic config.json that works with the previous image version but does not work with v3.0:
JSON:
{
    "ver": 2,
    "sources": [{
        "center": 852556250.0,
        "rate": 3000000,
        "error": -167,
        "lnaGain": 15,
                "mixGain": 15,
                "ifGain": 7,
        "digitalLevels": 4,
        "digitalRecorders": 4,
        "driver": "osmosdr",
        "device": "airspy=0x10A862DC351E2463"
    }, {
        "center": 858900000.0,
        "rate": 3000000,
        "error": -300,
        "lnaGain": 15,
                "mixGain": 15,
                "ifGain": 7,
        "digitalLevels": 4,
        "digitalRecorders": 4,
        "driver": "osmosdr",
        "device": "airspy=0x10A862DC346A2263"
    }],
    "systems": [{
        "control_channels": [859787500],
        "type": "p25",
        "shortName": "VIPER CLEM",
        "modulation": "qpsk"
    }]
}
 

IcomIcR20

Member
Premium Subscriber
Joined
Jun 16, 2014
Messages
856
For starters, after writing the image I am unable to update due to a lack of free space.

Perhaps the documentation should include something about expanding to utilize the whole SD?
I ran into the same thing. You can free up the remaining space on your SD card by: sudo raspi-config > Advanced Settings > Expand File System > Reboot.
 
Top