[Dovecot] Solved. Re: Services not starting in 2.1 (or 2.2)

Tommy Wareing tommyw at ntlworld.com
Tue Jul 16 00:04:01 EEST 2013

On Wed, Jul 10, 2013 at 06:33:55AM -0400, Charles Marcus wrote:
> On 2013-07-10 5:28 AM, Tommy Wareing <tommyw at ntlworld.com> wrote:
> >I'm trying to install Dovecot onto my QNAP NAS.
> QNAP NAS devices are notorious for having ancient versions of
> critical OS software (like the kernel, glib, OpenSSL, etc)...

It turns out that we were both maligining QNAP here.

I installed strace (which I hadn't expected to be able to do, but 
there's an ipkg for it), and ran 2.1.17 through.

The log file stopped at:
16:55:35.549868 stat64("/share/MD0_DATA", {st_mode=S_IFDIR|0777, st_size=4096, ...}) = 0
16:55:35.550006 stat64("/proc/fs/nfsd", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
16:55:35.550163 stat64("/.eaccelerator.tmp", {st_mode=S_IFDIR|0777, st_size=360, ...}) = 0
16:55:35.550300 stat64("/var/syslog_maildir", {st_mode=S_IFDIR|0777, st_size=40, ...}) = 0
16:55:35.550438 stat64("/mnt/thecus", 

It's checking the machine's mount points, and that last is where I'd had 
my old NAS mounted, to slurp the data off it. I'd then powered down the 
NAS, but hadn't unmounted it first, so I'd left a stale NFS handle, 
which caused the newer versions to hang (it's possible that they'd have 
eventually timed out and started up normally, but I'd never given them 
long enough).

umount -l /mnt/thecus, and everything runs fine.

Would it be worth generating a log message before checking the mount points?

> Otherwise, you'd probably get much better help on the QNAP forums...

Complete silence, pretty much as I'd expected!


More information about the dovecot mailing list