Ad Widget

Collapse

Cannot bind socket - Address already in use

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • vaas
    Junior Member
    • Mar 2021
    • 2

    #1

    Cannot bind socket - Address already in use

    Hello,

    I have problem with running the zabbix_server, log contains this information:

    49791:20210313:112241.956 server #25 started [icmp pinger #1]
    49790:20210313:112241.956 server #24 started [trapper #5]
    49795:20210313:112241.956 server #29 started [alerter #3]
    49795:20210313:112241.956 zbx_setproctitle() title:'alerter [connecting to the database]'
    49795:20210313:112241.956 In zbx_ipc_socket_open()
    49797:20210313:112241.956 zbx_setproctitle() title:'preprocessing worker #1 starting'
    49797:20210313:112241.956 In zbx_ipc_socket_open()
    49800:20210313:112241.956 zbx_setproctitle() title:'lld manager #1 starting'
    49800:20210313:112241.956 server #34 started [lld manager #1]
    49800:20210313:112241.956 In zbx_ipc_service_start() service:lld
    49800:20210313:112241.956 In zbx_ipc_socket_open()
    49800:20210313:112241.956 End of zbx_ipc_socket_open():FAIL
    49800:20210313:112241.956 End of zbx_ipc_service_start():FAIL
    49800:20210313:112241.956 cannot start LLD manager service: Cannot bind socket to "/var/run/zabbix/zabbix_server_lld.sock": [98] Address already in use.
    49758:20210313:112241.957 One child process died (PID:49800,exitcode/signal:1). Exiting ...
    49758:20210313:112241.957 zbx_on_exit() called
    49765:20210313:112241.960 itemid:27329 hostid:10218 templateid:27107
    49768:20210313:112241.960 server #2 started [housekeeper #1]
    49791:20210313:112241.960 zbx_setproctitle() title:'icmp pinger #1 [getting values]'
    zabbix_server [49758]: Error waiting for process with PID 49800: [10] No child processes
    49758:20210313:112241.966 In DBconnect() flag:1
    49758:20210313:112241.966 End of DBconnect():0
    49758:20210313:112241.966 In free_database_cache()
    49758:20210313:112241.966 In DCsync_all()
    49758:20210313:112241.966 In sync_history_cache_full() history_num:0
    49758:20210313:112241.966 End of sync_history_cache_full()
    49758:20210313:112241.966 In DCsync_trends() trends_num:0
    49758:20210313:112241.966 syncing trend data...
    49758:20210313:112241.966 query [txnlev:1] [begin;]
    49758:20210313:112241.966 query [txnlev:1] [commit;]
    49758:20210313:112241.966 syncing trend data done
    49758:20210313:112241.966 End of DCsync_trends()
    49758:20210313:112241.966 End of DCsync_all()
    49758:20210313:112241.966 End of free_database_cache()
    49758:20210313:112241.966 In free_configuration_cache()
    49758:20210313:112241.966 End of free_configuration_cache()
    49758:20210313:112241.966 In zbx_vc_destroy()
    49758:20210313:112241.966 End of zbx_vc_destroy()
    49758:20210313:112241.966 In free_selfmon_collector() collector:0x7f514d8bf000
    49758:20210313:112241.966 End of free_selfmon_collector()
    49758:20210313:112241.966 In zbx_unload_modules()
    49758:20210313:112241.966 End of zbx_unload_modules()
    49758:20210313:112241.966 Zabbix Server stopped. Zabbix 5.0.9 (revision 4d07aaafe2).

    When I stop zabbix, delete all sock files from /tmp and start it again, the zabbix_server runs for few seconds and then stops again with this error in log.

    Could you please advice?

    Kind Regards,
    Vaclav
  • gofree
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Dec 2017
    • 400

    #2
    could it be like here ?

    Comment

    • vaas
      Junior Member
      • Mar 2021
      • 2

      #3
      Yes, thank you very much. Cheers

      Comment

      Working...