X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8846B.15A5FFE8@onstor-exch02.onstor.net>; Wed, 12 Mar 2008 11:01:23 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Defect  TED00021741 [Cougar] user with CLUSTER,SECURITY in clustesr priveleges cannot find or view elog messages
Date: Wed, 12 Mar 2008 11:01:23 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E08D2A55A@onstor-exch02.onstor.net>
In-Reply-To: <20080311164220.32f4c2ff@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Defect  TED00021741 [Cougar] user with CLUSTER,SECURITY in clustesr priveleges cannot find or view elog messages
Thread-Index: AciD0YzGjOTEfdTpQl6CbymmShAlmQAkfFIg
References: <BB375AF679D4A34E9CA8DFA650E2B04E08D2A078@onstor-exch02.onstor.net><20080311155245.24cc6fab@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E08D2A105@onstor-exch02.onstor.net> <20080311164220.32f4c2ff@ripper.onstor.net>
From: "Kumar Vakacharla (HCL)" <kumarv@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

Andy,=20

	Yes, your approach is fine but I don't understand the need of
creating a separate file for that purpose. Instead we can directly
define the macro in /etc/cron.weekly/sysklogd itself. Please clarify??
(we need to incorporate similar change in /etc/cron.daily/sysklogd as
well)

I also found that command "logrotate /etc/logrotate.conf" is failing
because of a syntax error in /etc/logrotate.d/onstor and
/etc/logrotate.d/exim4-base files. We have used "K" instead of small
letter "k" while specifying the size.=20

Are we supposed to rotate elog messages weekly ?? Since I have seen it
configured that manner in conf file /etc/logrotate.d/onstor .

/var/log/onstor/messages {
        size 60K <-------------------------  should be small letter "k"
        rotate 5
        weekly  <------------------------------
        compress
        delaycompress
        create 644 root root
        sharedscripts
        postrotate
                /usr/bin/killall -HUP syslogd
                /onstor/bin/emrscron -s elog0 &
        endscript
}

I am planning to remove "weekly" property it as log may go very big.

Finally, I am unable to find the conf files "etc/cron.weekly/sysklogd",
"etc/cron.daily/sysklogd" and "/etc/logrotate.d/exim4-base" in the
branch. Will these files be generated during the build?? If so we need
to change upgrade script to handle this..Is it right??


Thanks,
Kumar.




-----Original Message-----
From: Andy Sharp=20
Sent: Tuesday, March 11, 2008 4:42 PM
To: Kumar Vakacharla (HCL)
Subject: Re: Defect TED00021741 [Cougar] user with CLUSTER,SECURITY in
clustesr priveleges cannot find or view elog messages

OK, I'll assign 22673 to you as well.  Go ahead and send the changes
you make to me for review as I am interested in this.

Here is a change I was thinking about for the savelog v. logrotate
problem, but I'm not sure it's the only way or even the best way.  I
don't know where /etc/syslog.conf currently comes from, but it's a sure
bet we will have to modify it to fix 22673.

I have not coded it or tried to test it.


Add a file /etc/default/sysklogd-listfiles to the release.  that would
be <branch>/linux/rootfs/etc/default/sysklogd-listfiles
The file should contain the line

SYSKLOGD_LIST_EXCLUDE_FILES=3D/var/log/onstor


Then,

Change line 29 of file /etc/cron.weekly/sysklogd from

for LOG in `syslogd-listfiles --weekly`

to=20

for LOG in `syslogd-listfiles $DONT_LIST --weekly`


Then add code after the three test lines at the beginning similar to
this:

if [ -r /etc/default/sysklogd-listfiles ] ; then
	. /etc/default/sysklogd-listfiles
fi

DONT_LIST=3D
if [ "$SYSKLOGD_LIST_EXCLUDE_FILES" ] ; then
	DONT_LIST=3D"-s $SYSKLOGD_LIST_EXCLUDE_FILES"
fi



On Tue, 11 Mar 2008 16:03:50 -0700 "Kumar Vakacharla (HCL)"
<kumarv@onstor.com> wrote:

> Andy,=20
>=20
> 	Not a problem you can assign me other log related bugs also
> as I am working on this.=20
>=20
> I might need your inputs if at all I am struck at some point of time.=20
>=20
> Thanks,
> Kumar.
>=20
> -----Original Message-----
> From: Andy Sharp=20
> Sent: Tuesday, March 11, 2008 3:53 PM
> To: Kumar Vakacharla (HCL)
> Subject: Re: Defect TED00021741 [Cougar] user with CLUSTER,SECURITY in
> clustesr priveleges cannot find or view elog messages
>=20
> Kumar,
>=20
> Are you working on this?  I can throw it in with all the other logging
> related bugs I'm working on if you haven't gotten too far.  Or, I can
> throw those bugs over to you ~:^)  There is at least another bug which
> is related in that it probably will require some fine tuning of
> syslog.conf. (TED00022673 - /var full on g5r204. log files are
> taking all the space.)
>=20
> Let me know.
>=20
> On Tue, 11 Mar 2008 14:52:43 -0700 "Kumar Vakacharla (HCL)"
> <kumarv@onstor.com> wrote:
>=20
> > Andy,=20
> >=20
> > =20
> >=20
> >       This problem is related to permissions of the elog messages
> > file.=20
> >=20
> >       In cougar, "/var/log/onstor/messages" files are being created
> > with permission 0x640 and as a result any users who logged into to
> > the system with their local useraccount are ending up with the error
> > "Permission Denied" when they try to execute "elog show " or "elog
> > find" command.
> >=20
> > Only root login can execute these commands.=20
> >=20
> > =20
> >=20
> > I have found that this is happening because of the savelog program
> > which is responsible for rotating files.=20
> >=20
> > =20
> >=20
> > File: /etc/cron.daily/sysklogd
> >=20
> > =20
> >=20
> >   savelog -g adm -m 640 -u root -c 7 $LOG >/dev/null
> >=20
> > =20
> >=20
> > So the savelog program is creating new files with 0x640 permissions.
> >=20
> > =20
> >=20
> > =20
> >=20
> > I think this problem should not be present now because you have
> > changed log rotation mechanism in linux so that it uses logrotate.
> > (change list :28107)
> >=20
> > But in the latest submittals still I see that these files are
> > getting created with 0x640 even though conf file says files should
> > be created with=20
> >=20
> > 0x644.=20
> >=20
> > =20
> >=20
> > File: /etc/logrotate.d/onstor
> >=20
> > =20
> >=20
> > /var/log/onstor/messages {
> >=20
> >     size 60K
> >=20
> >     rotate 5
> >=20
> >     weekly
> >=20
> >     compress
> >=20
> >     delaycompress
> >=20
> >     create 644 root root <--------------=20
> >=20
> >     sharedscripts
> >=20
> >     postrotate
> >=20
> >         /usr/bin/killall -HUP syslogd
> >=20
> >         /onstor/bin/emrscron -s elog0 &
> >=20
> >     endscript
> >=20
> > }
> >=20
> > =20
> >=20
> > Please clarify me whether you have changed log rotation mechanism in
> > cougar to use logrotate instead of default syslogd rotation  so
> > that I can proceed further.
> >=20
> > =20
> >=20
> > Please correct me if I am wrong.=20
> >=20
> > =20
> >=20
> > Thanks,
> >=20
> > Kumar.
> >=20
> > =20
> >=20
> > =20
> >=20
> > -----Original Message-----
> > From: tim.gardner@onstor.com [mailto:tim.gardner@onstor.com]=20
> > Sent: Tuesday, March 11, 2008 12:17 AM
> > To: Kumar Vakacharla (HCL); May Ma
> > Cc: Sandrine Boulanger; Vikas Saini
> > Subject: Defect TED00021741 [Cougar] user with CLUSTER,SECURITY in
> > clustesr priveleges cannot find or view elog messages
> >=20
> > =20
> >=20
> > id: TED00021741
> >=20
> > Headline: [Cougar] user with CLUSTER,SECURITY in clustesr priveleges
> > cannot find or view elog messages
> >=20
> > State: Assigned
> >=20
> > Submitter: maym
> >=20
> > Severity: 2-Major
> >=20
> > Note_Entry:=20
> >=20
> > Area_of_problem: SW-Privileges
> >=20
> > Release_Project: Cougar
> >=20
> > =20
> >=20
> > =20
> >=20
