Re: [Crm114-general] crm114 problems on virtual server (SElinux related?)

[Nico Kadel-G. <nk...@gm...>]

crm...@be... wrote:
> Dear all,
>
> I recently moved my mail server to a Virtual Private Server. We came from
> a dedicated Slackware server and crm114 ran fine there.
>
> On the virtual server, crm114 keeps throwing errors like 'Tried to fork
> your minion, but it failed.', 'Couldn't malloc one or more
> ofnewinputbuf,inbuf,outbuf,tempbuf.' and 'Couldn't malloc cdw->filetext.'
>
> Free and ulimit seem to report ok values:
>
>              total       used       free
> Mem:        196608     105704      90904
>
> ulimit -a
> core file size          (blocks, -c) 0
> data seg size           (kbytes, -d) unlimited
> max nice                        (-e) 0
> file size               (blocks, -f) unlimited
> pending signals                 (-i) 38912
> max locked memory       (kbytes, -l) 32
> max memory size         (kbytes, -m) unlimited
> open files                      (-n) 1024
> pipe size            (512 bytes, -p) 8
> POSIX message queues     (bytes, -q) 819200
> max rt priority                 (-r) 0
> stack size              (kbytes, -s) 10240
> cpu time               (seconds, -t) unlimited
> max user processes              (-u) 38912
> virtual memory          (kbytes, -v) unlimited
> file locks                      (-x) unlimited
>
> I tried different versions; statically and dynamically linked (-> because
> the static binary seemed awfully large to me), compiled BlameSteveJobs on
> another machine to get the latest & greatest, to no avail.
>
> The -w option seems to help with the minions error, but then more malloc 
> errors pop up.
>
> I tried the search function on the mailinglist archive but somehow I can't
> get that to work. Google yielded SElinux (the VPS environment is HyperVM)
> seems to have something to do with this; at least someone here pointed
> that out on:
> http://archive.netbsd.se/?ml=crm114-general&a=2007-12&t=5957112
>
> Any help much appreciated.
>
> Cheers,
> Ferenc
>   
I don't think any of us have worked with SELinux enough to just know 
what it should be set for: it depends massively on where and how you run 
it.. Can you set SELinux to 'permissive' mode and see if things work, 
and analyze the logs it reports to tune your SELinux?

And, are you using the latest release? Is the VM 64-bit? the latest 
release has a whole *stack* of modifications for 64-bit, and a lot of 
fixes of niggling old bugs.