On Fri, Mar 25, 2022 at 12:27 PM Greg Wooledge wrote:
> On Fri, Mar 25, 2022 at 04:51:51PM +, Adam Weremczuk wrote:
> > [Tue Mar 22 00:24:10 2022] Tasks state (memory values in pages):
> > [Tue Mar 22 00:24:10 2022] [ pid ] uid tgid total_vm rss
> > pgtables_bytes swapents
On Fri, Mar 25, 2022 at 04:51:51PM +, Adam Weremczuk wrote:
> [Tue Mar 22 00:24:10 2022] Tasks state (memory values in pages):
> [Tue Mar 22 00:24:10 2022] [ pid ] uid tgid total_vm rss
> pgtables_bytes swapents oom_score_adj name
> [Tue Mar 22 00:24:10 2022] [ 2211] 0 2211
Thanks all for picking up a discussion and all the useful hints.
The container has been behaving since reboot, using 0 swap ATM.
Post-mortem on dhcp service crash is showing 100% memory usage and OOM,
still not sure why though:
[Tue Mar 22 00:24:10 2022] apt-get invoked oom-killer:
Adam Weremczuk writes:
> The container was running like that for several months until this morning
> when its core service (dhcp) started failing.
Just a wild guess, but do you know what caused dhcp to fail? Was it too
little memory?
>
> I logged in to investigate and noticed 100% of swap
I use
dphys-swapfile
this is a system service that auto configures a swap at boot without
requiring a static partition.
it computes the size of an optimal swap file and or resizes an existing
swap file if necessary. it mounts, dismounts, and deletes the swap if not
wanted. it doesn't
On 3/22/22 07:55, Adam Weremczuk wrote:
Hi all,
I run a tiny and lightweight Debian 9.9 LXC container on Proxmox 6.2-6.
It has 512 MB of memory and 512 MB of swap assigned and typically needs
50-100 MB to operate.
Last year I started seeing about half of swap being used with very
little
On Tue, Mar 22, 2022 at 04:00:23PM -0400, Kenneth Parker wrote:
> On Tue, Mar 22, 2022 at 2:17 PM Greg Wooledge wrote:
>
> > On Tue, Mar 22, 2022 at 01:00:42PM -0500, Nicholas Geovanis wrote:
> > > That's the usual issue. The /tmp filesystem is usually configured to live
> > > in RAM,
> >
> >
On Tue, Mar 22, 2022 at 2:17 PM Greg Wooledge wrote:
> On Tue, Mar 22, 2022 at 01:00:42PM -0500, Nicholas Geovanis wrote:
> > That's the usual issue. The /tmp filesystem is usually configured to live
> > in RAM,
>
> That's not the default in Debian. Of course, it might have been set up
> that
On Tue, Mar 22, 2022 at 01:00:42PM -0500, Nicholas Geovanis wrote:
> That's the usual issue. The /tmp filesystem is usually configured to live
> in RAM,
That's not the default in Debian. Of course, it might have been set up
that way on the OP's system.
> at some point an application needed to
On Tue, Mar 22, 2022 at 12:21 PM Dan Ritter wrote:
> Charles Curley wrote:
> > On Tue, 22 Mar 2022 14:55:34 +
> > Adam Weremczuk wrote:
> >
> > > It has 512 MB of memory and 512 MB of swap assigned and typically
> > > needs 50-100 MB to operate.
> >
> > The rule of thumb to which I am
Charles Curley wrote:
> On Tue, 22 Mar 2022 14:55:34 +
> Adam Weremczuk wrote:
>
> > It has 512 MB of memory and 512 MB of swap assigned and typically
> > needs 50-100 MB to operate.
>
> The rule of thumb to which I am accustomed is to have a swap space
> double the physical RAM. If
On Tue, Mar 22, 2022 at 10:35:40AM -0600, Charles Curley wrote:
> On Tue, 22 Mar 2022 14:55:34 +
> Adam Weremczuk wrote:
>
> > It has 512 MB of memory and 512 MB of swap assigned and typically
> > needs 50-100 MB to operate.
>
> The rule of thumb to which I am accustomed is to have a swap
On Tue, 22 Mar 2022 14:55:34 +
Adam Weremczuk wrote:
> It has 512 MB of memory and 512 MB of swap assigned and typically
> needs 50-100 MB to operate.
The rule of thumb to which I am accustomed is to have a swap space
double the physical RAM. If necessary, you can create a swap file and
add
Hi all,
I run a tiny and lightweight Debian 9.9 LXC container on Proxmox 6.2-6.
It has 512 MB of memory and 512 MB of swap assigned and typically needs
50-100 MB to operate.
Last year I started seeing about half of swap being used with very
little use of RAM.
I then made the following
14 matches
Mail list logo
