Actions
Bug #12698
closedrudder-agent 4.3 install hangs on Debian 7
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
51
Name check:
Fix check:
Regression:
Description
Rudder agent install is stuck at some point, and can only resume if cf-serverd/execd are killed ( can be done easily by restarting service rudder-agent)
It seems that is a bug when some file descriptors are not closed properly making dpkg hangs ...
ps output:
root 2213 0.0 0.0 4164 708 pts/0 Ss+ 11:44 0:00 sh /tmp/ncf-setup test-local https://github.com/Normation/ncf.git#branches/rudder/4.3 rudder-4.3 root 2291 0.1 2.7 70196 27860 pts/0 S+ 11:44 0:00 apt-get -y install rudder-agent root 2703 0.0 0.2 12704 2700 pts/1 Ss+ 11:44 0:00 /usr/bin/dpkg --status-fd 42 --configure libyaml-0-2:amd64 uuid-runtime:amd64 rudder-agent:amd64 root 2713 0.0 1.2 60028 12932 pts/1 S+ 11:44 0:00 /usr/bin/perl -w /usr/share/debconf/frontend /var/lib/dpkg/info/rudder-agent.postinst configure root 2716 0.0 0.0 0 0 pts/1 Z+ 11:44 0:00 [rudder-agent.po] <defunct>
Here is the stuck output of apt-get
11:00:13 D��paquetage de rudder-agent (�� partir de .../rudder-agent_4.3.1-wheezy0_amd64.deb) ... 11:00:15 Traitement des actions diff��r��es (����triggers����) pour ����man-db����... 11:00:18 Param��trage de libyaml-0-2:amd64 (0.1.4-2+deb7u5) ... 11:00:19 Param��trage de uuid-runtime (2.20.1-5.3) ... 11:00:19 Param��trage de rudder-agent (4.3.1-wheezy0) ... 11:00:20 [1;32mok[0;39m[0;49m: Rudder agent is now disabled. 11:00:20 INFO: Ensuring correct permissions on the keys directory... Done. 11:00:20 INFO: Creating keys for Rudder agent... Done. 11:00:21 [1;32mok[0;39m[0;49m: Rudder agent has been enabled but not started, wait for next cron run. 11:00:21 ******************************************************************************** 11:00:21 rudder-agent has been installed (not started). This host can be a Rudder node. 11:00:21 To get started, configure your Rudder server's hostname and launch the agent: 11:00:21 # echo 'rudder.server' > /var/rudder/cfengine-community/policy_server.dat 11:00:21 # rudder agent start 11:00:21 This node will then appear in the Rudder web interface under 'Accept new nodes'. 11:00:21 ********************************************************************************
Actions