Run zgrep -i --color=always -A 10 -B 10 "Key in object structure" /var/log/syslog* | awk -F: '{if(f!=$1)print "=========="; f=$1; print $0;}'
and it should find all recent occurrences or that error and print 10 syslog lines before and after each one to see if there are any other related messages. for me it prints those from the most recent syslog file first but I don't know if that is guaranteed.
Where do the Where and What in the message you posted come from? Are these messages that you have detected in your flow and logged in some way?
If so I would be concerned that there is some flaw in that logic. I find it difficult to see how an Inject node that isn't even configured to repeat or fire on startup could generate such an error. That is what the image you posted is showing isn't it? On top of that the error isn't even getting logged by the system apparently
Yes, the message is being generated by an "error catching routine" I have written.
(Do you want me to post that?)
That is written to a file and I extract that information from the file.
The message is slightly altered as it also needs to go over MQTT, so all important things need to be in the payload part of the message.
Though I have been wrong many times before the error routine does seem to be good as I do get other errors and when I drill down on the message, it is pointing to the correct node.
In that case what do you see in syslog at that time. If it is a real error from a node then I would expect a message there.
Are you sure you are looking at the right pi?
syslog is the newest, then syslog.1, which probably isn't zipped. It probably doesn't end at the same time, well it does but the day before.
But if the date is 16th Jan then the message is probably long gone. syslog usually rolls over once a day unless you are logging a lot in which case it will roll over more quickly. I think the default is the current one and seven previous so once it is a week old it is too late.
I assume our posts crossed so you hadn't seen my previous one.
That confirms your system is as I would expect, you get a week or thereabouts retained.
It also explains why the command I suggested which searches the whole set didn't find anything.