[Bug 1287222] Re: openssh-client 6.5 regression bug with certain servers
The workaround is fine, but if you want more detailed description about the underlying issues (there are more than one) see the Red Hat bug: https://bugzilla.redhat.com/show_bug.cgi?id=1026430 -- 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/1287222 Title: openssh-client 6.5 regression bug with certain servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1287222/+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 1037607] Re: vmbuilder completely fails on Quantal due to kernel pae detection failure
Maybe you're right. I just followed the original patch. -- 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/1037607 Title: vmbuilder completely fails on Quantal due to kernel pae detection failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1037607/+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 1037607] Re: vmbuilder completely fails on Quantal due to kernel pae detection failure
I also confirm the patch in #3 works. However I'd suggest that rather than patching dapper.py, it would be better to do modify the quantal.py subclass (if that's the first release which requires /proc to be mounted). Otherwise you're going to change the build behaviour for all previous releases too. ** Patch added: Slightly cleaner way to handle dirty hack https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1037607/+attachment/4165701/+files/quantal.py.diff -- 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/1037607 Title: vmbuilder completely fails on Quantal due to kernel pae detection failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1037607/+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 1348672] [NEW] virsh memtune fails with LXC guests (lxcDomainGetMemoryParameters)
Public bug reported: [ubuntu 14.04 amd64 on Mac Mini, fully up to date] The virsh memtune function (see ftp://libvirt.org/libvirt/virshcmdref/html/sect-memtune.html) completely fails with LXC guests; it looks to be some sort of protocol/ABI problem. $ virsh -c lxc: ... virsh # memtune gold-lxc-20140717 error: Unable to get number of memory parameters error: unsupported flags (0x4) in function lxcDomainGetMemoryParameters Here is the XML for this guest: virsh # dumpxml gold-lxc-20140717 domain type='lxc' id='6265' namegold-lxc-20140717/name uuidb2a02d49-bb1e-4aec-81d1-58910892780e/uuid memory unit='KiB'327680/memory currentMemory unit='KiB'327680/currentMemory vcpu placement='static'1/vcpu resource partition/machine/partition /resource os type arch='x86_64'exe/type init/sbin/init/init /os clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/lib/libvirt/libvirt_lxc/emulator filesystem type='mount' accessmode='passthrough' source dir='/data1/lxc/gold-20140717/rootfs'/ target dir='/'/ /filesystem interface type='bridge' mac address='52:54:5d:00:0a:88'/ source bridge='br-lan'/ target dev='vnet0'/ /interface console type='pty' tty='/dev/pts/1' source path='/dev/pts/1'/ target type='lxc' port='0'/ alias name='console0'/ /console /devices seclabel type='none'/ /domain ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libvirt-bin 1.2.2-0ubuntu13.1.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Fri Jul 25 14:25:11 2014 InstallationDate: Installed on 2014-07-16 (8 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu.conf'] ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1348672 Title: virsh memtune fails with LXC guests (lxcDomainGetMemoryParameters) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1348672/+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 1348688] [NEW] LXC does not limit swap usage (memory.memsw.limit_in_bytes missing)
Public bug reported:
(Sorry I'm not sure exactly what package to report this against - kernel
perhaps? libvirt is what I was using to replicate the problem)
Host platform: ubuntu 14.04 amd64, Mac Mini, 16GB RAM.
Short version: create an LXC domain with memtune swap_hard_limit set
in the XML:
domain type='lxc'
namegold-lxc-20140717/name
uuidb2a02d49-bb1e-4aec-81d1-58910892780e/uuid
memory unit='KiB'327680/memory
currentMemory unit='KiB'327680/currentMemory
memtune
swap_hard_limit unit='KiB'131072/swap_hard_limit
/memtune
...
(full version at end of this report)
Now try to start it:
$ virsh -c lxc: start gold-lxc-20140717error: Failed to start domain
gold-lxc-20140717
error: internal error: guest failed to start: Unable to write to
'/sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/memory.memsw.limit_in_bytes':
No such file or directory
The reason this matters is because otherwise the LXC memory limit
applies only to real RAM used. If the guest exceeds this it can still
use as much swap space as it likes, and is therefore effectively
unlimited (and can happily DoS the swap disk).
Long version:
I created an ubuntu 14.04 i386 VM image using python-vmbuilder,
loopback-mounted it with qemu-nbd, and rsync'd it to create a root
filesystem for an LXC guest.
Then defined a guest using libvirt XML and started it using virsh -c
lxc: start domain (as per XML at end but without the memtune
section). It starts successfully, networking is fine, I can get a
console etc.
Now, the libvirt XML description says the guest's memory limit is 320MB:
memory unit='KiB'327680/memory
currentMemory unit='KiB'327680/currentMemory
and indeed the cgroups setting has been set:
$ cat
/sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/memory.limit_in_bytes
335544320
However inside the guest I can happily allocate as much memory as I
like, up to just under 4GB, which is the limit for a 32-bit guest.
Here's the test program I ran in the guest (usemem.c):
#include stdlib.h
#include unistd.h
#include stdio.h
int main(void)
{
char *p;
int i,j;
int ok=0, fail=0;
for (i=0; i4096; i++) {
p = malloc(1024*1024);
if (p) {
ok++;
for (j=0; j1024*1024; j++)
p[j] = rand();
}
else
fail++;
}
fprintf(stderr, Done: %d ok, %d fail\n, ok, fail);
sleep(600);
return fail ? 1 : 0;
}
Result from running:
Done: 4076 ok, 20 fail
View from the host:
nsrc@kit1:~/workshop-kit$ ps auxwww | grep usemem | grep -v grep
nsrc 10506 96.1 1.3 4192152 224776 ? S+ 14:41 0:55 ./usemem
$ cat
/sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/memory.limit_in_bytes
335544320
$ cat
/sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/memory.max_usage_in_bytes
335544320
$ cat
/sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/memory.usage_in_bytes
292331520
You can see there's definitely 4GB in use by this process, and yet the
cgroup thinks less than 280MB is in use, which is below the 320MB limit.
However if you look at swap usage in the host while the memory suck
program is running:
$ free
total used free sharedbuffers cached
Mem: 163383003066952 13271348 1684 1355121489268
-/+ buffers/cache:1442172 14896128
Swap: 166789083971248 12707660
and after it has terminated:
$ free
total used free sharedbuffers cached
Mem: 163383002774440 13563860 1684 1355441489188
-/+ buffers/cache:1149708 15188592
Swap: 16678908 5484 16673424
i.e. the LXC guest used nearly 4GB of swap, and then gave it up when it
terminated.
Additional info:
cgroup view from inside the guest:
$ cat /proc/self/cgroup
11:name=systemd:/
10:hugetlb:/
9:perf_event:/machine/gold-lxc-20140717.libvirt-lxc
8:blkio:/machine/gold-lxc-20140717.libvirt-lxc
7:freezer:/machine/gold-lxc-20140717.libvirt-lxc
6:devices:/machine/gold-lxc-20140717.libvirt-lxc
5:memory:/machine/gold-lxc-20140717.libvirt-lxc
4:cpuacct:/machine/gold-lxc-20140717.libvirt-lxc
3:cpu:/machine/gold-lxc-20140717.libvirt-lxc
2:cpuset:/machine/gold-lxc-20140717.libvirt-lxc
cgroup settings visible in the host:
$ ls /sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/
cgroup.clone_children memory.limit_in_bytes
cgroup.event_controlmemory.max_usage_in_bytes
cgroup.procsmemory.move_charge_at_immigrate
memory.failcnt memory.numa_stat
memory.force_empty memory.oom_control
memory.kmem.failcnt memory.pressure_level
memory.kmem.limit_in_bytes memory.soft_limit_in_bytes
memory.kmem.max_usage_in_bytes memory.stat
memory.kmem.slabinfomemory.swappiness
memory.kmem.tcp.failcnt memory.usage_in_bytes
memory.kmem.tcp.limit_in_bytes
[Bug 1348698] [NEW] libvirtd with lxc: cannot destroy domain (apparmor blocks kill signal)
Public bug reported: Host: ubuntu 14.04 amd64, Mac mini 16GB. * Prepare an Ubuntu 14.04 guest rootfs * Define an LXC instance using libvirt XML (see below) * virsh start -c lxc: domain * virsh destroy -c lxc: domain gives the following error: $ virsh -c lxc: destroy gold-lxc-20140717 error: Failed to destroy domain gold-lxc-20140717 error: Failed to kill process 18636: Permission denied and the following logged in /var/log/syslog on the host: Jul 25 15:21:22 kit1 kernel: [ 7735.523579] type=1400 audit(1406301682.520:40): apparmor=DENIED operation=signal profile=/sbin/dhclient pid=17503 comm=libvirtd requested_mask=receive denied_mask=receive signal=term peer=/usr/sbin/libvirtd Jul 25 15:21:22 kit1 kernel: [ 7735.523756] type=1400 audit(1406301682.520:41): apparmor=DENIED operation=signal profile=/sbin/dhclient pid=17503 comm=libvirtd requested_mask=receive denied_mask=receive signal=term peer=/usr/sbin/libvirtd The guest has an eth0 vnet NIC which is attached to a bridge on the host, and picks up an IP address through DHCP. It appears that libvirtd is being prevented from shutting down this dhclient process by apparmor, and this in turn aborts the whole 'destroy' operation. Workaround: kill the dhclient process by hand, before issuing the virsh destroy. (There is unfortunately no lxc:///session like qemu:///session to bypass libvirtd). Full XML: domain type='lxc' id='16776' namegold-lxc-20140717/name uuidb2a02d49-bb1e-4aec-81d1-58910892780e/uuid memory unit='KiB'327680/memory currentMemory unit='KiB'327680/currentMemory memtune hard_limit unit='KiB'524288/hard_limit /memtune vcpu placement='static'1/vcpu resource partition/machine/partition /resource os type arch='x86_64'exe/type init/sbin/init/init /os clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/lib/libvirt/libvirt_lxc/emulator filesystem type='mount' accessmode='passthrough' source dir='/data1/lxc/gold-20140717/rootfs'/ target dir='/'/ /filesystem interface type='bridge' mac address='52:54:5d:00:0a:88'/ source bridge='br-lan'/ target dev='vnet0'/ /interface console type='pty' tty='/dev/pts/1' source path='/dev/pts/1'/ target type='lxc' port='0'/ alias name='console0'/ /console /devices seclabel type='none'/ /domain ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libvirt-bin 1.2.2-0ubuntu13.1.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Fri Jul 25 15:18:44 2014 InstallationDate: Installed on 2014-07-16 (8 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu.conf'] ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1348698 Title: libvirtd with lxc: cannot destroy domain (apparmor blocks kill signal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1348698/+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 568687] Re: Built vm image file retains random temp filename
Still in 14.04. The other problem with the current directory containing temporary name approach is that it does not properly map to any libvirt storage type (either 'file' or 'directory'), and therefore cannot be managed properly through virsh or virt-manager, e.g. you can't clone it. -- 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/568687 Title: Built vm image file retains random temp filename To manage notifications about this bug go to: https://bugs.launchpad.net/server-papercuts/+bug/568687/+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 1342949] [NEW] nbd-server claims oldstyle exports not configured
Public bug reported:
[ubuntu 14.04]
Given the following config file:
/etc/nbd-server/config
[generic]
# If you want to run everything as root rather than the nbd user, you
# may either say root in the two following lines, or remove them
# altogether. Do not remove the [generic] section, however.
user = nbd
group = nbd
includedir = /etc/nbd-server/conf.d
listenaddr = 10.10.0.241
oldstyle = true
# What follows are export definitions. You may create as much of them as
# you want, but the section header has to be unique.
[disk1]
exportname = /data/nbd/disk1.img
flush = true
fua = true
port = 20001
When you restart nbd-server the following severe-sounding warning is
reported:
# service nbd-server restart
Restarting the Network Block Device server is pretty harsh on clients still
using it.
waiting 5 seconds...You have been warned!
Restarting Network Block Device server: Stopping Network Block Device server:
nbd-server.
** (process:19655): WARNING **: A port was specified, but oldstyle
exports were not requested. This may not do what you expect.
** (process:19655): WARNING **: Please read 'man 5 nbd-server' and search for
oldstyle for more info
nbd-server.
However very clearly oldstyle = true has been set in the config. This
config is definitely being read, because setting oldstyle = blah gives
an error about invalid boolean.
Looking at source: it seems that glob_flags is not updated until after
parse_cfile has returned:
servers = parse_cfile(config_file_pos, genconf, err);
/* Update global variables with parsed values. This will be
* removed once we get rid of global configuration variables. */
glob_flags |= genconf.flags;
However this warning comes from within parse_cfile and based on the
previous glob_flags setting.
if(s.port !(glob_flags F_OLDSTYLE)) {
g_warning(A port was specified, but oldstyle exports
were not requested. This may not do what you expect.);
g_warning(Please read 'man 5 nbd-server' and search
for oldstyle for more info);
}
And a process *is* running and listening on port 20001.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nbd-server 1:3.7-1
ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
Date: Wed Jul 16 20:34:44 2014
InstallationDate: Installed on 2014-07-16 (0 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64
(20140416.2)
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: nbd
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: nbd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug trusty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nbd in Ubuntu.
https://bugs.launchpad.net/bugs/1342949
Title:
nbd-server claims oldstyle exports not configured
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/1342949/+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 1310653] Re: python-vm-builder in Precise unable to build Trusty images
related (duplicate of?) #1287943 -- 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/1310653 Title: python-vm-builder in Precise unable to build Trusty images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1310653/+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 1287943] Re: vm-builder needs trusty suite
I see hang at Base system installed successfully too, building Trusty
VM under Precise 64-bit.
Last three lines of ps auxwww are:
root 20430 0.1 0.0 40060 9716 pts/2S+ 10:36 0:00
/usr/bin/python /usr/bin/vmbuilder kvm ubuntu --suite trusty --hostname trusty
--mem 512 --debug --dest /var/lib/libvirt/images/trusty
root 20432 0.0 0.0 0 0 pts/2Z+ 10:36 0:00 [debootstrap]
defunct
root 31685 0.0 0.0 9892 1180 ?Ss 10:37 0:00 udevd --daemon
There is a zombie debootstrap.
# pstree -s 20432
init───sshd───sshd───sshd───bash───sudo───bash───vmbuilder───debootstrap
# ps -o pid,ppid -C debootstrap
PID PPID
20432 20430
Same backtrace from ctrl-C:
^CTraceback (most recent call last):
File /usr/bin/vmbuilder, line 24, in module
cli.main()
File /usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py, line 216,
in main
distro.build_chroot()
File /usr/lib/python2.7/dist-packages/VMBuilder/distro.py, line 83, in
build_chroot
self.call_hooks('bootstrap')
File /usr/lib/python2.7/dist-packages/VMBuilder/distro.py, line 67, in
call_hooks
call_hooks(self, *args, **kwargs)
File /usr/lib/python2.7/dist-packages/VMBuilder/util.py, line 165, in
call_hooks
getattr(context, func, log_no_such_method)(*args, **kwargs)
File /usr/lib/python2.7/dist-packages/VMBuilder/plugins/ubuntu/distro.py,
line 136, in bootstrap
self.suite.debootstrap()
File /usr/lib/python2.7/dist-packages/VMBuilder/plugins/ubuntu/dapper.py,
line 269, in debootstrap
run_cmd(*cmd, **kwargs)
File /usr/lib/python2.7/dist-packages/VMBuilder/util.py, line 113, in
run_cmd
fds = select.select([x.file for x in [mystdout, mystderr] if not x.closed],
[], [])[0]
KeyboardInterrupt
So it's definitely a question of python waiting for data from the child,
but the child has gone away.
--
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/1287943
Title:
vm-builder needs trusty suite
To manage notifications about this bug go to:
https://bugs.launchpad.net/vmbuilder/+bug/1287943/+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 1287943] Re: vm-builder needs trusty suite
There is a nasty race condition in the code, which is easily fixed: --- /usr/share/pyshared/VMBuilder/util.py.orig 2010-06-10 17:20:58.0 + +++ /usr/share/pyshared/VMBuilder/util.py 2014-06-19 10:57:09.723017475 + @@ -108,9 +108,12 @@ mystdout = NonBlockingFile(proc.stdout, logfunc=logging.debug) mystderr = NonBlockingFile(proc.stderr, logfunc=(ignore_fail and logging.debug or logging.info)) -while not (mystdout.closed and mystderr.closed): +while True: +fdset = [x.file for x in [mystdout, mystderr] if not x.closed] +if not fdset: +break # Block until either of them has something to offer -fds = select.select([x.file for x in [mystdout, mystderr] if not x.closed], [], [])[0] +fds = select.select(fdset, [], [])[0] for fp in [mystderr, mystdout]: if fp.file in fds: fp.process_input() Unfortunately that doesn't fix the problem :-( Adding debugging shows that mystdout remains open, but does not show ready to read from select(). Oddly, it seems that mystderr.closed becomes true almost immediately after starting debootstrap. 2014-06-19 11:16:11,884 DEBUG : Calling bootstrap method in context plugin VMBuilder.plugins.ubuntu.distro. 2014-06-19 11:16:11,884 DEBUG : ['/usr/sbin/debootstrap', '--arch=i386', 'trusty', '/tmp/tmpBQAxhc', 'http://apt.ws.nsrc.org:3142/archive.ubuntu.com/ubuntu'] *** Starting ['/usr/sbin/debootstrap', '--arch=i386', 'trusty', '/tmp/tmpBQAxhc', 'http://apt.ws.nsrc.org:3142/archive.ubuntu.com/ubuntu'] *** mystdout=VMBuilder.util.NonBlockingFile object at 0x7fcade825550, closed=False mystderr=VMBuilder.util.NonBlockingFile object at 0x7fcade825610, closed=False fdset=[open file 'fdopen', mode 'rb' at 0x7fcadea726f0, open file 'fdopen', mode 'rb' at 0x7fcadea72780] selecting... fds=[open file 'fdopen', mode 'rb' at 0x7fcadea72780] mystdout=VMBuilder.util.NonBlockingFile object at 0x7fcade825550, closed=False mystderr=VMBuilder.util.NonBlockingFile object at 0x7fcade825610, closed=True fdset=[open file 'fdopen', mode 'rb' at 0x7fcadea726f0] selecting... fds=[open file 'fdopen', mode 'rb' at 0x7fcadea726f0] It could be true that debootstrap closes stderr immediately of course. -- 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/1287943 Title: vm-builder needs trusty suite To manage notifications about this bug go to: https://bugs.launchpad.net/vmbuilder/+bug/1287943/+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 1287943] Re: vm-builder needs trusty suite
I can replicate this issue with a standalone python script. http://pastebin.com/vTREYc9n It hangs at: read stdout: 'I: Base system installed successfully.\n' Furthermore, if I add a timeout to select and force it to read anyway, I get an IOError: read stdout: [Errno 11] Resource temporarily unavailable It's easy to eliminate the zombie child. You can reap the child explicitly by adding this to the main loop: sys.stderr.write(poll=%s\n % repr(proc.poll())) However even after the child has terminated, select() still says there's no data to read, and read() gives EAGAIN. Note: changing the code to use proc.communicate() also hangs and leaves a zombie child. And that uses threads rather than non-blocking sockets. This looks very much like a bug in python to me. -- 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/1287943 Title: vm-builder needs trusty suite To manage notifications about this bug go to: https://bugs.launchpad.net/vmbuilder/+bug/1287943/+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 1287943] Re: vm-builder needs trusty suite
FYI: the system I'm using has kernel 3.8.0-42-generic, i.e. it was
installed at the time when the raring enablement stack was active.
I can now reproduce with just a few lines:
---
import subprocess
args = ['/usr/sbin/debootstrap', '--arch=i386', 'trusty', '/tmp/tmpBQAxhc',
'http://archive.ubuntu.com/ubuntu']
stdin_arg = file('/dev/null', 'r')
proc = subprocess.Popen(args, stdin=stdin_arg, stdout=subprocess.PIPE,
stderr=subprocess.STDOUT)
print repr(proc.communicate())
---
strace shows the hang here:
...
read(4, I: Configuring initramfs-tools., 1224) = 34
read(4, I: Base system installed success..., 1190) = 39
read(4, 0xd61919, 1151) = ? ERESTARTSYS (To be restarted)
--- SIGCHLD (Child exited) @ 0 (0) ---
read(4,
--
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/1287943
Title:
vm-builder needs trusty suite
To manage notifications about this bug go to:
https://bugs.launchpad.net/vmbuilder/+bug/1287943/+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 1287943] Re: vm-builder needs trusty suite
Argh. Scrub what I said about python. I can reproduce without python! # /usr/sbin/debootstrap --arch=i386 trusty /tmp/tmpBQAxhc http://archive.ubuntu.com/ubuntu | strace cat db.out ... read(0, I: Configuring initramfs-tools., 32768) = 34 write(1, I: Configuring initramfs-tools., 34) = 34 read(0, I: Base system installed success..., 32768) = 39 write(1, I: Base system installed success..., 39) = 39 read(0, It hangs here - and there's no zombie child, so can't be debootstrap's fault. This is something really weird with pipes. -- 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/1287943 Title: vm-builder needs trusty suite To manage notifications about this bug go to: https://bugs.launchpad.net/vmbuilder/+bug/1287943/+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 1287943] Re: vm-builder needs trusty suite
OK, I found it. During debootstrap run, a process udevd --daemon is started. It persists when debootstrap gets to the end. If you kill it, the process reading from debootstrap's stdout is able to terminate. My guess is that stdout is being passed to that daemon, and it's holding it open. No idea of the fix though. Why is udevd being started in the first place? If it's being started as a daemon, why is it not closing its stdout? And if there is a reason for running it, shouldn't it be stopped before debootstrap finishes? -- 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/1287943 Title: vm-builder needs trusty suite To manage notifications about this bug go to: https://bugs.launchpad.net/vmbuilder/+bug/1287943/+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 1287943] Re: vm-builder needs trusty suite
I have raised these: Bug #1332155: debootstrap launches spurious udevd --daemon Bug #1332165: udevd --daemon does not close stdout -- 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/1287943 Title: vm-builder needs trusty suite To manage notifications about this bug go to: https://bugs.launchpad.net/vmbuilder/+bug/1287943/+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 1287943] Re: vm-builder needs trusty suite
The race condition in comment #17 is only true if mystdout.closed can become True asynchronously before we have called mystdout.close(). I'm not sure if there's any possibility of that. -- 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/1287943 Title: vm-builder needs trusty suite To manage notifications about this bug go to: https://bugs.launchpad.net/vmbuilder/+bug/1287943/+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 1185756] Re: drbd8-utils not compatible with linux-lts-raring kernel in 12.04
I'm not sure if anyone has mentioned it yet, but the command syntax to the drbdsetup command has changed totally between drbd8-utils 8.3 and 8.4 e.g. if you are using drbd-utils 8.3 then the command is drbdsetup /dev/drbd0 show if you are using drbd-utils 8.4 then the command is drbdsetup show /dev/drbd0 Therefore if you upgrade your kernel to the raring enablement one, your pacemaker (etc) scripts will break too. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/1185756 Title: drbd8-utils not compatible with linux-lts-raring kernel in 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+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 1185756] Re: drbd8-utils not compatible with linux-lts-raring kernel in 12.04
Hmm, just to clarify: when using the drbd8-utils 8.4 package and the kernel module 8.3, then drbdsetup execs the drbdsetup-83 compatibility module which implements the old syntax, and will also if necessary swap the first two arguments for forward compatibility However there are some commands that drbdsetup from drbd8-utils 8.3.10 accepts but drbdsetup-83 doesn't. For example, ganeti issues the following command: drbdsetup /dev/drbd2 disk /dev/xenvg/a614fd3b-d016-44a1-a6d6-c51334190757.disk0_data /dev/xenvg/a614fd3b-d016-44a1-a6d6-c51334190757.disk0_meta 0 -e detach --create-device -d 1024m This works with drbd8-utils 8.3.10, but gives USAGE: drbdsetup command device arguments options with 8.4 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/1185756 Title: drbd8-utils not compatible with linux-lts-raring kernel in 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+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 1310653] [NEW] python-vm-builder in Precise unable to build Trusty images
Public bug reported: Please backport python-vm-builder in Precise so that it can build Trusty images. In Trusty: python-vm-builder version 0.12.4+bzr489-0ubuntu2 $ ls /usr/lib/python2.7/dist-packages/VMBuilder/plugins/ubuntu/ dapper.py feisty.pycintrepid.py lucid.pyc precise.py saucy.pyc dapper.pyc gutsy.py intrepid.pyc maverick.py precise.pyc suite.py distro.py gutsy.pyc jaunty.py maverick.pyc quantal.py suite.pyc distro.pyc hardy.py jaunty.pycnatty.py quantal.pyc trusty.py edgy.py hardy.pyc karmic.py natty.pyc raring.pytrusty.pyc edgy.pyc__init__.py karmic.pyconeiric.pyraring.pyc feisty.py __init__.pyc lucid.py oneiric.pyc saucy.py In Precise: python-vm-builder version 0.12.4+bzr477-0ubuntu4 ls /usr/lib/python2.7/dist-packages/VMBuilder/plugins/ubuntu/ dapper.py feisty.pycintrepid.py lucid.pyc precise.py saucy.pyc dapper.pyc gutsy.py intrepid.pyc maverick.py precise.pyc suite.py distro.py gutsy.pyc jaunty.py maverick.pyc quantal.py suite.pyc distro.pyc hardy.py jaunty.pycnatty.py quantal.pyc edgy.py hardy.pyc karmic.py natty.pyc raring.py edgy.pyc__init__.py karmic.pyconeiric.pyraring.pyc feisty.py __init__.pyc lucid.py oneiric.pyc saucy.py (note missing trusty.py/pyc) ** Affects: vm-builder (Ubuntu) Importance: Undecided Status: New -- 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/1310653 Title: python-vm-builder in Precise unable to build Trusty images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1310653/+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 1278466] Re: [FFe] ceph firefly stable release
Just a note for early adopters to beware of: https://ceph.com/releases/v0-78-released/ Please note that while it is possible to create and test erasure coded pools in this release, the pools will not be usable when you upgrade to v0.79 as the OSDMap encoding will subtlely change. Please do not populate your test pools with important data that can’t be reloaded. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1278466 Title: [FFe] ceph firefly stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1278466/+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 865268] Re: snmpd reports wrong value for hrStorageSize on large filesystem
Also confirmed, this remains broken in 12.04 $ snmpwalk -v2c -c public storage3 hrStorageTable | grep \\.34HOST-RESOURCES-MIB::hrStorageIndex.34 = INTEGER: 34 HOST-RESOURCES-MIB::hrStorageType.34 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk HOST-RESOURCES-MIB::hrStorageDescr.34 = STRING: /disk/scratch HOST-RESOURCES-MIB::hrStorageAllocationUnits.34 = INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageSize.34 = INTEGER: 393941158 HOST-RESOURCES-MIB::hrStorageUsed.34 = INTEGER: 3959967469 Notice how hrStorageSize is much less than hrStorageUsed. Here is the real output from df: $ df -h /disk/scratch Filesystem Size Used Avail Use% Mounted on /dev/md127 66T 63T 2.8T 96% /disk/scratch $ df -k /disk/scratch Filesystem 1K-blocksUsed Available Use% Mounted on /dev/md127 70295241368 67379477428 2915763940 96% /disk/scratch But the values reported in hrStorageTable are: size = 393941158 * 4 = 1575764632 KiB = 1.47 TiB used = 3959967469 * 4 = 15839869876 KiB = 14.75 TiB -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-snmp in Ubuntu. https://bugs.launchpad.net/bugs/865268 Title: snmpd reports wrong value for hrStorageSize on large filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/865268/+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 865268] Re: snmpd reports wrong value for hrStorageSize on large filesystem
Looking at the source of net-snmp-5.4.3~dfsg, it appears to make no attempt to scale the block size to avoid 2^32 wrapping - see agent/mibgroup/host/hr_storage.c, var_hrstore() I have made a simple patch which fixes just this particular problem, so should be suitable for backporting to LTS. Once this patch has been applied, sane values are returned: $ snmpwalk -v2c -c public storage3 hrStorageTable | grep '\.34 'HOST-RESOURCES-MIB::hrStorageIndex.34 = INTEGER: 34 HOST-RESOURCES-MIB::hrStorageType.34 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk HOST-RESOURCES-MIB::hrStorageDescr.34 = STRING: /disk/scratch HOST-RESOURCES-MIB::hrStorageAllocationUnits.34 = INTEGER: 65536 Bytes HOST-RESOURCES-MIB::hrStorageSize.34 = INTEGER: 1098363146 HOST-RESOURCES-MIB::hrStorageUsed.34 = INTEGER: 1052804334 (Note: the agent modules are actually in libsnmp15, so after dpkg- buildpackage remember to install libsnmp15, libsnmp-base and snmpd) ** Patch added: hrStorage_large_filesystem.patch https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/865268/+attachment/3412218/+files/hrStorage_large_filesystem.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-snmp in Ubuntu. https://bugs.launchpad.net/bugs/865268 Title: snmpd reports wrong value for hrStorageSize on large filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/865268/+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 865268] [NEW] snmpd reports wrong value for hrStorageSize
Public bug reported: Look at hrStorageSize.34 in the below table. Notice that: (1) it's smaller than hrStorageUsed.34, so it can't possibly be right (2) it's the same as the previous row, hrStorageSize.33 $ snmpwalk -c public -v2c hostname hrStorageTable HOST-RESOURCES-MIB::hrStorageIndex.1 = INTEGER: 1 HOST-RESOURCES-MIB::hrStorageIndex.3 = INTEGER: 3 HOST-RESOURCES-MIB::hrStorageIndex.6 = INTEGER: 6 HOST-RESOURCES-MIB::hrStorageIndex.7 = INTEGER: 7 HOST-RESOURCES-MIB::hrStorageIndex.10 = INTEGER: 10 HOST-RESOURCES-MIB::hrStorageIndex.31 = INTEGER: 31 HOST-RESOURCES-MIB::hrStorageIndex.32 = INTEGER: 32 HOST-RESOURCES-MIB::hrStorageIndex.33 = INTEGER: 33 HOST-RESOURCES-MIB::hrStorageIndex.34 = INTEGER: 34 HOST-RESOURCES-MIB::hrStorageIndex.35 = INTEGER: 35 HOST-RESOURCES-MIB::hrStorageIndex.36 = INTEGER: 36 HOST-RESOURCES-MIB::hrStorageIndex.37 = INTEGER: 37 HOST-RESOURCES-MIB::hrStorageType.1 = OID: HOST-RESOURCES-TYPES::hrStorageRam HOST-RESOURCES-MIB::hrStorageType.3 = OID: HOST-RESOURCES-TYPES::hrStorageVirtualMemory HOST-RESOURCES-MIB::hrStorageType.6 = OID: HOST-RESOURCES-TYPES::hrStorageOther HOST-RESOURCES-MIB::hrStorageType.7 = OID: HOST-RESOURCES-TYPES::hrStorageOther HOST-RESOURCES-MIB::hrStorageType.10 = OID: HOST-RESOURCES-TYPES::hrStorageVirtualMemory HOST-RESOURCES-MIB::hrStorageType.31 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk HOST-RESOURCES-MIB::hrStorageType.32 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk HOST-RESOURCES-MIB::hrStorageType.33 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk HOST-RESOURCES-MIB::hrStorageType.34 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk HOST-RESOURCES-MIB::hrStorageType.35 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk HOST-RESOURCES-MIB::hrStorageType.36 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk HOST-RESOURCES-MIB::hrStorageType.37 = OID: HOST-RESOURCES-TYPES::hrStorageNetworkDisk HOST-RESOURCES-MIB::hrStorageDescr.1 = STRING: Physical memory HOST-RESOURCES-MIB::hrStorageDescr.3 = STRING: Virtual memory HOST-RESOURCES-MIB::hrStorageDescr.6 = STRING: Memory buffers HOST-RESOURCES-MIB::hrStorageDescr.7 = STRING: Cached memory HOST-RESOURCES-MIB::hrStorageDescr.10 = STRING: Swap space HOST-RESOURCES-MIB::hrStorageDescr.31 = STRING: / HOST-RESOURCES-MIB::hrStorageDescr.32 = STRING: /sys/fs/fuse/connections HOST-RESOURCES-MIB::hrStorageDescr.33 = STRING: /dev HOST-RESOURCES-MIB::hrStorageDescr.34 = STRING: /media/data HOST-RESOURCES-MIB::hrStorageDescr.35 = STRING: /media/data2 HOST-RESOURCES-MIB::hrStorageDescr.36 = STRING: /home/tomi/.gvfs HOST-RESOURCES-MIB::hrStorageDescr.37 = STRING: /media/monster1 HOST-RESOURCES-MIB::hrStorageAllocationUnits.1 = INTEGER: 1024 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.3 = INTEGER: 1024 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.6 = INTEGER: 1024 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.7 = INTEGER: 1024 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.10 = INTEGER: 1024 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.31 = INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.32 = INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.33 = INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.34 = INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.35 = INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.36 = INTEGER: 0 Bytes HOST-RESOURCES-MIB::hrStorageAllocationUnits.37 = INTEGER: 8192 Bytes HOST-RESOURCES-MIB::hrStorageSize.1 = INTEGER: 24732776 HOST-RESOURCES-MIB::hrStorageSize.3 = INTEGER: 49887332 HOST-RESOURCES-MIB::hrStorageSize.6 = INTEGER: 24732776 HOST-RESOURCES-MIB::hrStorageSize.7 = INTEGER: 18405520 HOST-RESOURCES-MIB::hrStorageSize.10 = INTEGER: 25154556 HOST-RESOURCES-MIB::hrStorageSize.31 = INTEGER: 116744604 HOST-RESOURCES-MIB::hrStorageSize.32 = INTEGER: 0 HOST-RESOURCES-MIB::hrStorageSize.33 = INTEGER: 3089665 HOST-RESOURCES-MIB::hrStorageSize.34 = INTEGER: 3089665 HOST-RESOURCES-MIB::hrStorageSize.35 = INTEGER: 388630628 HOST-RESOURCES-MIB::hrStorageSize.36 = INTEGER: 0 HOST-RESOURCES-MIB::hrStorageSize.37 = INTEGER: 1763671548 HOST-RESOURCES-MIB::hrStorageUsed.1 = INTEGER: 21206848 HOST-RESOURCES-MIB::hrStorageUsed.3 = INTEGER: 21266872 HOST-RESOURCES-MIB::hrStorageUsed.6 = INTEGER: 99780 HOST-RESOURCES-MIB::hrStorageUsed.7 = INTEGER: 18405520 HOST-RESOURCES-MIB::hrStorageUsed.10 = INTEGER: 60024 HOST-RESOURCES-MIB::hrStorageUsed.31 = INTEGER: 6489199 HOST-RESOURCES-MIB::hrStorageUsed.32 = INTEGER: 0 HOST-RESOURCES-MIB::hrStorageUsed.33 = INTEGER: 162 HOST-RESOURCES-MIB::hrStorageUsed.34 = INTEGER: 53617360 HOST-RESOURCES-MIB::hrStorageUsed.35 = INTEGER: 290113170 HOST-RESOURCES-MIB::hrStorageUsed.36 = INTEGER: 0 HOST-RESOURCES-MIB::hrStorageUsed.37 = INTEGER: 1163419544 brian@monitoring:~$ snmpwalk -c public -v2c recording1 hrStorageTable HOST-RESOURCES-MIB::hrStorageIndex.1 = INTEGER: 1 HOST-RESOURCES-MIB::hrStorageIndex.3 = INTEGER: 3 HOST-RESOURCES-MIB::hrStorageIndex.6 =
[Bug 865268] Re: snmpd reports wrong value for hrStorageSize
Looks like it could be related to this: https://bugzilla.redhat.com/show_bug.cgi?id=654384 Apparently a newer snmpd would clamp this value to 2^31, and an even newer snmpd would use a fake larger block size so as to be able to report on large filesystems: http://net-snmp.svn.sourceforge.net/viewvc/net-snmp?view=revisionrevision=19941 Workaround is to use the UCD-SNMP-MIB::dskTable instead, which can report dskAvail and dskPercent successfully for this large filesystem. ** Bug watch added: Red Hat Bugzilla #654384 https://bugzilla.redhat.com/show_bug.cgi?id=654384 ** Summary changed: - snmpd reports wrong value for hrStorageSize + snmpd reports wrong value for hrStorageSize on large filesystem -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-snmp in Ubuntu. https://bugs.launchpad.net/bugs/865268 Title: snmpd reports wrong value for hrStorageSize on large filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/865268/+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 430732] Re: radclient doesn't work
Still a problem in 10.04 LTS -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to freeradius in ubuntu. https://bugs.launchpad.net/bugs/430732 Title: radclient doesn't work -- 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
