[Bug 1546418] [NEW] samba-ad-dc leaves a stale pidfile when not needed
Public bug reported: The upstart script /etc/init.d/samba-ad-dc.conf runs samba -D even when the server role is "single server". This makes samba exit while leaving a stale /var/run/samba/samba.pid file. I've monitoring scripts that watch for stale pid files in /var/run/*/*.pid, which triggers false alerts. The older /etc/init.d/samba-ad-dc used to check the server role and skip starting samba when the role wasn't "active directory domain controller", thus no stale pidfiles were produced. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: samba 2:4.1.6+dfsg-1ubuntu2.14.04.12 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Wed Feb 17 10:09:31 2016 OtherFailedConnect: Yes SambaServerRegression: Yes SmbConfIncluded: No SourcePackage: samba UpgradeStatus: Upgraded to trusty on 2016-01-24 (23 days ago) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1546418 Title: samba-ad-dc leaves a stale pidfile when not needed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1546418/+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 862728] Re: Please stop defaulting to VCS="bzr"
*** This bug is a duplicate of bug 1357326 *** https://bugs.launchpad.net/bugs/1357326 ** This bug has been marked a duplicate of bug 1357326 Make default VCS git -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to etckeeper in Ubuntu. https://bugs.launchpad.net/bugs/862728 Title: Please stop defaulting to VCS="bzr" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/862728/+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 1501217] Re: Removing squid-deb-proxy-client leaves a stale but active config file, breaking apt
Experiments show that Acquire::http::ProxyAutoDetect "/bin/sh -c 'true'"; produces this error: Failed to exec method /bin/sh -c 'true' so I'm afraid options 1 and 2 are out :( -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1501217 Title: Removing squid-deb-proxy-client leaves a stale but active config file, breaking apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1501217/+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 1501217] Re: Removing squid-deb-proxy-client leaves a stale but active config file, breaking apt
I've some half-formed ideas: - if apt allows a shell command instead of just an executable name, maybe the config could be Acquire::http::ProxyAutoDetect "if [ -x /usr/share/squid-deb-proxy- client/apt-avahi-discover ]; then /usr/share/squid-deb-proxy-client/apt- avahi-discover; fi"; - if apt doesn't use the shell, but allows a command with arguments, and not just an executable name, maybe the config could be Acquire::http::ProxyAutoDetect "sh -c 'if [ -x /usr/share/squid-deb- proxy-client/apt-avahi-discover ]; then /usr/share/squid-deb-proxy- client/apt-avahi-discover; fi'"; - if apt is truly restricted to just a single executable name in that parameter, maybe the package could ship a small wrapper script that conditionally runs /apt-avahi-discover if it exists, with the wrapper script placed somewhre in /etc, so it's not removed on purge, e.g. Acquire::http::ProxyAutoDetect "/etc/squid-deb-proxy-client/apt- avahi-discover"; with /etc/squid-deb-proxy-client/apt-avahi-discover containing # you're not expected to modify this, see LP: #1501217 if [ -x /usr/share/squid-deb-proxy-client/apt-avahi-discover ]; then /usr/share/squid-deb-proxy-client/apt-avahi-discover fi I keep not finding the time to experiment and see if one of the first two ideas would work. I don't like the 3rd option. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1501217 Title: Removing squid-deb-proxy-client leaves a stale but active config file, breaking apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1501217/+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 1501217] Re: apt-get removing squid-deb-proxy-client leaves a stale config file
When Debian packages ship cron files, these usually test -x /usr/bin/programname before executing it, to prevent errors in case the package is removed but not purged. I thought it was required by the Debian policy, but I cannot find wording for it. Maybe it was just a courtesy. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1501217 Title: apt-get removing squid-deb-proxy-client leaves a stale config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1501217/+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 1166667] Re: The default configuration is missing the /etc/squid-deb-proxy/autogenerated/pkg-blacklist-regexp.acl file
Unfortunately this is not fixed. $ apt-cache policy squid-deb-proxy squid-deb-proxy: Installed: 0.8.10 Candidate: 0.8.10 Version table: *** 0.8.10 0 500 http://lt.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages 100 /var/lib/dpkg/status Every night I get an email like this: From: AnacronTo: root@mymachine Subject: Anacron job 'cron.daily' on mymachine Date: Fri, 9 Oct 2015 07:58:48 +0300 (EEST) /etc/cron.daily/logrotate: 2015/10/09 07:55:22| Warning: empty ACL: acl blockedpkgs urlpath_regex "/etc/squid-deb-proxy/autogenerated/pkg-blacklist-regexp.acl" -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/117 Title: The default configuration is missing the /etc/squid-deb- proxy/autogenerated/pkg-blacklist-regexp.acl file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/117/+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 1501217] Re: apt-get removing squid-deb-proxy-client leaves a stale config file
Same output if I do sudo apt-get install squid-deb-proxy-client apport-collect 1501217 I may have filed it against the wrong package? But apt-cache show squid-deb-proxy-client|grep Source Source: squid-deb-proxy so huh? bug in apport? I'm using Ubuntu 14.04 LTS. ** Changed in: squid-deb-proxy (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1501217 Title: apt-get removing squid-deb-proxy-client leaves a stale config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1501217/+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 1501217] Re: apt-get removing squid-deb-proxy-client leaves a stale config file
apport-collect says Package squid-deb-proxy not installed and no hook available, ignoring *** Updating problem report No additional information collected. because of course. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1501217 Title: apt-get removing squid-deb-proxy-client leaves a stale config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1501217/+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 1501217] [NEW] apt-get removing squid-deb-proxy-client leaves a stale config file
Public bug reported: If I apt-get remove squid-deb-proxy-client, every apt-get install/update/upgrade operation produces this error message: 0% [Working]Failed to exec method /usr/share/squid-deb-proxy-client /apt-avahi-discover The workaround is to apt-get purge squid-deb-proxy-client. ** Affects: squid-deb-proxy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1501217 Title: apt-get removing squid-deb-proxy-client leaves a stale config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1501217/+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 1005257] Re: squid-deb-proxy's logrotate job produces warnings / log spam
** This bug is no longer a duplicate of bug 117 The default configuration is missing the /etc/squid-deb-proxy/autogenerated/pkg-blacklist-regexp.acl file -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1005257 Title: squid-deb-proxy's logrotate job produces warnings / log spam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1005257/+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 1005257] Re: squid-deb-proxy's logrotate job produces warnings / log spam
** This bug has been marked a duplicate of bug 117 The default configuration is missing the /etc/squid-deb-proxy/autogenerated/pkg-blacklist-regexp.acl file -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1005257 Title: squid-deb-proxy's logrotate job produces warnings / log spam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1005257/+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 1459987] [NEW] ubuntu-vm-builder hangs after bootstrapping (precise host, trusty guest)
Public bug reported: I'm running ubuntu-vm-builder kvm trusty \ --libvirt qemu:///system \ --tmpfs=2048 \ --rootsize 20480 \ --ssh-key=/root/.ssh/authorized_keys \ --ssh-user-key=/root/.ssh/authorized_keys\ --lock-user \ --suite trusty \ --components main,restricted,universe,multiverse \ --addpkg openssh-server \ --addpkg avahi-daemon\ --addpkg vim \ --addpkg git \ --addpkg acpid \ --addpkg unattended-upgrades \ --addpkg command-not-found \ --addpkg software-properties-common \ --addpkg openjdk-7-jre-headless \ --addpkg htop\ --addpkg strace \ --addpkg linux-image-generic \ --hostname trusty64 \ --domain lan \ --bridge br0 \ --mem 1024 --cpus 2 It outputs 2015-05-29 12:43:06,265 INFO: Mounting tmpfs under /tmp/tmpJuZzghtmpfs 2015-05-29 12:43:06,269 INFO: Calling hook: preflight_check 2015-05-29 12:43:06,273 INFO: Calling hook: set_defaults 2015-05-29 12:43:06,274 INFO: Calling hook: bootstrap and then hangs. pstree shows that ubuntu-vm-builder has one zombie child (debootstrap) strace shows that ubuntu-vm-builder is waiting in select(5, [4], [], [], NULL) lsof shows that fd 4 is a pipe that is shared between ubuntu-vm-builder and udevd, and by udevd I mean a 2nd copy of udevd that's running in the tmpfs. /tmp/tmpJuZzghtmpfs/var/log/bootstrap.log mentions udev a few times: Selecting previously unselected package libudev1:amd64. dpkg: regarding .../libudev1_204-5ubuntu20_amd64.deb containing libudev1:amd64, pre-dependency problem: libudev1 pre-depends on multiarch-support multiarch-support is not installed. dpkg: warning: ignoring pre-dependency problem! Preparing to unpack .../libudev1_204-5ubuntu20_amd64.deb ... Unpacking libudev1:amd64 (204-5ubuntu20) ... ... Selecting previously unselected package udev. Preparing to unpack .../udev_204-5ubuntu20_amd64.deb ... Adding 'diversion of /bin/udevadm to /bin/udevadm.upgrade by fake-udev' Unpacking udev (204-5ubuntu20) ... ... Setting up udev (204-5ubuntu20) ... * Stopping the hotplug events dispatcher udevd Warning: Fake start-stop-daemon called, doing nothing ...done. * Starting the hotplug events dispatcher udevd ...done. Removing 'diversion of /bin/udevadm to /bin/udevadm.upgrade by fake-udev' Manually killing this copy of udevd allows ubuntu-vm-builder to proceed. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubuntu-vm-builder 0.12.4+bzr477-0ubuntu5 ProcVersionSignature: Ubuntu 3.2.0-84.121-generic 3.2.68 Uname: Linux 3.2.0-84-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.9 Architecture: amd64 Date: Fri May 29 12:58:00 2015 MarkForUpload: True PackageArchitecture: all ProcEnviron: LC_CTYPE=lt_LT.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vm-builder UpgradeStatus: Upgraded to precise on 2012-07-31 (1032 days ago) ** Affects: vm-builder (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise ** Summary changed: - ubuntu-vm-builder hangs after bootstrapping + ubuntu-vm-builder hangs after bootstrapping (precise host, trusty guest) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/1459987 Title: ubuntu-vm-builder hangs after bootstrapping (precise host, trusty guest) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1459987/+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 180551] Re: Postfix myhostname defaults to uname() not gethostname().
Bug still present in Trusty (14.04 LTS). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/180551 Title: Postfix myhostname defaults to uname() not gethostname(). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/180551/+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 908901] Re: awstats confused by 408 entries in apache log files
Upstream bug: https://sourceforge.net/p/awstats/bugs/914/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to awstats in Ubuntu. https://bugs.launchpad.net/bugs/908901 Title: awstats confused by 408 entries in apache log files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/908901/+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 1252467] Re: /etc/cron.d/awstats: wrong user for cron job
Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745620 ** Bug watch added: Debian Bug tracker #745620 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745620 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to awstats in Ubuntu. https://bugs.launchpad.net/bugs/1252467 Title: /etc/cron.d/awstats: wrong user for cron job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1252467/+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 1320709] Re: incorrect info in /usr/share/doc/awstats/README.Debian.gz about logrotate
BTW awstats 7.3 currently in Debian unstable uses 'su -l -c ... www- data' in http://sources.debian.net/src/awstats/7.3%2Bdfsg-1/debian/prerotate.sh/, which is installed as /etc/logrotate.d/httpd-prerotate/awstats. Eventually that version will be synced into Ubuntu. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to awstats in Ubuntu. https://bugs.launchpad.net/bugs/1320709 Title: incorrect info in /usr/share/doc/awstats/README.Debian.gz about logrotate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1320709/+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 1357326] Re: Make default VCS git
Bazaar is effectively abandoned. etckeeper's upstream default is git. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to etckeeper in Ubuntu. https://bugs.launchpad.net/bugs/1357326 Title: Make default VCS git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1357326/+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 1397849] [NEW] cron script errors about 'Argument perl_version isn't numeric'
*** This bug is a duplicate of bug 1397706 *** https://bugs.launchpad.net/bugs/1397706 Public bug reported: I got the following emails for two nights in a row: /etc/cron.daily/spamassassin: Argument perl_version isn't numeric in numeric ge (=) at (eval 616) line 1. Argument perl_version isn't numeric in numeric ge (=) at (eval 1100) line 1. Nov 29 07:01:11.552 [522] warn: Argument perl_version isn't numeric in numeric ge (=) at (eval 550) line 1. Nov 29 07:01:11.765 [522] warn: Argument perl_version isn't numeric in numeric ge (=) at (eval 1034) line 1. I was unable to reproduce them by running sh -x /etc/cron.daily/spamassassin this morning. There have been no software updates since Nov 25, according to /var/log/dpkg.log, so I'm forced to assume the appearance of these warnings depends on the contents of wherever spamassassing goes to fetch its updates. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: spamassassin 3.3.1-1 ProcVersionSignature: Ubuntu 2.6.32-27.49-generic 2.6.32.26+drm33.12 Uname: Linux 2.6.32-27-generic i686 Architecture: i386 Date: Mon Dec 1 06:52:08 2014 PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en_GB:en_US:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: spamassassin ** Affects: spamassassin (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1397849 Title: cron script errors about 'Argument perl_version isn't numeric' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1397849/+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 1397849] Re: cron script errors about 'Argument perl_version isn't numeric'
*** This bug is a duplicate of bug 1397706 *** https://bugs.launchpad.net/bugs/1397706 Looks like a duplicate of bug 1397706. (Launchpad's bug search didn't show it to me, when I searched for 'perl_version' in all spamassassin's bugs. Google found it.) ** This bug has been marked a duplicate of bug 1397706 Argument perl_version isn't numeric in numeric -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1397849 Title: cron script errors about 'Argument perl_version isn't numeric' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1397849/+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 1381537] Re: Dovecot version in precise too old to switch off SSLv3 protocol for poodle fix
Dovecot uses Unix password authentication by default. If those passwords leak, they can be used to ssh in and perhaps even for sudo. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1381537 Title: Dovecot version in precise too old to switch off SSLv3 protocol for poodle fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1381537/+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 975985] [NEW] please start sshd as early as possible during boot
Public bug reported: I've servers that take 20-40 minutes to fscheck all local filesystems. The server is pingable during that time, but doesn't allow ssh access. It would be nice if I could ssh in after the essential filesystems (/, /usr, /var) are mounted, without waiting for the rest (/srv, or non- FHS-y /apps, /backups, /stuff). ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- 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/975985 Title: please start sshd as early as possible during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/975985/+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 909558] [NEW] Default conffile change in hardy - lucid transition silently stops etckeeper hooks
Public bug reported: To reproduce: 1. install Hardy 2. apt-get install etckeeper 3. etckeeper init # will create /etc/.git, since that's the default 4. upgrade to Lucid 5. apt-get install something Expected behaviour: * apt-get install runs the apt hooks and adds two commits to the /etc git repository Actual behaviour: * nothing happens Elaboration: * The default VCS setting in /etc/etckeeper/etckeeper.conf has changed from git to bzr. Since the conffile was not modified, dpkg replaced it with the new version on upgrade. Now etckeeper commit fails to find /etc/.bzr and complains, while etckeeper pre-install/post-install silently do nothing. If a sysadmin doesn't manually invoke 'etckeeper commit' (preferring manual 'git commit'), he may not notice those apt hooks stopped working until he tries to look at 'git log' about a year later. ** Affects: etckeeper (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to etckeeper in Ubuntu. https://bugs.launchpad.net/bugs/909558 Title: Default conffile change in hardy - lucid transition silently stops etckeeper hooks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/909558/+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 383926] Re: ssh-aggent stopped accepting connections
I do not know how to reproduce the problem. It never happened again to me on Jaunty or on Karmic. -- ssh-aggent stopped accepting connections https://bugs.launchpad.net/bugs/383926 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- 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 383926] [NEW] ssh-aggent stopped accepting connections
Public bug reported: Suddenly my ssh-agent stopped accepting connections: $ ssh-add -l Could not open a connection to your authentication agent. It is still running (pid 4530, which matches the value of $SSH_AGENT_PID), but doesn't appear to be listening on the socket (/tmp/keyring-Kp3t4b/socket.ssh according to $SSH_AUTH_SOCK). The socket exists in the filesystem, but neither lsof, nor fuser, nor netstat -x show anything about it. What lsof shows is that ssh-agent is listening on /tmp/ssh-PcVXlL4456/agent.4456, which doesn't appear in my environment at all. pstree indicates that pid 4530 was launched as /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --executex-session-manag but /proc/4530/exe confirms it is running the /usr/bin/ssh-agent process. I used ssh-agent successfully this morning, and it stopped working when I openend gnome-terminal with several tabs each trying to ssh into a different local host. (I've used that techinque succesfully in the past.) I do not know how to reproduce the problem. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: openssh-client 1:5.1p1-5ubuntu1 ProcEnviron: LC_CTYPE=lt_LT.UTF-8 PATH=(custom, user) LANG=lt_LT.UTF-8 SHELL=/bin/bash SourcePackage: openssh Uname: Linux 2.6.28-12-generic i686 ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- ssh-aggent stopped accepting connections https://bugs.launchpad.net/bugs/383926 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- 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 383926] Re: ssh-aggent stopped accepting connections
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/27524381/Dependencies.txt -- ssh-aggent stopped accepting connections https://bugs.launchpad.net/bugs/383926 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- 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 383926] Re: ssh-aggent stopped accepting connections
Checking a working GNOME session (on another machine) I see that normally it's gnome-keyring that's listening on socket.ssh. I don't have a gnome-keyring process running (and I don't see gnome-keyring- daemon either). Neither ~/.xsession-errors nor /var/log/* have any recent error messages from gnome-keyring (though the first is truncated -- ...Too much output, ignoring rest... -- since it's filled with some strange Mono tracebacks from Migo.Syndication.RssParser). ** Changed in: openssh (Ubuntu) Status: New = Invalid ** Also affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New -- ssh-aggent stopped accepting connections https://bugs.launchpad.net/bugs/383926 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- 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 383926]
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/27526943/Dependencies.txt -- ssh-aggent stopped accepting connections https://bugs.launchpad.net/bugs/383926 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- 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 342655] Re: Confusing debconf message when upgrading
It would be even better if sysstat didn't ask anything and just moved the obsolete data files to /var/log/sysstat.old, and added a notice in NEWS.Debian explaining why. Best, of course, would be to do the above (for backup purposes) *and* convert the data files into the new format automatically. -- Confusing debconf message when upgrading https://bugs.launchpad.net/bugs/342655 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to sysstat in ubuntu. -- 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 105251] Re: NetworkManager wrongly releases DHCP IP
Motin: check the other dhclient hooks: grep exit /etc/dhcp3/dhclient-exit-hooks.d/* -- NetworkManager wrongly releases DHCP IP https://bugs.launchpad.net/bugs/105251 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- 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 105251] Re: NetworkManager wrongly releases DHCP IP
The whereami bug was already reported as bug 239740 -- NetworkManager wrongly releases DHCP IP https://bugs.launchpad.net/bugs/105251 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- 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