Config problem: Service #0 is missing name
Okay. So following up on the problems I was discussing weeks ago, I have hand-patched dovecot to work around problems that I believe may be in libc and not dovecot.
Trying to get the properly built and installed dovecot-2.2.35, however, is giving me an error I haven’t seen before. I presume that something got munged while I was hand-configuring and installing/uninstalling/reinstalling the port in recent weeks.
Running on a FreeBSD 11-stable machine, when I run “service dovecot start”, it tells me:
% sudo service dovecot start Starting dovecot. Fatal: Error reading configuration: Invalid settings: Service #0 is missing name /usr/local/etc/rc.d/dovecot: WARNING: failed to start dovecot %
Surprisingly, googling for “Service #0 is missing name” didn’t yield a suggestion. My config is the same as it had been previously, I believe. Does anyone have an idea what might be wrong here?
Thanks.
- ChrisOn Mar 25, 2018, at 10:37, Aki Tuomi <aki.tuomi@dovecot.fi> wrote:
Without looking at your config I'd say you have a nameless service section, like
service {
}
Name goes after keyword service.
Yeah, I don’t seem to. This was the same config that was working before things stopped for other reasons last month. I think I may’ve overlooked something in my hand-coded replacement for libc functionality. I’m testing that now.
[time goes by]
Yup. My error. Sorry for the noise on the list, it’s running now.
- Chris
participants (2)
-
Aki Tuomi
-
Chris Ross