[Dovecot] Services not starting in 2.1 (or 2.2)
I'm trying to install Dovecot onto my QNAP NAS. I apologise for this! It means I'm not working in a normal environment, and don't (necessarily) have the normal range of tools available (or the most up to date version of those tools).
It seems that 2.0.21 works (at least, as far as I've tested), but 2.1.17 and 2.2.4 won't start up their child services.
I've got the source code for all three from http://www.dovecot.org/download.html, and, for experimental purposes, I'm configuring with: ./configure --prefix=/opt
The configure script ends by reporting: Install prefix . : /opt File offsets ... : 64bit I/O polling .... : epoll I/O notifys .... : inotify SSL ............ : yes (OpenSSL) GSSAPI ......... : no passdbs ........ : static passwd passwd-file shadow checkpassword : -pam -bsdauth -sia -ldap -sql -vpopmail userdbs ........ : static prefetch passwd passwd-file checkpassword nss : -ldap -sql -vpopmail SQL drivers .... : : -pgsql -mysql -sqlite
The dovecot.conf I'm using, at the moment, is the absolute minimal to fire things up: protocols = imap listen = * ssl_cert =
dovecot -n is happy, and reports those four lines back to me.
When I start this up, I get, in /var/log/messages file: Jul 10 10:09:28 QNAP mail.info dovecot: master: Dovecot v2.0.21 starting up (core dumps disabled)
and ps shows: [admin@qnap dovecot]# ps -ef | grep dovecot admin 11478 1 0 10:09 ? 00:00:00 /opt/sbin/dovecot dovecot 11479 11478 0 10:09 ? 00:00:00 dovecot/anvil admin 11480 11478 0 10:09 ? 00:00:00 dovecot/log admin 11482 11478 0 10:09 ? 00:00:00 dovecot/config admin 11525 455 0 10:10 pts/5 00:00:00 grep dovecot
All is right with the world! Well, until I try to use dovecot properly, at which point I'll need a full configuration. But it's alright so far! :)
However, if I go through the same routine with Dovecot 2.1.17, I get the appropriate message in messages: Jul 10 10:12:45 QNAP mail.info dovecot: master: Dovecot v2.1.17 starting up (core dumps disabled)
But this time, ps shows: [admin@qnap dovecot-2.1.17]# ps -ef | grep dovecot admin 15259 1 0 10:12 ? 00:00:00 /opt/sbin/dovecot admin 15294 455 0 10:12 pts/5 00:00:00 grep dovecot
and the child services don't seem to have started. This is born out by the fact that no network connections work: they stall, and then eventually time out (telnet localhost 143 produces no output at all, until I disconnect it). Even dovecot stop has trouble, taking several seconds before it returns me to the prompt, and *not* killing the existing process. dovecot -n is still happy however (and in a full configuration, components which don't require the services seem to work properly, such as dovecot-lda, if it doesn't require auth).
I'm not sure that I need those newer versions of dovecot, so I'll get back to version 2.0 for now. But I'd certainly like the option, and imagine that somebody else might care as to what the problem is!
-- Tommy Wareing
On 2013-07-10 5:28 AM, Tommy Wareing tommyw@ntlworld.com wrote:
I'm trying to install Dovecot onto my QNAP NAS.
Which device, and what version of OS?
QNAP NAS devices are notorious for having ancient versions of critical OS software (like the kernel, glib, OpenSSL, etc)...
If you haven't already, check and see if the new 4.x OS version is available for your device, and if so, and you aren't already running it, update it, and try again.
Otherwise, you'd probably get much better help on the QNAP forums...
--
Best regards,
Charles
On Wed, Jul 10, 2013 at 06:33:55AM -0400, Charles Marcus wrote:
On 2013-07-10 5:28 AM, Tommy Wareing tommyw@ntlworld.com wrote:
I'm trying to install Dovecot onto my QNAP NAS.
Which device, and what version of OS?
Whoops! Sorry, I was concentrating too much on the specifics of the problem, and not enough on my setup!
It's a TS-869L, with version 4.0.1 of the firmware. (So it's running on an Intel Atom CPU, if that's at all relevant)
uname -a reports: Linux qnap.mrwolf.afraid.org 3.4.6 #1 SMP Tue Jun 4 20:08:41 CST 2013 x86_64 GNU/Linux and dovecot -n agrees: # OS: Linux 3.4.6 x86_64 ext4
QNAP NAS devices are notorious for having ancient versions of critical OS software (like the kernel, glib, OpenSSL, etc)...
Yup, I'd already tripped over that quite a lot. I've installed updates from ipkg, but those aren't the most up to date either (dovecot 1.2.0 beta!)
I'm happy to check for further updates of "stuff", or supply version numbers, or run other diagnostics, but without knowing the sort of "stuff" I'm looking for, that's probably not helpful.
make check, incidentally, passes satisfactorily on all three builds.
If you haven't already, check and see if the new 4.x OS version is available for your device, and if so, and you aren't already running it, update it, and try again. Already done.
Otherwise, you'd probably get much better help on the QNAP forums...
I'm trying there as well. But trying to identify an active, relevant sub-forum is an interesting challenge in its own right :) Fingers crossed!
-- Tommy Wareing
On 7/10/2013 8:09 AM, Tommy Wareing wrote:
On Wed, Jul 10, 2013 at 06:33:55AM -0400, Charles Marcus wrote:
On 2013-07-10 5:28 AM, Tommy Wareing tommyw@ntlworld.com wrote:
I'm trying to install Dovecot onto my QNAP NAS.
Did you create the "dovenull" user, which is needed by 2.1+? I ran dovecot 2.1.7 on my stock SS-439 quite successfully, until I completely gave up on the QNAP firmware and reinstalled it with Ubuntu.
Anyway, try this, which worked for me back on QNAP 3.7.x:
/bin/adduser -DHS -g "XDove user" -h /tmp -s /bin/false dovecot /bin/adduser -DHS -g "XDove user" -h /tmp -s /bin/false dovenull <start dovecot etc>
Tom.
On Wed, Jul 10, 2013 at 08:42:20AM -0400, Tom Talpey wrote:
On 7/10/2013 8:09 AM, Tommy Wareing wrote:
On Wed, Jul 10, 2013 at 06:33:55AM -0400, Charles Marcus wrote:
On 2013-07-10 5:28 AM, Tommy Wareing tommyw@ntlworld.com wrote:
I'm trying to install Dovecot onto my QNAP NAS.
Did you create the "dovenull" user, which is needed by 2.1+? I ran dovecot 2.1.7 on my stock SS-439 quite successfully, until I completely gave up on the QNAP firmware and reinstalled it with Ubuntu.
I may end up with a "real" operating system yet. But I've only had the box for a fortnight, so it seems a little early for gutting it so completely ;)
Yes, I've got dovecot and dovenull users. In fact (just to check), doveconf for 2.0.21 complains if dovenull's not there: doveconf: Error: default_login_user doesn't exist: dovenull doveconf: Fatal: Error in configuration file /opt/etc/dovecot/dovecot.conf: default_login_user doesn't exist: dovenull
Interestingly, it doesn't complain about the absence of dovecot.
(I'll put 'em back now ;-)
-- Tommy Wareing
On 7/10/2013 9:22 AM, Tommy Wareing wrote:
On Wed, Jul 10, 2013 at 08:42:20AM -0400, Tom Talpey wrote:
On 7/10/2013 8:09 AM, Tommy Wareing wrote:
On Wed, Jul 10, 2013 at 06:33:55AM -0400, Charles Marcus wrote:
On 2013-07-10 5:28 AM, Tommy Wareing tommyw@ntlworld.com wrote:
I'm trying to install Dovecot onto my QNAP NAS.
Did you create the "dovenull" user, which is needed by 2.1+? I ran dovecot 2.1.7 on my stock SS-439 quite successfully, until I completely gave up on the QNAP firmware and reinstalled it with Ubuntu.
Yes, I've got dovecot and dovenull users. In fact (just to check), doveconf for 2.0.21 complains if dovenull's not there: doveconf: Error: default_login_user doesn't exist: dovenull doveconf: Fatal: Error in configuration file /opt/etc/dovecot/dovecot.conf: default_login_user doesn't exist: dovenull
Interestingly, it doesn't complain about the absence of dovecot.
I guess I'd suggest configuring both log_path and info_log_path to point somewhere, and look for additional clues in the output. Maybe a missing home directory or a permissions problem on one of the sockets in /var/run/dovecot, something like that. Remember the QNAP firmware puts a bunch of that stuff in a very small ramdisk.
Tom.
On 2013-07-10 8:09 AM, Tommy Wareing tommyw@ntlworld.com wrote:
On Wed, Jul 10, 2013 at 06:33:55AM -0400, Charles Marcus wrote:
Otherwise, you'd probably get much better help on the QNAP forums... I'm trying there as well. But trying to identify an active, relevant sub-forum is an interesting challenge in its own right :) Fingers crossed!
Cool - please by all means report back if/when you get an answer, as I have a couple of TS-569P's that I was considering trying to install dovecot...
--
Best regards,
Charles
Tommy Wareing skrev den 2013-07-10 14:09: [snip]
Otherwise, you'd probably get much better help on the QNAP forums...
I'm trying there as well. But trying to identify an active, relevant sub-forum is an interesting challenge in its own right :) Fingers crossed!
yes qnap qpkg have btw xmail, dont know if its based on dovecot, but its more a maintained package then dovecot in ipkg is, is you running mta aswell in qnap ?
wish from my side is that qnap change to gentoo portage, and then let portage maintainers support qnap hardware, its just a wish, just installing gentoo is not a problem, its just loose what software qnap makes :(
http://wiki.qnap.com/wiki/Category:XDove is the only dovecot link i could find that is not just ipkg install dovecot :=)
i think you have done ipkg update, ipkg upgrade, so this does not help old packages :(
i self have a ts-419p+
On Wed, Jul 10, 2013 at 06:33:55AM -0400, Charles Marcus wrote:
On 2013-07-10 5:28 AM, Tommy Wareing tommyw@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!
-- Tommy
participants (4)
-
Benny Pedersen
-
Charles Marcus
-
Tom Talpey
-
Tommy Wareing