1834290 Members
3062 Online
110066 Solutions
New Discussion

rc3 related problem

 
Seshan
Advisor

rc3 related problem

I hav a HP9000 A class with 11.11OS version. this has Oracle and Weblogic running on it as well SeeBeyond.. I am new to this site and we had a problem that tnslistener was not coming up. On rebooting the server, n/w services did not come up, SAM said that there was no NIC in the system. HP engineer in the site found that rc2 and rc3 scripts were found in the wrong / opposite dirs. starting of init.net, etc had to be done one by one and so on.. i went through the earlier records forthis machine and found that the same thing had happend in the last call report from HP and that too was during a reboot, saying NIC was not recognised. Why does this happen? How can you check which scripts are to be in rc3 and those in rc2? Can the NIC go undetected?

Rgds/Seshan
5 REPLIES 5
harry d brown jr
Honored Contributor

Re: rc3 related problem

I'm not sure "how" it happened, but I have attached a sample of my rc's

live free or die
harry
Live Free or Die
Seshan
Advisor

Re: rc3 related problem

thanks harry

but the beauty is this problem has happened beofre.. ANy idea how to check the memory utilisation currently on the system? I did get a c script, but what is the c compiler
command in HP UX? cc does not seem to work...
Rgds/Seshan
Tapas Jha
Valued Contributor

Re: rc3 related problem

Hi,

Check for /etc/inittab file. By default what is the run level.

Check for existance of /sbin/init.d/* files.
Check for /etc/rc.config file, /etc/rc.config.d/netconf file(Here IP Addr. Netmask ... are defined.
Check for /sbin/rc?.d/* files. Here you will find that files are linked to /sbin/init.d/ files. You will find S and K in the prefix which means Start and Kill script.

Rgds
Tapas
Tapas Jha
Patrick Wallek
Honored Contributor

Re: rc3 related problem

The /sbin/init.d/rc?.d scripts (actually links) are not going to just move from one directory to another on their own.

Someone or some job somewhere HAS to be doing it. If you have multiple people with the root password, change it NOW and only give it to the people that really need it.

You could also try going through your cron jobs and see if there are any strange jobs there.

I would also be VERY tempted to turn on auditing (the system has to be trusted) and monitor the /sbin/init.d/rc?.d directories to see who/what is changing them if this happens again.
Seshan
Advisor

Re: rc3 related problem

Thanks guys, it is true that a few users hav access to root equivalent rights, but how can that leave the NIC to be undetected? that 2 twice? i shall check cron as you hav advised.. i believe the killer could be users related to an app called Seebeyond... an idea on this application?

RGds/Seshan