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 rep
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
** 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 Ubun
** 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.
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.
**
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 i
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 t
Unfortunately this is not fixed.
$ apt-cache policy squid-deb-proxy
squid-deb-proxy:
Installed: 0.8.10
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
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 ap
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
*** 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 Ubun
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 f
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
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 noti
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 U
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
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 notificati
Public bug reported:
I'm running
ubuntu-vm-builder kvm trusty \
--libvirt qemu:///system \
--tmpfs=2048 \
--rootsize 20480 \
--ssh-key=/root/.ssh/authorized_keys
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 i
Adding
exec >> /tmp/dhcp.debug 2>&1
set -x
to the end of /etc/dhcp3/dhclient-exit-hooks.d/debug showed that the
culprit on one system was a whereami script that did 'exit 1'
prematurely, stopping /etc/dhcp3/dhclient-exit-hooks.d/_dhcdbd from
being run. Here's the relevant line of code:
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
Ubu
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.
--
Just a comment: 'exit' is not the only way to terminate a shell script
prematurely; if any of the scripts call 'set -e' and then any of the
commands executed after that fails (i.e. returns a non-zero exit code)
the script will terminate.
I would suggest the same debugging technique: adding
exec
Hm, interesting. I didn't know things changed in Intrepid. I changed
/etc/dhcp3/dhclient-exit-hooks.d/debug and asked it to print debugging
output to /tmp/dhclient-script.debug, yet when I reconnected to the
network, that file was not created. So it seems that network-manager
talks to the dhcp c
I upgraded to Jaunty today and was confused by the systat question
dialog too.
What a user sees is this:
Configuring sysstat
[ ] Do you want post-installation script to remove these data files?
[ Help ]
The first reaction is "huh? what files?". The second reaction is to try
the [ Help ] bu
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.
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/s
** 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
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 g
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: gnome-keyring 2.26.1-0ubuntu1
PackageArchitecture: i386
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=lt_LT.UTF-8
LC_CTYPE=lt_LT.UTF-8
Uname: Linux 2.6.28-12-generic i686
UserGroups: adm admin audio cdrom davfs2 dialout dip floppy f
** 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
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/138
*** 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 "
*** 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 duplicat
35 matches
Mail list logo
