axis2c.log is full of spurious (and full of typos) errors

[Thierry Carrez]

Every 5 seconds, the following error is logged to /var/log/eucalyptus/axis2c.log 16 times:

[Tue Oct 20 09:53:30 2009] [error] error.c(94) OXS ERROR [x509.c:287 in openssl_x509_get_subject_key_identifier] oxs defualt error , The extenension index of NID_subject_key_identifier is not valid

This is both noisy and distracting, since Eucalyptus seems to work alright.

[Thierry Carrez (ttx)]

It's possible to set Axis2LogLevel to "critical" instead of "error" but that doesn't sound like a good idea. Fixing the root cause of the spurious error would be a better way to fix this.

[Dustin Kirkland  (kirkland)]

Moving this over to axis2c, as this isn't something Dan says can be solved in Eucalyptus itself.

[Thierry Carrez (ttx)]

This is actually a

[Thierry Carrez (ttx)]

... a rampart issue.

[Thierry Carrez (ttx)]

It's possible to suppress that specific error message by patching it out in
./src/omxmlsec/openssl/x509.c:

oxs_error(env, OXS_ERROR_LOCATION, OXS_ERROR_DEFAULT,
                  "The extenension index of NID_subject_key_identifier is not valid");

However I suspect this is a valid error so I'd rather fix the underlying reason. It's difficult to check with rampart upstream since their source code repository at https://svn.apache.org/repos/asf/webservices/rampart/trunk/c is now dead.

Some more explanation of why Eucalyptus's use of rampart triggers that error message could be handy.