[Kolab-devel] setup-errors on Mageia

Thomas Spuhler thomas at btspuhler.com
Fri Oct 12 07:37:43 CEST 2012


On Wednesday, October 10, 2012 09:02:42 PM Thomas Spuhler wrote:
> On Wednesday, October 10, 2012 08:44:31 PM Thomas Spuhler wrote:
> > On Monday, October 08, 2012 01:32:56 AM Torsten Grote wrote:
> > > On Sunday 07 October 2012 20:51:23 Thomas Spuhler wrote:
> > > >     components[component_name]['function'](conf.cli_args, kw)
> > > >   
> > > >   File
> > > >   "/usr/lib/python2.7/site-packages/pykolab/setup/setup_ldap.py",
> > > >   line
> > > > 
> > > > 251, in execute
> > > > 
> > > >     stderr=subprocess.PIPE
> > > >   
> > > >   File "/usr/lib64/python2.7/subprocess.py", line 679, in __init__
> > > >   
> > > >     errread, errwrite)
> > > >   
> > > >   File "/usr/lib64/python2.7/subprocess.py", line 1249, in
> > > >   _execute_child
> > > >   
> > > >     raise child_exception
> > > > 
> > > > OSError: [Errno 2] No such file or directory
> > > 
> > > Could it be that this is caused by bug #1052?
> > > 
> > > If so, could you please check if provided patch works for Mageia?
> > > 
> > > Regards,
> > > Torsten
> > > 
> > > #1052 https://issues.kolab.org/show_bug.cgi?id=1052
> > 
> > Actually, the dirsrv starts manually:
> > 
> > # systemctl start dirsrv.target
> > # systemctl status dirsrv.target
> > dirsrv.target - 389 Directory Server
> > 
> >           Loaded: loaded (/usr/lib/systemd/system/dirsrv.target;
> >           disabled) Active: active since Wed, 10 Oct 2012 20:22:29
> >           -0700; 4s ago
> > 
> > But this seems to be the issue:
> > Oct 10 20:25:04 localhost.localdomain kolabd[6851]: File
> > "/usr/lib64/python2.7/os.py", line 157, in makedirs
> > Oct 10 20:25:04 localhost.localdomain kolabd[6851]: mkdir(name, mode)
> > Oct 10 20:25:04 localhost.localdomain kolabd[6851]: OSError: [Errno 13]
> > Permission denied: '/var/run/kolabd'
> > Oct 10 20:25:04 localhost.localdomain systemd[1]: Failed to start Kolab
> > Groupware Server..
> > Oct 10 20:32:07 localhost.localdomain systemd[1]: Stopped Kolab Groupware
> > Server..
> > Oct 10 20:36:07 localhost.localdomain systemd[1]: Starting Kolab
> > Groupware Server....
> > 
> > What permission should  dir /var/run/kolabd' have?
> > 
> > 
> > When I start it manually:
> > # systemctl start kolabd.service
> > #systemctl status kolabd.service
> > kolabd.service - Kolab Groupware Server.
> > 
> >           Loaded: loaded (/usr/lib/systemd/system/kolabd.service;
> >           disabled) Active: active (running) since Wed, 10 Oct 2012
> >           20:42:14 -0700;
> > 
> > 8s ago
> > 
> >          Process: 7612 ExecStart=/usr/sbin/kolabd $FLAGS (code=exited,
> > 
> > status=0/SUCCESS)
> > 
> >         Main PID: 7613 (kolabd)
> >         
> >           CGroup: name=systemd:/system/kolabd.service
> >           
> >                   └ 7613 /usr/bin/python /usr/sbin/kolabd --fork -l
> >                   warning
> 
> Hmmm... we have
> # locate systemctl
> /usr/bin/systemctl

I opened /var/run to world writable and the kolabd now starts. (We can resolve this later)
But the setup-still has a problem. I get this:

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).

2012-10-11 22:30:13,188 pykolab.setup INFO Setting up 389 Directory Server
Traceback (most recent call last):
  File "/sbin/setup-kolab", line 42, in <module>
    setup.run()
  File "/usr/lib/python2.7/site-packages/pykolab/setup/__init__.py", line 42, 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_ldap.py", line 251, in execute
    stderr=subprocess.PIPE
  File "/usr/lib64/python2.7/subprocess.py", line 679, in __init__
    errread, errwrite)
  File "/usr/lib64/python2.7/subprocess.py", line 1249, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory

What should I look for?

-- 
Best regards
Thomas Spuhler




More information about the devel mailing list