Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: DBMail: users

DBMail 3 - problems with pid-files

 

 

DBMail users RSS feed   Index | Next | Previous | View Threaded


miles at atmos

Feb 25, 2012, 1:41 AM

Post #1 of 3 (221 views)
Permalink
DBMail 3 - problems with pid-files

Hi folks,

I struggled for quite a few hours trying to get the imapd and lmtpd
daemons running. They always ended with a segment fault before coming up.

After trying to track down the issue, it seems like the pid-files for
the daemons cannot be created in /var/run with the nobody:nogroup
privileges. When I created the directory /var/run/dbmail, with
nobody:nogroup ownership, and started both daemons with the parameter -p
and explicitly assigned the full path to the pid-files in
/var/run/dbmail, everything worked OK.

I'm replacing an older DBMail 2.2.16 installation, and there is no
issue with that, the pid-files and state-files owned by root:root, but
under 3.0.0, they are owned by nobody:nogroup.

I've not seen it in the documentation, maybe it should be mentioned, as
it saves lots of troubleshooting.

OS: Slackware 13.37 x86_64 (same problem under two different installations)

Regards,

Peter

_______________________________________________
DBmail mailing list
DBmail [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail


miles at atmos

Feb 25, 2012, 2:19 AM

Post #2 of 3 (208 views)
Permalink
Re: DBMail 3 - problems with pid-files [In reply to]

Sorry I brought this up. It was answered in previous posts (should
probably clean my glasses ;-)

Peter

On 25.2.2012 10:41, Peter Milesson wrote:
> Hi folks,
>
> I struggled for quite a few hours trying to get the imapd and lmtpd
> daemons running. They always ended with a segment fault before coming up.
>
> After trying to track down the issue, it seems like the pid-files for
> the daemons cannot be created in /var/run with the nobody:nogroup
> privileges. When I created the directory /var/run/dbmail, with
> nobody:nogroup ownership, and started both daemons with the parameter -p
> and explicitly assigned the full path to the pid-files in
> /var/run/dbmail, everything worked OK.
>
> I'm replacing an older DBMail 2.2.16 installation, and there is no issue
> with that, the pid-files and state-files owned by root:root, but under
> 3.0.0, they are owned by nobody:nogroup.
>
> I've not seen it in the documentation, maybe it should be mentioned, as
> it saves lots of troubleshooting.
>
> OS: Slackware 13.37 x86_64 (same problem under two different installations)
>
> Regards,
>
> Peter

_______________________________________________
DBmail mailing list
DBmail [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail


h.reindl at thelounge

Feb 25, 2012, 2:43 AM

Post #3 of 3 (208 views)
Permalink
Re: DBMail 3 - problems with pid-files [In reply to]

however, additional info to this topic

if you are running Fedora >= 15 or any other distribution using
"systemd" instead sysvinit /var/run/ is only a zmpfs and created
folders are lost at the next rebuild

the "/etc/tmpfiles.d/dbmail.conf" below creates it autoamatically at
boot, one oftne made packaging mistake to forget this and create
the directory only at install time leading to work the first

[root [at] srv-rhsof:~]$ mount | grep /var/run

tmpfs on /var/run type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755)

[root [at] srv-rhsof:~]$ cat /etc/tmpfiles.d/dbmail.conf
d /var/run/dbmail 0755 dbmail dbmail -

Am 25.02.2012 11:19, schrieb Peter Milesson:
> Sorry I brought this up. It was answered in previous posts (should probably clean my glasses ;-)
>
> Peter
>
> On 25.2.2012 10:41, Peter Milesson wrote:
>> Hi folks,
>>
>> I struggled for quite a few hours trying to get the imapd and lmtpd
>> daemons running. They always ended with a segment fault before coming up.
>>
>> After trying to track down the issue, it seems like the pid-files for
>> the daemons cannot be created in /var/run with the nobody:nogroup
>> privileges. When I created the directory /var/run/dbmail, with
>> nobody:nogroup ownership, and started both daemons with the parameter -p
>> and explicitly assigned the full path to the pid-files in
>> /var/run/dbmail, everything worked OK.
>>
>> I'm replacing an older DBMail 2.2.16 installation, and there is no issue
>> with that, the pid-files and state-files owned by root:root, but under
>> 3.0.0, they are owned by nobody:nogroup.
>>
>> I've not seen it in the documentation, maybe it should be mentioned, as
>> it saves lots of troubleshooting.
>>
>> OS: Slackware 13.37 x86_64 (same problem under two different installations)

--

Mit besten Grüßen, Reindl Harald
the lounge interactive design GmbH
A-1060 Vienna, Hofmühlgasse 17
CTO / software-development / cms-solutions
p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40
icq: 154546673, http://www.thelounge.net/

http://www.thelounge.net/signature.asc.what.htm
Attachments: signature.asc (0.26 KB)

DBMail users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.