DLP manager 9.2 - rms heartbeat issue when I restarted the STINGRAY service

[mcote]

Hi guys, I recently installed the DLP manager 9.2 on a physical IBM server to make few tests before put this beast in the production network. The installation is successfully complet and everything is working properly.

So , I changed the network setting files and then just reboot as the normal procedure is required. At this state, my trouble is started.

After the first reboot, I verified the STINGRAY service status and it's stopped. I tried to restart but I'm always stuck under the second rms service.

The process stopped when the rms_heartbeat should be start.

Then the following error message appeared:

"Slave (sig_service) is not responding"

I checked my /etc/fstab and /etc/mstab config to be sure my slave HD is mounted properly and everything look fine.

So, I think that I have a issue with the RMS_HEARTBEAT starting process.

Thanks for your help.

Message was edited by: mcote on 22/12/11 8:12:04 CST AM

Message was edited by: mcote on 22/12/11 8:12:42 CST AM

[Firewall-Joe]

" I changed the network setting files" This is where you broke it.  You can't change the network setting on the box.  It has to be done through the NDLP GUI.

Restore the VM and try again.

Message was edited by: Firewall-Joe on 12/23/11 12:12:57 AM GMT-06:00

[mcote]

I don't think so because I changed 3 network setting files directly on the box.

/etc/resolv.conf

/etc/sysconfig/network

/etc/sysconfig/network-scripts/ifcfg-eth1

I don't know if you have another network setting that I don't know but, yes you can change every config with the CLI. It's a linux core.

Anyway, thanks.