Carlos Llamas wrote:
> I made a PHP script which locks a specific file in a NFS directory, measuring
> every step involved. Then exported the results to CSV and graphed it on ELK
> because I am more familiar with it.
Thanks for the additional details. It sounds like you have a
reproducible test
Carlos Llamas wrote:
> When this happens, apache2 processes on a backend VM (NFS client
> machine) wait in state D for a long time (I was only able to trace a
> file, and lasted 90s until file unlocked).
It sounds like the process is trying to unlock a file, and the system
call hangs for 90 secon
Hello,
We are facing this problem too with 3 backend VMs and a NFS VM.
Both servers are Google Cloud Compute Engine instances with plenty of CPU
and RAM. We don't see any correlation with high CPU or RAM usage whenever
this happens on any machine. When this happens, apache2 processes on a
backend
Hi
We recently migrated to new nfs server running on debian 12 bookworm
On the client Apache processes started randomly switching to D state,
In apache fluststatus Process 93661 a mis 10786 sec
=
4-1 93661 1598/ W 15.92 10786 0 2367404 0.0 71.45 142.44 172.20.1.47 http/1.1
sisca.gr
Who knows what pulseaudio developers were smoking when they wrote that
code. I'm glad you got this solved for now. I hope it's permanently
solved for you too.
On Tue, 8 Mar 2022, Daniel Fishman wrote:
> The first two things didn't work, but while I worked on a switch to
> pipewire (with a limi
The first two things didn't work, but while I worked on a switch to
pipewire (with a limited success, since pipewire is experimental
in the current stable and misses important features that I need
and which are already available in pulseaudio), I stumbled upon
a workaround which fixed the problem
> as soon as it is started (goes into an uninterruptible sleep). I couldn't
> understand what is the cause for this behavior - maybe somebody can provide
> an idea?
>
> Initially, pulse worked as expected - the machine doesn't have any fixed
> output devices, sound was us
Hello,
I have an up-to-date Debian stable machine where pulseaudio becomes stuck
as soon as it is started (goes into an uninterruptible sleep). I couldn't
understand what is the cause for this behavior - maybe somebody can provide
an idea?
Initially, pulse worked as expected - the ma
Hey folks,
One of our users has a few processes that are refusing to die -
according to /proc, they all have open file descriptors to his
mailbox, and are all listed as being in the uninterruptible sleep
mode. I assume that they are all stuck in I/O wait on that file for
some reason - at any
9 matches
Mail list logo