All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel List <xen-devel@lists.xen.org>
Cc: Ian Campbell <Ian.Campbell@citrix.com>
Subject: xl errors if /var/log/xen doesn't exist
Date: Mon, 13 Jan 2014 14:32:50 +0000	[thread overview]
Message-ID: <52D3F912.7080004@citrix.com> (raw)

Hello,

As part of running XenRT on a XenServer experimental build on top of
Xen-4.4.0-rc1, I encountered the following error which is far from helpful:

$ xl create /root/minios.cfg
xl: fatal error: xl_cmdimpl.c:457: No such file or directory: logfile =
open(fullname, O_WRONLY|O_CREAT|O_APPEND, 0644)
Parsing config from /root/minios.cfg
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus:
daemonizing child [32476] exited with error status 3
Parsing config from /root/minios.cfg

The root cause of the issue is that the directly /var/log/xen didn't
exist (because I messed up the packaging).

Because of the CHK_SYSCALL() macro which prints a string-ized version of
its argument, the error message omits the key detail (i.e. which file
doesn't exist).  Furthermore, the string 'fullname' is a complete path
which has been returned from "libxl_create_logfile()" without error.

If the failure to create a logfile is a fatal error (which itself is
probably not correct - what about a RO dom0 which strictly logs to
rsyslog?), then either xl or libxl should assume the responsibility of
ensuring that its logging directory actually exists, and
"libxl_create_logfile()" seems like a prime candidate to assume this
responsibility.

~Andrew

             reply	other threads:[~2014-01-13 14:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 14:32 Andrew Cooper [this message]
2014-01-13 15:07 ` xl errors if /var/log/xen doesn't exist Ian Campbell
2014-01-13 15:15   ` Processed: " xen

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=52D3F912.7080004@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.