Rudder

Hello Siemen, thank for reporting your issue!

Is there a time delay on the node and the root server ?

Can you show a screen of the entries in the techical log tab ?

Is the reporting on the root server ok ?

Thanks for the quick reply,

What exactly do you mean with time delay? If you mean network wise, Ping times are less then 1msec, Time on all servers is configured correctly.

How would i be able to get this screen?

The clients report to the root server without a problem.( the last seen is updated every 5 minutes)

Sorry about the late reply, I missed your answer.

For reporting to be ok, the date on the node and the server needs to be synchronized on both server and nodes ( run 'date' command on both, if you see a delay you have a problem)

About the "technical logs" tab, on a Node detail, click on the tab "technical log", one of the rightmost tabs and take a screenshot of the table displayed

Was it working before, or is it a new install ?

Thank for your screens!

So from your two screen, i can see the the node could not update it's policies so is still using an old reporting format.

Two questions:

• when running 'rudder agent update' on the faulty node, do you get an error ?

If there is an error we have a tool on Rudder server: run 'rudder server debug <ip-faulty-node>' then run 'rudder agent run' on the node. can you share the output ?

A common update error is that Rudder serveur is not resolving correctly the node hostname, it may be the case here (to check run 'getent hostname-of-your-node' on the server )

oops, i tolds you wrong commands, sorry! :(

it's 'rudder agent update' you need to run after running rudder-server-debug and not rudder agent run!

and getent command is "getent hosts <hostname-of-your-node>"

from logs, i can see that your node is identified as debian-test, is that correct ? or should it be the other one ?

Now it is my time to apologize. I uploaded the wrong log file. ill update you ASAP

I did another reset/reinit on the Stream-Server.

It is reporting again for at least 20 mins now. Ill let you know if it stays that way.

Your server cannot determine that your stream-server ip is your stream-server, you need to htlp him finds out

easiest way is to define the line in the /etc/hosts of your server rudder about stream-server

That is weird. Because it is reporting correctly now.
If this was the issue it would fail all the time right?

Why would the rudder master need to have the name of the client hosts? I thought this was all done over IP.

I think this issue has been resolved. I have no clue what caused it to report that way but apperently it is fixed in the latest release.

I'm wondering if it can't be linked to #8051, to ? The symptoms are quite alike.

I did indeed ran that command so it might be related.