retitle 604231 chef-solr: installation fails, unable to connect to node, nodedown thanks
Hi there!
On Sun, 21 Nov 2010 11:14:05 +0100, Lucas Nussbaum wrote:
> While testing the installation of all packages in unstable, I ran
> into the following problem:
>
> Setting up chef-solr (0.8.16-4.1) ...
> Error: unable to connect to node 'rab...@parapluie-8': nodedown
> diagnostics:
> - nodes and their ports on parapluie-8: [{rabbitmqctl24301,59110}]
> - current node: 'rabbitmqctl24...@parapluie-8'
> - current node home dir: /var/lib/rabbitmq
> - current node cookie hash: fJiJth+YsTHJfj5ZQWvUSQ==
> Creating vhost "/chef" ...
> Error: unable to connect to node 'rab...@parapluie-8': nodedown
> diagnostics:
> - nodes and their ports on parapluie-8: [{rabbitmqctl24349,46122}]
> - current node: 'rabbitmqctl24...@parapluie-8'
> - current node home dir: /var/lib/rabbitmq
> - current node cookie hash: fJiJth+YsTHJfj5ZQWvUSQ==
> dpkg: error processing chef-solr (--configure):
> subprocess installed post-installation script returned error exit status 2
> configured to not write apport reports
> Errors were encountered while
> processing:
> chef-solr
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> The full build log is available from:
> http://people.debian.org/~lucas/logs/2010/11/20/chef-solr.log
>
> It is reproducible by installing your package in a clean chroot, using
> the debconf Noninteractive frontend, and priority: critical.
The problem is not the debconf frontend used, but the fact that the node
is down, given that it is reproducible on a cowbuilder chroot even with
an interactive debconf frontend:
=====
(sid)r...@gismo:/# unset DEBIAN_FRONTEND
(sid)r...@gismo:/# apt-get install chef-solr
[...]
������������������������������������������������Ĵ Configuring chef-solr
�������������������������������������������������Ŀ
� Please choose a password for the default user (named "chef") in the AMQP
server queue, under the default RabbitMQ vhost �
� (also "/chef").
�
�
�
� RabbitMQ's rabbitmqctl program, which will be used to set this password,
cannot read input from a file. Instead it will �
� be passed as a command-line argument, so the password should not include any
shell meta-characters that could cause �
� errors, such as "!".
�
�
�
� Password for the AMQP user "chef":
�
�
�
�
****____________________________________________________________________________________________________________________
�
�
�
� <Ok>
�
�
�
����������������������������������������������������������������������������������������������������������������������������
Error: unable to connect to node rab...@gismo: nodedown
diagnostics:
- nodes and their ports on gismo: [{rabbitmqctl25863,47783}]
- current node: rabbitmqctl25...@gismo
- current node home dir: /var/lib/rabbitmq
- current node cookie hash: x1rh/KXp98TJcRmgh8eJTA==
Creating vhost "/chef" ...
Error: unable to connect to node rab...@gismo: nodedown
diagnostics:
- nodes and their ports on gismo: [{rabbitmqctl25892,45949}]
- current node: rabbitmqctl25...@gismo
- current node home dir: /var/lib/rabbitmq
- current node cookie hash: x1rh/KXp98TJcRmgh8eJTA==
dpkg: error processing chef-solr (--configure):
subprocess installed post-installation script returned error exit status 2
configured to not write apport reports
Setting up default-jre-headless
(1:1.6-40) ...
Setting up ca-certificates-java (20100412) ...
creating /etc/ssl/certs/java/cacerts...
done.
Errors were encountered while processing:
chef-solr
E: Sub-process /usr/bin/dpkg returned an error code (1)
(sid)r...@gismo:/#
=====
Thx, bye,
Gismo / Luca
signature.asc
Description: Digital signature
