[ZBX-24521] Zabbix server startup failed after increasing StartDiscovery value Created: 2024 May 22  Updated: 2024 Aug 05  Resolved: 2024 Aug 05

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: 7.0.0rc1
Fix Version/s: 7.0.3rc1, 7.2.0alpha1

Type: Documentation task Priority: Minor
Reporter: Kazuo Ito Assignee: Arturs Dancis
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 2h
Original Estimate: Not Specified

Attachments: File zabbix_server.log.tzr.gz    
Team: Team B
Sprint: S24-W30/31
Story Points: 1

 Description   

Zabbix server fails to start after setting StartDiscovery to 1000 in zabbix_server.conf.

303348:20240522:025350.269 Starting Zabbix Server. Zabbix 7.0.0rc1 (revision c3509cfd591).
303348:20240522:025350.269 ****** Enabled features ******
303348:20240522:025350.269 SNMP monitoring:           YES
303348:20240522:025350.269 IPMI monitoring:           YES
303348:20240522:025350.269 Web monitoring:            YES
303348:20240522:025350.269 VMware monitoring:         YES
303348:20240522:025350.269 SMTP authentication:       YES
303348:20240522:025350.269 ODBC:                      YES
303348:20240522:025350.269 SSH support:               YES
303348:20240522:025350.269 IPv6 support:              YES
303348:20240522:025350.269 TLS support:               YES
303348:20240522:025350.269 ******************************
303348:20240522:025350.269 using configuration file: /etc/zabbix/zabbix_server.conf
303348:20240522:025350.283 current database version (mandatory/optional): 06050304/06050304
303348:20240522:025350.283 required mandatory version: 06050304
303349:20240522:025350.289 starting HA manager
303349:20240522:025350.294 HA manager started in active mode
303348:20240522:025350.295 server #0 started [main process]
303350:20240522:025350.296 server #1 started [service manager #1]
303351:20240522:025350.296 server #2 started [configuration syncer #1]
303352:20240522:025350.454 server #3 started [alert manager #1]
303355:20240522:025350.455 server #6 started [alerter #3]
303358:20240522:025350.456 server #9 started [lld worker #1]
303359:20240522:025350.457 server #10 started [lld worker #2]
303360:20240522:025350.457 server #11 started [housekeeper #1]
303361:20240522:025350.457 server #12 started [timer #1]
303362:20240522:025350.458 server #13 started [http poller #1]
303365:20240522:025350.459 server #16 started [history syncer #1]
303367:20240522:025350.461 server #18 started [history syncer #3]
303366:20240522:025350.463 server #17 started [history syncer #2]
303364:20240522:025350.463 server #15 started [discovery manager #1]
303370:20240522:025350.466 server #21 started [proxy poller #1]
303363:20240522:025350.466 server #14 started [browser poller #1]
303357:20240522:025350.468 server #8 started [lld manager #1]
303372:20240522:025350.469 server #22 started [self-monitoring #1]
303373:20240522:025350.470 server #23 started [task manager #1]
303368:20240522:025350.471 server #19 started [history syncer #4]
303356:20240522:025350.472 server #7 started [preprocessing manager #1]
303356:20240522:025350.486 [1] thread started [preprocessing worker #1]
303356:20240522:025350.486 [2] thread started [preprocessing worker #2]
303356:20240522:025350.486 [3] thread started [preprocessing worker #3]
303369:20240522:025350.486 server #20 started [escalator #1]
303354:20240522:025350.489 server #5 started [alerter #2]
303381:20240522:025350.491 server #25 started [poller #2]
303364:20240522:025350.492 Cannot initialize discovery manager: cannot initialize maximum number of concurrent checks per worker, user limit of file descriptors is insufficient
303382:20240522:025350.493 server #26 started [poller #3]
303374:20240522:025350.494 server #24 started [poller #1]
303383:20240522:025350.497 server #27 started [poller #4]
303353:20240522:025350.499 server #4 started [alerter #1]
303384:20240522:025350.500 server #28 started [poller #5]
303385:20240522:025350.502 server #29 started [unreachable poller #1]
303391:20240522:025350.504 server #35 started [icmp pinger #1]
303397:20240522:025350.505 server #41 started [history poller #5]
303398:20240522:025350.508 server #42 started [availability manager #1]
303404:20240522:025350.508 server #48 started [configuration syncer worker #1]
303388:20240522:025350.510 server #32 started [trapper #3]
303389:20240522:025350.512 server #33 started [trapper #4]
303348:20240522:025350.513 One child process died (PID:303364,exitcode/signal:1). Exiting ...
303349:20240522:025350.514 HA manager has been paused
303387:20240522:025350.514 server #31 started [trapper #2]
303353:20240522:025350.516 cannot read alert manager service request
303355:20240522:025350.516 cannot read alert manager service request
303386:20240522:025350.517 server #30 started [trapper #1]
303354:20240522:025350.519 cannot read alert manager service request
303390:20240522:025350.520 server #34 started [trapper #5]
303349:20240522:025350.534 HA manager has been stopped
303348:20240522:025350.538 syncing trend data...
303348:20240522:025350.538 syncing trend data done
303348:20240522:025350.539 Zabbix Server stopped. Zabbix 7.0.0rc1 (revision c3509cfd591).

StartDiscovery of 0, 250, 251, 300 succeeded.
StartDiscovery of 1000, 999, 800 failed.



 Comments   
Comment by Arturs Dancis [ 2024 Jul 26 ]

Thank you for reporting! Documentation updated:

  • Discovery > Network discovery > Configuring a network discovery rule (7.0, 7.2; added link to Zabbix server StartDiscoverers parameter for additional context)
  • Configuration > Items > Item value preprocessing > Preprocessing details (7.0, 7.2; clarified warning note)
  • Appendixes > Process configuration > Zabbix server (7.0, 7.2; clarified footnote 1; added footnote 1 to StartDiscoverers parameter description)
Generated at Fri Apr 04 15:53:35 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.