Skip to main content
Readybreak
Readybreak
New Member
September 15, 2023
Question

Issues with Configuring EMS ADconnector

  • September 15, 2023
  • 3 replies
  • 2514 views

Hi Team,

 

Setting up the ADconnector for my trial version of Forticlient EMS Cloud, i complete the configuration following this guide: AD connector | FortiClient 7.2.1 | Fortinet Document Library

 

Everything seems successful and the log looks all good, but then it shows the error: Log Level Monitor got error checking for new level: error sending to event server: redis: nil

This just keeps repeating. Full log:
2023-09-15T13:35:29.151+1000 INFO adconnector/adconnector.go:85 Starting FortiClient EMS AD Connector - 7.2.1.793
2023-09-15T13:35:29.152+1000 INFO adconnector/adconnector.go:301 No config for [azure] AzureTimeoutSecs, using default value: 60 sec
2023-09-15T13:35:29.152+1000 INFO adconnector/adconnector.go:116 Loaded 0 domains from configuration file
2023-09-15T13:36:17.786+1000 INFO common/common.go:262 Started log level monitor routine
2023-09-15T13:36:19.750+1000 WARN common/common.go:267 Log Level Monitor got error checking for new level: error sending to event server: redis: nil
2023-09-15T13:36:20.279+1000 INFO connector/adconnector_service.go:78 Received 0 domains from daemon
2023-09-15T13:37:03.678+1000 INFO connector/adconnector_service.go:171 [site:default][host:domaincontroller]: Starting domain server for domaincontroller:389
2023-09-15T13:37:03.678+1000 INFO connector/adconnector_service.go:177 [site:default][host:domaincontroller]: Starting domain server for domaincontroller:389
2023-09-15T13:37:03.683+1000 INFO connector/adconnector_service.go:385 [site:default][host:domaincontroller]: Connected to LDAP server domaincontroller:389
2023-09-15T13:37:20.854+1000 WARN common/common.go:267 Log Level Monitor got error checking for new level: error sending to event server: redis: nil
2023-09-15T13:38:22.040+1000 WARN common/common.go:267 Log Level Monitor got error checking for new level: error sending to event server: redis: nil

 

 

Any ideas?

3 replies

spoojary
Staff
spoojary
Staff
September 15, 2023

The error Log Level Monitor got error checking for new level: error sending to event server: redis: nil suggests an issue with the communication between the AD Connector and the Redis event server.  Ensure that the Redis event server is running and accessible. Also, verify the connection configurations for Redis in the AD Connector setup. If everything appears fine, consider restarting the AD Connector and the Redis server. If the error persists, consult Fortinet's technical support.

Readybreak
ReadybreakAuthor
New Member
September 17, 2023

Unable to contact support as this is a trial instance, I was directed here. All configuration seems correct as per the guide and I have restart, reinstalled and changed to a different server. No blocks are visible on the firewall.

When adding the configuration to the EMS instance, it passes the initial check and allows me to save, but then any further checks or syncs it fails.

Need to get this resolved before purchasing and would prefer the cloud version over the onprem instance.

Readybreak
ReadybreakAuthor
New Member
September 22, 2023

I am now not even able to see any traffic hitting my IP address when just directly connecting from the my EMS Cloud instance, this needs looking into immediately. I have no control over my cloud EMS instance and stuff like this is certainly going to make me look elsewhere

Terms & ConditionsAccessibility statement