[Bug 1306877] Re: sshd stops accepting new connections after configuration reload
This is the change I mentioned above: https://github.com/nya3jp/openssh-debian/commit/0334ce32304e9ba2a10ee5ca49ca6e8ff3ba6cf4 As a workaround, I commented out these two lines in /etc/init/ssh.conf: # env SSH_SIGSTOP=1 # expect stop Now initctl reload ssh works fine, though I'm not really sure I'm doing a right thing. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1306877 Title: sshd stops accepting new connections after configuration reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1306877/+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 1299802] Re: upgrade-juju 1.16.6 - 1.18 (tip) fails
** Branch linked: lp:ubuntu/trusty-proposed/juju-core -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1299802 Title: upgrade-juju 1.16.6 - 1.18 (tip) fails To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1299802/+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 1306208] Re: juju scp no longer allows multiple extra arguments to pass throug
** Branch linked: lp:ubuntu/trusty-proposed/juju-core -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1306208 Title: juju scp no longer allows multiple extra arguments to pass throug To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1306208/+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 1303697] Re: peer relation disappears during upgrade of juju
** Branch linked: lp:ubuntu/trusty-proposed/juju-core -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1303697 Title: peer relation disappears during upgrade of juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1303697/+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 1306296] Re: juju cannot downgrade to same major.minor version with earlier patch number
** Branch linked: lp:ubuntu/trusty-proposed/juju-core -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1306296 Title: juju cannot downgrade to same major.minor version with earlier patch number To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1306296/+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 1303735] Re: public-address change to internal bridge post juju-upgrade
** Branch linked: lp:ubuntu/trusty-proposed/juju-core -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1303735 Title: public-address change to internal bridge post juju-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1303735/+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 1303880] Re: Juju 1.18.0, can not deploy local charms without series
** Branch linked: lp:ubuntu/trusty-proposed/juju-core -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1303880 Title: Juju 1.18.0, can not deploy local charms without series To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1303880/+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 1305839] Re: FFe: Support for Third Party Driver Installation
The key difference in my mind is recoverability. In the server case, the install is by nature largely automated, and often will fail altogether if you don't for example have the ability to configure your hard drives. Perhaps an analogy for the desktop would be to ask the question - what if a popular, common device that was required for system installation in a large percentage of cases required a non-free driver to be on the disk and used by default. We would certainly opt to make that device installable; consider our approach on phones, where we accept binary blobs and invest a lot to deliver a free userspace. I don't think we're crossing a significant new line here. There are many pieces of no-charge proprietary software we COULD be installing to make the product better, but we don't, given our values. In this case, I see no moral high ground in crippling the install unless someone answered an ideological question. We often forget how hard it is for new users to come up to speed - we know all the permutations and combinations and tradeoffs, most users do not. Consider also how comfortable we are enabling people to run Ubuntu on proprietary clouds - where they will never see the code beneath the code, as it were. Having said all this, I didn't clarify earlier that this mechanism should only be used for hardware which has no free driver. We should always silently select the free driver if such a driver exists, and if people want to go hunting for a proprietary one, ensure they can find them in a standard, supportable, upgradeable fashion, but not use it by default. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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 1306208] Re: juju scp no longer allows multiple extra arguments to pass throug
This bug was fixed in the package juju-core - 1.18.1-0ubuntu1 --- juju-core (1.18.1-0ubuntu1) trusty; urgency=medium * New upstream point release, including fixes for: - Upgrading juju 1.16.6 - 1.18.x fails (LP: #1299802). - Peer relation disappears during juju-upgrade (LP: #1303697). - public-address of units changes to internal bridge post upgrade (LP: #1303735). - Unable to deploy local charms without series (LP: #1303880). - juju scp no longer allows multiple extra arguments to be passed (LP: #1306208). - juju cannot downgrade to same major.minor version with earlier patch number (LP: #1306296). -- James Page james.p...@ubuntu.com Sat, 12 Apr 2014 07:04:37 +0100 ** Changed in: juju-core (Ubuntu Trusty) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1306208 Title: juju scp no longer allows multiple extra arguments to pass throug To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1306208/+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 1306296] Re: juju cannot downgrade to same major.minor version with earlier patch number
This bug was fixed in the package juju-core - 1.18.1-0ubuntu1 --- juju-core (1.18.1-0ubuntu1) trusty; urgency=medium * New upstream point release, including fixes for: - Upgrading juju 1.16.6 - 1.18.x fails (LP: #1299802). - Peer relation disappears during juju-upgrade (LP: #1303697). - public-address of units changes to internal bridge post upgrade (LP: #1303735). - Unable to deploy local charms without series (LP: #1303880). - juju scp no longer allows multiple extra arguments to be passed (LP: #1306208). - juju cannot downgrade to same major.minor version with earlier patch number (LP: #1306296). -- James Page james.p...@ubuntu.com Sat, 12 Apr 2014 07:04:37 +0100 ** Changed in: juju-core (Ubuntu Trusty) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1306296 Title: juju cannot downgrade to same major.minor version with earlier patch number To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1306296/+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 1299802] Re: upgrade-juju 1.16.6 - 1.18 (tip) fails
This bug was fixed in the package juju-core - 1.18.1-0ubuntu1 --- juju-core (1.18.1-0ubuntu1) trusty; urgency=medium * New upstream point release, including fixes for: - Upgrading juju 1.16.6 - 1.18.x fails (LP: #1299802). - Peer relation disappears during juju-upgrade (LP: #1303697). - public-address of units changes to internal bridge post upgrade (LP: #1303735). - Unable to deploy local charms without series (LP: #1303880). - juju scp no longer allows multiple extra arguments to be passed (LP: #1306208). - juju cannot downgrade to same major.minor version with earlier patch number (LP: #1306296). -- James Page james.p...@ubuntu.com Sat, 12 Apr 2014 07:04:37 +0100 ** Changed in: juju-core (Ubuntu Trusty) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1299802 Title: upgrade-juju 1.16.6 - 1.18 (tip) fails To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1299802/+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 1303697] Re: peer relation disappears during upgrade of juju
This bug was fixed in the package juju-core - 1.18.1-0ubuntu1 --- juju-core (1.18.1-0ubuntu1) trusty; urgency=medium * New upstream point release, including fixes for: - Upgrading juju 1.16.6 - 1.18.x fails (LP: #1299802). - Peer relation disappears during juju-upgrade (LP: #1303697). - public-address of units changes to internal bridge post upgrade (LP: #1303735). - Unable to deploy local charms without series (LP: #1303880). - juju scp no longer allows multiple extra arguments to be passed (LP: #1306208). - juju cannot downgrade to same major.minor version with earlier patch number (LP: #1306296). -- James Page james.p...@ubuntu.com Sat, 12 Apr 2014 07:04:37 +0100 ** Changed in: juju-core (Ubuntu Trusty) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1303697 Title: peer relation disappears during upgrade of juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1303697/+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 1303880] Re: Juju 1.18.0, can not deploy local charms without series
This bug was fixed in the package juju-core - 1.18.1-0ubuntu1 --- juju-core (1.18.1-0ubuntu1) trusty; urgency=medium * New upstream point release, including fixes for: - Upgrading juju 1.16.6 - 1.18.x fails (LP: #1299802). - Peer relation disappears during juju-upgrade (LP: #1303697). - public-address of units changes to internal bridge post upgrade (LP: #1303735). - Unable to deploy local charms without series (LP: #1303880). - juju scp no longer allows multiple extra arguments to be passed (LP: #1306208). - juju cannot downgrade to same major.minor version with earlier patch number (LP: #1306296). -- James Page james.p...@ubuntu.com Sat, 12 Apr 2014 07:04:37 +0100 ** Changed in: juju-core (Ubuntu Trusty) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1303880 Title: Juju 1.18.0, can not deploy local charms without series To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1303880/+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 1303735] Re: public-address change to internal bridge post juju-upgrade
This bug was fixed in the package juju-core - 1.18.1-0ubuntu1 --- juju-core (1.18.1-0ubuntu1) trusty; urgency=medium * New upstream point release, including fixes for: - Upgrading juju 1.16.6 - 1.18.x fails (LP: #1299802). - Peer relation disappears during juju-upgrade (LP: #1303697). - public-address of units changes to internal bridge post upgrade (LP: #1303735). - Unable to deploy local charms without series (LP: #1303880). - juju scp no longer allows multiple extra arguments to be passed (LP: #1306208). - juju cannot downgrade to same major.minor version with earlier patch number (LP: #1306296). -- James Page james.p...@ubuntu.com Sat, 12 Apr 2014 07:04:37 +0100 ** Changed in: juju-core (Ubuntu Trusty) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1303735 Title: public-address change to internal bridge post juju-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1303735/+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 992004] Re: System Freezes after Undocking then Docking - HP 8740W
For me this happened only with unity. Using Gnome, it didn't happen so far. OS: Arch Linux with Unity Lenovo T400 with Advanced Mini Dock -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/992004 Title: System Freezes after Undocking then Docking - HP 8740W To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/992004/+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 1305839] Re: FFe: Support for Third Party Driver Installation
Hi, I think everyone is largely aligned with the freedom aspects of this. This is certainly not a concern for myself at least. What is concerning to me, is that this feature feels rushed and somewhat unfinished. I just had a quick look at the code that landed for this feature: There is no support for third party drivers in enlistment, commissioning or fastpath/curtin. I am guessing the first two can be ignored, depending on the nature of the driver; but the fastpath seems a big loss. The drivers.yaml file is a monolithic file that ships with the code- base. I might have expected this to be a yaml per-driver file, allowing easier stacking, probably managed via an external mechanism (simplestream?). I am guessing drivers.yaml would appear to be a config file that I can maintain as a sysadmin. Am I allowed to add extra modalias as new hardware comes out, myself? What about third party drivers I wish to add? What experience should I expect on upgrade? This, if added now, feels like something that is needlessly hard to upgrade from. It seems the binary drivers udeb for the reference implementation is pulled from both plain http (via wget, without validating against a signed Release file), AND when the PPA is added the signing key is also retrieved over plain http. This would imply a trust failure on both parts of this. It matches the kernel of the current install. Assuming that the pxe installer is still using the netboot from the current installer, is there any assurance that without warning - installs will suddenly stop working, until the third-party repository has updated it? The modalias matching seems to be quite nice. It looks like I can only support one third party driver per node. Is there likely to be a scenario where multiple drivers may be required? Only amd64 is supported as part of this feature. Is it not anticipated that other arches will require third-party drivers? I don't think the archive pocket matters weather this is Universe or Main. By current process, the only thing moving to Universe would achieve is removal from the install media (which could equally be done if in main). Meaning that squeezing in prior to release is even less relevant. HWE Kernel FFe bug 1281765, is left unfinished. Is this something also planned to land? To be clear, I am not against this feature. I was proposing that if landed as a HWE feature post release, where this can be fully implemented without encumbering the upgrade process to be needlessly complicated. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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 1302044] Re: permissions on /var/lib/glance/image* are wrong
** Also affects: openstack-manuals Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to glance in Ubuntu. https://bugs.launchpad.net/bugs/1302044 Title: permissions on /var/lib/glance/image* are wrong To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-manuals/+bug/1302044/+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 1306994] [NEW] powernap loadavg monitor fails to detect load
Public bug reported: Ubuntu Precise, amd64, powernap 2.17-0ubuntu2 Symptoms: system gets shut down even under load, although the loadmonitor had been configured. Fix: /usr/lib/python2.7/dist-packages/powernap/monitors/LoadMonitor.py : Replace 36 if os.getloadavg()[0] t: with 36 if os.getloadavg()[0] float(t): and it works. ** Affects: powernap Importance: Undecided Status: New ** Affects: powernap (Ubuntu) Importance: Undecided Status: New ** Also affects: powernap (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to powernap in Ubuntu. https://bugs.launchpad.net/bugs/1306994 Title: powernap loadavg monitor fails to detect load To manage notifications about this bug go to: https://bugs.launchpad.net/powernap/+bug/1306994/+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 16669] Re: Squid: Compile with --enable-ssl
I have done a build of squid 3.4.4 with ssl enabled. See https://launchpad.net/~dirk-computer42/+archive/c42-other -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/16669 Title: Squid: Compile with --enable-ssl To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/16669/+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 1307008] [NEW] cgmanager doesn't stop on shutdown
Public bug reported: cgmanager doesn't stop on shutdown causing umount: / is busy. lsof, processlist and mounts logged at umountfs step are attached. ** Affects: cgmanager (Ubuntu) Importance: Undecided Status: New ** Attachment added: lsof https://bugs.launchpad.net/bugs/1307008/+attachment/4082103/+files/lsof -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cgmanager in Ubuntu. https://bugs.launchpad.net/bugs/1307008 Title: cgmanager doesn't stop on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1307008/+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 1305839] Re: FFe: Support for Third Party Driver Installation
I'm not sure our approach on phones should be held up as a benchmark here, it was a pragmatic solution to rapid iteration on devices that weren't built for Ubuntu. It's also code that we control (from the point of view of us shipping it in the archive, us being able to audit and fix it, etc). Even if we take away the non-free part of the argument, is it really sane to have an installer silently grabbing things from third-party non- Ubuntu repositories without the sysadmin first confirming that this is what they want? I'm not arguing this be done on a per-node basis, that's madness. As you say, server installations are automated, and should remain that way. But, automating installation of nodes doesn't mean that installing and configuring the master needs to also be so silent as to not point out to the user that we intend to fetch drivers from third parties, should their hardware not work out of the box with Ubuntu. As I pointed out, this feature will fail hard in a well-firewalled network anyway (how many server farms that poke a hole for archive.ubuntu.com, or have a local mirror, will have a hole poked for ppa.launchpad.net? My bet is pretty close to zero). So, by warning them up front of our intent, we can also point out that they might need to read the config and poke some firewall holes too (or mirror the content locally and change the config to point to it). I understand the urge to automate this all, but I not only feel it's dangerously close to dishonest, I also suspect it won't at all work in practice, except for test farms on Canonical employees' networks that already have unfettered access to the hosts in question. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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 1307037] [NEW] ntp causes time to accelerate
Public bug reported: 1) Description:Ubuntu 14.04 LTS Release:14.04 2) ntp: Installed: (none) Candidate: 1:4.2.6.p5+dfsg-3ubuntu2 Version table: 1:4.2.6.p5+dfsg-3ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 3) normal time evolution 4) accelerating/decelerating time My clock time accelerates and decelerates. Everything is normal in the bios, however in Trusty I get this strange behavior. I launched a remote session and recorded the following from time.is in a chrome browser session to show the problem: https://www.youtube.com/watch?v=BpQ7kdkA34g Note the speedup of the clock (esp at the 20 sec mark) and the major drift If I uninstall ntp, I don't experience these problems.I was changing ntp servers before I purged ntp, but I don't see why this would happen with any server. I also was having problems with my computer starting (ram timing issues?) but it works fine now, and I wasn't having this problem in the bios, only in ubuntu. ACPI also was disabled in the bios. And the only kernel option I'm passing is text. Sorry I can't give any other information, but if you have any questions, I can try my best to answer them. ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Description changed: - 1) Description:Ubuntu 14.04 LTS Release:14.04 2) ntp: - Installed: (none) - Candidate: 1:4.2.6.p5+dfsg-3ubuntu2 - Version table: - 1:4.2.6.p5+dfsg-3ubuntu2 0 - 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages + Installed: (none) + Candidate: 1:4.2.6.p5+dfsg-3ubuntu2 + Version table: + 1:4.2.6.p5+dfsg-3ubuntu2 0 + 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 3) normal time evolution 4) accelerating/decelerating time - - My clock time accelerates and decelerates. Everything is normal in the bios, however in Trusty I get this strange behavior. I launched a remote session and recorded the following from time.is in a chrome browser session to show the problem: + My clock time accelerates and decelerates. Everything is normal in the + bios, however in Trusty I get this strange behavior. I launched a + remote session and recorded the following from time.is in a chrome + browser session to show the problem: https://www.youtube.com/watch?v=BpQ7kdkA34g - Note the speedup of the clock (esp at the (1 min 20 mark) and the major + Note the speedup of the clock (esp at the 20 sec mark) and the major drift If I uninstall ntp, I don't experience these problems.I was changing ntp servers before I purged ntp, but I don't see why this would happen with any server. I also was having problems with my computer starting (ram timing issues?) but it works fine now, and I wasn't having this problem in the bios, only in ubuntu. ACPI also was disabled in the bios. And the only kernel option I'm passing is text. Sorry I can't give any other information, but if you have any questions, I can try my best to answer them. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1307037 Title: ntp causes time to accelerate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1307037/+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 99795] Re: heimdal uses wrong path to ldapi-socket
** Changed in: openldap2 (Debian) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2 in Ubuntu. https://bugs.launchpad.net/bugs/99795 Title: heimdal uses wrong path to ldapi-socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap2/+bug/99795/+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 1195607] Re: iscsitarget-dkms broken since kernel 3.10.0
I'm seeing the problem today on a new install I'm setting up of 3.11.0-19-generic: ... make KERNELRELEASE=3.11.0-19-generic -C /lib/modules/3.11.0-19-generic/build M=/var/lib/dkms/iscsitarget/1.4.20.2/build(bad exit status: 2) Error! Bad return status for module build on kernel: 3.11.0-19-generic (x86_64) Consult /var/lib/dkms/iscsitarget/1.4.20.2/build/make.log for more information. san@iSCSI-SAN:/$ more /var/lib/dkms/iscsitarget/1.4.20.2/build/make.log DKMS make.log for iscsitarget-1.4.20.2 for kernel 3.11.0-19-generic (x86_64) Sat Apr 12 17:46:40 PDT 2014 make: Entering directory `/usr/src/linux-headers-3.11.0-19-generic' LD /var/lib/dkms/iscsitarget/1.4.20.2/build/built-in.o LD /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/built-in.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/tio.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/iscsi.o CC [M] /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/nthread.o /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/nthread.c: In function âdo_recvâ: /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/nthread.c:145:1: warning: the frame size of 1104 bytes is larger than 1024 bytes [-Wframe-larger-than=] CC [M] /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/wthread.o /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/wthread.c: In function âworker_threadâ: /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/wthread.c:73:28: error: void value not ignored as it ought to be /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/wthread.c:74:3: error: implicit declaration of function âget_io_contextâ [-Werror=implicit-function-declaration] /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/wthread.c:74:21: warning: assignment makes pointer from integer without a cast [enabled by default] cc1: some warnings being treated as errors make[2]: *** [/var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/wthread.o] Error 1 make[1]: *** [/var/lib/dkms/iscsitarget/1.4.20.2/build/kernel] Error 2 make: *** [_module_/var/lib/dkms/iscsitarget/1.4.20.2/build] Error 2 make: Leaving directory `/usr/src/linux-headers-3.11.0-19-generic' san@iSCSI-SAN:/$ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1195607 Title: iscsitarget-dkms broken since kernel 3.10.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1195607/+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 1195607] Re: iscsitarget-dkms broken since kernel 3.10.0
I got it working with the following: wget http://ftp.ubuntu.com/ubuntu/pool/universe/i/iscsitarget /iscsitarget-dkms_1.4.20.3+svn499-0ubuntu2_all.deb sudo dpkg -i iscsitarget-dkms_1.4.20.3+svn499-0ubuntu2_all.deb -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1195607 Title: iscsitarget-dkms broken since kernel 3.10.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1195607/+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 1307037] Re: ntp causes time to accelerate
So after messing with the computer, it seems that the problem was there with ntp. So I'm not certain it's related to ntp. Sorry about that. But I searched google high and low, and I couldn't find a single person that was having this problem. I suspect it might be something to do with MB/Ram/timing, I have no idea. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1307037 Title: ntp causes time to accelerate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1307037/+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
