Re: 3.0 on Debian Wheezy: 'kolab-saslath' (?) related failure n boot sequence
Paul Klos <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kolab |
|---|---|
| Message-ID | <20121006223723.6960c792__9557.61556183479$1349555864$gmane$org@Nokia-N900> |
Op Sat, 6 Oct 2012 23:17:27 +0300 Johannes Graumann <[email protected]> schreef: > Hello, > > On Saturday, October 06, 2012 22:04:31 Paul Klos > wrote: > > Which package version of kolab-saslauthd have you > > installed? > dpkg - l --> 0.5.5-6.1 > Ok, that's the latest. It's supposed to check if the necessary paths exist and also set the correct permissions. > > > > What are the permissions/ownership > > on /run/saslauthd/mux (both the dir and the socket > > please)? > ls -la /run/saslauthd/mux > srwxrwxrwx 1 root root 0 Oct 6 > 20:07 /run/saslauthd/mux > > Socket? That's chinese to me ... does this help? Sorry about that, the file named mux is actually a socket but that doesn't really matter. ls -la /run/saslauthd would be nice, though. > > > After that, can you delete the > > directory /run/saslauthd and restart the daemon? > Hmm ... obviously it's not running upon boot > ps -A |grep saslauthd > 1353 ? 00:00:00 saslauthd > 1636 ? 00:00:00 saslauthd > 1638 ? 00:00:00 saslauthd > 1639 ? 00:00:00 saslauthd > 1640 ? 00:00:00 saslauthd > > But I can start it no prob ... > service kolab-saslauthd start && ps -A |grep > saslauthd 1353 ? 00:00:00 saslauthd > 1636 ? 00:00:00 saslauthd > 1638 ? 00:00:00 saslauthd > 1639 ? 00:00:00 saslauthd > 1640 ? 00:00:00 saslauthd > 3053 pts/0 00:00:00 kolab-saslauthd > > No deletions required!? > Maybe check the permissions on /run/saslauthd/mux again after you run it? Also ps Ukolab should show kolab-saslauthd. I'm not sure about the saslauthd processes. Which user owns these? > Joh > > > > > Paul > > > > > > Op Sat, 06 Oct 2012 19:52:49 +0300 > > > > Johannes Graumann <[email protected]> > > schreef: > > > Hi, > > > > > > When going through all the moves to get kolab > > > somewhat running on wheezy (using the kolabsys > > > deb repository), the startup-log of my lxc > > > container looks like what's documented below. > > > Can anyone please point give hints what might > > > be wring given the > > > > > > > Traceback (most recent call last): > > > > File > > > > > > > > "/usr/lib/python2.7/dist-packages/saslauthd/__init__.py", > > > > line 114, > > > > > > in run > > > > > > > self.do_saslauthd() > > > > > > > > File > > > > > > > > "/usr/lib/python2.7/dist-packages/saslauthd/__init__.py", > > > > line 164, > > > > > > in do_saslauthd > > > > > > > s.bind('/var/run/saslauthd/mux') > > > > > > > > File "/usr/lib/python2.7/socket.py", line > > > > 224, > > > > > > > > in meth return getattr(self._sock,name)(*args) > > > > error: [Errno 13] Permission denied > > > > Traceback occurred, please report a bug at > > > > http://bugzilla.kolabsys.com > > > > > > traceback? > > > > > > Thanks, Joh > > > > > > lxc-start -n kolab.<MyDomain>.org > > > INIT: version 2.88 booting > > > [info] Using makefile-style concurrent boot in > > > runlevel S. hostname: you must be root to change > > > the host name mount: permission denied > > > mount: permission denied > > > [info] Setting the system clock. > > > hwclock: Cannot access the Hardware Clock via > > > any known method. hwclock: Use the --debug > > > option to see the details of our search for an > > > access method. [warn] Unable to set System > > > Clock to: Sat Oct 6 16:46:07 UTC 2012 ... > > > (warning). [ ok ] Activating swap...done. > > > mount: permission denied > > > [ ok ] Cleaning up temporary files... /tmp. > > > mount: permission denied > > > mount: permission denied > > > mount: permission denied > > > mount: permission denied > > > [warn] Mount point '/dev/console' does not > > > exist. Skipping mount. ... (warning). > > > [warn] Mount point '/dev/ptmx' does not exist. > > > Skipping mount. ... (warning). > > > [ ok ] Activating lvm and md swap...done. > > > [....] Checking file systems...fsck from > > > util-linux 2.20.1 done. > > > [ ok ] Mounting local filesystems...done. > > > [ ok ] Activating swapfile swap...done. > > > mount: permission denied > > > mount: permission denied > > > [ ok ] Setting kernel variables ...done. > > > [ ok ] Cleaning up temporary files.... > > > [ ok ] Configuring network interfaces...done. > > > [ ok ] Cleaning up temporary files.... > > > [ ok ] Setting up X socket > > > directories... /tmp/.X11-unix /tmp/.ICE-unix. > > > [FAIL] startpar: service(s) returned failure: > > > hostname.sh ... failed! INIT: Entering > > > runlevel: 2 [info] Using makefile-style > > > concurrent boot in runlevel 2. Starting > > > amavisd: head: cannot open `/etc/mailname' for > > > reading: No such file or directory amavisd-new. > > > [....] Starting web server: apache2httpd (pid > > > 1136) already running . ok [ ok ] Starting NTP > > > server: ntpd. > > > > > > Traceback (most recent call last): > > > File > > > > > > "/usr/lib/python2.7/dist-packages/saslauthd/__init__.py", > > > line 114, in run self.do_saslauthd() > > > > > > File > > > > > > "/usr/lib/python2.7/dist-packages/saslauthd/__init__.py", > > > line 164, in do_saslauthd > > > s.bind('/var/run/saslauthd/mux') File > > > "/usr/lib/python2.7/socket.py", line 224, in > > > meth return getattr(self._sock,name)(*args) > > > error: [Errno 13] Permission denied Traceback > > > occurred, please report a bug at > > > http://bugzilla.kolabsys.com [ ok ] Starting > > > periodic command scheduler: cron. [ ok ] > > > Starting OpenBSD Secure Shell server: sshd. > > > [ ok ] Starting 389 DS instance kolab: .... > > > [ ok ] Removing stale PID > > > file /var/run/dbus/pid.. [ ok ] Starting system > > > message bus: dbus. [info] > > > No /etc/dirsrv/admin-serv/adm.conf file is > > > present. [ ok ] Starting SASL Authentication > > > Daemon: saslauthd. Starting SpamAssassin Mail > > > Filter Daemon: Oct 6 16:46:10.389 [1190] warn: > > > logger: failed to add syslog method: logger: > > > syslog initialization failed spamd. [ ok ] > > > Starting MySQL database server: mysqld .. > > > [info] Checking for tables which need an > > > upgrade, are corrupt or were not closed > > > cleanly.. [ ok ] Starting ClamAV daemon: > > > clamd . [ ok ] Starting ClamAV virus database > > > updater: freshclam. [ ok ] Starting Postfix > > > Mail Transport Agent: postfix. [FAIL] startpar: > > > service(s) returned failure: cyrus-imapd ... > > > failed! > > > > > > > > > _______________________________________________ > > > Kolab-devel mailing list > > > [email protected] > > > https://www.intevation.de/mailman/listinfo/kolab-devel