The SecsorConnect Pod logs shows that it has Found...
# umh-support
l
The SecsorConnect Pod logs shows that it has Found the IFM Gateway
apparently there is a bug in sensorconnect, which causes it to continue finding the device (it did not crash), but it keeps running and sending nothing to kafka. we will receive the logs in a couple of hours. a pod restart fixes the problem (but also deletes the logs)
@lmullane that that power cycling the gateway does not fix the bug, and apparently only sensorconnect restart. @Ferdinand @DaruZero can one of you take a look there what could have gone wrong here?
@lmullane just to confirm: you turned down the power of the ifm gaetway for a couple of seconds, turned it on again and the error was still like this right?
what happens if you open the device in the browser?
l
I reset power before our initial call at 12:30 , on this failure 14:05 I have not reset IFM yet
Will I power cycle the IFM Gateway ?
j
can you first try to connect to the gateway with your browser?
l
The IFM Gateway is currently not responding through the Browser
I can ping its IP
IFM Gateway bug, note I still have not power cycled it in case you want me to do anything while in that state
j
ok, if you cannot reach the gateway its likely an ifm bug. but it should be fixed with a restart
lets just flash the new firmware to be on the safe side here
l
I agree the IFM Gateway has a bug, it should not go unresponsive. However restarting it does not resolve the issue, However Removing the SensorConnect Pod, and waiting for the UMH stack to Start another SensorConnect POD does get the stack working again, Before I flash the IFM Gateway would it be better to fix the SensorConnect POD, ie once the Gateway is restarted the SensorConnect should detect and work as normal ?
a
I think is also the Same bug that we had at 🥩
j
Hypothesis: maybe sensorconnect is doing too many requests, stuck in an endless loop, etc and overloads the ifm gateway, so that is stays unresponsive. What you can try is lowering the poll rate in the environment variables. Can you try setting LOWER_POLLING_TIME_MS in the sensorconnect pod or deployment from 20 to 500? And then check whether the gateway is unresponsive? Also, let's try flashing the new firmware
l
Ok, I will try that and report back, thanks for the help again Jermuk
Just trying to figure how to change it
k:{"name":"LOWER_POLLING_TIME_MS"}: .: {} f:name: {} f:value: {}
or is it
- name: LOWER_POLLING_TIME_MS value: '20'
If I try to change second option UMH lens generates a ERROR when saving
f
the 2nd one
Can you show me which error you get ?
l
There is a recording of the process I'm using
f
Ok, ill check if this is incorrectly documented, but you are supposed to change it in the StatefulSet
l
ah ok I'll try there so
Yes I was able to change the setting in StatefulSet, thanks for your help Flinnenberg. I restart the simulation and leave run for a few hours
Its still working, but I need to go to office, but I will leave it run overnight to see how it gets on
I left the Stack run overnight on my laptop and its still working (so that's over 12 hours) . Only change I made so far wash the "LOWER_POLLING_TIME_MS" change from 20 to 500. (so IFM Gateway not flashed yet) .
I'm still a bit concerned that the SensorConnect Pod fails after a few hours at the 20ms setting. Ok the IFM Gatway bug could be the source, but I think the SensorConnect POD needs to be robust to handle it, ie on a customer site all sorts of things may go wrong, network and power outages etc
j
i understand your concern, we could set the lower polling time to 500 by default. there is already a complicated logic inside of of sensorconnect trying not to overload the ifm gateways with old firmware (like for example LOWER_POLLING_TIME_MS), but the point where the ifm IO-link master fails is also dependent on the amount of sensors that are connected, which makes it hard for us to establish a logic there. we even talked with the ifm people about that and they already said that its a bug on their side and flashing the new firmware will fix it.
l
ok thanks for the Feedback Jermuk, I'll flash the IFM Gateway with the pre-release version of the firmware and do some further tests
Ok Just a update, I flashed the IFM Gateway yesterday. I left it run overnight again and its still working I guess over 30 hours now
2 Views