Thanks.

 

Yep - I disabled SELinux during the OS install though I will mention
that FC6 has a nice little config tool for SELinux now that might
actually make me consider using it for something with less time
pressure.

 

I had worked it out before you wrote.   The main problem I found is that
for whatever reasons FC5 and  FC6 (and maybe FC4 - I haven't looked at
that yet) don't install xinetd by default!   When I did the client
software install NBU apparently checked for xinetd and not finding it
assumed it was running inetd (it wasn't) so just created an inetd.conf
with what it wanted.   (To me that sounds a little brain dead but
considering the answer to my second question who am I to talk? :-( )

 

Anyway based on the realization it didn't have xinetd I did the
following to get it going:

 

Doing "yum install xinetd" got me the correct xinetd stuff binary.

 

Running "/etc/init.d/xinetd start" got it running.

 

Reinstalled the NBU client and it created the appropriate files under
/etc/xinetd.d

 

Started a test backup which was sitting at "connecting" until it dawned
on me I hadn't updated iptables (firewall) for NBU.   I ran
/etc/init.d/iptables stop to turn off iptables since it's an internal
box.   I'll probably go ahead and do firewall setup for it later since
I'd already worked that out for some external boxes running earlier
versions of RedHat but for now it's running the backup so I'll leave it
alone.   

 

By the way for anyone reading it in the archives - if you decide not to
use iptables and Veritas firewall setup make sure you use chkconfig to
disable the automatic start of iptables on reboots.

 

________________________________

From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Cornely,
David
Sent: Wednesday, February 21, 2007 6:07 PM
To: veritas-bu at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Redhat or Fedora 2.6 kernel NB 5.1?

 

This is what I've done to get it working on Fedora (I forget the exact
kernel version).  Don't know if this will work for you but it's here if
you want to try.

 

1) Turned off SELinux because it was preventing some shared library
activity required by bpcd.  You have the option of running Security
Enhanced Linux on Fedora but it's very paranoid and makes it hard to do
a lot of things.  So, we turned it off.  Here's how:
-Edit the /etc/selinux/config file and set the SELINUX variable to
"disabled"
-Rebooted the server (required to have this change take effect)

2) Ran the iptables commands to allow NBU servers access but I used the
IP address of the master/media server instead of the hostname.

3) Then ran this to save the new iptables rules:
# /sbin/service iptables save

4) Restarted xinetd
/etc/init.d/xinetd restart

Then we could access the client via NBU.

 

________________________________

From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Jeff
Lightner
Sent: Wednesday, February 21, 2007 14:15
To: veritas-bu at mailman.eng.auburn.edu
Subject: [Veritas-bu] Redhat or Fedora 2.6 kernel NB 5.1?

 

Before anyone says it - I know none of the 2.6 kernels for RH/FC are in
the compatibility matrix.

My question is despite the above has anyone got it successfully working
on either Redhat or Fedora Core version 4 or higher with the 2.6 kernel?

If so would you be willing to share how you got it going or at least the
xinetd changes you made for it?

It seems I saw a thread about this some time ago but I can't find it in
the archives.

By the way - is there a way to search the archives for keywords?   The
page I went to just gives me the archives by month so I have to open
each one and even then I can only search on the thread titles.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20070221/3b7bb689/attachment.htm