Page MenuHomePhabricator
Create Task
Maniphest T38748

[OPS] syslog::server (in test) unusuable
Closed, ResolvedPublic
Actions

Description

We have rsyslog installed with the base package on all servers. That also trigger the installation of misc::remote-syslog which use rsyslog to send logs to a central box.

When setting up the central box, one has to use the syslog::server class which try to install syslog-ng instead of rsyslog but still has misc::remote-syslog.

The end result is that each time puppet run on the host, whatever syslog system runs at that time is replaced by a the other one.

How to reproduce:

Log on deployment-syslog
Run twice: puppetd -tv

Version: unspecified
Severity: normal

Details

Reference
bz36748

Related Objects
Search...

StatusSubtypeAssignedTask
 ResolvedNoneT39079 deployment-prep root tracking bug (tracking)
 ResolvedNoneT39081 admin tools on beta (tracking)
 ResolvedNoneT38748 [OPS] syslog::server (in test) unusuable

Event Timeline

• bzimport raised the priority of this task from to Medium.Nov 22 2014, 12:28 AM
• bzimport added projects: Beta-Cluster-Infrastructure, acl*sre-team.
• bzimport set Reference to bz36748.
• bzimport added a subscriber: Unknown Object (MLST).
hashar created this task.May 10 2012, 10:02 PM
hashar added a comment.May 15 2012, 11:00 AM

Moving to beta project. Raising priority since that means we have no log!

From a quick discussion with Ryan, instances indeed include base class and thus always have misc::remote-syslog.

hashar added a comment.May 24 2012, 5:57 AM

Moving bug back to pool and tagging for ops to look at.

While I am there, the correct puppet classes are:

base::remote-syslog (installs rsyslog)
misc::syslog-server (installs syslog-ng)

We need a way to conditionally disable the inclusion of base::remote-syslog to let misc::syslog-server install syslog-ng.

hashar added a comment.Jul 25 2012, 7:34 PM

https://gerrit.wikimedia.org/r/16661

hashar added a comment.Oct 17 2012, 9:25 PM

Gerrit change has been abandoned. Ops do not want the hack that is based on a labs instance name and would like the whole syslog system to be rethought. Not going to happen anytime soon unfortunately.

hashar added a comment.Mar 6 2013, 12:01 AM

Bringing back the topic again on ops list and with a new change:
https://gerrit.wikimedia.org/r/#/c/51668

hashar added a comment.Jul 26 2013, 9:28 PM

Change https://gerrit.wikimedia.org/r/#/c/51668 got merged.

On deployment-bastion, I have applied the class misc::syslog-server and created a symlink /home/wikipedia/syslog to /data/project/logs/syslog.

The file is now getting messages from all the instances :-]

Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL