Recently I updated from 6.2.3 to 6.2.4 and every single one of my Windows agents broke.
1. Been doing some testing and the msi log showed "PSK not Valid"
2. It is the same PSK that I used in 6.2.3
3. Setup a couple of clean VMs and pushed the 6.2.4 agent to one and the 6.2.3 agent to the other, the 6.2.3 agent worked but the the 6.2.4 agent gave the "PSK not Valid" error
4. The original PSK was created on Ubuntu using "openssl rand -hex 32" from the Zabbix documentation
5. The weird thing is that if I manually install 6.2.4 I can use the PSK code without error
This leads me to believe that something in the unattended installation of 6.2.4 that there is an error.
I have no idea on how to tell anyone at Zabbix about my findings. Nor can I find any changes to the psk requirements for 6.2.4
Guess I am reverting to 6.2.3
Additionally, a google search is showing that I am not the only one with this issue. I hope that this post shows up for others with the issue and provides them with some clarity. Better yet if you know how to fix it let me know.
1. Been doing some testing and the msi log showed "PSK not Valid"
2. It is the same PSK that I used in 6.2.3
3. Setup a couple of clean VMs and pushed the 6.2.4 agent to one and the 6.2.3 agent to the other, the 6.2.3 agent worked but the the 6.2.4 agent gave the "PSK not Valid" error
4. The original PSK was created on Ubuntu using "openssl rand -hex 32" from the Zabbix documentation
5. The weird thing is that if I manually install 6.2.4 I can use the PSK code without error
This leads me to believe that something in the unattended installation of 6.2.4 that there is an error.
I have no idea on how to tell anyone at Zabbix about my findings. Nor can I find any changes to the psk requirements for 6.2.4
Guess I am reverting to 6.2.3
Additionally, a google search is showing that I am not the only one with this issue. I hope that this post shows up for others with the issue and provides them with some clarity. Better yet if you know how to fix it let me know.
Comment