** Changed in: postfix (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753470
Title:
Postconf segfaults every 5 minutes
To manage notifications about
FYI, this is fixed in 3.3.1 upstream, so when that lands, this diff can
be dropped.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753470
Title:
Postconf segfaults every 5 minutes
To manage
This bug was fixed in the package postfix - 3.3.0-1ubuntu0.1
---
postfix (3.3.0-1ubuntu0.1) bionic; urgency=medium
* debian/patches/fix-postconf-segfault.diff: Fix a postconf segfault
when map file cannot be read. Thanks to Viktor Dukhovni . (LP: #1753470)
-- Karl Stenerud
SRU verification on Bionic:
root@bp1:~# dpkg -l| grep postfix
ii postfix 3.3.0-1 amd64 High-performance mail transport agent
root@bp1:~# sudo -u ubuntu /usr/sbin/postconf virtual_alias_map
Segmentation fault
root@bp1:~# apt-get -qq update && apt-get install -V postfix
...
The following
Hello Ari, or anyone else affected,
Accepted postfix into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/postfix/3.3.0-1ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
- [Original Description]
-
- Fresh install of 18.04 server. Every 5 minutes postconf segfaults:
-
- Mar 5 14:30:05 hostname-here kernel: [ 672.082204] postconf[12975]: segfault
at 40 ip 564d613ff053 sp 7ffc39e19b90 error 4 in
postconf[564d613e7000+25000]
- Mar
** Description changed:
+ [Original Description]
+
Fresh install of 18.04 server. Every 5 minutes postconf segfaults:
- Mar 5 14:30:05 hostname-here kernel: [ 672.082204] postconf[12975]:
segfault at 40 ip 564d613ff053 sp 7ffc39e19b90 error 4 in
postconf[564d613e7000+25000]
-
** Merge proposal linked:
https://code.launchpad.net/~kstenerud/ubuntu/+source/postfix/+git/postfix/+merge/353267
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753470
Title:
Postconf segfaults
** Changed in: postfix (Ubuntu Bionic)
Assignee: (unassigned) => Karl (kstenerud)
** Changed in: postfix (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It's not forgotten, in fact, I have the ideal candidate to work on this
bug :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753470
Title:
Postconf segfaults every 5 minutes
To manage
It's not forgotten, in fact, I have the ideal candidate to work on this
bug :)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1753470
Title:
Postconf segfaults every 5 minutes
To manage
Anything new here? Still experiencing this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753470
Title:
Postconf segfaults every 5 minutes
To manage notifications about this bug go to:
** Tags added: bitesize
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1753470
Title:
Postconf segfaults every 5 minutes
To manage notifications about this bug go to:
** Tags added: bitesize
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753470
Title:
Postconf segfaults every 5 minutes
To manage notifications about this bug go to:
** Package changed: update (Ubuntu) => postfix (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753470
Title:
Postconf segfaults every 5 minutes
To manage notifications about this bug go
** Package changed: postfix (Ubuntu) => update (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753470
Title:
Postconf segfaults every 5 minutes
To manage notifications about this bug go
** Changed in: postfix (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753470
Title:
Postconf segfaults every 5 minutes
To manage notifications about this bug
** Changed in: postfix (Ubuntu Bionic)
Milestone: None => bionic-updates
** Changed in: postfix (Ubuntu Bionic)
Status: New => Triaged
** Changed in: postfix (Ubuntu Bionic)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
** Also affects: postfix (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753470
Title:
Postconf segfaults every 5 minutes
To manage
** Changed in: postfix (Ubuntu Bionic)
Milestone: None => bionic-updates
** Changed in: postfix (Ubuntu Bionic)
Status: New => Triaged
** Changed in: postfix (Ubuntu Bionic)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
** Bug watch added: Debian Bug tracker #898271
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898271
** Also affects: postfix (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898271
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Bug watch added: Debian Bug tracker #898271
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898271
** Also affects: postfix (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898271
Importance: Unknown
Status: Unknown
--
You received this bug notification
This bug was fixed in the package postfix - 3.3.0-1ubuntu1
---
postfix (3.3.0-1ubuntu1) cosmic; urgency=medium
* debian/patches/fix-postconf-segfault.diff: Fix a postconf segfault
when map file cannot be read. Thanks to Viktor Dukhovni . (LP: #1753470)
-- Andreas Hasenack
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/postfix/+git/postfix/+merge/345296
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753470
Title:
Postconf segfaults
** Changed in: postfix (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: postfix (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
** Changed in: postfix (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: postfix (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Monday, May 07, 2018 08:56:52 PM you wrote:
> Thanks Scott, I did email postfix-users with subject "NULL pointer deref
> in pcf_check_dbms_client() with unreadable map file", but I'm not
> subscribed. Checking the archive at https://marc.info/?l=postfix->
> users=1=201805=2 doesn't show my
Thanks Scott, I did email postfix-users with subject "NULL pointer deref
in pcf_check_dbms_client() with unreadable map file", but I'm not
subscribed. Checking the archive at https://marc.info/?l=postfix-
users=1=201805=2 doesn't show my message, so I guess I should
subscribe. Or perhaps it's just
Thanks Scott, I did email postfix-users with subject "NULL pointer deref
in pcf_check_dbms_client() with unreadable map file", but I'm not
subscribed. Checking the archive at https://marc.info/?l=postfix-
users=1=201805=2 doesn't show my message, so I guess I should
subscribe. Or perhaps it's just
On Monday, May 07, 2018 03:43:26 PM you wrote:
> I think the only contact to the developers is their postfix-devel
> mailing list here:
>
> http://www.postfix.org/lists.html
postfix-devel is generally for developers of postfix. Users should use
postfix-users (even for code issues like this).
On Monday, May 07, 2018 04:47:07 PM you wrote:
> And this is new in 3.3.0. I was also looking for some git/svn/bzr/cvs
> repository to check the history of these changes, but couldn't find it.
This is maintained by one of the primary postfix developers:
https://github.com/vdukhovni/postfix
It's
On Monday, May 07, 2018 03:14:56 PM you wrote:
> vstream_fopen() did return 0 and errno was set to EACCES, I don't know
> why that check is excluding the permission problem. I emailed upstream
> (couldn't find a bugtracker for it).
There is no postfix bugtracker upstream. Did you mail the
And this is new in 3.3.0. I was also looking for some git/svn/bzr/cvs
repository to check the history of these changes, but couldn't find it.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
And this is new in 3.3.0. I was also looking for some git/svn/bzr/cvs
repository to check the history of these changes, but couldn't find it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753470
I think the only contact to the developers is their postfix-devel
mailing list here:
http://www.postfix.org/lists.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753470
Title:
Postconf
The crash happens in vstream_fileno(fp), because fp is a null pointer:
if ((fp = vstream_fopen(cf_file, O_RDONLY, 0)) == 0
&& errno != EACCES) {
msg_warn("open \"%s\" configuration \"%s\": %m",
dp->db_type, cf_file);
The crash happens in vstream_fileno(fp), because fp is a null pointer:
if ((fp = vstream_fopen(cf_file, O_RDONLY, 0)) == 0
&& errno != EACCES) {
msg_warn("open \"%s\" configuration \"%s\": %m",
dp->db_type, cf_file);
** Changed in: postfix (Ubuntu)
Importance: Medium => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753470
Title:
Postconf segfaults every 5 minutes
To manage notifications about this bug
** Changed in: postfix (Ubuntu)
Importance: Medium => Low
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1753470
Title:
Postconf segfaults every 5 minutes
To manage notifications
Agreed, and I can still reproduce this in bionic with postfix 3.3.0-1:
ubuntu@bionic-postfix:~$ postconf virtual_alias_map
Segmentation fault (core dumped)
ubuntu@bionic-postfix:~$ dpkg-query -W postfix
postfix 3.3.0-1
ubuntu@bionic-postfix:~$ ll /etc/postfix/valiases.cf
-rw-r- 1 root root
Agreed, and I can still reproduce this in bionic with postfix 3.3.0-1:
ubuntu@bionic-postfix:~$ postconf virtual_alias_map
Segmentation fault (core dumped)
ubuntu@bionic-postfix:~$ dpkg-query -W postfix
postfix 3.3.0-1
ubuntu@bionic-postfix:~$ ll /etc/postfix/valiases.cf
-rw-r- 1 root root
[Expired for postfix (Ubuntu) because there has been no activity for 60
days.]
** Changed in: postfix (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I finally found the actual culprit. It's a Munin-plugin that gets
Postfix statistics, it calls postconf to figure out Postfix paths.
While the issue is now clear, I think the symptom is still out there,
you can crash postconf if you run it with a user that doesn't have
permissions to read every
I think I got it now.
Postconf can't read valiases.cf as user Postfix. I changed the file
ownership and permission to allow group postfix to read it, which makes
running postconf as user postfix work now.
Curiously the segfault still happens every 5 minutes.
--
You received this bug
After some "yank out lines until the issue stops" detective work, I
think I've traced the issue to be this line in Postfix's main.cf:
virtual_alias_maps = pgsql:/etc/postfix/valiases.cf
valiases.cf is very basic example of PostgreSQL based alias maps
configuration:
query = SELECT real_address
Do you have mail in the queue? -> sudo mailq
Do you have another 5min cron job that is perhaps failing and therefore
sending an email?
Can you see any ownership and permissions problems in the postfix
directories? Try "sudo postfix check", and maybe do a quick manual
inspection in /var/spool,
Do you have mail in the queue? -> sudo mailq
Do you have another 5min cron job that is perhaps failing and therefore
sending an email?
Can you see any ownership and permissions problems in the postfix
directories? Try "sudo postfix check", and maybe do a quick manual
inspection in /var/spool,
The AppArmor error message appears to be related to already reported
but, and is unrelated. Stunnel was work-in-progress so that's not a
problem. Livepatchd doesn't start because 18.04 doesn't currently have
Live patch support yet.
** Attachment added: "df.txt"
** Attachment added: "syslog.txt"
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1753470/+attachment/5071338/+files/syslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753470
Title:
The problem leaves no traces in any of the logs, but then again I can't
find anything that wouldn't work either. Postfix works just fine.
There's no crontab jobs or anything that would fire sending a message or
anything, besides sending messages works fine as well, with no error
messages. It's
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1753470/+attachment/5071339/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753470
Title:
Thanks for filing this bug in Ubuntu.
Do you know what is making this call every 5min? I couldn't locate a
cronjob about it.
You seem to have other services also failing to start:
-- Logs begin at Tue 2018-02-27 14:59:49 EET, end at Mon 2018-03-05 14:25:05
EET. --
Mar 05 14:19:03 hostname
Thanks for filing this bug in Ubuntu.
Do you know what is making this call every 5min? I couldn't locate a
cronjob about it.
You seem to have other services also failing to start:
-- Logs begin at Tue 2018-02-27 14:59:49 EET, end at Mon 2018-03-05 14:25:05
EET. --
Mar 05 14:19:03 hostname
53 matches
Mail list logo
