Re: setup-errors on Mageia

Thomas Spuhler <[email protected]>
Newsgroups gmane.comp.kde.devel.kolab
Message-ID <201210142104.15085.thomas__29374.411647632$1350273874$gmane$org@btspuhler.com>
On Sunday, October 14, 2012 11:10:07 AM Jeroen van Meeuwen (Kolab Systems) wrote:
> On 2012-10-10 23:44, Thomas Spuhler wrote:
> > 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?
> 
> /var/run/kolabd/ is used to write out the pid file into.
> 
> If kolabd (the process, not the service) starts as kolab:kolab, it
> expects this directory to exist and have kolab:kolab permissions.
> 
> You can start kolabd as kolab:kolab from within the service management
> (some sysvinit or systemd), while you can also start it as root:root at
> which point kolabd itself will setuid/setgid to kolab:kolab - after
> creating the /var/run/kolabd/ directory and writing out its pid file.
> 
> Kind regards,
> 
> Jeroen van Meeuwen

It's very strange. When I install the set of kolab packages using urpmi kolab, the directory 
/run/kolabd/ doesn't exits

/var/run/ is a link to /run/

After uninstalling kolab-server and re-installing it, the directory is there with user/group 
kolab/kolab

-- 
Best regards
Thomas Spuhler
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.