1 Topic by prib

  • prib
  • Member
  • Offline
  • Registered: 2011-06-08
  • Posts: 3

Topic: Policyd Segmentation Fault

Hello,

I recently moved our iRedMail 0.61 installation from a dedicated server to an Amazon EC2 micro instance. It's working just fine, but I had to remove "check_policy_service inet:127.0.0.1:10031" from "smtpd_recipient_restrictions" in "/etc/postfix/main.cf", otherwise I could not receive e-mails.
The problem is that when I try to run postfix-policyd, I get:

starting policyd v1.82
Segmentation fault

I have already enabled debugging in /etc/postfix-policyd.conf, but nothing shows up in mail.info or mail.log.
Anyone has any clue on this one?

Thanks,
paulo

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,088

Re: Policyd Segmentation Fault

Not sure why it happened, it could be something wrong with Amazon EC2 OS.

3 Reply by prib (edited by prib 2011-06-08 20:15:52)

  • prib
  • Member
  • Offline
  • Registered: 2011-06-08
  • Posts: 3

Re: Policyd Segmentation Fault

I forgot to say that I'm using exactly the same OS as before: Ubuntu 10.04 LTS.

And if I run "strace /usr/sbin/postfix-policyd restart" the last output lines are:

write(1, "starting policyd v1.82\n", 23starting policyd v1.82
) = 23
getrlimit(RLIMIT_NOFILE, {rlim_cur=1024, rlim_max=1024}) = 0
setrlimit(RLIMIT_NOFILE, {rlim_cur=4097, rlim_max=4097}) = 0
socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 3
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Segmentation fault

So the problem seems to be in the socket() line.

4 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,088

Re: Policyd Segmentation Fault

prib wrote:

I forgot to say that I'm using exactly the same OS as before: Ubuntu 10.04 LTS.

Still no idea. Are you running the latest Ubuntu 10.04.x?

5 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,088

Re: Policyd Segmentation Fault

prib wrote:

I forgot to say that I'm using exactly the same OS as before: Ubuntu 10.04 LTS.

Still no idea. Are you running the latest Ubuntu 10.04.x?

6 Reply by prib

  • prib
  • Member
  • Offline
  • Registered: 2011-06-08
  • Posts: 3

Re: Policyd Segmentation Fault

ZhangHuangbin wrote:

Still no idea. Are you running the latest Ubuntu 10.04.x?

Yes, it's Ubuntu 10.04.2 LTS.

7 Reply by xelaboy

  • xelaboy
  • Member
  • Offline
  • Registered: 2011-07-08
  • Posts: 2

Re: Policyd Segmentation Fault

I know I am bringing up an old thread, but I really really would like to know what came of this.

I'm in the same situation and really need policyd working

I commented it out of my main.cf but of course now I am getting a ton of spam everywhere.

Did you fix it? If so what do I need to do to fix it? (This thread comes up pretty quick in google so it would be good if there was a fix here.)

8 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,088

Re: Policyd Segmentation Fault

Did you try to re-install it? Are you using official Ubuntu apt repositories?

9 Reply by xelaboy

  • xelaboy
  • Member
  • Offline
  • Registered: 2011-07-08
  • Posts: 2

Re: Policyd Segmentation Fault

Yes I am. I have not.

How would I re-install policyd?

10 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,088

Re: Policyd Segmentation Fault

Use the built-in package management tool, e.g. yum, apt-get/dpkg, etc.

11 Reply by gregw

  • gregw
  • Member
  • Offline
  • Registered: 2012-01-07
  • Posts: 1

Re: Policyd Segmentation Fault

xelaboy wrote:

I know I am bringing up an old thread,
Did you fix it? If so what do I need to do to fix it? (This thread comes up pretty quick in google so it would be good if there was a fix here.)

for what it is worth,  I was having the same issue too till I realized i was trying to start an older policyd (1.82) process using the newer config file (from 2.0.11).   

my strace output produced the same error as you had:

getrlimit(RLIMIT_NOFILE, {rlim_cur=1024, rlim_max=1024}) = 0
setrlimit(RLIMIT_NOFILE, {rlim_cur=4097, rlim_max=4097}) = 0
socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 3
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Segmentation fault


if you haven't figured it out by now(i see this is an older posting),  make sure everything is in sync.

-g