# K3S Second Master and Agent shows Metrics Error

**URL:** <https://forums.suse.com/t/k3s-second-master-and-agent-shows-metrics-error/40779>\
**Category:** k3s, k3OS, and k3d\
**Created:** [May 26, 2023, 6:18am UTC](https://forums.suse.com/t/k3s-second-master-and-agent-shows-metrics-error/40779 "2023-05-26T06:18:09Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![redshoq](https://avatars.discourse-cdn.com/v4/letter/r/9dc877/32.png) [@redshoq](https://forums.suse.com/u/redshoq)\
**Post date:** [May 26, 2023, 6:18am UTC](https://forums.suse.com/t/k3s-second-master-and-agent-shows-metrics-error/40779/1 "2023-05-26T06:18:09Z")

</div>

Hello there,

I got a cluster with three serviers. 2 master & 1 slave. When i do a ‘sudo kubectl get nodes -o wide’ from master 1 everything workes fine. When I do the same on the second master i get the following messages:

 ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/a/a47ced14aaa8561181318e162e2ff01407b310cd.png)

as I learned from the documentation port 10250 must be reachable on every node. Thats the case.  
Port 10250 is open between the servers.

Can anyone give me a hint what I am missing here?
