[Bug 1068756] Re: IPv6 Privacy Extensions enabled on Ubuntu Server by default
I don't think you are correct. Here's why: the comments in the file mentioned in my original bug report (of which I actually included the full contents of the file) state the following: '2 - prefer privacy addresses and use them over the normal addresses.' Heavy emphasis on the word prefer. These addresses will be preferred for *ALL* IPv6 traffic. This means that for all outbound IPv6 traffic, unless explicitly bound, it will use the privacy extension address. Which is correct, this is what software *should* do. In addition to that, addresses brought up with privacy extension enabled are global addresses. So even if said software were to bring use the 'global' address they would get the privacy extension address as it is preferred. The kernel is working right, the software is working right, the bug is that the server image has this enabled by default. So in short, you're absolutely wrong. The server image should not have this enabled, and the software that is communicating over IPv6 is doing *exactly* what it should. It's using the preferred IPv6 address. I'm okay with this being enabled for desktops, but it has *no* place in server environments. -Tim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1068756 Title: IPv6 Privacy Extensions enabled on Ubuntu Server by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1068756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1068756] Re: IPv6 Privacy Extensions enabled on Ubuntu Server by default
The problem is that by default pieces of software will use that address when communicating over IPv6. Such as wget downloading a file over IPv6 or connecting to a system using SSH. This should absolutely not be the default for a server system. -Tim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1068756 Title: IPv6 Privacy Extensions enabled on Ubuntu Server by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1068756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1068756] [NEW] IPv6 Privacy Extensions enabled on Ubuntu Server by default
Public bug reported: Ubuntu 12.04 LTS and Ubuntu 12.10 server images both ship with the IPv6 Privacy Extensions enabled (as defined in RFC 4941[0]). Not only are they enabled, but these addresses are preferred over addresses obtained using SLAAC. While is may be considered a reasonable default on an image being used on a personal computer, it's not something that is sane to have enabled by default in a server environment. Having this extension enabled can wreak havoc if you are expecting a specific IPv6 address when you know the MAC addresses of your systems beforehand. The file that is responsible for causing this to be defaulted to enabled is: "/etc/sysctl.d/10-ipv6-privacy.conf". This file appears to be part of the procps package (as per the output of 'dpkg -S') and contains the following: # IPv6 Privacy Extensions (RFC 4941) # --- # IPv6 typically uses a device's MAC address when choosing an IPv6 address # to use in autoconfiguration. Privacy extensions allow using a randomly # generated IPv6 address, which increases privacy. # # Acceptable values: #0 - don’t use privacy extensions. #1 - generate privacy addresses #2 - prefer privacy addresses and use them over the normal addresses. net.ipv6.conf.all.use_tempaddr = 2 net.ipv6.conf.default.use_tempaddr = 2 In short, IPv6 privacy extensions should not be enabled by default when deploying an Ubuntu server image. In a server environment you should be able to reliably determine your IPv6 address based on the MAC address of the system. Thank you for taking the time to look in to this as well as consider changing the default behavior of Ubuntu server. -Tim Heckman [0] http://tools.ietf.org/html/rfc4941 ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Tags: networking precise quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1068756 Title: IPv6 Privacy Extensions enabled on Ubuntu Server by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1068756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980917] Re: Failed to create pty - disabling logging for job
James, Is it conceivable that we will see a fix released in time for the Ubuntu 12.04.1 release in August? I think it's taken quite a bit longer than need to triage this bug and determine the priority of the fix. It's affecting quite a large number of people on different platforms. I'm simply trying to understand what the priority is, if any, to get a fix in place. Are paying customers of Canonical still having this issue? Is this the type of support Ubuntu users can expect on an LTS release? PixMe: Not sure the comments of this bug are the proper place to get help for such an issue. I'm not familiar with Pandaboard, but I'm fairly certain this bug is completely unrelated. I'd suggest reaching out to the community forum. -Tim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980917 Title: Failed to create pty - disabling logging for job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/980917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980917] Re: Failed to create pty - disabling logging for job
Christopher: Would you be able to clarify how your upgrade going sideways is related to a bug in Upstart when /dev/pts isn't mounted by an initrd? -Tim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980917 Title: Failed to create pty - disabling logging for job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/980917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980917] Re: Failed to create pty - disabling logging for job
James: It seems that this is a chicken and egg problem when someone doesn't have an initramfs. I'm quite alright with logging being disabled if "/dev/pts" isn't mounted. The problem I have is the large amount of unhelpful errors that are printed on the console. If this could be a concise error, that would be great: "init: Failed to create pty - temporarily disabling job logging" And that should be the only error, in my opinion. On the opposing side, I can see where having the specific job that wasn't logged noted. However, that doesn't happen now. And if it flooded the console, I don't think I'd be for it. Again, without knowing how Upstart processes jobs (maybe I should fix that), I would probably be okay with something like: "init: Failed to create pty - disabling job logging for the following: Job1, Job2, Job3, etc." Simply add a job to the end of the comma-separated list if it isn't logged. -Tim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980917 Title: Failed to create pty - disabling logging for job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/980917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980917] Re: Failed to create pty - disabling logging for job
Hello James, Thank you for taking the time to look in to this bug as well as get back to me. The explanation of the issue definitely makes the problem more clear. However, I am intrigued by the fact that something so important is assumed, and that Upstart errors when it encounters something different (such as there being no initramfs thus /dev/pts not being mounted). However, I'm not intimately familiar with the inner workings, but I would hope there's a way to fix it without having to implement the '--no-log' workaround. The custom-compiled kernel that's being used to boot the system should have sufficient PTY support enabled: ~# zgrep -i "pty" /proc/config.gz CONFIG_UNIX98_PTYS=y CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=256 Thank you for the suggestion for the workaround. Sadly, I don't think that's something I can implement due to some restrictions with the environment that Ubuntu 12.04 LTS will be running in (at least in my case). But if this isn't something you guys are able to resolve in Upstart before release, alternative options may need to be looked at. I would also love to be able to have job logging enabled, as I feel it is an important addition to Upstart. Thank you again for your time, James. I look forward to seeing how this issue irons out. -Tim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980917 Title: Failed to create pty - disabling logging for job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/980917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980917] Re: Failed to create pty - disabling logging for job
** Tags added: precise ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980917 Title: Failed to create pty - disabling logging for job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/980917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 936667] Re: Upstart early job logging causes boot failure for systems with no initramfs (error is "No available ptys")
As I believe this issue is entirely separate from the bug this fixed, I opened a new bug report relating to the errors I am seeing on the hvc0 console as a guest in a Xen environment: - https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/980917 -Tim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/936667 Title: Upstart early job logging causes boot failure for systems with no initramfs (error is "No available ptys") To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/936667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980917] Re: Failed to create pty - disabling logging for job
** Description changed: I believe this bug is in Upstart due to similar bug that was recently fixed: - https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/936667 I am booting Ubuntu 12.04 LTS (x86) as a domU under Xen. After the previous bug was fixed, I still received the errors but the system now - boots. However, during the boot process I see a lot of these errors: + boots which is an improvement. During the boot process I see a few + combinations of this error: init: Failed to create pty - disabling logging for job init: Temporary process spawn error: No such file or directory - These combination of errors print, and then this line is spat out - multiple times: + After those two stop, I see a few more of these errors: init: Failed to create pty - disabling logging for job - I'm currently using a custom compiled kernel that exists outside of the - filesystem. The issue also is present on the Ubuntu-supplied Linux - kernel booted under PV-GRUB. + The above error also prints if I type "poweroff" or "shutdown" + + This system's ultimate destiny is to operate using a custom-compiled + Linux kernel that does not exist on the filesystem. Both the Ubuntu- + supplied Linux kernel and the custom-compiled Linux kernel are afflicted + by this bug. Any suggestions would be greatly appreciated. -Tim + + //edit: added more details, edited for clarity. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980917 Title: Failed to create pty - disabling logging for job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/980917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980917] [NEW] Failed to create pty - disabling logging for job
Public bug reported: I believe this bug is in Upstart due to similar bug that was recently fixed: - https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/936667 I am booting Ubuntu 12.04 LTS (x86) as a domU under Xen. After the previous bug was fixed, I still received the errors but the system now boots. However, during the boot process I see a lot of these errors: init: Failed to create pty - disabling logging for job init: Temporary process spawn error: No such file or directory These combination of errors print, and then this line is spat out multiple times: init: Failed to create pty - disabling logging for job I'm currently using a custom compiled kernel that exists outside of the filesystem. The issue also is present on the Ubuntu-supplied Linux kernel booted under PV-GRUB. Any suggestions would be greatly appreciated. -Tim ** Affects: upstart (Ubuntu) Importance: Undecided Status: New ** Description changed: I believe this bug is in Upstart due to similar bug that was recently fixed: - https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/936667 I am booting Ubuntu 12.04 LTS (x86) as a domU under Xen. After the previous bug was fixed, I still received the errors but the system now boots. However, during the boot process I see a lot of these errors: init: Failed to create pty - disabling logging for job init: Temporary process spawn error: No such file or directory These combination of errors print, and then this line is spat out multiple times: init: Failed to create pty - disabling logging for job I'm currently using a custom compiled kernel that exists outside of the - filesystem. The issue also is present on the distribution-supplied - Linux kernel. + filesystem. The issue also is present on the Ubuntu-supplied Linux + kernel. Any suggestions would be greatly appreciated. -Tim ** Description changed: I believe this bug is in Upstart due to similar bug that was recently fixed: - https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/936667 I am booting Ubuntu 12.04 LTS (x86) as a domU under Xen. After the previous bug was fixed, I still received the errors but the system now boots. However, during the boot process I see a lot of these errors: init: Failed to create pty - disabling logging for job init: Temporary process spawn error: No such file or directory These combination of errors print, and then this line is spat out multiple times: init: Failed to create pty - disabling logging for job I'm currently using a custom compiled kernel that exists outside of the filesystem. The issue also is present on the Ubuntu-supplied Linux - kernel. + kernel booted under PV-GRUB. Any suggestions would be greatly appreciated. -Tim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980917 Title: Failed to create pty - disabling logging for job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/980917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 936667] Re: Upstart early job logging causes boot failure for systems with no initramfs (error is "No available ptys")
I'm still getting this error when booting 12.04 as a domU with the 1.5-0ubuntu1 Upstart package installed. The system does boot, and I am able to get to my console. However, the hvc0 console is initially flooded with these messages. Any ideas? -Tim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/936667 Title: Upstart early job logging causes boot failure for systems with no initramfs (error is "No available ptys") To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/936667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
