script monitor needs a database user

Bug #134012 reported by Stuart Bishop on 2007-08-22
2
Affects Status Importance Assigned to Milestone
Launchpad itself
High
Stuart Bishop

Bug Description

All scripts should connect as a unique database user.

To fix this involves:

 * Editing database/schema/security.cfg to add the new user with relevant permissions

 * Updating jubany's pg_ident.conf to allow connections as the new user for forster.

 * Updating the monitoring script to connect as the new user

 * Rolling out the code.

Related branches

Stuart Bishop (stub) on 2007-08-22
Changed in launchpad:
importance: Undecided → Medium
status: New → Confirmed
Joey Stanford (joey) wrote :

Untargeting from 1.1.19 due to no owner. Maybe we can get james to do this for 1.1.10? Stu can you ask him about this please?

Robert Collins (lifeless) wrote :

This needs an update for pgbouncer etc. Assigning to stub to re-define the bug and/or execute.

Changed in launchpad:
importance: Medium → High
assignee: nobody → Stuart Bishop (stub)
Stuart Bishop (stub) wrote :

script_monitor and script_monitor_nagios exist in security.cfg.

script-monitor.py and script-monitor-nagios.py will be hard coded to use these users once they exist on production.

Changed in launchpad:
status: Triaged → In Progress
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
William Grant (wgrant) on 2011-09-25
tags: added: qa-untestable
removed: qa-needstesting
Stuart Bishop (stub) wrote :

RT #48134 on granting access to the new users

Stuart Bishop (stub) wrote :

RT #49154 to get the crontabs updated to connect as the correct users.

William Grant (wgrant) on 2012-06-21
Changed in launchpad:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers