Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1200471
| From | Craig Small <csmall@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#1072831: getting memory info fails when running under lxc |
| Date | 2024-06-11 01:00 +0200 |
| Message-ID | <INW9z-21d0-3@gated-at.bofh.it> (permalink) |
| References | <IN5RD-1vdB-3@gated-at.bofh.it> <IN5RD-1vdB-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Sun, 9 Jun 2024 at 01:03, Paul Slootman <paul@debian.org> wrote: > # free > free: Unable to create meminfo structure That's procps_meminfo_new() failing but /proc/meminfo exists. The function: checks the parameters allocates some memory for the structure runs meminfo_make_hash_failed(), which sets up the hashtable runs meminfo_read failed which does some opens, seeks and reads. Could you check to see if in the container that lxcfs has overwritten the /proc/meminfo file? They sometimes do this for /proc/uptime. They might have messed one of the lines up and choked procps; I'm thinking like a tab/space at the end of the line or something that looks right to a human but not a computer. I think we'll need to either run a strace on free or a debugger to see where exactly the issue is. I'm not particularly worried about ps. This is a library meminfo issue so fixing free should fix ps too. procps after 3.3.17 has a *lot* of changes, but I didn't think parsing the meminfo file was one of those. - Craig
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#1072831: getting memory info fails when running under lxc Paul Slootman <paul@debian.org> - 2024-06-08 17:10 +0200
Bug#1072831: getting memory info fails when running under lxc Craig Small <csmall@debian.org> - 2024-06-11 01:00 +0200
Bug#1072831: getting memory info fails when running under lxc Paul Slootman <paul@debian.org> - 2024-06-11 11:30 +0200
Bug#1072831: getting memory info fails when running under lxc Paul Slootman <paul@debian.org> - 2024-06-11 13:30 +0200
Bug#1072831: getting memory info fails when running under lxc Jim Warner <james.warner@comcast.net> - 2024-06-12 16:50 +0200
Bug#1072831: getting memory info fails when running under lxc Jim Warner <james.warner@comcast.net> - 2024-06-12 17:00 +0200
Bug#1072831: getting memory info fails when running under lxc Craig Small <csmall@debian.org> - 2024-06-23 09:50 +0200
Bug#1072831: getting memory info fails when running under lxc Craig Small <csmall@dropbear.xyz> - 2024-06-23 23:50 +0200
Bug#1072831: getting memory info fails when running under lxc Paul Slootman <paul@debian.org> - 2024-06-24 13:40 +0200
csiph-web