Re: [Bug 1139159] Re: Postfix does not restart properly when using SSL
Just to note, there was also a single character change (from # to %) in the
first line of the patch to change the ".NEW" from being created as a
subdirectory of the target (and thus removed if new=1 ) to being on the
same level with ".NEW" appended (so the next mv succeeds)
On Sat, Mar 2, 2013 at 11:57 AM, LaMont Jones wrote:
> Finally saw what was meant there. Confirmed, doing the mkdir
> "${dest_dir}.NEW" will be unconditional (inside that box) as of 2.10.0-1
>
> ** Changed in: postfix (Ubuntu)
>Status: New => Confirmed
>
> ** Changed in: postfix (Ubuntu)
> Assignee: (unassigned) => LaMont Jones (lamont)
>
> ** Changed in: postfix (Ubuntu)
>Status: Confirmed => Fix Committed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1139159
>
> Title:
> Postfix does not restart properly when using SSL
>
> Status in “postfix” package in Ubuntu:
> Fix Committed
>
> Bug description:
> I was running into a problem where postfix would not start up
> correctly after being restarted (either manually, via automated
> process, or from reboot). Postfix would always start without its SSL
> certs in place (which caused a problem in my configuration); a
> subsequent restart would fix it, resulting in a situation where every-
> other-start was successful.
>
> I tracked the problem down to an issue in the init script that copies
> the certs from the SSL location to the postfix location. In a
> nutshell, it was creating a new directory for holding the copies files
> as subdirectory of the target, then deleting the target (including the
> "new" subdirectory), and subsequently failing to copy the new
> directory into the appropriate location.
>
> Patch that fixed the problem is attached.
>
> Using ubuntu server 12.10
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1139159/+subscriptions
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1139159
Title:
Postfix does not restart properly when using SSL
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1139159/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1139159] Re: Postfix does not restart properly when using SSL
It is /etc/ssl/certs/ Thanks, -B On Sat, Mar 2, 2013 at 11:42 AM, LaMont Jones wrote: > What is the value for smtp_tls_CApath in your configuration? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1139159 > > Title: > Postfix does not restart properly when using SSL > > Status in “postfix” package in Ubuntu: > New > > Bug description: > I was running into a problem where postfix would not start up > correctly after being restarted (either manually, via automated > process, or from reboot). Postfix would always start without its SSL > certs in place (which caused a problem in my configuration); a > subsequent restart would fix it, resulting in a situation where every- > other-start was successful. > > I tracked the problem down to an issue in the init script that copies > the certs from the SSL location to the postfix location. In a > nutshell, it was creating a new directory for holding the copies files > as subdirectory of the target, then deleting the target (including the > "new" subdirectory), and subsequently failing to copy the new > directory into the appropriate location. > > Patch that fixed the problem is attached. > > Using ubuntu server 12.10 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1139159/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1139159 Title: Postfix does not restart properly when using SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1139159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1139159] [NEW] Postfix does not restart properly when using SSL
Public bug reported: I was running into a problem where postfix would not start up correctly after being restarted (either manually, via automated process, or from reboot). Postfix would always start without its SSL certs in place (which caused a problem in my configuration); a subsequent restart would fix it, resulting in a situation where every-other-start was successful. I tracked the problem down to an issue in the init script that copies the certs from the SSL location to the postfix location. In a nutshell, it was creating a new directory for holding the copies files as subdirectory of the target, then deleting the target (including the "new" subdirectory), and subsequently failing to copy the new directory into the appropriate location. Patch that fixed the problem is attached. Using ubuntu server 12.10 ** Affects: postfix (Ubuntu) Importance: Undecided Status: New ** Patch added: "Patch for the postfix init script to fix the included issue." https://bugs.launchpad.net/bugs/1139159/+attachment/3553559/+files/postfix-init.patch ** Description changed: I was running into a problem where postfix would not start up correctly after being restarted (either manually, via automated process, or from reboot). Postfix would always start without its SSL certs in place (which caused a problem in my configuration); a subsequent restart would fix it, resulting in a situation where every-other-start was successful. - I tracked the problem down to an issue in the code that copies the certs - from the SSL location to the postfix location. In a nutshell, it was - creating a new directory for holding the copies files as subdirectory of - the target, then deleting the target (including the "new" subdirectory), - and subsequently failing to copy the new directory into the appropriate - location. + I tracked the problem down to an issue in the init script that copies + the certs from the SSL location to the postfix location. In a nutshell, + it was creating a new directory for holding the copies files as + subdirectory of the target, then deleting the target (including the + "new" subdirectory), and subsequently failing to copy the new directory + into the appropriate location. Patch that fixed the problem is attached. Using ubuntu server 12.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1139159 Title: Postfix does not restart properly when using SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1139159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 802081] Re: qemu raw/nocache fails to operate on LVM partition with 4k sector size
** Description changed: On the host machine, a disk is configured with 4k sector sizes: --- sudo fdisk /dev/sdd Disk /dev/sdd: 4000.6 GB, 4000627818496 bytes 255 heads, 63 sectors/track, 60797 cylinders Units = cylinders of 16065 * 4096 = 65802240 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0xf8eabb69 --- ... and when fdisking the lvm parition, also reports properly: --- Disk /dev/VMsVG/mail: 21.0 GB, 2097152 bytes 255 heads, 63 sectors/track, 318 cylinders Units = cylinders of 16065 * 4096 = 65802240 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x6a3bdb21 --- - However, within a VM using the LVM parition as a raw disk, its fdisk reports a 512 block size: + However, within a guest VM using the LVM parition as a raw disk, its fdisk reports a 512 block size: --- Disk /dev/vda: 21.0 GB, 2097152 bytes 16 heads, 63 sectors/track, 5079 cylinders Units = cylinders of 1008 * 4096 = 4128768 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x915c306a using cache=none, which is established practice for best performance on - raw devices, the host system repeatedly fails to write to the disk, due + raw devices, the guest system repeatedly fails to write to the disk, due to it trying to write 512 byte sectors while the backing is 4096. + + Both systems are using Ubuntu 11.04 server. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/802081 Title: qemu raw/nocache fails to operate on LVM partition with 4k sector size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/802081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 802081] [NEW] qemu raw/nocache fails to operate on LVM partition with 4k sector size
Public bug reported: On the host machine, a disk is configured with 4k sector sizes: --- sudo fdisk /dev/sdd Disk /dev/sdd: 4000.6 GB, 4000627818496 bytes 255 heads, 63 sectors/track, 60797 cylinders Units = cylinders of 16065 * 4096 = 65802240 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0xf8eabb69 --- ... and when fdisking the lvm parition, also reports properly: --- Disk /dev/VMsVG/mail: 21.0 GB, 2097152 bytes 255 heads, 63 sectors/track, 318 cylinders Units = cylinders of 16065 * 4096 = 65802240 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x6a3bdb21 --- However, within a VM using the LVM parition as a raw disk, its fdisk reports a 512 block size: --- Disk /dev/vda: 21.0 GB, 2097152 bytes 16 heads, 63 sectors/track, 5079 cylinders Units = cylinders of 1008 * 4096 = 4128768 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x915c306a using cache=none, which is established practice for best performance on raw devices, the host system repeatedly fails to write to the disk, due to it trying to write 512 byte sectors while the backing is 4096. ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: 4k kvm lvm qemu sector -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/802081 Title: qemu raw/nocache fails to operate on LVM partition with 4k sector size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/802081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
