https://www.umh.app logo
Join Discord
Powered by
Its Here 🙂
# umh-support
o
j
@Ferdinand how can it happen that this error message appears? Maybe a upgrade gone wrong?
Copy code
{"log.level":"error","@timestamp":"2023-02-21T14:40:04.652Z","log.origin":{"file.name":"internal/kafkaMessageTrace.go","file.line":25},"message":"SerialNumber is empty","ecs.version":"1.6.0"}
{"log.level":"error","@timestamp":"2023-02-21T14:40:04.652Z","log.origin":{"file.name":"sensorconnect/kafka.go","file.line":43},"message":"Failed to send Kafka message: microservice name is empty","ecs.version":"1.6.0"}
f
@Jermuk maybe. To fix it, @Onur Can KARAMAN - ASO you can manually add it to sensorconnect, by editing it's deployment. In the env section, add the key value pair
Copy code
- name: SERIAL_NUMBER
  value: default
o
I'm doing this through the value yaml file. Is it true?
I added it here, but the data did not come. I also got errors when I hit the save button.
It didn't register even though I pressed the register button.
I added it here, but there is no change.
j
What do the logs say?
or are you not able to update sensorconnect at all?
o
I restarted the pod.
j
seems to me that everything is working? but you are not able to see them in MQTT explorer? Can you check in kowl?
o
I can't see kowl in pods. I had this problem once but I can't remember how we solved it. Anydesk is installed on my computer at the office. I can give you ID and password if you want. To solve it faster.
j
ahh, kowl is now called console. Can you check it there?
o
This is how I see things. Now I'll try if it's coming from node-red. But it doesn't show up in Explorer.
Data does not come on node-red. It only shows up in kowl.
@Jermuk When I want to visualize the data, I get an error like this in V1 Datasource. Especially in OEE KPIs. V2 can show some data. But OEE is important to us. Can I show it in v2 too?
I did something like this for now to read data from the sensor 🙂 Until I solve the problem 😄
flows-2
By the way, I just realized. This is the version I have, but the latest on the website is 0.9.10. Could it be caused by that?
j
Just to be sure: there is also data in those topics, correct? If yes, can you send me a log from the mqtt Kafka bridge?
OEE should also be possible in v2. Can you send me a log of factoryinsight?
No, the latest is actually v0.9.11. So everything is good here 🙂
o
In v2, only tag and custom options appear after selecting the machine. I saw it in KPI on the website, but it doesn't show up for me. I think it was opened in a thread on github about it.
Good morning, Now I'm starting to have another problem. The products I send with Addproduct are not registered in the database. But State and ProcessValue seem to be registering. Short Note: I wonder if it would be better if I did a re-installation 😄
united-manufacturing-hub-kafkatopostgresql-7cd84c66c4-brgwpunited-manufacturing-hub-mqttkafkabridge-7d888f7dfb-ppg2z
j
@Ferdinand how can that be?
have you seen this error message? 
Error parsing message: no timestamp [map[Word0:240]] (ia.sensordatas.port2)
can you show me whether it appears in Kafka?
o
How can I do that?
Jeremy in the past I deleted everything while updating. Then you (or Alex, I couldn't remember :)) You were connected and re -installed the version 9.5 (we protected the data.). Can we do something similar here? At that time, everything started to work stable. After establishing a Flatcar during the installation, I noticed that UMH was not established. I created a namespace and set up Umh in that way. (As explained in the deployment section on the website.) I wonder if it could be because of it. I think that when there is more than one problem instead of a single problem, something went wrong during the installation.
j
So you installed UMH using this tutorial (https://learn.umh.app/guides/getstarted/installation/installation-guide-flatcar/), but UMH was not showing up in Lens so you had to install it in your own? Do you have today time at 15:00 Ankara time (13:00 German time)? I'd like to take a look via Anydesk to see what happened during the installation.
o
True, I installed it as in this recipe, but after the installation was finished, the umh namespace was not created.
j
good that you mentioned that! i've send you an invite
o
I further, 1. kubectl create namespace united-manufacturing-hub I created namespace with this code. 2. helm install united-manufacturing-hub united-manufacturing-hub/united-manufacturing-hub -n united-manufacturing-hub I also installed with this code.
j
from journalctl -u umh-install:
Copy code
Feb 21 07:09:23 flatcar-1-umh-Default systemd[1]: Starting Run UMH installation script...
Feb 21 07:09:23 flatcar-1-umh-Default sh[834]: Installing the United Manufacturing Hub. This might take a while...
Feb 21 07:09:23 flatcar-1-umh-Default sh[834]: Installing as user: root
Feb 21 07:09:23 flatcar-1-umh-Default sh[834]: Adding helm repo...
Feb 21 07:09:23 flatcar-1-umh-Default sh[837]: "united-manufacturing-hub" already exists with the same configuration, skipping
Feb 21 07:09:23 flatcar-1-umh-Default sh[834]: Added helm repo!
Feb 21 07:09:23 flatcar-1-umh-Default sh[834]: Creating namespace united-manufacturing-hub...
Feb 21 07:09:24 flatcar-1-umh-Default sh[854]: Error from server (ServiceUnavailable): the server is currently unable to handle the request (post namespaces)
Feb 21 07:09:24 flatcar-1-umh-Default sh[834]: Failed to create kubernetes namespace for united-manufacturing-hub, aborting setup
Feb 21 07:09:24 flatcar-1-umh-Default systemd[1]: Started Run UMH installation script.
Feb 21 07:32:42 flatcar-1-umh-Default systemd[1]: umh-install.service: Deactivated successfully.
Feb 21 07:32:42 flatcar-1-umh-Default systemd[1]: Stopped Run UMH installation script.
Copy code
Error parsing message: no timestamp [map[product_id:MB-1 time_per_unit_in_seconds:180]] (ia.factoryinsight.ankaramf.freze1.addproduct)
OEE is returning a 204 in old datasource and does not show up at all in new datasource
d
you will need a timestamp_ms for all messages sent or else kafka will not accept it and send it to the database..
one way to do it is to have a function node just before mqtt to add a timestamp to the message.
msg.payload["timestamp_ms"] = Date.now(); return msg;
j
We are at the moment fixing just that. One cause was that we are de-duplicating messages on the bridge. If you are not using a timestamp, then the messages will be the same (especially for your addProduct test flow) and will therefore only pass once. I do not know if @Ferdinand also fixed the issue with the first message noch being send to Kafka as well. I know he deployed a hot fix for Onur.
d
yes i had the same problem the other day when connecting some new nodes,, first i had some NaN-values which i thought was the problem then i saw the error in kafta when it complained about the timestamp so i just figured you wanted to have it like that so i just added a timestamp to the messages.
f
@Onur Can KARAMAN - ASO Iv updated your factoryinsight, kafkatopostgresql and grafana-umh version. You can now query KPI's
o
Thank you all so much guys. You are King 🙂
2 Views
PreviousNext
Powered by