Paweł Zimny's questions

I recently upgraded Zabbix to 5.4.1 and I wanted to start using scheduled report, but I've got some problems with conifguration (error Cannot connect to web service: couldn't connect to server).

My Zabbix is running in Docker on Debian Buster. Everything is based on official containers: Zabbix Server (PostgreSQL), Zabbix Frontend (Apache, PostreSQL) and PostgreSQL12.

According do documentation (https://www.zabbix.com/documentation/current/manual/appendix/install/web_service) I installed Google Chrome browser:

• wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
• sudo apt install ./google-chrome-stable_current_amd64.deb

and Zabbix Web Service

• wget https://repo.zabbix.com/zabbix/5.4/debian/pool/main/z/zabbix-release/zabbix-release_5.4-1+debian10_all.deb
• dpkg -i zabbix-release_5.4-1+debian10_all.deb
• apt install zabbix-web-service

I eddited zabbix_web_service.conf:
AllowedIP=127.0.0.1,::1,0.0.0.0/0,zabbix

I edited zabbix_server.conf:
StartReportWriters=1
WebServiceURL=http://localhost:10053/report

I eddited settings in Zabbix Frontend - Administration -> General -> Other
Frontend URL: http://localhost:8085 (frontend is available at port 8085)

But when I try to test report generating i get error:
Cannot connect to web service: couldn't connect to server

I've already tried with other Frontend URLs, but nothings seems to work. I tried with: http://localhost:10053/report http://192.168.10.18:8085/ http://192.168.10.18:10053/report

I've verified that I get answear from http://192.168.10.18:10053/report : {"detail":"Method is not supported."}

What else can I check/try?

I've completed a clean install of Webcon (2019.1.4.250) on Sharepoint (2016), everything went smooth, but when I try to open any Webcon page I get an error:

I've alread reinstalled Webcon and I gave all required rights to the IIS, but it didn't solve the problem.

Any idea what else I can do to resolve that error?

I am already using active agents on other servers and everything works really nice. I've performed installation of Zabbix agent on new server and I've set the same config as in other active agents. The problem is my agent can't connect to the server.

Logs:

End of zbx_tls_connect():FAIL error:'SSL_connect() I/O error: [0x00002746] An existing connection was forcibly closed by the remote host.'
active check configuration update from [hidden_address:10051] started to fail (TCP successful, cannot establish TLS to [[hidden_address]:10051]: SSL_connect() I/O error: [0x00002746] An existing connection was forcibly closed by the remote host.)
End of refresh_active_checks():FAIL

I am sure that PSK key and ID is set correctly in both agent and server. My config (works on other agents):

LogFile=C:\Zabbix\zabbix_agentd.log
DebugLevel=5
Server=hidden_address
ListenPort=10051
Hostname=hidden_name
ServerActive=hidden_address
EnableRemoteCommands=1

TLSConnect=psk
TLSAccept=psk
TLSPSKFile=C:\Zabbix\conf\client.txt
TLSPSKIdentity=hidden_id 

Port is opened on both sides and I have checked with Test-NetConnection in Powershell that I can connect from agent to server on specifed port (10051).

Any idea what else I can check or try to do to fix the problem?

My goal is to allow users to use Windows Hello on their computers which are connected to the domain. It doesn't have to be Hello for business. At the moment users even can't see Windows Hellow section in sign in settings, for example:

We are using Hybird AD, I've tried many combinations of settings in group policy. Right now I've got enabled options:

• Tun on convenience PIN sign-in (in Logon settings)
• Use Windows Hello for Business (in Hello for Business settings)
• Use biometrics (in Hello for Business settings)
• Use a hardware security device (in Hello for Business settings)
• Allow the use of biometrics (in Biometrics settings)
• Allow users to log on using biometrics (in Biometrics settings)
• Allow domain users to log on using biometrics (in Biometrics settings)

After disconnecting machine from domain, Windows Hellow appears and works alright. Machine is runing on Windows 10 Enterprise, version 2004.

What else I can try to do to allow users to use Windows Hello (PIN, fingerprint, facial recognition)?

I'm trying to create Zabbix item with key which contains commas, it results with "Too many parameters." error. I don't see any opportunity to get rid off comma in my key. I've already tried many ways of enclosing key or parts of it in quotes, double quotes etc. but nothing worked for me. I don't want to use "Database monitor" item type, I'd like to stay with simple "Zabbix agent".

My key is

system.run[sqlcmd -S SERVERNAME-q "SELECT Count(Datediff(second, mail_tsinsert, mail_tsupdate)) FROM   TABLENAME WHERE Datediff(second, mail_tsinsert, mail_tsupdate) > 200"]

of course I've changed the servername and tablename for the sake of the example, query works like a charm when executed in cmd.

Is there a way to escape zabbix item keys?

I'm trying to use Zabbix for monitoring CPU usage by different processes on Windows Server. Processes to monitor are not determined upfront. I want to use LLD to monitor top 3 CPU demanding processes.

Currently I've created a discovery rule that returns top 3 CPU demanding processes at given moment, for example:

{
   {
      "name":"DistributedCacheService",
      "value":"9238.09375"
   },
   {
      "name":"System",
      "value":"6649.234375"
   },
   {
      "name":"svchost",
      "value":"5224.40625"
   }
}

Then I've created macros using json paths and item prototype and that's where i started to experience problems. I'm using earlier created LLD macro for item name and I'm using system.run command for obtaning a value in key field. Item name is supposed to process name and item key, value is supposed the CPU usage by that process. [enter image description here][1] [1]: https://isstatic.aoverflow.com/HuNbd.png

When testing discovery rule and item prototype everything runs fine, but when i try to run that discovery rule I get an error

"Cannot create item: item with the same key "system.run[powershell.exe -nolog -command "(Get-Process | Sort-Object CPU -desc | Select-Object -index 0 | Format-Table -Aut...]" already exists."

Firstly, there is no other item with the same key.

Secondly, when my discovery rule will detect other processes, there will have to be created other items with the same key. Other names, but the same key

Is it even possible to create processes CPU usage monitoring using LLD? I don't want to be stuck with predefined processes, I would like to have them dynamicly added with LLD.