[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bbproxy with multiple targets in beta package patches
- To: hobbit (at) hswn.dk
- Subject: bbproxy with multiple targets in beta package patches
- From: Buchan Milne <bgmilne (at) staff.telkomsa.net>
- Date: Fri, 14 Jul 2006 17:29:46 +0200
- Organization: Telkom Internet
- User-agent: KMail/1.9.1
I was running a Hobbit server on the beta package with the allinone patch July
04 2006. However, we now want the hosts being monitored by this ("old")
Hobbit server accessible from our other ("new") Hobbit server (running
4.1.2p1). We can tolerate differences in log file/port/proc features for a
while until we upgrade the "new" server.
So, as when migrating from BB to Hobbit, I set hobbitd to listed on port 1985
on the "old" server, set up bbproxy to forward to localhost:1985 and
the "new" Hobbit server, and transferred the relevant data.
However, now the "old" server is not getting data from clients, but the "new"
one is, eg cpu, disk, files, memory, msgs, ports, procs are purple on
the "old" server but green on the "new" sever (and collecting in the RRDs).
The bbproxy section on the "old" server has:
[bbproxy]
#DISABLED
ENVFILE /usr/lib/hobbit/server/etc/hobbitserver.cfg
CMD
$BBHOME/bin/bbproxy --hobbitd --bbdisplay=127.0.0.1:1985,10.10.9.32:1984 --report=$MACHINE.bbproxy --pidfile=$BBSERVERLOGS/bbproxy.pid
LOGFILE $BBSERVERLOGS/bbproxy.log
Any ideas, or is this a potential, or known, bug in 4.2 ? (I'm building the rc
as I type ... but would appreciate any ideas).
Regards,
Buchan
--
Buchan Milne
ISP Systems Specialist
B.Eng,RHCE(803004789010797),LPIC-2(LPI000074592)