public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Robert Obkircher <r.obkircher@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH v4 pve-container 1/5] Ensure that container startup warnings are displayed if startup fails.
Date: Mon, 17 Nov 2025 16:15:11 +0100	[thread overview]
Message-ID: <1d72e2f4-d9f9-4208-adbc-8e57cc66186e@proxmox.com> (raw)
In-Reply-To: <5373a455-9501-49e6-a37e-d760e0761c78@proxmox.com>

Am 17.11.25 um 12:30 PM schrieb Robert Obkircher:
> 
> On 11/13/25 17:14, Fiona Ebner wrote:
>> Am 13.11.25 um 4:04 PM schrieb Robert Obkircher:
>>> During container startup, warnings are written to a file, which is
>>> later logged to the RESTEnvironment. This should also happen in the
>>> presence of errors, so move it outside the eval block.
>>>
>>> Signed-off-by: Robert Obkircher <r.obkircher@proxmox.com>
>>> ---
>>>   src/PVE/LXC.pm | 6 ++++--
>>>   1 file changed, 4 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm
>>> index 89ccb54..44e20bc 100644
>>> --- a/src/PVE/LXC.pm
>>> +++ b/src/PVE/LXC.pm
>>> @@ -2976,10 +2976,12 @@ sub vm_start {
>>>             # if debug is requested, print the log it also when the
>>> start succeeded
>>>           print_ct_stderr_log($vmid) if $is_debug;
>> Should the same be done for the error log here?
> This is only for debug output in case of success. The preceding call
> already prints the log if it dies.

Oh, right, it's usually starting the monitor that fails.

Without '--debug', there's just not much to work with:

[I] root@pve9a1 ~# pct start 101
sync_wait: 34 An error occurred in another process (expected sequence
number 7)
__lxc_start: 2127 Failed to spawn container "101"
startup for container '101' failed

Maybe we could print a line to tell users that there is '--debug' after
such a failure to get more info? Or we might want to set a log level for
the non-debug start-up ('-l ERROR' or '-l WARN'). From a quick test,
this doesn't seem to behave as expected though, i.e. the log with '-l
DEBUG' has more lines of level ERROR than the log with '-l ERROR', which
is strange :S and would need to be looked into.

But it's independent of this series :)


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

  reply	other threads:[~2025-11-17 15:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 15:02 [pve-devel] [PATCH v4 pve-container 0/5] warn that nesting may be required Robert Obkircher
2025-11-13 15:02 ` [pve-devel] [PATCH v4 pve-container 1/5] Ensure that container startup warnings are displayed if startup fails Robert Obkircher
2025-11-13 16:14   ` Fiona Ebner
2025-11-17 11:30     ` Robert Obkircher
2025-11-17 15:15       ` Fiona Ebner [this message]
2025-11-13 15:03 ` [pve-devel] [PATCH v4 pve-container 2/5] Propagate prestart-hook warnings to task-log Robert Obkircher
2025-11-13 16:36   ` Fiona Ebner
2025-11-17 11:31     ` Robert Obkircher
2025-11-17 15:32       ` Fiona Ebner
2025-11-13 15:03 ` [pve-devel] [PATCH v4 pve-container 3/5] fix #6897: warn that nesting may be required for systemd Robert Obkircher
2025-11-13 15:03 ` [pve-devel] [PATCH v4 pve-container 4/5] fix #6897: constrain and untaint path for systemd version detection Robert Obkircher
2025-11-13 15:03 ` [pve-devel] [PATCH v4 pve-container 4/5] fix #6897: constrain and untaint path when detecting systemd version Robert Obkircher
2025-11-13 15:03 ` [pve-devel] [PATCH v4 pve-container 5/5] fix #6897: also warn in the post_clone and post_create hooks Robert Obkircher

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=1d72e2f4-d9f9-4208-adbc-8e57cc66186e@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=r.obkircher@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