UEC/Eucalyptus installation test: 20090927.1

[Thierry Carrez]

Thierry Carrez wrote:
> Looking back at the cluster controller there is an issue which may be
> related to registration:
> 
> Repeated in httpd-cc_error_log:
> [Mon Sep 28 10:08:53 2009] [notice] child pid 4416 exit signal
> Segmentation fault (11)
> 
> Once, in /var/log/eucalyptus/axis2c.log:
> [Mon Sep 28 10:06:20 2009] [error] http_transport_utils.c(2557) Service
> or operation not found
> 
> I'm investigating that.

This is apparently triggered by the upstart-ification of the
eucalyptus-cc initscript. If you save a copy of
/etc/init.d/eucalyptus-cc before upgrading to the autoregister branch,
you can use that script to start eucalyptus-cc without triggering those
errors.

Looking at the upstart job, it seems to start apache2 with the same
configuration... I tried to push up apache and axis2 loglevels to get
more information, without so much success.
/var/log/eucalyptus/axis2c.log show in the case of upstart:

[debug] apache2_worker.c(238) http://localhost:8774/axis2/services/
[debug] apache2_worker.c(280) Client HTTP version HTTP/1.0
[debug] rest_disp.c(114) Checking for service using target endpoint
address : http://localhost:8774/axis2/services/
[error] http_transport_utils.c(2557) Service or operation not found

while in the case of the init.d script they never query services at
http://localhost:8774/axis2/services/ (always services/EucalyptusGL or
services/EucalyptusCC), and this error is not triggered.

The http_transport_utils.c error appears only once in the logs, while
the apache child segfault appears every 8 seconds or so.

-- 
Thierry Carrez
Technical lead, Ubuntu server team || Canonical Ltd.