[Bug 1550784] Re: kea dhcp server daemons brought up before networking

2016-10-19 Thread Hugo Slabbert 
@Halvor

Yes; no joy on that.

My understanding is that systemd-networkd-wait-online is only effective
if you're running systemd-networkd, which I'm not, as this is a vanilla
Ubuntu 16.04 *server* instance, with ifupdown, not NetworkManager or
systemd-networkd.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550784

Title:
  kea dhcp server daemons brought up before networking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-kea/+bug/1550784/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1550784] Re: kea dhcp server daemons brought up before networking

2016-09-12 Thread Hugo Slabbert 
This seems to be more than just kea affected.  From what I can tell,
systemd's network-online.target and network.target are basically useless
on 16.04 server.  I'm running 16.04 server with ifupdown, which is stock
as far as I can tell, so I'm running neither systemd-networkd or
NetworkManager and any references to network.target or network-
online.target in systemd unit definitions seem to do nothing.

This works around it successfully:

http://unix.stackexchange.com/questions/209832/debian-systemd-network-
online-target-not-working

...but we really shouldn't have to write shell wrappers around ifquery
in a systemd unit definition just to get a daemon to wait for network,
IMHO.

$ uname -a
Linux cherry 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

$ dpkg --get-selections | grep ifup
ifupdowninstall

$ dpkg -s systemd
Package: systemd
Status: install ok installed
Priority: important
Section: admin
Installed-Size: 18792
Maintainer: Ubuntu Developers 
Architecture: amd64
Multi-Arch: foreign
Version: 229-4ubuntu7
Replaces: systemd-services, udev (<< 228-5)
Provides: systemd-services
Depends: libacl1 (>= 2.2.51-8), libapparmor1 (>= 2.9.0-3+exp2), libaudit1 (>= 
1:2.2.1), libblkid1 (>= 2.19.1), libcap2 (>= 1:2.10), libcryptsetup4 (>= 
2:1.4.3), libgpg-error0 (>= 1.14), libkmod2 (>= 5~), libmount1 (>= 2.26.2), 
libpam0g (>= 0.99.7.1), libseccomp2 (>= 2.1.0), libselinux1 (>= 2.1.9), 
libsystemd0 (= 229-4ubuntu7), util-linux (>= 2.27.1), mount (>= 2.26), adduser, 
libcap2-bin
Pre-Depends: libc6 (>= 2.17), libgcrypt20 (>= 1.6.1), liblzma5 (>= 
5.1.1alpha+20120614), libselinux1 (>= 1.32)
Recommends: libpam-systemd, dbus
Suggests: systemd-ui, systemd-container
Breaks: apparmor (<< 2.9.2-1), ifupdown (<< 0.8.5~), lsb-base (<< 4.1+Debian4), 
lvm2 (<< 2.02.104-1), systemd-shim (<< 8-2), udev (<< 228-5)
Conflicts: klogd, systemd-services
Conffiles:
 /etc/dbus-1/system.d/org.freedesktop.hostname1.conf 
f55c94d000b5d62b5f06d38852977dd1
 /etc/dbus-1/system.d/org.freedesktop.locale1.conf 
5893ab03e7e96aa3759baceb4dd04190
 /etc/dbus-1/system.d/org.freedesktop.login1.conf 
4aac4fe1a99c9fca83c85b80e4e0c2ba
 /etc/dbus-1/system.d/org.freedesktop.network1.conf 
162e9a90d8f824f79ef2c6390827ec7b
 /etc/dbus-1/system.d/org.freedesktop.resolve1.conf 
6969148b4616c56a5c9065cec5ab0775
 /etc/dbus-1/system.d/org.freedesktop.systemd1.conf 
846824928e39a465c06c3aae53510535
 /etc/dbus-1/system.d/org.freedesktop.timedate1.conf 
682369fbf3de26b21e775732c89a2bbe
 /etc/dhcp/dhclient-exit-hooks.d/timesyncd a891f21f45b0648b7082d999bf424591
 /etc/pam.d/systemd-user 3bdb96b18046bd209135cdfe73421db6
 /etc/systemd/bootchart.conf 7cb6c9cab8ec511882e0e05fceb87e45
 /etc/systemd/journald.conf d928a3ce9f51fcff8ed925270f14a2aa
 /etc/systemd/logind.conf 5b41bb868487d1013382b738f6648328
 /etc/systemd/resolved.conf cc77726b02979ddc8b034a338f7bdea9
 /etc/systemd/system.conf 1340491c660f9eb234c92fe1225ff427
 /etc/systemd/timesyncd.conf 4e1cf2b5f85dff6c1f186135b9f66a85
 /etc/systemd/user.conf 2eaf5976751be8864d0555f30814d832
Description: system and service manager
 systemd is a system and service manager for Linux. It provides aggressive
 parallelization capabilities, uses socket and D-Bus activation for starting
 services, offers on-demand starting of daemons, keeps track of processes
 using Linux control groups, supports snapshotting and restoring of the system
 state, maintains mount and automount points and implements an elaborate
 transactional dependency-based service control logic.
 .
 systemd is compatible with SysV and LSB init scripts and can work as a
 drop-in replacement for sysvinit.
 .
 Installing the systemd package will not switch your init system unless you
 boot with init=/bin/systemd or install systemd-sysv in addition.
Homepage: http://www.freedesktop.org/wiki/Software/systemd
Original-Maintainer: Debian systemd Maintainers 


$ dpkg -s kea-dhcp4-server
Package: kea-dhcp4-server
Status: install ok installed
Priority: extra
Section: net
Installed-Size: 1126
Maintainer: Ubuntu Developers 
Architecture: amd64
Source: isc-kea
Version: 1.0.0-1build1
Depends: kea-common (= 1.0.0-1build1), libc6 (>= 2.4), libgcc1 (>= 1:3.0), 
libstdc++6 (>= 5.2)
Suggests: kea-doc
Conffiles:
 /etc/init.d/kea-dhcp4-server d6fd55ff46468ab22f7ffe45c69ee12c
 /etc/kea/kea-dhcp4.conf 55ecde1ffcdbaef3986557df293c842a
Description: ISC KEA IPv4 DHCP server
 KEA is an IPv4 and IPv6 DHCP server developed by Internet Systems Consortium
 providing a very high-performance with PostgreSQL, MySQL and memfile backends.
 .
 This package provides the IPv4 DHCP server.
Original-Maintainer: Adam Majer 
Homepage: http://kea.isc.org/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

[Bug 1316293] Re: unable to start

2015-01-18 Thread Hugo Slabbert 
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.
https://bugs.launchpad.net/bugs/1316293

Title:
  unable to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1316293/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1316293] Re: unable to start

2015-01-18 Thread Hugo Slabbert 
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.
https://bugs.launchpad.net/bugs/1316293

Title:
  unable to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1316293/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1316293] Re: unable to start

2015-01-14 Thread Hugo Slabbert 
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 out at the moment but will check further this evening if perhaps
there are some TLS issues to clean up with slapd on that box that could
be causing amavis issues.

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1316293/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1316293] Re: unable to start

2015-01-14 Thread Hugo Slabbert 
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 out at the moment but will check further this evening if perhaps
there are some TLS issues to clean up with slapd on that box that could
be causing amavis issues.

-- 
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1316293/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1316293] Re: unable to start

2015-01-11 Thread Hugo Slabbert 
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

uname is 3.13.0-43-generic

mail logs are similar:
Jan 11 22:24:02 bamboo amavis[5657]: logging initialized, log level 5, syslog: 
amavis.mail
Jan 11 22:24:02 bamboo amavis[5657]: starting. /usr/sbin/amavisd-new at 
bamboo.slabnet.com amavisd-new-2.7.1 (20120429), Unicode aware, 
LANG=en_US.UTF-8
Jan 11 22:24:02 bamboo amavis[5657]: perl=5.018002, user=, EUID: 128 (128);  
group=, EGID: 138 138 (138 138)
Jan 11 22:24:02 bamboo amavis[5657]: INFO: no optional modules: Unix::Getrusage
Jan 11 22:24:02 bamboo amavis[5657]: SpamControl: attempting to load scanner 
SpamAssassin, module Amavis::SpamControl::SpamAssassin
Jan 11 22:24:02 bamboo amavis[5657]: SpamControl: scanner SpamAssassin, module 
Amavis::SpamControl::SpamAssassin
Jan 11 22:24:02 bamboo amavis[5657]: INFO: SA version: 3.4.0, 3.004000, no 
optional modules: Encode::Detect IP::Country::Fast auto::NetAddr::IP::full6 
auto::NetAddr::IP:
:Util::inet_n2dx auto::NetAddr::IP::Util::inet_n2ad 
auto::NetAddr::IP::Util::inet_any2n auto::NetAddr::IP::Util::ipv6_aton
Jan 11 22:24:02 bamboo amavis[5657]: SpamControl: init_pre_chroot on 
SpamAssassin done
Jan 11 22:24:02 bamboo amavis[5657]: bind to /var/lib/amavis/amavisd.sock|unix, 
127.0.0.1:10024/tcp

...then nothing, though amavisd-new runs fine in debug in the foreground
as per original poster's report.

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1316293/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1316293] Re: unable to start

2015-01-11 Thread Hugo Slabbert 
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

uname is 3.13.0-43-generic

mail logs are similar:
Jan 11 22:24:02 bamboo amavis[5657]: logging initialized, log level 5, syslog: 
amavis.mail
Jan 11 22:24:02 bamboo amavis[5657]: starting. /usr/sbin/amavisd-new at 
bamboo.slabnet.com amavisd-new-2.7.1 (20120429), Unicode aware, 
LANG=en_US.UTF-8
Jan 11 22:24:02 bamboo amavis[5657]: perl=5.018002, user=, EUID: 128 (128);  
group=, EGID: 138 138 (138 138)
Jan 11 22:24:02 bamboo amavis[5657]: INFO: no optional modules: Unix::Getrusage
Jan 11 22:24:02 bamboo amavis[5657]: SpamControl: attempting to load scanner 
SpamAssassin, module Amavis::SpamControl::SpamAssassin
Jan 11 22:24:02 bamboo amavis[5657]: SpamControl: scanner SpamAssassin, module 
Amavis::SpamControl::SpamAssassin
Jan 11 22:24:02 bamboo amavis[5657]: INFO: SA version: 3.4.0, 3.004000, no 
optional modules: Encode::Detect IP::Country::Fast auto::NetAddr::IP::full6 
auto::NetAddr::IP:
:Util::inet_n2dx auto::NetAddr::IP::Util::inet_n2ad 
auto::NetAddr::IP::Util::inet_any2n auto::NetAddr::IP::Util::ipv6_aton
Jan 11 22:24:02 bamboo amavis[5657]: SpamControl: init_pre_chroot on 
SpamAssassin done
Jan 11 22:24:02 bamboo amavis[5657]: bind to /var/lib/amavis/amavisd.sock|unix, 
127.0.0.1:10024/tcp

...then nothing, though amavisd-new runs fine in debug in the foreground
as per original poster's report.

-- 
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1316293/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1316293] Re: unable to start

2015-01-08 Thread Hugo Slabbert 
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.

Perhaps give that a shot?

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1316293/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1316293] Re: unable to start

2015-01-08 Thread Hugo Slabbert 
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.

Perhaps give that a shot?

-- 
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1316293/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs