Open mitch0667 opened 8 months ago
Note: it even killed my k8s cluster :S
┌────────────────────────────────────────────────────────────── Nodes(all)[3] ───────────────────────────────────────────────────────────────┐
│ NAME↑ STATUS ROLE VERSION PODS AGE │
│ k8s-master Ready control-plane v1.28.2 8 120d │
│ um250 NotReady <none> v1.28.2 17 120d │
│ um300 NotReady <none> v1.28.2 8 120d │
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning SystemOOM 46m kubelet System OOM encountered, victim process: php-fpm82, pid: 498675
Warning SystemOOM 42m kubelet System OOM encountered, victim process: php-fpm82, pid: 498539
Warning FreeDiskSpaceFailed 42m kubelet Failed to garbage collect required amount of images. Attempted to fre
e 8805430067 bytes, but only found 0 bytes eligible to free.
Normal NodeHasSufficientMemory 39m (x8 over 11d) kubelet Node um250 status is now: NodeHasSufficientMemory
Normal NodeHasNoDiskPressure 39m (x11 over 11d) kubelet Node um250 status is now: NodeHasNoDiskPressure
Normal NodeHasSufficientPID 39m (x8 over 11d) kubelet Node um250 status is now: NodeHasSufficientPID
Warning SystemOOM 39m kubelet System OOM encountered, victim process: php-fpm82, pid: 498618
Normal NodeNotReady 39m (x2 over 11h) kubelet Node um250 status is now: NodeNotReady
Normal NodeReady 39m (x7 over 11d) kubelet Node um250 status is now: NodeReady
Warning FreeDiskSpaceFailed 37m kubelet Failed to garbage collect required amount of images. Attempted to fre
e 9408688947 bytes, but only found 0 bytes eligible to free.
Warning ImageGCFailed 37m kubelet Failed to garbage collect required amount of images. Attempted to fre
e 9408688947 bytes, but only found 0 bytes eligible to free.
Warning FreeDiskSpaceFailed 32m kubelet Failed to garbage collect required amount of images. Attempted to fre
e 9408807731 bytes, but only found 0 bytes eligible to free.
Warning ImageGCFailed 32m kubelet Failed to garbage collect required amount of images. Attempted to fre
e 9408807731 bytes, but only found 0 bytes eligible to free.
Warning FreeDiskSpaceFailed 27m kubelet Failed to garbage collect required amount of images. Attempted to fre
e 9408897843 bytes, but only found 0 bytes eligible to free.
Warning FreeDiskSpaceFailed 22m kubelet Failed to garbage collect required amount of images. Attempted to fre
e 9408946995 bytes, but only found 0 bytes eligible to free.
Warning SystemOOM 17m kubelet System OOM encountered, victim process: php-fpm82, pid: 499747
Normal NodeNotReady 16m (x8 over 11d) node-controller Node um250 status is now: NodeNotReady
Hello,
Since I upgraded to v14.1.0, I noticed that my server is consuming lot of ressources. While digging, several instances of ffmpeg are launched in the background when I navigate to Piwigo album that contain video.
At some point, I even experienced server that runs Piwigo not responding anymore.
This is what I get in /tmp folder:
Do you know what is the purpose of these ffmepg tasks? Is there any way to avoid it?
Thanks!