landscape-package-search does not start

Bug #1446399 reported by David Britton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Charm
Fix Released
High
Данило Шеган

Bug Description

It's a copy from our hosted config. Not from what we normally include in the LDS package. PID file is wrong, and the account-threshold is wrong. Not sure if anything else.

It also fails to to start on just a regular charm deploy (check /var/log/upstart/*.log). `lsctl status` would probably tell you the same, not sure.

It Would be nice to add an integration test to cover this (lsctl status should be 0 status) after a deploy.

Related branches

David Britton (dpb)
tags: added: kanban
tags: removed: kanban
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Besides the pid path being wrong, the section is a bit messed up with extra blank lines:
"""
[package-search]

host = localhost

port = 9250
stores = main package resource-1
pid-path = /srv/landscape.canonical.com/var/landscape-package-search.pid
account-threshold = 1000
"""

Changed in landscape-charm:
importance: Undecided → High
summary: - package-search stanza is wrong
+ landscape-package-search does not start
Changed in landscape-charm:
status: New → In Progress
assignee: nobody → Данило Шеган (danilo)
Changed in landscape-charm:
status: In Progress → Fix Committed
Changed in landscape-charm:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.