[packaging] [Bug 1682] New: setup-kolab ist broken again on 12.2 and 12.3 RC2 (i586)

Kolab Bugzilla noreply at kolab.org
Wed Mar 6 19:20:40 CET 2013


https://issues.kolab.org/show_bug.cgi?id=1682

            Bug ID: 1682
           Summary: setup-kolab ist broken again on 12.2 and 12.3 RC2
                    (i586)
    Classification: Kolab Server
           Product: Kolab Server
           Version: 3.0.0
          Hardware: PC
                OS: openSuSE 12.2
            Status: NEW
          Severity: critical
          Priority: P3
         Component: packaging - rpm - suse
          Assignee: aj at ajaissle.de
          Reporter: m00nraker at gmx.net
                CC: packaging-bugs at lists.kolabsys.com
       Ticket Type: ---

Hi Aeneas,

last week setup-kolab under a fresh installed openSuse 12.2 runs through
without any major issues. After setup I could navigate to the kolab webadmin
panel and login with the username "cn=Directory Manager". On the first view
that looks good. But after a reboot it was not possible to login to the
webadmin panel again. It always says: unknown username or password. Something
like that was reported on the German mailing list.

So today I rolled out a fresh openSuse 12.3 RC2 (i586) in a Virtual Box
environment and installed Kolab from the unstable repos again.

This time setup-kolab seems to be broken. It stops during setup.

kolab:~ # setup-kolab -d 3 -l error

Please supply a password for the LDAP administrator user 'admin', used to login
to the graphical console of 389 Directory server.

Administrator password [QPz6cvJMYWFsNpU]: 
Confirm Administrator password: 

Please supply a password for the LDAP Directory Manager user, which is the
administrator user you will be using to at least initially log in to the Web
Admin, and that Kolab uses to perform administrative tasks.

Directory Manager password [CzV4wUFtDot4eZ-]: 
Confirm Directory Manager password: 

Please choose the system user and group the service should use to run under.
These should be existing, unprivileged, local system POSIX accounts with no
shell.

User [nobody]: 
Group [nobody]: 

This setup procedure plans to set up Kolab Groupware for the following domain
name space. This domain name is obtained from the reverse DNS entry on your
network interface. Please confirm this is the appropriate domain name space.

gurus.de [Y/n]: 

The standard root dn we composed for you follows. Please confirm this is the
root
dn you wish to use.

dc=gurus,dc=de [Y/n]: 

Setup is now going to set up the 389 Directory Server. This may take a little
while (during which period there is no output and no progress indication).

2013-03-06 18:53:13,814 pykolab.setup INFO Setting up 389 Directory Server
ln -s '/usr/lib/systemd/system/dirsrv.target'
'/etc/systemd/system/multi-user.target.wants/dirsrv.target'

Please supply a Cyrus Administrator password. This password is used by Kolab to
execute administrative tasks in Cyrus IMAP. You may also need the password
yourself to troubleshoot Cyrus IMAP and/or perform other administrative tasks
against Cyrus IMAP directly.

Cyrus Administrator password [YCHMRKFGEzsGTnw]: 
Confirm Cyrus Administrator password: 

Please supply a Kolab Service account password. This account is used by various
services such as Postfix, and Roundcube, as anonymous binds to the LDAP server
will not be allowed.

Kolab Service password [vnMtmkBH8_5Bhqa]: 
Confirm Kolab Service password: 
2013-03-06 18:54:16,330 pykolab.setup INFO Writing out configuration to
kolab.conf
2013-03-06 18:54:16,357 pykolab.setup INFO Inserting service users into LDAP.
2013-03-06 18:54:17,574 pykolab.setup INFO Writing out cn=kolab,cn=config
2013-03-06 18:54:17,689 pykolab.setup INFO Adding domain gurus.de to list of
domains for this deployment
2013-03-06 18:54:17,730 pykolab.setup INFO Disabling anonymous binds
2013-03-06 18:54:17,790 pykolab.setup INFO Enabling attribute uniqueness plugin
2013-03-06 18:54:17,838 pykolab.setup INFO Enabling referential integrity
plugin
2013-03-06 18:54:17,883 pykolab.setup INFO Enabling and configuring account
policy plugin
2013-03-06 18:54:17,979 pykolab.setup INFO Adding the kolab-admin role
2013-03-06 18:54:18,058 pykolab.setup INFO Setting access control to
dc=gurus,dc=de
Failed to issue method call: No such file or directory
Traceback (most recent call last):
  File "/usr/sbin/setup-kolab", line 42, in <module>
    setup.run()
  File "/usr/lib/python2.7/site-packages/pykolab/setup/__init__.py", line 43,
in run
    components.execute('_'.join(to_execute))
  File "/usr/lib/python2.7/site-packages/pykolab/setup/components.py", line
170, in execute
    execute(component)
  File "/usr/lib/python2.7/site-packages/pykolab/setup/components.py", line
202, in execute
    components[component_name]['function'](conf.cli_args, kw)
  File "/usr/lib/python2.7/site-packages/pykolab/setup/setup_mta.py", line 317,
in execute
    fp.write(t.__str__())
  File "/usr/lib/python2.7/site-packages/Cheetah/Template.py", line 1005, in
__str__
    rc = getattr(self, mainMethName)()
  File "cheetah_DynamicallyCompiledCheetahTemplate_1362592465_25_80101.py",
line 123, in respond
NameMapper.NotFound: cannot find 'MYHOME'
kolab:~ # 

(same result on openSuse 12.2)

BTW, why did you deleted the previous bug report? The bugs are still present.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolabsys.com/pipermail/packaging-bugs/attachments/20130306/d88e9615/attachment.htm>


More information about the packaging-bugs mailing list