Redpanda starting no logs found Issue
# umh-support
z
Hi, I have an umh-core instance running on an edge device, and I can see it connected in the management console. The problem occurs when I try to add a bridge in the data flow. I have this error
starting: redpanda: starting: no logs found
. I’m running a minimal configuration, here is my config.yaml :
Copy code
yaml
internal:
    topicbrowser:
        desiredState: active
    redpanda:
        desiredState: active
agent:
    location:
        0: xxx
        1: ""
        2: ""
        3: ""
        4: ""
        5: ""
        6: ""
    releaseChannel: stable
    communicator:
        apiUrl: https://management.umh.app/api
        authToken: XXX
    metricsPort: 8080
    enableResourceLimitBlocking: false
I also checked the container logs, and it seems this is why redpanda does not start ? does anyone have an idea of what might be causing this and what exactly is happening ?
UPDATE: I restarted from scratch. I no longer see errors in the logs, but I still have the same issue when trying to add a bridge. Upon further investigation, here is what i found : Redpanda does not seem to have started at all, i tried this to check the port :
Copy code
bash
sudo docker exec -it umh-core netstat -tlnp | grep 9092
In the volume, i have an empty
coredump
dir inside
redpanda
:
Copy code
bash
~$ ls -lR /srv/volumes/umh-core-data/redpanda/
/srv/volumes/umh-core-data/redpanda/:
total 4
drwxr-xr-x 2 nobody nogroup 4096 Nov  7 11:21 coredump

/srv/volumes/umh-core-data/redpanda/coredump:
and if i try to force the start of redpanda :
Copy code
bash
sudo docker exec -it umh-core sh -c "redpanda start --check; echo $?"
i get :
Copy code
Aborted
134
Note : hardware architecture is `aarch64`:
Copy code
bash
$ uname -m
aarch64
j
I am currently looking at this. What hardwaredevice are you using exactly? it could be that we dont support aarch64 in redpanda, i am currently evaluating
(sorry for the late reply)
Are you running it on a Raspberry Pi? the issue here is that Redpanda doesnt support it. We should update our documentation accordingly
can you do a
cat /proc/cpuinfo
?
z
Hi thanks for the reply ! Yeah then this was the issue 🥲 at least now I know why it didnt work
j
:/
d
digging a little deeper through the issues i reached this: https://github.com/raspberrypi/linux/issues/4375 basically what i read there is that this is not a hardware limitation but a compatibility issue in the kernel configuration for a decent number of applications
2 Views