Similar Problem with BackupPC un Ubuntu 14.04:
http://sourceforge.net/p/backuppc/mailman/backuppc-
users/thread/alpine.DEB.2.10.1505121831320.27187%40diaspar.physics.unc.edu/#msg34107271
Removing ssl start_tls from /etc/ldap.conf allows BackupPC to start.
Both applicaions using perl:
perl 5,
Similar Problem with BackupPC un Ubuntu 14.04:
http://sourceforge.net/p/backuppc/mailman/backuppc-
users/thread/alpine.DEB.2.10.1505121831320.27187%40diaspar.physics.unc.edu/#msg34107271
Removing ssl start_tls from /etc/ldap.conf allows BackupPC to start.
Both applicaions using perl:
perl 5,
Similar to John, I can confirm 2.10.1-1 from Debian also runs without
issue on my setup (thanks to John for the pointer and a bunch of the
digging on this one).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Similar to John, I can confirm 2.10.1-1 from Debian also runs without
issue on my setup (thanks to John for the pointer and a bunch of the
digging on this one).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in Ubuntu.
Also tried SSL with LDAPS on port 636, but still the same problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316293
Title:
unable to start
To manage notifications about this bug go to:
Reverted to an earlier snapshot of the virtual machine I was testing
amavisd on, then installed the latest Debian package of amavisd-new
(version 2.10.1-1) and can confirm that this works.
Could this be a candidate for a backport release?
Although I am still not sure of the cause of this bug.
CORRECTION: After updating the configuration and reverting to debugging
options I think the latest Debian package of amavisd-new (version
2.10.1-1) will run when STARTTLS is enabled in /etc/ldap.conf. Needs
more testing.
--
You received this bug notification because you are a member of Ubuntu
Reverted to an earlier snapshot of the virtual machine I was testing
amavisd on, then installed the latest Debian package of amavisd-new
(version 2.10.1-1) and can confirm that this works.
Could this be a candidate for a backport release?
Although I am still not sure of the cause of this bug.
Also tried SSL with LDAPS on port 636, but still the same problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in Ubuntu.
https://bugs.launchpad.net/bugs/1316293
Title:
unable to start
To manage notifications about
Also tried the latest Debian package of amavisd-new (version 2.10.1-1)
and that has the same problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316293
Title:
unable to start
To manage
Also tried the latest Debian package of amavisd-new (version 2.10.1-1)
and that has the same problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in Ubuntu.
https://bugs.launchpad.net/bugs/1316293
Title:
unable to
CORRECTION: After updating the configuration and reverting to debugging
options I think the latest Debian package of amavisd-new (version
2.10.1-1) will run when STARTTLS is enabled in /etc/ldap.conf. Needs
more testing.
--
You received this bug notification because you are a member of Ubuntu
Yes, I also have a few error messages containing amavis[1533]: nss-
ldap: do_open: do_start_tls failed:stat=-1.
Removing ssl start_tls from /etc/ldap.conf allows amavis to start. So
the problem looks to be when amavis checking libnss when it is set to
use LDAP with STARTTLS.
The TLS
Yes, I also have a few error messages containing amavis[1533]: nss-
ldap: do_open: do_start_tls failed:stat=-1.
Removing ssl start_tls from /etc/ldap.conf allows amavis to start. So
the problem looks to be when amavis checking libnss when it is set to
use LDAP with STARTTLS.
The TLS
I have meet this problem with email servers that have been upgraded from
Ubuntu 12.04 (precise) to Ubuntu 14.04 (trusty). Amavis starts at
boot and with the debug option, but fails to start via the init script
or the command line ('sudo -u amavis strace /usr/sbin/amavisd-new
start').
I have done
I have meet this problem with email servers that have been upgraded from
Ubuntu 12.04 (precise) to Ubuntu 14.04 (trusty). Amavis starts at
boot and with the debug option, but fails to start via the init script
or the command line ('sudo -u amavis strace /usr/sbin/amavisd-new
start').
I have done
I'm also running slapd on the affected box. Similar setup:
- amavis user and group are local
- only end user users and groups in ldap
Checking back a bit further in the logs, I did also find this in syslog:
Jan 11 21:59:06 bamboo amavis[2820]: nss-ldap: do_open: do_start_tls
failed:stat=-1
I'm
I'm also running slapd on the affected box. Similar setup:
- amavis user and group are local
- only end user users and groups in ldap
Checking back a bit further in the logs, I did also find this in syslog:
Jan 11 21:59:06 bamboo amavis[2820]: nss-ldap: do_open: do_start_tls
failed:stat=-1
I'm
Scratch my supposed fix.; the service started up fine after the reboot,
but failed after any subsequent restarts. I'm currently stuck running
it in debug as well. Box was installed as 14.04 x64 from scratch; not a
12.04 upgrade.
$ dpkg-query --show amavisd-new
amavisd-new 1:2.7.1-2ubuntu3
Scratch my supposed fix.; the service started up fine after the reboot,
but failed after any subsequent restarts. I'm currently stuck running
it in debug as well. Box was installed as 14.04 x64 from scratch; not a
12.04 upgrade.
$ dpkg-query --show amavisd-new
amavisd-new 1:2.7.1-2ubuntu3
I hit a similar issue. Happened to stumble across a forum post that
pointed to a non-qualified hostname in /etc/hostname. On my new 14.04
install I found I actually *did* have a non-qualified name in
/etc/hostname. I changed that to an FQDN, bounced the box, and amavis
then started up fine.
I hit a similar issue. Happened to stumble across a forum post that
pointed to a non-qualified hostname in /etc/hostname. On my new 14.04
install I found I actually *did* have a non-qualified name in
/etc/hostname. I changed that to an FQDN, bounced the box, and amavis
then started up fine.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: amavisd-new (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316293
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: amavisd-new (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in Ubuntu.
** Description changed:
- I have an issue on Ubuntu 14.04 (upgrade from 12.04) that when I enable
@bypass_spam_checks_maps = (%bypass_spam_checks, \@bypass_spam_checks_acl,
\$bypass_spam_checks_re);
+ I have an issue on Ubuntu 14.04 (upgrade from 12.04) that when I enable
** Description changed:
- I have an issue on Ubuntu 14.04 (upgrade from 12.04) that when I enable
@bypass_spam_checks_maps = (%bypass_spam_checks, \@bypass_spam_checks_acl,
\$bypass_spam_checks_re);
+ I have an issue on Ubuntu 14.04 (upgrade from 12.04) that when I enable
26 matches
Mail list logo
