https://www.umh.app logo
Join Discord
Powered by
Issue: Protocol Converter Deploy Failed
# umh-support
t
This happens each time I try again....or save anyway
If I close the window the protocol converter goes to initializing the log, I see this...
Attempting to Save and Deploy the Conveter again
action-log-1
Ok, so I am trying to add a 2nd connection to the same mqtt broker....maybe you can't do this?
j
Yes, you can only add a single protocol converter to a connection
What happened here must have been some networking edge cases, that the UI allowed you to setup a second protocol converter (but then the backend refused it)
t
I have 2 connections....1 protocol converter per connection
both connections are same broker....seems that the 2nd connection protocol converter causes issues....
l
t
j
what do you mean? if you have two connections, you should be able to setup a protocol converter for each of them. what could happen is that you get an error message if you copy pasted the client_id and not let it autogenerate
oh, this is defnitely looking like a bug!
it is stuck in initializing state
@Athavan kanapuli can you look into this?
t
I only modified the topics for the input and the processing. I'm trying to put both the iiotsensors and oee demo. Connection 1 is iotsensors it has 1 converter, the default template, this deployed ok. Connection 2 is oee demo it is same broker, with 1 protocol converter, I copied and pasted in the topics, left the url and client id alone. Then pasted in the Processing code. Issue occurs on 2nd connection protocol converter.
a
Hi @trentc I am trying to reproduce your problem. However, I have a quick question. So you did not overwrite the 
client_id
while creating protocol converter Connection 2 ? Also, what's the version of companion that you're running ?
t
Copy code
Connection 1 Protocol Input
mqtt:
  urls:
    - tcp://192.168.100.25:1883
  topics:
    - ia/raw/development/ioTSensors/Temperature
    - ia/raw/development/ioTSensors/Humidity
  client_id: 899aea2d-830b-4113-9f5b-41d4892796c8


Connection 2 Protocol Input
 mqtt:
  urls:
    - tcp://192.168.100.25:1883
  topics:
    - umh/raw/cologne/ehrenfeld/unicorn/work_order_create
    - umh/raw/cologne/ehrenfeld/unicorn/work_order_start
    - umh/raw/cologne/ehrenfeld/unicorn/work_order_stop
    - umh/raw/cologne/ehrenfeld/unicorn/state
    - umh/raw/cologne/ehrenfeld/unicorn/count
    - umh/raw/cologne/ehrenfeld/unicorn/bad_count
    - umh/raw/cologne/ehrenfeld/unicorn/power
    - umh/raw/cologne/ehrenfeld/unicorn/oven/power
    - umh/raw/cologne/ehrenfeld/unicorn/oven/state
    - umh/raw/cologne/ehrenfeld/unicorn/conveyor/power
    - umh/raw/cologne/ehrenfeld/unicorn/conveyor/state
  client_id: d19d049d-faa9-428a-8803-1835a46e8c26
a
Thanks , this looks good
While I am still working on this bug, Can you also try deleting the second problematic connection and try creating the new one to check if it fixes your problem quickly 🙂
t
I’ve actually done this multiple times, deleting and recreating… I’ll try again though
1. Deleted trouble protocol converter 2. Deleted trouble connection 3. Waited about a minute for anything in the background to finish...just in case... 4. Create new connection 5. Create new protocol converter - ERROR still exists...."deploy failed"
a
Ooops. Is it possible to get at the K3s configmap of the ManagementCompanion ? I guess the configmap is bit messed which is causing this
t
How would I do that?
I have full access to the instance....so I can get anything with a little guidance.
did my bug take down the whole platform? I can't log in now...lol
j
oh, same for me
let me check
see also the post mortem 🙂
PreviousNext
Powered by