XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Build from sources error -- EISDIR: illegal operation on a directory, read

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    9 Posts 3 Posters 7.8k Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D Offline
      Dude417
      last edited by olivierlambert

      Debian 11

      Following directions from :

      https://xen-orchestra.com/docs/installation.html#from-the-sources

      Everything looks fine until I get to "yarn start".
      then :

      xo@XO-Source:~/xen-orchestra/packages/xo-server$ yarn start
yarn run v1.22.22
$ node dist/cli.mjs
āœ– EISDIR: illegal operation on a directory, read
Error: EISDIR: illegal operation on a directory, read
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
xo@XO-Source:~/xen-orchestra/packages/xo-server$

      I have tried installing as both a limited user "xo", and as root... same error.
      It appears to be a error where a directory is found rather that a file...
      Any ideas what log files / config files I should be looking at ???

      1 Reply Last reply Reply Quote 0
      • D Offline
        Dude417 @Danp
        last edited by

        @Danp

        Well.... yes...šŸ˜Š I was copying it, but I was also dropping a copy in the /etc/xo-server/config.toml directory as well....apparently i was trying to get ahead of the game.

        As soon as I removed the /etc/xo-server/config.toml path and sample.config.toml file, everything loaded. šŸ˜„

        1 Reply Last reply Reply Quote 1
        • DanpD Offline
          Danp Pro Support Team
          last edited by

          What does node -v return?

          D 1 Reply Last reply Reply Quote 0
          • D Offline
            Dude417 @Danp
            last edited by

            @Danp
            V20.12.2

            1 Reply Last reply Reply Quote 0
            • DanpD Offline
              Danp Pro Support Team
              last edited by

              From our docs šŸ˜‰ --

              XO requires Node.js 18.

              D 1 Reply Last reply Reply Quote 0
              • D Offline
                Dude417 @Danp
                last edited by

                @Danp

                root@XO-SourceBuild:/home/xo/xen-orchestra/packages/xo-server# yarn start
yarn run v1.22.22
$ node dist/cli.mjs
āœ– EISDIR: illegal operation on a directory, read
Error: EISDIR: illegal operation on a directory, read
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
root@XO-SourceBuild:/home/xo/xen-orchestra/packages/xo-server# node -v
v18.20.2
root@XO-SourceBuild:/home/xo/xen-orchestra/packages/xo-server#
                1 Reply Last reply Reply Quote 0
                • DanpD Offline
                  Danp Pro Support Team
                  last edited by

                  Well, at least we've rules out Node being the issue. šŸ˜†

                  Did you forget to create the config.toml file?

                  Now you have to create a config file for xo-server:

                  cd packages/xo-server
mkdir -p ~/.config/xo-server
cp sample.config.toml ~/.config/xo-server/config.toml
                  D 1 Reply Last reply Reply Quote 0
                  • D Offline
                    Dude417 @Danp
                    last edited by

                    @Danp

                    Well.... yes...šŸ˜Š I was copying it, but I was also dropping a copy in the /etc/xo-server/config.toml directory as well....apparently i was trying to get ahead of the game.

                    As soon as I removed the /etc/xo-server/config.toml path and sample.config.toml file, everything loaded. šŸ˜„

                    1 Reply Last reply Reply Quote 1
                    • olivierlambertO olivierlambert marked this topic as a question on
                    • olivierlambertO olivierlambert has marked this topic as solved on
                    • planedropP Offline
                      planedrop Top contributor
                      last edited by

                      I know this is an old topic and was resolved, however I am seeing a similar issue but my node version is right and I have NOT copied the sample config file to /etc/xo-server/config.toml, only to my .config/xo-server/ directory.

                      Specifically seeing this picture below, I'm sure I'm doing something wrong and just fumbling but I've followed the docs a few times.

                      007ebea3-02e4-462d-845f-d083430673fa-image.png

                      planedropP 1 Reply Last reply Reply Quote 0
                      • planedropP Offline
                        planedrop Top contributor @planedrop
                        last edited by

                        @planedrop Ignore me, I did make a dumb mistake, all is working now.

                        1 Reply Last reply Reply Quote 0

                        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                        With your input, this post could be even better šŸ’—

                        Register Login
                        • First post
                          Last post