[Pkg-salt-team] Bug#922064: [salt-master] Salt master doesn't start anymore after update

[Benjamin Drung]

Am Dienstag, den 12.02.2019, 17:42 +0100 schrieb Dirk Heinrichs:
> Am 12.02.19 um 17:37 schrieb Benjamin Drung:
> 
> > So then it is a bug in psutil. Can you attach the content of
> > /proc/meminfo?
> 
> Here you are:
> # cat /proc/meminfo
> MemTotal:       16350148 kB
> MemFree:         3822056 kB
> MemAvailable:    9057676 kB
> Buffers:            1356 kB
> Cached:          4943992 kB
> SwapCached:            0 kB
> Active:          7324360 kB
> Inactive:         948080 kB
> Active(anon):    3682896 kB
> Inactive(anon):   326888 kB
> Active(file):    3641464 kB
> Inactive(file):   621192 kB
> Unevictable:           0 kB
> Mlocked:               0 kB
> SwapTotal:             0 kB
> SwapFree:              0 kB
> Dirty:                28 kB
> Writeback:             0 kB
> AnonPages:       3327100 kB
> Mapped:           450524 kB
> Shmem:            682688 kB
> Slab:            2764932 kB
> SReclaimable:    1286500 kB
> SUnreclaim:      1478432 kB
> KernelStack:       11024 kB
> PageTables:        30728 kB
> NFS_Unstable:          0 kB
> Bounce:                0 kB
> WritebackTmp:          0 kB
> CommitLimit:     8175072 kB
> Committed_AS:    8113820 kB
> VmallocTotal:   34359738367 kB
> VmallocUsed:           0 kB
> VmallocChunk:          0 kB
> Percpu:             8272 kB
> HardwareCorrupted:     0 kB
> AnonHugePages:   1359872 kB
> ShmemHugePages:        0 kB
> ShmemPmdMapped:        0 kB
> HugePages_Total:       0
> HugePages_Free:        0
> HugePages_Rsvd:        0
> HugePages_Surp:        0
> Hugepagesize:       2048 kB
> Hugetlb:               0 kB
> DirectMap4k:     8894708 kB
> DirectMap2M:     7806976 kB
> DirectMap1G:           0 kB

That file works fine.

> > psutil failed to parse it on your machine.
> 
> Hmm, is this new in 2018.3.4? Didn't have this problem with 2018.3.3.

As already stated. This is a bug in python3-psutil. It's not salt fault
and therefore the update is not the reason.

> And could it be because it's an LXC Container?

Very likely. Can you send me the output of /proc/meminfo from inside
the container?

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

1&1 IONOS Cloud GmbH | Greifswalder Str. 207 | 10405 Berlin | Germany
E-mail: benjamin.drung at cloud.ionos.com | Web: www.ionos.de

Head Office: Berlin, Germany
District Court Berlin Charlottenburg, Registration number: HRB 125506 B
Executive Management: Christoph Steffens, Matthias Steinberg, Achim
Weiss

Member of United Internet