Ended up here via Bug #1236239 with 16.04 (beta)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1214379
Title:
pinger crashed with SIGSEGV in malloc_consolidate()
To manage notifica
@louis-bouchard yes, that patch does not work under Xenial.
Workaround is to manually replace all occurrences of /usr/sbin/squid with
/usr/sbin/squid3 in /etc/init.d/squid-deb-proxy, /etc/init/squid-deb-proxy.conf
and /usr/share/squid-deb-proxy/init-common.sh
--
You received this bug notifica
Consider destroying the cluster created by package installation (or
inhibiting its creation), and calling pg_createcluster yourself with the
'--data-checksums' option available in PG 9.3. This will allow
PostgreSQL to detect corrupted files and fail appropriately.
--
You received this bug notific
stub@aargh:~$ sudo systemctl status lxc
● lxc.service - LXC Container Initialization and Autoboot Code
Loaded: loaded (/lib/systemd/system/lxc.service; enabled; vendor preset:
enabled)
Active: active (exited) since Mon 2015-10-12 16:57:31 ICT; 20h ago
Process: 1190 ExecStart=/usr/lib/x86_6
Is this Bug #1490110 ?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1504496
Title:
package lxc 1.1.4-0ubuntu0.1 failed to install/upgrade: subprocess
installed post-installation scr
** Attachment added: "main.log"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1490110/+attachment/4478084/+files/main.log
** Changed in: lxc (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribe
** Attachment added: "apt-term.log"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1490110/+attachment/4478083/+files/apt-term.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/14
2015-09-29 10:30:55,881 INFO cache.commit()
2015-09-29 10:30:55,881 DEBUG failed to SystemUnLock() (E:Not locked)
2015-09-29 11:04:11,358 ERROR got an error from dpkg for pkg: 'lxc':
'subprocess installed post-installation script returned error exit status 100'
2015-09-29 11:04:11,358 DEBUG runni
Upgrade to wily failed here with this error. Possible trigger was
having juju-local installed, which seemed to create a bit of a
dependency mess with juju-local, lxc-templates and lxc.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lx
Public bug reported:
I am interested in priming the lxc cache on new hosts, but this is
problematic because /var/cache/lxc is not world readable.
Could it become world readable?
This bug should be WONTFIX if the cache can contain secrets or 'private'
images. But ideally these would be declared p
I think this is dependent on security bug #892552
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/802117
Title:
juju ssh/scp/run commands cause spurious key errors
To manage notificati
The root users .ssh/known_hosts is also getting polluted by 'juju run',
which is causing subsequent 'juju run' commands to fail when IP
addresses are recycled.
I'm also seeing IP addresses recycled much more often, especially with
the local provider which now reuses them immediately.
** Changed i
Public bug reported:
Please allow specifying a MIRROR in /etc/default/squid-deb-proxy , and
use this setting to rewrite http://(*.)?archive.ubuntu.com/ to $MIRROR.
This would be of most benefit to mobile users.
http://scyu.logdown.com/posts/260278-squid-deb-proxy-redirect-default-
ubuntu-reposito
Amulet tests are spuriously failing due to this bug. IP addresses get
recycled as the leases expire, and the 'juju run' commands Amulet makes
fail due to the old host key being in the root users known_hosts file.
==
ERROR: test s
** Also affects: python-swiftclient
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to swift in Ubuntu.
https://bugs.launchpad.net/bugs/130
Title:
metadata update should not delete large f
** Also affects: python-swiftclient (Ubuntu Utopic)
Importance: Undecided
Status: Confirmed
** Also affects: python-swiftclient (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: python-swiftclient (Ubuntu Utopic)
Status: Confirmed => Fix Released
** Chan
** Also affects: python-swiftclient (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-swiftclient in Ubuntu.
https://bugs.launchpad.net/bugs/1282861
Title:
crash on content-en
A less obvious problem is that an invalid host key causes SSH tunneling
to be disabled.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/802117
Title:
juju ssh/scp commands cause spuriou
Public bug reported:
I'm collecting large numbers of network interface logs in
/var/log/upstart, named like /var/log/upstart/network-interface-
vethzNgy6Y.log.1.gz
I believe these are being created by lxc or one of its dependencies.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: lxc 1.0.1
Public bug reported:
Juju is storing volatile data in ~/.juju/cache, whereas Ubuntu tries to
follow http://standards.freedesktop.org/basedir-spec/basedir-spec-
latest.html which tells us the 'correct' location is
$XDG_CACHE_HOME/juju, defaulting to ~/.cache/juju.
Stuffing the cache in the same di
Bug #395281 has some relevant discussions
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/670289
Title:
Laptop won't shut down with rabbitmq running
To manage notifications
** This bug is no longer a duplicate of bug 395281
pam_ck_connector.so is called for non-login sessions
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/670289
Title:
Lapto
--
Need option to not launch server on boot
https://bugs.launchpad.net/bugs/660460
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify
Public bug reported:
Binary package hint: rabbitmq-server
There is no option to disable rabbitmq-server on startup in
/etc/default/rabbitmq.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: rabbitmq-server 1.8.0-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
Uname: Linu
24 matches
Mail list logo
