Insufficient security privilge to add a row - SunMC 3.5.1
Hi All,
I've a strange behaviour with my SunMC server.
Yesterday, I've made a fresh install and push a common config on some agents (+/-40) without any problem of security.
Today, I've tried to add a new process row to monitor but I received back an error like "Insufficient security privilege to add a row" on all my agents. I did nothing since yesterday. I've checked if my user was in the esadm group, it is.
Do anyone have an idea ?
Thanks in advance !
Quentin.
[513 byte] By [
qsavary] at [2007-11-26 7:41:33]
# 1
Hi Quentin,
> Today, I've tried to add a new process row to monitor
> but I received back an error like "Insufficient
> security privilege to add a row" on all my agents. I
> did nothing since yesterday. I've checked if my user
> was in the esadm group, it is.
-are you using the same user that you used yesterday to load the modules on all 40 Agents?
-are all 40 Agents reporting the security error, or just one/some of them
-was the "fresh install" just a fresh install of your SunMC Server, or the Agents as well?
-have you tried to add the row manually? Or have you only tried with a Task/Managed-Jobs?
Regards,
Mike.Kirk@HalcyonInc.com
http://www.HalcyonInc.com
# 2
I've found a workaround just now.
I've relaunched on all my agents the command /opt/SUNWsymon/sbin/configure -r, to force the change of the seed password.
Now it's working correctly but I'll keep an eye on it as I don't see where I've made a change.
For your questions :
-are you using the same user that you used yesterday to load the modules on all 40 Agents?
YES
-are all 40 Agents reporting the security error, or just one/some of them
YES ALL
-was the "fresh install" just a fresh install of your SunMC Server, or the Agents as well?
Only the server but it was working for hours because i've reloaded the metrics on agents without any problems.
-have you tried to add the row manually? Or have you only tried with a Task/Managed-Jobs?
Both with the same results.
I've add the patch 118389-09 which apparently didn't correct anything but at least removed some doubts.
Many thanks,
Quentin.
