SunMC 3.6 and Solaris 10 06/06
Greetings,
As I have to move my SunMC off one server (because IBM Netview cant run on the same system because it wants ports 162, 163 and 164) and put it on another, I thought hey, why not try Solaris 10 06/06. We are talking about a fresh installation on a new system.
I have a serious problem because half of the components (especially the agent, config something or other and the trap "receiver") related to SunMC core dump all the time. The Sun smf keeps starting them so my system is grinding itself to a halt. I have a call in with Sun on this but so far, no luck. It may have something to do with 06/06 being brand new. They told me there was a similiar call and it may be related to port 162 being used by something else.
Has anyone seen this before? I don't want to go back to Solaris 9 if I can help it.
Is there any chance that 3.6.1 is any better?
Stephen
# 1
What do you see when you run the following command:
/opt/SUNWsymon/util/bin/ctail -f /var/opt/SUNWsymon/log/agent.log
Look for whatever comes before the line containing "Channel already exists: syslog" - which is the agent starting. You can also look at the cfgserver.log and trap.log.
Message was edited by:
CraigWyllie-HalcyonInc.com
# 2
I had a look at the three logs and nothing interesting was before that Channel message. I totally gave up on using 3.6 on this host. The smf logs (from svcs -x) kept saying the processes were core dumping. Funny that there was no event in the messages file. I mucked about with coreadm trying to get a core dump. No luck. I set the specific variable to get a core dump because normally sunmc coredumps with a rlimit of zero (0) . No luck.
I downloaded 3.6.1 and installed that and it all runs well enough.I have to work out the SunFire platform privileges. I have exactly the same groups as my other system but it wont let me do anything on my 6800's.
Something odd was happening with 3.6 installation. Netstat -a never showed the ports 162, 163 and 164 in use. During the installation, it said that port 161 was in use. I know for a fact, it is not being used. I had turned off all processes that used those ports. We run a package that uses port 6161. 3.6.1 installation still complained about 161 but this time it started using the other ports.
I must admit that 3.6.1 looks very interesting. There are a number of things that I have to work out with it but well done to you guys.
Stephen
