I don't know what we have done to our
# umh-supportt
trentc
04/30/2025, 9:20 PMI don't know what we have done to our tag browser in the console....but it is so broke....i've logged out, and cleared cookies and re-logged in.....it finds no tags...but there is data flowing from protocol converters, kafka, mqtt, and sql bridges....
https://cdn.discordapp.com/attachments/984083100520808478/1367249327055179847/image.png?ex=6813e5a9&is=68129429&hm=26fc5ea21383f1cda0ae3fdf7511d810808bc78ec3af2baff2d6e1d9e777740c&
trentc
04/30/2025, 9:23 PMAt one point in time, I was trying to clean up some setup data by deleting topics in Redpanda and all of the data in timescaledb....
when I broke it the first time, I deleted all topics and data, and all protocol converters....
Then started over....and everything started working again....
but....currently I'm trying to avoid "starting fresh"....so how do we recover?
j
jermuk
05/02/2025, 9:09 AMFYI: we have a long vacation weekend here in Germany, which started yesterday. So it might take to Monday until you get an answer from our team.
To recover, maybe restart the management companion?
jermuk
05/05/2025, 11:51 AM@Ferdinand @Athavan kanapuli can one of you take a look here?
f
Ferdinand
05/05/2025, 11:57 AM@trentc Did a restart of the mgmtcompanion work for you ?
Otherwise, can you send me the recent log of it ?
sudo $(which kubectl) logs --kubeconfig /etc/rancher/k3s/k3s.yaml -n mgmtcompanion mgmtcompanion-0sudo $(which kubectl) logs --kubeconfig /etc/rancher/k3s/k3s.yaml -n mgmtcompanion mgmtcompanion-0 > $HOME/logs.txtt
trentc
05/05/2025, 11:57 AMYea, seems to have fixed it.
f
Ferdinand
05/05/2025, 11:58 AMOk.
If it occures again it would be nice if you can send me the logs before restarting, so we can investigate & deploy a permanent fix 🙂
2 Views