[BryanDH]

I’m seeing this behavior too. If I reboot the master, it stops and sometimes won’t start the spiraling replication for 3-4 days.

My master was upgraded from 10.3.9, so I’m wondering if there is some cruft floating around.

Bryan

[BryanDH]

One strange side effect after applying the 10.3.8 update…

My IMAP users have no problems at all. POP users discoverd that all messages saved on the server were downloaded again, resulting in duplicate messages. I got a lot of calls this morning about this. One user had 6000 messages stored, all of which came down again! =-O

Bryan

[BryanDH]

I applied the 10.3.8 Combo Update and things are working again. And it seems Apple pulled the security update.

Bryan

[BryanDH]

Hi:

I think you posted this on the Apple board. I tried the reinstall. No luck on my side.

Bryan

[BryanDH]

Yeah…it seems like this update has broken quite a few things. It’s unfortunate, because it’s an important security update for cyrus and SASL.

[BryanDH]

I started having the dreaded "Could not log on to timsieved daemon on your IMAP server localhost. Please contact your administrator" error in SquirrelMail, after having things working great for the past few months. I checked permissions on thepwauxprop.* files…they were fine. I opened up console.log to see if anything interesting was going on. Sure enough, an instance of timsieved was reporting that it could not connect to the saslauthd server because the connection was refused. I checked to see if any saslauthd processes were running. There were none. I remembered that the sieve installer puts an entry in watchdog.conf, so watchdog should be keeping saslauthd up and running. Something was amiss.

To investigate, I watched the console.log as I did a stop and a start of watchdog. Here was the results when saslauthd attempted to launch:

Dec 9 15:54:35 mailserver saslauthd[14673]: main : could not open pid lock file: /var/state/saslauthd/saslauthd.pid.lock
Dec 9 15:54:35 mailserver saslauthd[14673]: main : open: Permission denied
Dec 9 15:54:35 mailserver saslauthd[14673]: main : Check to make sure the directory exists and is
Dec 9 15:54:35 mailserver saslauthd[14673]: main : writeable by the user this process runs as.

The permissions on the lock file in my case were:

-w——- 1 cyrus wheel 6 9 Dec 00:40 saslauthd.pid.lock

So the whole thing got screwed because of this lock file. The file was unable to be cleared. I changed the permissions to 600, then restarted watchdog. This time, there were no errors from saslauthd in the log, and 5 saslauthd processes were listed when I did a ps -aux | grep sasl

I logged into SquirrelMail, and clicked on the filters. Everything was working again!

Maybe this can help some of you who are getting this error. try checking the saslauthd component and see if it’s bringing down the house.

Bryan

[QUOTE BY= lcalderon] I get the following message whenever I click on the FILTERS button in SquirrelMail. I see others are getting the same error, any ideas on how to fix?

Could not log on to timsieved daemon on your IMAP server localhost.
Please contact your administrator[/QUOTE] :

[Author]

Posts