You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
After setting up a master cluster on 3007.0 I noticed the following errors being logged whenever the salt-master service is restarted. These logs appear to be indicating successful communication between masters on TCP 4520, not errors.
2024-03-24T13:10:27.409651-05:00 salt1 salt-master[108565]: [ERROR ] Received new key from peer 192.168.40.76
2024-03-24T13:10:27.617687-05:00 salt1 salt-master[108565]: [ERROR ] Received new key from peer 192.168.40.77
Setup
Three Debian 12 VMs configured as a Salt Master Cluster
on-prem machine
VM (KVM)
VM running on a cloud service, please be explicit and add details
container (Kubernetes, Docker, containerd, etc. please specify)
or a combination, please be explicit
jails if it is FreeBSD
classic packaging
onedir packaging
used bootstrap to install
Steps to Reproduce the behavior
Tail /var/log/salt/master and restart the salt-master service on one of the cluster nodes
Expected behavior
I would expect to only see these messages when the master log_level is set to info
Versions Report
salt --versions-report
Salt Version:
Salt: 3007.0Python Version:
Python: 3.10.13 (main, Feb 19 2024, 03:31:20) [GCC 11.2.0]Dependency Versions:
cffi: 1.16.0cherrypy: unknowndateutil: 2.8.2docker-py: Not Installedgitdb: Not Installedgitpython: Not InstalledJinja2: 3.1.3libgit2: 1.7.2looseversion: 1.3.0M2Crypto: Not InstalledMako: Not Installedmsgpack: 1.0.7msgpack-pure: Not Installedmysql-python: Not Installedpackaging: 23.1pycparser: 2.21pycrypto: Not Installedpycryptodome: 3.19.1pygit2: 1.14.1python-gnupg: 0.5.2PyYAML: 6.0.1PyZMQ: 25.1.2relenv: 0.15.1smmap: Not Installedtimelib: 0.3.0Tornado: 6.3.3ZMQ: 4.3.4Salt Package Information:
Package Type: onedirSystem Versions:
dist: debian 12.5 bookwormlocale: utf-8machine: x86_64release: 6.1.0-18-amd64system: Linuxversion: Debian GNU/Linux 12.5 bookworm
The text was updated successfully, but these errors were encountered:
Description
After setting up a master cluster on 3007.0 I noticed the following errors being logged whenever the salt-master service is restarted. These logs appear to be indicating successful communication between masters on TCP 4520, not errors.
Setup
Three Debian 12 VMs configured as a Salt Master Cluster
Steps to Reproduce the behavior
Tail /var/log/salt/master and restart the salt-master service on one of the cluster nodes
Expected behavior
I would expect to only see these messages when the master
log_level
is set toinfo
Versions Report
salt --versions-report
The text was updated successfully, but these errors were encountered: