-
Notifications
You must be signed in to change notification settings - Fork 396
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed during create_start_clean: :eacces #142
Comments
|
The |
1.) Post up what you get when you run 2.) Is the parent directory of rel writeable by your account as well? |
I temporary resolved this issue. cp -r /usr/local/Cellar/elixir/1.3.2 /usr/local/Cellar/elixir/1.3.2.bak
chmod -R +w /usr/local/Cellar/elixir/1.3.2
cp -r /usr/local/Cellar/erlang/19.0.2 /usr/local/Cellar/erlang/19.0.2.bak
chmod -R +w /usr/local/Cellar/erlang/19.0.2
mix release I think it is not proper method. |
I am at least four levels deep in a development tree that is fully owned by my account, under my home folder. |
@melpon: |
All I can suggest is try starting with a brand new clean, minimal phoenix
app and see if you still see the issue. No doubt there's something about
your particular configuration that's causing this behavior to occur and
until we isolate the cause it's pretty much impossible to figure out what's
going on. Start with a clean, minimal phoenix app and if you don't see the
error then slowly start adding stuff to it to make it look like your app.
If you see the error with a clean, minimal phoenix app that's much easier
to research.
oc
…On Tue, Nov 29, 2016 at 1:52 AM, Andreas Guther ***@***.***> wrote:
@melpon <https://github.com/melpon>:
I also use brew and I tried what you suggested with the permissions but
that did not help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#142 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJXFUJXzdgp4I_NQonoKTVRanxSnbtvks5rC8uZgaJpZM4K9R8D>
.
--
Onorio Catenacci
http://onor.io
http://www.google.com/+OnorioCatenacci
|
Andreas,
It might also benefit you if you look at these guidelines on creating a
Minimal, Complete and Verifiable example. http://stackoverflow.com/help/mcve
Certainly would speed up research on this and get you closer to an answer.
It might be that while creating a MCVE you may find the answer yourself.
oc
…On Tue, Nov 29, 2016 at 1:52 AM, Andreas Guther ***@***.***> wrote:
@melpon <https://github.com/melpon>:
I also use brew and I tried what you suggested with the permissions but
that did not help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#142 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJXFUJXzdgp4I_NQonoKTVRanxSnbtvks5rC8uZgaJpZM4K9R8D>
.
--
Onorio Catenacci
http://onor.io
http://www.google.com/+OnorioCatenacci
|
Ignore that last comment. The details of this are split between here and
StackOverflow and I didn't recall your note posted on StackOverflow that
you have reproduced this issue with a bare Phoenix install.
You're sure that you're not getting issues from Erlang itself? I see some
notes about running Erlang on MacOSX (Jaguar) here:
erlang.org/download/otp_src_R9C-0.readme You may want to insure that Erlang
is working correctly. Are you seeing any issue with either Erl or Erlc?
oc
On Tue, Nov 29, 2016 at 9:50 AM, Onorio Catenacci <Catenacci@ieee.org>
wrote:
… Andreas,
It might also benefit you if you look at these guidelines on creating a
Minimal, Complete and Verifiable example. http://stackoverflow.
com/help/mcve Certainly would speed up research on this and get you
closer to an answer. It might be that while creating a MCVE you may find
the answer yourself.
oc
On Tue, Nov 29, 2016 at 1:52 AM, Andreas Guther ***@***.***>
wrote:
> @melpon <https://github.com/melpon>:
> I also use brew and I tried what you suggested with the permissions but
> that did not help.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#142 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAJXFUJXzdgp4I_NQonoKTVRanxSnbtvks5rC8uZgaJpZM4K9R8D>
> .
>
--
Onorio Catenacci
http://onor.io
http://www.google.com/+OnorioCatenacci
--
Onorio Catenacci
http://onor.io
http://www.google.com/+OnorioCatenacci
|
@melpon It worked for me for now. |
@andreasguther would you mind running this with strace attached and pastebin the log? The last file it attempts to open should tell us what it's trying to load from the filesystem and thus where it's failing. Before you do that though, could you try with |
@bitwalker The last few entries are the following.
Last night I forgot to check the start_clean.boot file. I am editing this post and ere is the content of the directory:
|
@OnorioCatenacci: Thank you for taking your time and providing suggestions. I can run my application without problem with my current environment. I also run other applications from other projects with the same configuration. It is with distillery that I see the problem. I tried to collect all the information about reproducing including creating the minimal project in the initial description. I understand it is long but I tried to answer all the questions from the issue template. |
I just change my configuration to point to distillery master and could then build release for both the basic phoenix and my project. |
@andreasguther A new release was published since your last message, so you can switch to that rather than pointing to master :) |
Steps to reproduce
mix phoenix.new hello_phoenix
{:distillery, "~> 0.10"}
mix deps.get
mix release init
mix release
- You should see the following errorVerbose Logs
Paste the output of the release command you ran with the
--verbose
flag.Description of issue
I would like to find a completed release build.
I have seen the same error using exrm and that was the reason I moved to distillery. In case it might give a hint, here is the stack trace when using exrm:
rel/config.exs
, as it is oftenmy first troubleshooting question, and you'll save us both time :)
another? If so, please link the doc here so it can be updated if
it's a documentation issue, or so that the fix can be based around
what's documented.
The text was updated successfully, but these errors were encountered: