That does make sense…I think :-) 

 

Could you send me (off list!) the entries file, a dump of the SA registry and 
tell me what entries are giving the problems (UID of them, at least of one of 
them) 

 

From: Servers Alive Discussion List [mailto:[email protected]] On Behalf Of 
[email protected]
Sent: Monday, March 14, 2011 3:02 PM
To: Servers Alive Discussion List
Subject: RE: [SA-list] Problem with new user management 

 

Sorry, don't know why I included the OID errors. Brainfreeze. 

Using a server which fails, I've done a test looking at the security event log 
of a server using "person" ID, and then again using "check" ID. The "check" ID 
appears in the security log as a successful login. The "person" ID doesn't 
appear there at all. Does that make sense? 

Ian 

_________________________________
Ian K Gray
OEL IS - European Infrastructure Support
Tel: +44 1236 502661
Mob: +44 7881 518854
Ad eundum quo nemo ante iit 



From:        "Dirk Bulinckx" <[email protected]> 
To:        Servers Alive Discussion List <[email protected]> 
Date:        14/03/2011 12:49 
Subject:        RE: [SA-list] Problem with new user management 
Sent by:        Servers Alive Discussion List <[email protected]> 
--------------------------------------------------------------------------------






The logging you show is mostly about MIB lookups (and this is due to the same 
installer issue that causes the groups.grp not to be "moved" to the new 
location). 
 
 
When you get the access denied, can you see on the (remote)system what user is 
being used for the login?   
 
From: Servers Alive Discussion List [mailto:[email protected] 
(mailto:[email protected])] On Behalf Of [email protected]
Sent: Monday, March 14, 2011 1:16 PM
To: Servers Alive Discussion List
Subject: [SA-list] Problem with new user management 
  
(Sorry I seem to be flooding the list today!) 

I've found a strange problem with the new user management stuff. It's working 
fine with most of the checks I've changed so far, but one (a perfmon memory 
check) only seems to work if I set the username within the check (as before). 
If I use the centrally set user (which is the same user for all checks like 
this), it gives me an access denied error. 

Here's the log extract - first time (fail) using the central person, second 
time (success) using user set in check: 

Monday, March 14, 2011 12:05:08 PM GBCN-AP03 Mem 
Monday, March 14, 2011 12:05:08 PM GBCN-AP03 Perfmon (Memory,% Committed Bytes 
In Use,) gave errorAccess is denied. 
( 5) 
Monday, March 14, 2011 12:05:08 PM PERFMON took 63 ms(571) 
Monday, March 14, 2011 12:05:20 PM ERR mibdb_OIDlookup: oidObject not found: 
.1.3.6.1.4.1.3530.5.9.21.0( 0) 
Monday, March 14, 2011 12:05:20 PM ERR mibdb_OIDlookup: oidObject not found: 
.1.3.6.1.4.1.3530.5.9.21( 0) 
Monday, March 14, 2011 12:05:27 PM ERR mibdb_OIDlookup: oidObject not found: 
.1.3.6.1.4.1.3530.5.9.21.0( 0) 
Monday, March 14, 2011 12:05:27 PM ERR mibdb_OIDlookup: oidObject not found: 
.1.3.6.1.4.1.3530.5.9.21( 0) 
Monday, March 14, 2011 12:05:27 PM ERR mibdb_OIDlookup: oidObject not found: 
.1.3.6.1.4.1.3530.5.9.21.0( 0) 
Monday, March 14, 2011 12:05:27 PM ERR mibdb_OIDlookup: oidObject not found: 
.1.3.6.1.4.1.3530.5.9.21( 0) 
Monday, March 14, 2011 12:05:28 PM ERR mibdb_OIDlookup: oidObject not found: 
.1.3.6.1.4.1.3530.5.9.21.0( 0) 
Monday, March 14, 2011 12:05:28 PM ERR mibdb_OIDlookup: oidObject not found: 
.1.3.6.1.4.1.3530.5.9.21( 0) 
Monday, March 14, 2011 12:05:28 PM ERR mibdb_OIDlookup: oidObject not found: 
.1.3.6.1.4.1.3530.5.9.21.0( 0) 
Monday, March 14, 2011 12:05:28 PM ERR mibdb_OIDlookup: oidObject not found: 
.1.3.6.1.4.1.3530.5.9.21( 0) 
Monday, March 14, 2011 12:05:30 PM ERR mibdb_OIDlookup: oidObject not found: 
.1.3.6.1.4.1.318.2.3.3.0( 0) 
Monday, March 14, 2011 12:05:30 PM ERR mibdb_OIDlookup: oidObject not found: 
.1.3.6.1.4.1.318.2.3.3( 0) 
Monday, March 14, 2011 12:05:30 PM ERR mibdb_OIDlookup: oidObject not found: 
.1.3.6.1.4.1.318.2.3.3.0( 0) 
Monday, March 14, 2011 12:05:30 PM ERR mibdb_OIDlookup: oidObject not found: 
.1.3.6.1.4.1.318.2.3.3( 0) 
Monday, March 14, 2011 12:05:30 PM ERR mibdb_OIDlookup: oidObject not found: 
.1.3.6.1.4.1.318.2.3.3.0( 0) 
Monday, March 14, 2011 12:05:30 PM ERR mibdb_OIDlookup: oidObject not found: 
.1.3.6.1.4.1.318.2.3.3( 0) 
Monday, March 14, 2011 12:05:32 PM GBCN-AP03 Mem 
Monday, March 14, 2011 12:05:33 PM GBCN-AP03 Perfmon (Memory,% Committed Bytes 
In Use,) gave  10.605035 
Monday, March 14, 2011 12:05:33 PM Perfmon (GBCN-AP03 Memory,% Committed Bytes 
In Use,) up 
Monday, March 14, 2011 12:05:33 PM PERFMON took 360 ms(571) 

Any ideas?? 

_________________________________
Ian K Gray
OEL IS - European Infrastructure Support
Tel: +44 1236 502661
Mob: +44 7881 518854
Ad eundum quo nemo ante iit 
______________________________________________________________________________


Any opinions expressed in this email are those of the individual and not 
necessarily of the Company. This email and any files transmitted with it, 
including replies and forwarded copies (which may contain alterations) 
subsequently transmitted from the Company are confidential and solely for the 
use of the intended recipient. It may contain material protected by legal 
privilege. If you are not the intended recipient or the person responsible for 
delivering to the intended recipient, be advised that you have received this 
email in error and that any use is strictly prohibited. Please notify the 
sender immediately of the error and delete any copies of this message

Warning: Although the Company has taken reasonable precautions to ensure that 
no viruses are present in this e-mail, the Company cannot accept responsibility 
for any loss or damage arising from the use of this e-mail or attachments.
______________________________________________________________________________
Oki Europe Limited. Registered Office:Blays House, Wick Road, Egham TW20 0HJ. 
Company No:2203086. VAT No:481 011975


To unsubscribe send a message with UNSUBSCRIBE in the subject line to 
[email protected]
If you use auto-responders (like out-of-the-office messages), make sure that 
they are not sent to the list nor to individual members. Doing so will cause 
you to be automatically removed from the list. 



To unsubscribe send a message with UNSUBSCRIBE in the subject line to 
[email protected]
If you use auto-responders (like out-of-the-office messages), make sure that 
they are not sent to the list nor to individual members. Doing so will cause 
you to be automatically removed from the list. 


______________________________________________________________________________


Any opinions expressed in this email are those of the individual and not 
necessarily of the Company. This email and any files transmitted with it, 
including replies and forwarded copies (which may contain alterations) 
subsequently transmitted from the Company are confidential and solely for the 
use of the intended recipient. It may contain material protected by legal 
privilege. If you are not the intended recipient or the person responsible for 
delivering to the intended recipient, be advised that you have received this 
email in error and that any use is strictly prohibited. Please notify the 
sender immediately of the error and delete any copies of this message

Warning: Although the Company has taken reasonable precautions to ensure that 
no viruses are present in this e-mail, the Company cannot accept responsibility 
for any loss or damage arising from the use of this e-mail or attachments.
______________________________________________________________________________
Oki Europe Limited. Registered Office:Blays House, Wick Road, Egham TW20 0HJ. 
Company No:2203086. VAT No:481 011975


To unsubscribe send a message with UNSUBSCRIBE in the subject line to 
[email protected]
If you use auto-responders (like out-of-the-office messages), make sure that 
they are not sent to the list nor to individual members. Doing so will cause 
you to be automatically removed from the list. 

To unsubscribe send a message with UNSUBSCRIBE in the subject line to 
[email protected]
If you use auto-responders (like out-of-the-office messages), make sure that 
they are not sent to the list nor to individual members. Doing so will cause 
you to be automatically removed from the list. 

Reply via email to