Project

General

Profile

Actions

Bug #2728

closed

/opt/rudder/bin/rudder-init.sh failure on Debian 6 / rudder 2.3

Added by Gonéri Le Bouder over 11 years ago. Updated about 9 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Packaging
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

rudder-init.sh fail on the following line:

/opt/rudder/sbin/slapadd -l $BOOTSTRAP_PATH &> $TMP_LOG

This insert fails:

dn: configurationRuleTarget=special:all,groupCategoryId=SystemGroups,groupCategoryId=GroupRoot,ou=Rudder,cn=rudder-configuration
objectClass: specialConfigurationRuleTarget
objectClass: top
configurationRuleTarget: special:all
cn: All servers
description: A special target which matches absolutly all known nodes, including policy servers
isActivated: TRUE
isSystem: TRUE

5016ad96 str2entry: entry -1 has invalid DN "configurationRuleTarget=special:all,groupCategoryId=SystemGroups,groupCategoryId=GroupRoot,ou=Rudder,cn=rudder-configuration" 
slapadd: could not parse entry (line=105)
root@srv00015:~# /opt/rudder/bin/rudder-init.sh

Welcome to the Rudder initialization script

This script will configure your Rudder root server.
It can be run as many times as you want.

Please enter the fully qualified domain name that will be used to access the web interface of the Rudder server (i.e rudder.example.com): rudder.toto.infra

Enter network allowed to access server (i.e 192.168.0.0/24): 172.28.220.0/24
172.28.220.0/24
Network(s) added:
172.28.220.0/24
Add more networks? (yes/no) no
no

Enter server IP: 172.28.220.207
172.28.220.207

Do you want to add sample data (for demos)? (yes/no) no
no

An LDAP database has been detected.
Do you want to reinitialize it? (yes/no) yes
yes

Do you want to reset initial promises ? (yes/no) yes
yes

Hostname: rudder.toto.infra
Allowed networks: 172.28.220.0/24
Server IP: 172.28.220.207
Add sample data? no
Reinitialize LDAP database? yes
Reset Initial Promises? yes

Hit any key to continue....
Configuring and installing initial Cfengine promises... done.
Initializing LDAP database...ERROR: Execution failed! Aborting.
An error occured. Please check /tmp/rudder.X7EPjAkabN.log for details.
root@srv00015:~# cat /tmp/rudder.X7EPjAkabN.log
5016aa6c str2entry: entry -1 has invalid DN "configurationRuleTarget=special:all,groupCategoryId=SystemGroups,groupCategoryId=GroupRoot,ou=Rudder,cn=rudder-configuration" 
slapadd: could not parse entry (line=105)
Actions #1

Updated by Nicolas PERRON over 11 years ago

Which is the version used ?
Please display the result of this command:

aptitude show rudder-server-root

Actions #2

Updated by Gonéri Le Bouder over 11 years ago

I realize, use a mixed 2.3/2.4 installation... sorry

ii  rudder-cfengine-community           2.4.0~beta2-squeeze0         Configuration management and audit tool - CFEngine server component
ii  rudder-inventory-endpoint           2.3.8-squeeze0               Configuration management and audit tool - service to receive inventory data
ii  rudder-inventory-ldap               2.4.0~beta2-squeeze0         Configuration management and audit tool - OpenLDAP
ii  rudder-jetty                        2.3.8-squeeze0               Configuration management and audit tool - Jetty application server
ii  rudder-policy-templates             2.3.8-squeeze0               Configuration management and audit tool -  policy templates
ii  rudder-reports                      2.3.8-squeeze0               Configuration management and audit tool - reports database
ii  rudder-server-root                  2.3.8-squeeze0               Configuration management and audit tool - root server base package
ii  rudder-webapp                       2.3.8-squeeze0               Configuration management and audit tool - webapp

Actions #3

Updated by Nicolas PERRON over 11 years ago

Gonéri Le Bouder wrote:

I realize, use a mixed 2.3/2.4 installation... sorry

[...]

Ok, I wasn't able to reproduce this bug.
Jonathan, could you reject this bug, please ?

Actions #4

Updated by Gonéri Le Bouder over 11 years ago

I would say, such dependencies should be managed by dpkg with source:Version:

rudder-inventory-ldap (>= ${source:Version})

Actions #5

Updated by Jonathan CLARKE over 11 years ago

  • Status changed from New to Rejected
  • Assignee deleted (Jonathan CLARKE)
  • Target version set to 2.3.9

Gonéri Le Bouder wrote:

I would say, such dependencies should be managed by dpkg with source:Version:
rudder-inventory-ldap (>= ${source:Version})

This has now been done, see #2758 (actually using ${binary:Version}).

Since the original problem of this bug was due to a mix of versions, I'm rejecting. However, thank you very much Gonéri for pointing this out (version dependencies).

Actions #6

Updated by Nicolas PERRON about 11 years ago

  • Project changed from Rudder to 34
  • Category deleted (11)
Actions #7

Updated by Benoît PECCATTE about 9 years ago

  • Project changed from 34 to Rudder
  • Category set to Packaging
Actions

Also available in: Atom PDF