Public bug reported:
Upgrade hung; needed to kill rpcbind and clear the postinst script to
get it to finish.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: rpcbind 0.2.1-2ubuntu2.2
ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27
Uname: Linux 3.13.0-68-generic x86_64
The code which sets up the role lives here:
https://github.com/juju/juju/blame/8da94246468a4da71e62894f7a8a1bbbce112697/mongo/admin.go#L136
The roles we are setting up are:
Roles: []mgo.Role{
mgo.RoleDBAdminAny,
mgo.RoleUserAdminAny,
mgo.RoleClusterAdmin,
** Also affects: maas/1.7
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-tx-tftp in Ubuntu.
https://bugs.launchpad.net/bugs/1317705
Title:
Commissioning x86_64 node never
For reference, this is the libvirt page which covers bridge timeouts
affecting PXE booting:
http://wiki.libvirt.org/page/PXE_boot_%28or_dhcp%29_on_guest_failed#Long_Forward_Delay_Time_on_Bridge
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: maas
Milestone: None = 1.7.3
** Changed in: maas
Importance: Undecided = Critical
--
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/1389830
Title:
Don't use wlan0
This continues to waste our time as users end up with broken
configurations that require manual surgery in /etc/maas.
--
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/1389830
Title:
See also bug 1401841.
** Changed in: maas
Status: Invalid = Triaged
--
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/1389830
Title:
Don't use wlan0 for cluster to region
Adding a task for Ubuntu to handle adding wsmancli to the Suggests line.
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
See also bug 1272016 (which I have just reopened).
--
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/1389830
Title:
Don't use wlan0 for cluster to region communication [when cluster and
This bug suggests a problem with rabbit, which is gone in 1.7 and trunk.
** Changed in: maas (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Reopening; I have investigated and I don't think that we are strictly
not allowed to ask debconf questions.
** Changed in: maas
Status: Invalid = Won't Fix
** Changed in: maas
Status: Won't Fix = Triaged
** Changed in: maas
Milestone: None = 1.7.2
--
You received this bug
See also bug 1068383.
--
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/1272016
Title:
Which interface to bind maas-region-controller to should be a debconf
question
To manage
See also bug 1068383.
--
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/1273197
Title:
maas-cluster-controller does not update pserv.yaml when dpkg-
reconfigure is run
To manage
** Also affects: maas
Importance: Undecided
Status: New
--
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/1269046
Title:
Nodes created manually and then enlisted are forgotten
** Also affects: maas
Importance: Undecided
Status: New
--
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/1268783
Title:
traceback in celery-region log when maas controls DNS
** Also affects: maas
Importance: Undecided
Status: New
--
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/1270165
Title:
Stop action does not power systems down
To manage
** Also affects: maas
Importance: Undecided
Status: New
--
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/1268713
Title:
import-boot-images doesn't seem to do anything on
** Changed in: maas (Ubuntu)
Status: New = Fix Released
--
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/994887
Title:
Nodes listing does not support sorting
To manage
** Also affects: maas
Importance: Undecided
Status: New
--
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/1266893
Title:
unable to complete getting the ephemeral images
To
** Also affects: maas
Importance: Undecided
Status: New
--
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/1294711
Title:
power management broken after upgrade from saucy
To
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Milestone: None = 1.7.2
** Changed in: maas
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Also affects: maas
Importance: Undecided
Status: New
--
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/1396740
Title:
etherwake does not wake up machines
To manage
** Also affects: maas
Importance: Undecided
Status: New
--
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/1305907
Title:
boot: section in pserv.yaml is obsolete
To manage
** Also affects: maas
Importance: Undecided
Status: New
--
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/1350270
Title:
/var/log/maas/maas.log doesn't come back if deleted
To
** Also affects: maas
Importance: Undecided
Status: New
--
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/1312988
Title:
MAAS hands 2 ips when juju-bootstrapping- 1 MAC
** Also affects: maas
Importance: Undecided
Status: New
--
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/1331909
Title:
Always get invalid SSH Public Key
To manage
** Also affects: maas
Importance: Undecided
Status: New
--
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/1374054
Title:
no ssh access to commissioning or enlistment
To manage
** Also affects: maas
Importance: Undecided
Status: New
--
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/1358586
Title:
fails to deploy machines when eth0 does not exist
To
** Also affects: maas
Importance: Undecided
Status: New
--
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/1316214
Title:
maas package should depend or suggest libvirt-bin for
** Changed in: maas
Milestone: None = 1.7.2
--
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/1306178
Title:
maas-region-controller-min overwrites changes to
We're not on a bridged network (nor are there VMs) so we may be seeing a
different bug, or perhaps both situations trigger the same symptom. I'll
try playing with the timeout.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in
I installed a newer version of pxelinux to see if that is the culprit.
It doesn't work, but /some/ traffic between the nodes now happens when
transferring the kernel:
11:54:03.181388 IP 10.0.0.12.49164 10.0.0.1.tftp: 77 RRQ
ubuntu/amd64/generic/trusty/release/boot-kernel octet tsize 0 blksize
Static ARP did not help.
Setting the MTU to 1200 caused pxelinux.0 to fail transferring with
similar, but different behaviour:
12:12:50.699971 IP 10.0.0.12.2071 10.0.0.1.tftp: 32 RRQ pxelinux.0 octet
blksize 1456
12:12:50.773393 IP 10.0.0.1.59263 10.0.0.12.2071: UDP, length 15
Oh, I'm mistaken -- it's exactly the same as before. I hadn't noticed
that the machine had replied once before going offline.
Gavin looked up the ARP issue and it turns out that pxelinux doesn't
respond to ARP when in the keyboard read loop and when in the tftp
send/recv loop, so that's why
Okay, we did a lot of debugging and tracing attempting to find the
problem. In the end, it was hardware.
I upgraded manually to a newer version of syslinux and pxelinux which
/did/ appear to be working, albeit VERY slowly. It seems that the 6.x
syslinux network stack is more tolerant of errors,
** Changed in: maas
Assignee: zack (jnrflatwork) = (unassigned)
--
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/1246236
Title:
pxe boot from maas fails due to time out
To manage
When we start transferring the kernel over, the machine on the other
side stops responding:
15:59:23.563014 IP 10.0.0.12.49164 10.0.0.1.tftp: 77 RRQ
ubuntu/amd64/generic/trusty/release/boot-kernel octet tsize 0 blksize 1408
15:59:23.578439 IP 10.0.0.1.59570 10.0.0.12.49164: UDP, length 29
** Also affects: munin via
http://munin-monitoring.org/ticket/1161
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #649283
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649283
** Also affects: munin (Debian) via
As noted in comment #4, the fix for this is quite straightforward; just
wrap the qw calls (i.e. the argument to foreach) in parenthesis. It's
fixed in Trusty, btw.
** Changed in: munin (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member
Could this be caused by improper quoting in the script which invokes
amttool?
power_pass={{power_pass}}
[...]
issue_amt_command() {
LC_ALL='C' AMT_PASSWORD=$power_pass amttool $ip_address $@
}
Though if the ShellTemplate is quoting this correctly, it shouldn't be a
problem:
kiko@gasolinux:~$
See also bug 1398196.
--
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/1389830
Title:
Don't use wlan0 for cluster to region communication [when cluster and
region are on same machine]
See also bug 1398159
--
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/1246236
Title:
pxe boot from maas fails due to time out
To manage notifications about this bug go to:
** Changed in: maas
Milestone: None = 1.7.1
--
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/1246236
Title:
pxe boot from maas fails due to time out
To manage notifications about
** Changed in: maas
Importance: Undecided = High
--
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/1382774
Title:
Postgresql installation for MAAS fails on locales missing language
This was confirmed fixed today by Juan Ciarlante and will go out with
1.7.0. Fantastic!
--
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/1382190
Title:
LXCs assigned IPs by MAAS DHCP
Could packaging detect whether the cluster and region are on the same
machine and if so use lo?
--
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/1389830
Title:
Don't use wlan0 for
** Changed in: maas
Status: Invalid = Fix Committed
** Branch linked: lp:~andreserl/maas/release_beta7_utopic
--
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/1379144
Title:
** Changed in: maas (Ubuntu)
Status: Fix Committed = Confirmed
--
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/1377964
Title:
maas-proxy logrotate permission denied
To manage
** Changed in: maas
Milestone: 1.7.0 = next
** Changed in: maas
Assignee: Graham Binns (gmb) = Jeroen T. Vermeulen (jtv)
--
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/1373261
** Changed in: maas
Milestone: 1.7.0 = 1.7.1
--
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/1381058
Title:
Upgrading introduces a spurious cluster controller
To manage
** Changed in: maas
Status: Invalid = Fix Committed
--
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/1382266
Title:
maas-proxy fails to start on freshly installed MAAS
To manage
** Changed in: maas
Milestone: next = 1.7.1
--
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/1373261
Title:
pserv.yaml rewrite breaks when MAAS URL uses IPv6 address
To manage
** Changed in: maas
Milestone: next = 1.7.1
--
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/1382774
Title:
Postgresql installation for MAAS fails on locales missing language
** Changed in: maas
Status: Triaged = Fix Committed
** Changed in: maas (Ubuntu)
Status: Confirmed = Fix Committed
--
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/1382266
I like this! I would like it even more if we found a way to avoid
multiple GENERATEs for /24s.
--
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/1382190
Title:
LXCs assigned IPs by MAAS
** Changed in: maas (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: maas
Status: Invalid = Incomplete
--
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/1382266
Title:
Let's try #2, though we will need to limit the size of the dynamic range
as part of that.
--
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/1382190
Title:
LXCs assigned IPs by MAAS DHCP
Well, whatever we do let's please not race with the lxc creation. That
would be worse than fixing this bug. :)
--
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/1382190
Title:
LXCs
** Changed in: maas
Milestone: None = next
--
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/1274947
Title:
juju lxc instances deployed via MAAS don't have resolvable hostnames
To
The problem is that I need to leave them triaged or I miss them in the
milestone list.
--
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/1373261
Title:
pserv.yaml rewrite breaks when
I see the postinst does indeed include a chown as the fix for bug
1377964. So someone explain to me, how could the postinst not get run if
the package is installed?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Changed in: maas
Status: Invalid = Triaged
--
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/1373261
Title:
pserv.yaml rewrite breaks when MAAS URL uses IPv6 address
To manage
** Changed in: maas
Milestone: None = 1.7.0
--
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/1381058
Title:
Upgrading introduces a spurious cluster controller
To manage
Public bug reported:
As per
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1274947/comments/13
we are not generating DNS PTR entries for LXC deployments on MAAS-driven
DHCP; I assume this has regressed with the new static assignment
mechanism.
This is a regression from 1.5 behaviour and
Public bug reported:
I installed MAAS 1.7 tip, and once the installation was done I changed
the IP address of the region controller. The cluster controller of
course can't connect to the region and that point, but because it
continuously respawns it fills the log with entries of the type:
Oh, I see, I need to change the IP in 3 places:
maas-cluster-http.conf
maas_local_settings.py:
pserv.yaml
And restart the cluster. But then, I get an error about the stream not
being accessible in pserv.log, which confusingly is caused by the region
not having been restarted. Weird.
--
You
Targeting to 1.7 and assigning to Julian to see what can be done about
it.
** Changed in: maas
Milestone: None = 1.7.0
** Changed in: maas
Importance: Undecided = Critical
** Changed in: maas
Assignee: (unassigned) = Julian Edwards (julian-edwards)
--
You received this bug
Public bug reported:
After a fresh install of MAAS, I went to set up my cluster, and I
entered an IP address that did not match the interface's IP address. It
succeeded in saving and nothing complained, but the DHCP daemon would
not start, reporting the following in the syslog (but not in any
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Milestone: None = next
--
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/1382196
Title:
** Changed in: maas
Status: Confirmed = Fix Committed
** Changed in: maas
Milestone: 1.7.0 = 1.6.1
** Changed in: maas
Milestone: 1.6.1 = None
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Changed in: maas
Status: Triaged = In Progress
--
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/1087183
Title:
MaaS cloud-init configuration specifies 'manage_etc_hosts:
** Changed in: maas
Milestone: None = 1.7.0
--
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/1379144
Title:
maas-proxy package won't install when upgrading from older version
To
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Andres, can you assign this one to yourself?
** Changed in: maas
Milestone: None = 1.7.0
--
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/1373261
Title:
pserv.yaml rewrite breaks
** Changed in: maas
Assignee: (unassigned) = Raphaël Badin (rvb)
--
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/1087183
Title:
MaaS cloud-init configuration specifies
** Changed in: maas
Assignee: (unassigned) = Julian Edwards (julian-edwards)
--
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/1367455
Title:
MAC address for node's IPMI is reversed
** Changed in: maas
Assignee: (unassigned) = Jason Hobbs (jason-hobbs)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-django in Ubuntu.
https://bugs.launchpad.net/bugs/1363348
Title:
[SRU] Multipart base64 file decoding
** Changed in: maas
Assignee: (unassigned) = Andres Rodriguez (andreserl)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas-enlist in Ubuntu.
https://bugs.launchpad.net/bugs/1081660
Title:
If maas-enlist fails to reach a DNS
Scott, Julian, I'm reopening this and marking it critical for 1.7, but
please file a new bug if that's a better way of handling it.
** Changed in: maas
Status: Fix Released = Confirmed
** Changed in: maas
Milestone: None = 1.7.0
** Changed in: maas
Importance: High = Critical
--
I see the same issue reported on my server every once in a while.
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 1361 (/usr/sbin/winbindd).
This means there was a problem with the program, such as a segfault.
Below is a backtrace for this process generated
Actually my traceback is completely different from what the reporter had
:-/
--
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/781195
Title:
Winbind service stops often
To manage
I'm using a slightly modified version of the ypbind file posted in
comment 5 on my diskless clients and it's working fine. The modification
is around the starting condition:
# XXX: the original file checks if net-device-up IFACE=!lo, but I can't
# get that to work. And this seems to race a bit
** Summary changed:
- NIS upstart dependancy broken for lucid
+ NIS upstart dependency broken for lucid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/569757
Title:
NIS upstart
** Also affects: qemu-linaro
Importance: Undecided
Status: New
** Also affects: qemu-linaro (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
Public bug reported:
Binary package hint: chkrootkit
This seems to be a regression from previous versions. Here's what I am
seeing on Lucid:
ii chkrootkit 0.49-3 rootkit detector
k...@anthem:~$ sudo /usr/lib/chkrootkit/ifpromisc
lo: not promisc and no packet sniffer sockets
I was referring to http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=525370 but now that I see it it's not exactly the
same issue.
So I think something is wrong in my cron.daily script, then, because I'm
seeing this in my email notifications. Let me check. Okay, so if
cron.daily is running its
Date: Tue, 6 Jul 2010 06:42:22 -0300
From: Cron Daemon r...@xxx
To: r...@xxx
Subject: Cron r...@anthem test -x /usr/sbin/anacron || ( cd / run-parts
--report /etc/cron.daily )
/etc/cron.daily/chkrootkit:
[...]
eth1: PACKET SNIFFER(/usr/sbin/dhcpd3[3805])
[...]
--
chkrootkit daily
I've run into this problem and applied the change as a workaround -- and
it allowed the installation to succeed.
** Changed in: net-snmp (Ubuntu)
Status: New = Confirmed
--
snmpd fails to upgrade
https://bugs.launchpad.net/bugs/589056
You received this bug notification because you are a
The easy workaround for this problem is just to killall -u snmp before
retrying the snmp install. Of course, once you get past that point, you
may very well run into bug 589056..
--
package snmpd failed to upgrade: userdel: user snmp is currently logged in
https://bugs.launchpad.net/bugs/573391
Public bug reported:
Binary package hint: bind9
When starting up the Jaunty-current bind9 daemon, a warning is printed
out in the daemon log which says:
max open files (1024) is smaller than max sockets (4096)
ii bind9
1:9.5.1.dfsg.P2-1ubuntu0.3 Internet Domain Name
90 matches
Mail list logo
