public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: Marco Gaiarin <gaio@lilliput.linux.it>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] Peak load at 7.30AM...
Date: Wed, 26 Apr 2023 12:48:48 +0200	[thread overview]
Message-ID: <e5cnhj-36o.ln1@hermione.lilliput.linux.it> (raw)


Situation: a debian stretch mostly 'samba server' for a 150+ clients, in a
couple of phisical server; VM get replicated between the two server every 30
minutes.

Very frequently at 7.30 the VM got a high peak rate, becaming mostly
irresponsive; after fiddling a bit, i've added a watchdog LOAD limit, and
the VM now reboot.

Looking at logs, it seems caused by the replica of the 7.30:

	Apr 26 07:30:12 vdmsv1 qemu-ga: info: guest-ping called
	Apr 26 07:30:13 vdmsv1 qemu-ga: info: guest-fsfreeze called

and after some (6 to 8 minutes) watchdog reset it:

	Apr 26 07:36:11 vdmsv1 watchdog[2525]: loadavg 57 33 14 is higher than the given threshold 80 32 16!
	Apr 26 07:36:11 vdmsv1 watchdog[2525]: shutting down the system because of error 253 = 'load average too high'


Some notes:

1) the replica run every 30 minutes; no other of the 47 replicas of the day
  seems sufficient to trigger a reboot.

2) the phisical server during the high peak seems totally unaffected (no
  high iodelay, no sensible load/cpu...).

3) at 7.30 there's no user (they arrive around 8.15).


I'm doing some hypotesis; for example debian by default rotate logs at 6.30,
but looking at file dates logs are completely rotated before the 7.00, so
the 7.00 replica could have triggered the reboot...


Someone have some hint on how can i debug this!?


Thanks.

-- 
  E allora osservi gli altri giocare
  e` un gioco strano devi imparare			(E. Bennato)





             reply	other threads:[~2023-04-26 12:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26 10:48 Marco Gaiarin [this message]
2023-04-26 14:17 ` Laurent CARON
2023-04-27 12:32 ` Marco Gaiarin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e5cnhj-36o.ln1@hermione.lilliput.linux.it \
    --to=gaio@lilliput.linux.it \
    --cc=pve-user@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal