[Bug 1730966] Re: Dovecot cannot bind to address on boot
I think you can safely close this. nginx is behaving just like dovecot, postfix even worse. It has to be something with the networking on my end. Sorry for the trouble. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730966 Title: Dovecot cannot bind to address on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1730966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730966] Re: Dovecot cannot bind to address on boot
The problem appears to disappear if I configure the additional addresses using multiple "iface eth0 inet static" blocks as described in "iproute2 method" https://wiki.debian.org/NetworkConfiguration#Multiple_IP_addresses_on_one_Interface -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730966 Title: Dovecot cannot bind to address on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1730966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730966] Re: Dovecot cannot bind to address on boot
The dedicated address for dovecot is configured in /etc/network/interfaces using up ip addr add 5.6.7.8/24 dev $IFACE within auto eth0 iface eth0 inet static address 1.2.3.4 netmask 255.255.255.0 gateway 1.2.3.1 dns-nameservers 10.10.10.10 20.20.20.20 The same goes for the IPv6. up ip addr add 2a02:1234:1234:1234::2/64 dev $IFACE within iface eth0 inet6 static address 2a02:1234:1234:1234::1 netmask 64 gateway fe80::1 accept_ra 0 autoconf 0 privext 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730966 Title: Dovecot cannot bind to address on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1730966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730966] Re: Dovecot cannot bind to address on boot
Follow-up: It won't work after network-online.target either. The only solution I have at the moment is letting it bind to 0.0.0.0 and :: The problem also occurs with nginx. Also, postfix doesn't start at all unless I remove the override.conf file. The weird thing is that it doesn't throw any error, nor does it write anything into the log. It will simply not start and systemctl reports that the process exited. I am slowly starting to think that something is screwed with systemd on my system which I upgraded from 17.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730966 Title: Dovecot cannot bind to address on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1730966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730966] Re: Dovecot cannot bind to address on boot
** Description changed: I have specified a hostname dovecot should bind to, but upon start, I get errors written to syslog such as "Cannot assign requested address". The hostname is specified in /etc/hosts for an IPv4 and IPv6 address and the IPs are registered in /etc/network/interfaces If I start the service after boot, everything works as expected. Maybe adding an override to start after network-online.target and systemd- - resolved.target would fix the problem. Postfix already has such a + resolved.service would fix the problem. Postfix already has such a config. I am running Ubuntu 17.10 and dovecot is 2.2.27-3ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730966 Title: Dovecot cannot bind to address on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1730966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730966] [NEW] Dovecot cannot bind to address on boot
Public bug reported: I have specified a hostname dovecot should bind to, but upon start, I get errors written to syslog such as "Cannot assign requested address". The hostname is specified in /etc/hosts for an IPv4 and IPv6 address and the IPs are registered in /etc/network/interfaces If I start the service after boot, everything works as expected. Maybe adding an override to start after network-online.target and systemd- resolved.target would fix the problem. Postfix already has such a config. I am running Ubuntu 17.10 and dovecot is 2.2.27-3ubuntu1 ** Affects: dovecot (Ubuntu) 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/1730966 Title: Dovecot cannot bind to address on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1730966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712899] Re: New release 2.2.32
Thanks for the info! :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712899 Title: New release 2.2.32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1712899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712899] Re: New release 2.2.32
Any news on this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712899 Title: New release 2.2.32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1712899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712899] Re: New release 2.2.32
What does next cycle mean? New Ubuntu major version? 2.2.31+ contain an welcome change which allows using both RSA and ECDSA certificates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712899 Title: New release 2.2.32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1712899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512002] Re: Annoying dialog "Authentication is required to change your own user data"
I don't know if this is related, but I have s imilar problem under Xubuntu 15.04 that is still present in 15.10. Everytime I lock my computer and come back and unlock it, I have one or multiple "Authentication is required to change your own user data" popups. It seems to be dependant on the time the PC was locked. If it was locked for two or three minutes, there's only one or maybe two authentication boxes that appear one after another. However, if I come back after lunch (30 minutes), I once had to enter the password 18 times, but usually it stops after 10 popups. Highly annoying. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512002 Title: Annoying dialog "Authentication is required to change your own user data" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1-gnome/+bug/1512002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 262679] Re: eeepc-acpi-scripts is not installable
On my 1005HGO (1005HAG with UMTS modem) running Xubuntu 10.10, the following keys work: Volume up (F12), Volume down (F11), Mute (F10), Brightness up (F6), Brightness down (F5) and Sleep (F1). The following keys do not work: Display off (F7), Mousepad off (F3), WLAN off (F2) and the non-keyboard button for turning off the mousepad. Since I don't have an external display to test, I cannot tell if the Switch dsplay (F8) key works. I also don't know what exactly the F4 key does. Its icon is a rectangle with rounded corners and inside there are four arrows pointing outwards to the edges - reminds me of a full-screen key or something. I also cannot test the F9 key that opens the task manager under Windows because I don't have any graphical task manager installed. By the way, all Fn keys that don't trigger special actions, such as Home, End, Page up, Page down, Num lock, etc. work fine. -- eeepc-acpi-scripts is not installable https://bugs.launchpad.net/bugs/262679 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
