cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devdeep Singh" <devdeep.si...@citrix.com>
Subject Re: Review Request 12994: CLOUDSTACK-3216 Logs in the Software router are not being rotated
Date Mon, 29 Jul 2013 13:26:11 GMT

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/12994/#review24116
-----------------------------------------------------------

Ship it!


Committed to 4.2 and master. Kindly close the request.

- Devdeep Singh


On July 27, 2013, 1:09 p.m., Rajesh Battala wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12994/
> -----------------------------------------------------------
> 
> (Updated July 27, 2013, 1:09 p.m.)
> 
> 
> Review request for cloudstack, Alex Huang, Devdeep Singh, Ram Ganesh, and Hugo Trippaers.
> 
> 
> Bugs: 3216
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> -------
> 
> Issue:
> ==========
> logrotate.conf and logrotate config files in logrotate.d folder are having "x" permission.

> hence logrotate daemon not able to use this config 
> logrotate reports the error as 
> /etc# /usr/sbin/logrotate -d -v /etc/logrotate.conf
> reading config file /etc/logrotate.conf
> including /etc/logrotate.d
> Ignoring apache2 because of bad file mode.
> reading config file apt
> reading config file aptitude
> reading config file conntrackd
> Ignoring dnsmasq because of bad file mode.
> reading config file dpkg
> Ignoring haproxy because of bad file mode.
> reading config file monit
> Ignoring ppp because of bad file mode.
> Ignoring rsyslog because of bad file mode.
> ==========================
> 
> Fix:
> ===
> while generating the cloudscripts.tgz file, I had modified to include the logrotate.conf
and logrotate config files under logrotate.d with 644 permission which will fix the issue.

> this is will fix the "bad file mode" error. 
> 
> 
> Diffs
> -----
> 
>   patches/pom.xml 00eec02 
> 
> Diff: https://reviews.apache.org/r/12994/diff/
> 
> 
> Testing
> -------
> 
> 1. after generating new systemvm.iso tested the new router/ssvm/console proxy.
> 
> logrotate -d -v /etc/logrotate.conf
> reading config file /etc/logrotate.conf
> including /etc/logrotate.d
> reading config file apache2
> reading config file apt
> reading config file aptitude
> reading config file conntrackd
> reading config file dnsmasq
> reading config file dpkg
> reading config file haproxy
> reading config file monit
> reading config file ppp
> reading config file rsyslog
> 
> 
> 2. Verified after launching the VR, new instances are getting IP and hostname properly.
> 
> 
> Thanks,
> 
> Rajesh Battala
> 
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message