Results 1 to 7 of 7

Thread: Livestatus Broker error. Can't interact with Thruk UI

  1. #1
    Junior Member
    Join Date
    May 2011
    Posts
    13

    Livestatus Broker error. Can't interact with Thruk UI

    Hi,

    I just upgraded to Shinken 1.4, but I am now experiencing a strange problem. I can't interact with the UI anymore.
    When I click on a service to re-schedule it, I get this in my brokerd.log :
    Code:
    [Livestatus Broker] Closing socket failed: [Errno 107] Transport endpoint is not connected
    For information, I installed via the tarball ( ./install -i ).

    Did anyone experience the same problem ?

    Regards,

    Pierre

  2. #2
    Shinken project leader
    Join Date
    May 2011
    Location
    Bordeaux (France)
    Posts
    2,131

    Re: Livestatus Broker error. Can't interact with Thruk UI

    Look at broker logs, should be something there.
    No direct support by personal message. Please open a thread so everyone can see the solution

  3. #3
    Junior Member
    Join Date
    May 2011
    Posts
    13

    Re: Livestatus Broker error. Can't interact with Thruk UI

    I looked at them very closely but :
    Code:
    2013-11-17 07:30:23,504 [1384669823] Error :  [Livestatus Query] Error: 'Contactgroups' object has no attribute '__itersorted__'
    2013-11-17 07:30:23,546 [1384669823] Error :  [Livestatus Query] Error: 'Contacts' object has no attribute '__itersorted__'
    2013-11-17 07:30:23,588 [1384669823] Error :  [Livestatus Query] Error: 'Services' object has no attribute '__itersorted__'
    2013-11-17 07:30:23,715 [1384669823] Error :  [Livestatus Query] Error: 'Services' object has no attribute '__itersorted__'
    2013-11-17 07:30:23,763 [1384669823] Error :  [Livestatus Query] Error: 'Hosts' object has no attribute '__itersorted__'
    2013-11-18 07:30:05,082 [1384756205] Warning : Printing stored debug messages prior to our daemonization
    2013-11-18 09:48:25,806 [1384764505] Warning : [Livestatus Broker] Closing socket failed: [Errno 107] Transport endpoint is not connected
    (reboot by cron at 7:30, and manual check at 9:48)

    Even with broker-debug.log :
    Code:
    [...]
    [1384765709] Debug :  [Livestatus Broker] Connection 12 is idle since 0 seconds (idle)
    
    [1384765709] Debug :  [Livestatus Broker] Connection 12 is idle since 0 seconds (idle)
    
    [1384765709] Debug :  [Livestatus Broker] Shutdown socket 12
    [1384765709] Debug :  [Livestatus] Request duration 0.0004s
    REQUEST>>>>>
    COMMAND [1384765709] SCHEDULE_FORCED_SVC_CHECK;shinken.ti.smile.fr;Shinken pollers;1384765709
    
    
    [1384765709] Debug :  [Livestatus Broker] Connection 13 is idle since 0 seconds (idle)
    
    [1384765709] Debug :  [Livestatus Query Metainfo] ge_contains_filters: []
    [1384765709] Debug :  [Livestatus Query Metainfo] unique_ge_contains_filters: []
    [1384765709] Debug :  [Livestatus Query Metainfo] ge_contains_filters: []
    [1384765709] Debug :  [Livestatus Query Metainfo] unique_ge_contains_filters: []
    [1384765709] Debug :  [Livestatus] Request duration 0.0017s
    REQUEST>>>>>
    GET services
    Columns: description
    Filter: host_name = shinken.ti.smile.fr
    Filter: description = Shinken pollers
    OutputFormat: json
    ResponseHeader: fixed16
    WaitTimeout: 10000
    WaitCondition: last_check >= 1384765709
    WaitObject: shinken.ti.smile.fr;Shinken pollers
    WaitTrigger: check
    
    
    [1384765709] Debug :  [Livestatus Broker] Connection 10 is idle since 0 seconds (waiting)
    
    [1384765709] Debug :  [Livestatus Broker] Connection 13 is idle since 0 seconds (idle)
    
    [1384765709] Warning : [Livestatus Broker] Closing socket failed: [Errno 107] Transport endpoint is not connected
    [1384765709] Info :  [Livestatus Broker] Closed socket 13
    [1384765709] Debug :  [Livestatus Regenerator] Hint is 4
    [...]
    I don't really know where should I focus...

    Regards,

    Pierre

  4. #4
    Shinken project leader
    Join Date
    May 2011
    Location
    Bordeaux (France)
    Posts
    2,131

    Re: Livestatus Broker error. Can't interact with Thruk UI

    Which Thruk page raise this query? If I'm not wrong the wait queries got problems in the livestatus module since a previous refactoring. The only known ui to use them was multisite, thruk was not.
    No direct support by personal message. Please open a thread so everyone can see the solution

  5. #5

    Re: Livestatus Broker error. Can't interact with Thruk UI

    Thruk uses the wait feature for a long time already. Its a great way to do a reschedule with a single click and return the next page whenever the check has been executed.

    For example, press the "now" button on the action menu of any host or service.

  6. #6
    Shinken project leader
    Join Date
    May 2011
    Location
    Bordeaux (France)
    Posts
    2,131

    Re: Livestatus Broker error. Can't interact with Thruk UI

    Hum ok, so we will have to fix the wait queries
    No direct support by personal message. Please open a thread so everyone can see the solution

  7. #7

    Re: Livestatus Broker error. Can't interact with Thruk UI

    You can disable that feature in the thruk_local.conf, but i think its a really very usefull feature.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •