[bug-notifications] [cswclassutils 0003469]: Zone support for syslog_ng
Mantis Bug Tracker
noreply at opencsw.org
Fri May 29 14:14:17 CEST 2009
A NOTE has been added to this issue.
======================================================================
http://www.opencsw.org/mantis/view.php?id=3469
======================================================================
Reported By: automatthias
Assigned To: bonivart
======================================================================
Project: cswclassutils
Issue ID: 3469
Category: packaging
Reproducibility: always
Severity: major
Priority: normal
Status: feedback
======================================================================
Date Submitted: 2009-03-14 16:34 CET
Last Modified: 2009-05-29 14:14 CEST
======================================================================
Summary: Zone support for syslog_ng
Description:
After installing syslog_ng, there is imported service definition into SMF,
but it's lacking on all non-global zones.
vsol01 ~ # svcs cswsyslog_ng
STATE STIME FMRI
online 0:58:42 svc:/network/cswsyslog_ng:default
vsol01-zone1 ~ # svcs cswsyslog_ng
svcs: Pattern 'cswsyslog_ng' doesn't match any instances
STATE STIME FMRI
======================================================================
----------------------------------------------------------------------
(0005725) ihsan (reporter) - 2009-03-24 15:46
http://www.opencsw.org/mantis/view.php?id=3469#c5725
----------------------------------------------------------------------
The smf manifest is provided by cswclassutils. I'll transfer this bug to
cswlcassutils.
----------------------------------------------------------------------
(0005730) bonivart (manager) - 2009-03-24 22:04
http://www.opencsw.org/mantis/view.php?id=3469#c5730
----------------------------------------------------------------------
Ok, I have to do some tests to reproduce the problem. In the meantime, I
guess you can just install the package into each zone manually, I hope it's
not too many.
----------------------------------------------------------------------
(0005995) bonivart (manager) - 2009-04-21 19:03
http://www.opencsw.org/mantis/view.php?id=3469#c5995
----------------------------------------------------------------------
Still haven't had time to test but wondering if it's just cswclassutils not
being present in the (sparse) zones?
----------------------------------------------------------------------
(0006218) bonivart (manager) - 2009-05-28 16:42
http://www.opencsw.org/mantis/view.php?id=3469#c6218
----------------------------------------------------------------------
I really can't get any further without more info. I will have to assume
that the install was done from a sparse zone so CSWcswclassutils (which
contains files in /usr) failed. The fix is to install CSWcswclassutils from
the global zone.
----------------------------------------------------------------------
(0006219) bonivart (manager) - 2009-05-28 16:43
http://www.opencsw.org/mantis/view.php?id=3469#c6219
----------------------------------------------------------------------
I have added info about the sparse zone issue on the wiki.
----------------------------------------------------------------------
(0006221) automatthias (reporter) - 2009-05-29 11:36
http://www.opencsw.org/mantis/view.php?id=3469#c6221
----------------------------------------------------------------------
It is fixable, I've created
http://apps.sourceforge.net/trac/gar/changeset/5096 with a proposal.
----------------------------------------------------------------------
(0006223) bonivart (manager) - 2009-05-29 13:38
http://www.opencsw.org/mantis/view.php?id=3469#c6223
----------------------------------------------------------------------
Why is that a fix and for what? Please explain what's the problem first? Is
it a problem with syslog_ng or cswclassutils?
And who are you? automaciej from IRC, wahwah from Sourceforge?
----------------------------------------------------------------------
(0006225) automatthias (reporter) - 2009-05-29 13:54
http://www.opencsw.org/mantis/view.php?id=3469#c6225
----------------------------------------------------------------------
Yes, it's the same person: automaciej from irc == wahwah from sourceforge
== maciej from the mailing list
In short: The original problem was that syslog_ng didn't get started in
non-global zones. Changeset 5096 fixes that.
Longer explanation: I don't think that the SMF manifest was provided by
cswclassutils. There was an XML file in the 'files' folder. Changeset 5096
ports syslog_ng to mgar v2 and switches SMF handling to cswclassutils. As a
side note, I don't think this bug belongs to cswclassutils or common, it
belongs to syslog_ng.
----------------------------------------------------------------------
(0006226) bonivart (manager) - 2009-05-29 14:09
http://www.opencsw.org/mantis/view.php?id=3469#c6226
----------------------------------------------------------------------
Ok, thanks for the clarification. :-)
According to your link Ihsan already used the SMF support through
cswclassutils:
SPKG_CLASSES = none cswinitsmf
That class autogenerates a manifest and that's what gets imported so even
if he somehow packaged another manifest I doubt very much it was used, it
may have been there as some contrib stuff.
But as I have tried to mention before, cswclassutils contains files in
/usr so if you're running a sparse zone and tries to install, in this case,
syslog_ng from it, the dependency installation of cswclassutils will fail
since /usr is read-only. The fix is to have cswclassutils installed from
the global zone so the dependency is fulfilled beforehand.
----------------------------------------------------------------------
(0006227) automatthias (reporter) - 2009-05-29 14:14
http://www.opencsw.org/mantis/view.php?id=3469#c6227
----------------------------------------------------------------------
I see, you thought that I installed the package in a sparse zone -- that
wasn't the case.
Say, you have machine foo with zones foo-zone1 and foo-zone2. You install
syslog_ng in the global zone of foo. When you do that, foo-zone1 and
foo-zone2 will inherit syslog_ng. What I expect to happen is to have
syslog_ng up and running on foo-zone1 and foo-zone2 as well as in the
global zone. This wasn't happening, hence this bug.
Issue History
Date Modified Username Field Change
======================================================================
2009-03-14 16:34 automatthias New Issue
2009-03-24 13:09 ihsan Status new => assigned
2009-03-24 13:09 ihsan Assigned To => ihsan
2009-03-24 15:46 ihsan Note Added: 0005725
2009-03-24 15:46 ihsan Status assigned =>
acknowledged
2009-03-24 15:46 ihsan Project syslog_ng =>
cswclassutils
2009-03-24 22:02 bonivart Status acknowledged =>
assigned
2009-03-24 22:02 bonivart Assigned To ihsan => bonivart
2009-03-24 22:04 bonivart Note Added: 0005730
2009-04-21 19:03 bonivart Note Added: 0005995
2009-05-28 16:42 bonivart Note Added: 0006218
2009-05-28 16:43 bonivart Note Added: 0006219
2009-05-28 16:43 bonivart Status assigned => closed
2009-05-28 16:43 bonivart Resolution open => not fixable
2009-05-29 11:36 automatthias Note Added: 0006221
2009-05-29 11:36 automatthias Status closed => feedback
2009-05-29 11:36 automatthias Resolution not fixable => reopened
2009-05-29 13:38 bonivart Note Added: 0006223
2009-05-29 13:54 automatthias Note Added: 0006225
2009-05-29 14:09 bonivart Note Added: 0006226
2009-05-29 14:14 automatthias Note Added: 0006227
======================================================================
More information about the bug-notifications
mailing list