logrotate - hobbit
list Brian Lynch
For anyone using 'logrotate', the following file will rotate all the hobbit
logs.
Create the file as logrotate.cfg:
# Configuration file for logrotate application
#
# Add the following line to cron:
# 0 8 * * * /usr/sbin/logrotate [hobbit directory]/server/etc/logrotate.cfg
#
# Global options
compress
/var/log/hobbit/bbcombotest.log {
missingok
weekly
rotate 5
}
/var/log/hobbit/bb-display.log {
missingok
weekly
rotate 5
}
/var/log/hobbit/bb-retest.log {
missingok
weekly
rotate 5
}
/var/log/hobbit/enadis.log {
missingok
weekly
rotate 5
}
/var/log/hobbit/history.log {
missingok
weekly
rotate 5
}
/var/log/hobbit/hobbitd.log {
missingok
weekly
rotate 5
postrotate
/bin/kill -HUP `cat /var/log/hobbit/hobbitd.pid`
endscript
}
/var/log/hobbit/hobbitlaunch.log {
missingok
weekly
rotate 5
postrotate
/bin/kill -HUP `cat /var/log/hobbit/hobbitlaunch.pid`
endscript
}
/var/log/hobbit/larrd-data.log {
missingok
weekly
rotate 5
}
/var/log/hobbit/larrd-status.log {
missingok
weekly
rotate 5
}
/var/log/hobbit/page.log {
missingok
weekly
rotate 5
}
/var/log/hobbit/purple.log {
missingok
weekly
rotate 5
}
list Rich Smrcina
Great stuff Brian. Thanks for contributing.
▸
Brian Lynch wrote:For anyone using 'logrotate', the following file will rotate all the
hobbit logs.
Create the file as logrotate.cfg:
# Configuration file for logrotate application
#
# Add the following line to cron:
# 0 8 * * * /usr/sbin/logrotate [hobbit directory]/server/etc/logrotate.cfg
#
# Global options
compress
/var/log/hobbit/bbcombotest.log {
missingok
weekly
rotate 5
}
/var/log/hobbit/bb-display.log {
missingok
weekly
rotate 5
}
/var/log/hobbit/bb-retest.log {
missingok
weekly
rotate 5
}
/var/log/hobbit/enadis.log {
missingok
weekly
rotate 5
}
/var/log/hobbit/history.log {
missingok
weekly
rotate 5
}
/var/log/hobbit/hobbitd.log {
missingok
weekly
rotate 5
postrotate
/bin/kill -HUP `cat /var/log/hobbit/hobbitd.pid`
endscript
}
/var/log/hobbit/hobbitlaunch.log {
missingok
weekly
rotate 5
postrotate
/bin/kill -HUP `cat /var/log/hobbit/hobbitlaunch.pid`
endscript
}
/var/log/hobbit/larrd-data.log {
missingok
weekly
rotate 5
}
/var/log/hobbit/larrd-status.log {
missingok
weekly
rotate 5
}
/var/log/hobbit/page.log {
missingok
weekly
rotate 5
}
/var/log/hobbit/purple.log {
missingok
weekly
rotate 5
}
--
Rich Smrcina VM Assist, Inc. Main: (262)392-2026 Cell: (XXX)XXX-XXXX Ans Service: (360)715-2467 user-61add9955ef9@xymon.invalid Catch the WAVV! http://www.wavv.org WAVV 2005 - Colorado Springs - May 20-24, 2005
list Gary Baluha
I ran across the following thread when looking up some info on setting up logrotate (linux) for Hobbit. I'm curious, though... The man page for hobbitd says that SIGHUP will cause hobbitd to "Re-read the bb-hosts configuration file." Does that mean the example below with the postrotate command will actually work as intended, or will it only have hobbitd re-read the config file? Re: [hobbit] logrotate - hobbit - *To*: user-ae9b8668bcde@xymon.invalid - *Subject*: Re: [hobbit] logrotate - hobbit - *From*: Rich Smrcina <user-cf452ff334e0@xymon.invalid> - *Date*: Mon, 23 May 2005 00:26:00 -0500 - *References*: <user-c21512171268@xymon.invalid<http://www.hswn.dk/hobbiton/2005/05/msg00283.html>;
- *User-agent*: Mozilla Thunderbird 1.0.2 (X11/20050317)
▸
Great stuff Brian. Thanks for contributing. Brian Lynch wrote: For anyone using 'logrotate', the following file will rotate all the hobbit logs. Create the file as logrotate.cfg: # Configuration file for logrotate application # # Add the following line to cron: # 0 8 * * * /usr/sbin/logrotate [hobbit directory]/server/etc/logrotate.cfg # # Global options compress /var/log/hobbit/bbcombotest.log { missingok weekly rotate 5 } /var/log/hobbit/bb-display.log { missingok weekly rotate 5 } /var/log/hobbit/bb-retest.log { missingok weekly rotate 5 } /var/log/hobbit/enadis.log { missingok weekly rotate 5 } /var/log/hobbit/history.log { missingok weekly rotate 5 } /var/log/hobbit/hobbitd.log { missingok weekly rotate 5 postrotate /bin/kill -HUP `cat /var/log/hobbit/hobbitd.pid` endscript } /var/log/hobbit/hobbitlaunch.log { missingok weekly rotate 5 postrotate /bin/kill -HUP `cat /var/log/hobbit/hobbitlaunch.pid` endscript } /var/log/hobbit/larrd-data.log { missingok weekly rotate 5 } /var/log/hobbit/larrd-status.log { missingok weekly rotate 5 } /var/log/hobbit/page.log { missingok weekly rotate 5 } /var/log/hobbit/purple.log { missingok weekly rotate 5 } -- Rich Smrcina VM Assist, Inc. Main: (262)392-2026 Cell: (XXX)XXX-XXXX Ans Service: (360)715-2467 user-61add9955ef9@xymon.invalid Catch the WAVV! http://www.wavv.org WAVV 2005 - Colorado Springs - May 20-24, 2005
list Henrik Størner
▸
On Wed, Oct 25, 2006 at 01:32:19PM -0400, Gary Baluha wrote:
I'm curious, though... The man page for hobbitd says that SIGHUP will cause hobbitd to "Re-read the bb-hosts configuration file." Does that mean the example below with the postrotate command will actually work as intended, or will it only have hobbitd re-read the config file?
It does in fact work. SIGHUP triggers both a configfile reload, and a re-opening of the logfiles. Regards, Henrik
list T.J. Yang
Hobbit has very good feature that hobbit server accepting message existing bb client. But is it possible to code hobbit client to have a mode to compatible with existing BB server ? Tear down an existing BB server is not as easy as it seems. Regards T.J. Yang All-in-one security and maintenance for your PC. Get a free 90-day trial! http://clk.atdmt.com/MSN/go/msnnkwlo0050000002msn/direct/01/?href=http://www.windowsonecare.com/?sc_cid=msn_hotmail
list Gary Baluha
I feel your pain, as we too are migrating our BB server (actually, servers) into a single Hobbit server. To add to the complexity, the hobbit server is on an entirely different subnet (and thus IP) as the BB server, so ACL changes need to be made as well. However, considering the many additional features Hobbit has that BB doesn't, I think in the end it actually makes it easier to manually convert everything to the Hobbit server syntax. It also forces you to look in to some of the additional features in Hobbit. However, if you aren't so concerned about using the additional features (except for the trend graphing), the only thing that should be required to get it working in "compatibility" mode is just add the hosts on the server to the bb-hosts file, and repoint the BB clients to the new Hobbit server (and hope ACL changes aren't also required). What specifically is slowing you down in your migration?
▸
On 10/25/06, T.J. Yang <user-8e841282cda5@xymon.invalid> wrote:Hobbit has very good feature that hobbit server accepting message existing bb client. But is it possible to code hobbit client to have a mode to compatible with existing BB server ? Tear down an existing BB server is not as easy as it seems. Regards T.J. Yang All-in-one security and maintenance for your PC. Get a free 90-day trial! http://clk.atdmt.com/MSN/go/msnnkwlo0050000002msn/direct/01/?href=http://www.windowsonecare.com/?sc_cid=msn_hotmail
list T.J. Yang
From: "Gary Baluha" <user-ae3e15c22de1@xymon.invalid> Reply-To: user-ae9b8668bcde@xymon.invalid To: user-ae9b8668bcde@xymon.invalid Subject: Re: [hobbit] Hobbit client feature request: bb client compatible mode Date: Wed, 25 Oct 2006 16:32:44 -0400
▸
I feel your pain, as we too are migrating our BB server (actually, servers)
into a single Hobbit server. To add to the complexity, the hobbit server
is
on an entirely different subnet (and thus IP) as the BB server, so ACL
changes need to be made as well.
However, considering the many additional features Hobbit has that BB
doesn't, I think in the end it actually makes it easier to manually convert
everything to the Hobbit server syntax. It also forces you to look in to
some of the additional features in Hobbit. However, if you aren't so
concerned about using the additional features (except for the trend
graphing), the only thing that should be required to get it working in
"compatibility" mode is just add the hosts on the server to the bb-hosts
file, and repoint the BB clients to the new Hobbit server (and hope ACL
changes aren't also required).
What specifically is slowing you down in your migration?
Two benefits for this request.
1. replace per-seat license bb client with hobbit client to save
administration overhead(ie, counting number of bb clients and paying the
license).
2. Avoid the rrd and logfile migration from bb to hobbit.
one can have both bb and hobbit server up and receiving bb messages.
once new hobbit server
contain one year data/logs then bb server can be turn off.
tj
▸
On 10/25/06, T.J. Yang <user-8e841282cda5@xymon.invalid> wrote:Hobbit has very good feature that hobbit server accepting message existing bb client. But is it possible to code hobbit client to have a mode to compatible with existing BB server ? Tear down an existing BB server is not as easy as it seems. Regards T.J. Yang All-in-one security and maintenance for your PC. Get a free 90-day trial! http://clk.atdmt.com/MSN/go/msnnkwlo0050000002msn/direct/01/?href=http://www.windowsonecare.com/?sc_cid=msn_hotmail
Add a Yahoo! contact to Windows Live Messenger for a chance to win a free trip! http://www.imagine-windowslive.com/minisites/yahoo/default.aspx?locale=en-us&hmtagline
list Henrik Størner
▸
On Wed, Oct 25, 2006 at 03:22:47PM -0500, T.J. Yang wrote:
Hobbit has very good feature that hobbit server accepting message existing bb client. But is it possible to code hobbit client to have a mode to compatible with existing BB server ?
No.
Tear down an existing BB server is not as easy as it seems.
I don't buy that. Converting a BB server to Hobbit requires you to do two (maybe three) things: * Move the RRD files around; there's a script included with Hobbit which takes care of that. Takes a few minutes at most. * Convert your alert configuration from BB to Hobbit. Even for a moderately complex alert setup, I would guess you could do it in a day or two (can be done in advance). * Server-side scripts may need a bit of tweaking, but for the most part they should work if you enable the compatibility module to save status logs and disable-files. The logfiles are compatible between BB and Hobbit. The bb-hosts file is backward compatible so you can copy it from BB to Hobbit (not the other way around). The client configuration is different, but that doesn't matter when we're discussing the server migration. So I disagree with your premise that migrating a server from BB to Hobbit is difficult. It is a lot more difficult to make the Hobbit clients compatible with a BB server. E.g. there is no way you can get a BB server to push the configuration to a Hobbit client without re-implementing parts of the Hobbit server in the BB network daemon. Regards, Henrik
list Buchan Milne
▸
On Wednesday 25 October 2006 22:32, Gary Baluha wrote:
I feel your pain, as we too are migrating our BB server (actually, servers) into a single Hobbit server. To add to the complexity, the hobbit server is on an entirely different subnet (and thus IP) as the BB server, so ACL changes need to be made as well.
But, you could set your BB server up to run a proxy (on the default port) which proxies to your Hobbit server, as well as the real BB server. Or, if you are running the 4.2 clients, you could use the msgcache feature, so Hobbit polls the clients for their data. If the issue is the network tests, the proxy solution should work, until you need to remove the server (but, that you would have to do regardless of software). Regards, Buchan -- Buchan Milne ISP Systems Specialist - Monitoring/Authentication Team Leader B.Eng,RHCE(803004789010797),LPIC-2(LPI000074592)
list Gary Baluha
▸
On 10/26/06, Buchan Milne <user-9b139aff4dec@xymon.invalid> wrote:
On Wednesday 25 October 2006 22:32, Gary Baluha wrote:I feel your pain, as we too are migrating our BB server (actually, servers) into a single Hobbit server. To add to the complexity, the hobbit server is on an entirely different subnet (and thus IP) as the BB server, soACLchanges need to be made as well.But, you could set your BB server up to run a proxy (on the default port) which proxies to your Hobbit server, as well as the real BB server.
The problem is, we have 3 different BB servers for several different
networks, including those that aren't allowed to communicate between each
other, for security purposes. What you describe is certainly a good idea,
but for our purposes, I'm finding it easier to move the hosts individually
to Hobbit. However, if we get down to only a few hosts left on the BB
servers, we may do just that finish the migration, and deal with the ACLs at
a more convenient time.
▸
Or, if you are running the 4.2 clients, you could use the msgcache feature,so Hobbit polls the clients for their data.
We have very restrictive network ACLs, so even that method will require some
ACL changes.
▸
If the issue is the network tests, the proxy solution should work, until youneed to remove the server (but, that you would have to do regardless of software).
Yeah, we also have several network tests, such as connection, smtp, dns,
ftp, etc.
Regards,Buchan