command line user does not have read and write permissions on generated directory












0















command line user does not have read and write permissions on
generated directory. Please address this issue before using Magento command line




when I was trying to run php bin/magento indexer:reindex.



And I found I get the exactly same error when I tried to run the php bin/magento lines, I checked the post Error after magento upgrade, and have already changed the permission of generated folder, and then give bin/magento file to 744 (executable), and I used ls -l, the ownership of the folder is below to my account. I am using Magento 2.2, so there is no di folder under var folder.
So why does this error happen?



Thanks for any advises.



enter image description here



enter image description here










share|improve this question














bumped to the homepage by Community yesterday


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Please check folder and files owner/group
    – Jugal Kishor
    Aug 1 '18 at 8:33
















0















command line user does not have read and write permissions on
generated directory. Please address this issue before using Magento command line




when I was trying to run php bin/magento indexer:reindex.



And I found I get the exactly same error when I tried to run the php bin/magento lines, I checked the post Error after magento upgrade, and have already changed the permission of generated folder, and then give bin/magento file to 744 (executable), and I used ls -l, the ownership of the folder is below to my account. I am using Magento 2.2, so there is no di folder under var folder.
So why does this error happen?



Thanks for any advises.



enter image description here



enter image description here










share|improve this question














bumped to the homepage by Community yesterday


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Please check folder and files owner/group
    – Jugal Kishor
    Aug 1 '18 at 8:33














0












0








0








command line user does not have read and write permissions on
generated directory. Please address this issue before using Magento command line




when I was trying to run php bin/magento indexer:reindex.



And I found I get the exactly same error when I tried to run the php bin/magento lines, I checked the post Error after magento upgrade, and have already changed the permission of generated folder, and then give bin/magento file to 744 (executable), and I used ls -l, the ownership of the folder is below to my account. I am using Magento 2.2, so there is no di folder under var folder.
So why does this error happen?



Thanks for any advises.



enter image description here



enter image description here










share|improve this question














command line user does not have read and write permissions on
generated directory. Please address this issue before using Magento command line




when I was trying to run php bin/magento indexer:reindex.



And I found I get the exactly same error when I tried to run the php bin/magento lines, I checked the post Error after magento upgrade, and have already changed the permission of generated folder, and then give bin/magento file to 744 (executable), and I used ls -l, the ownership of the folder is below to my account. I am using Magento 2.2, so there is no di folder under var folder.
So why does this error happen?



Thanks for any advises.



enter image description here



enter image description here







magento2 magento2.2






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 11 '17 at 18:08









James ChenJames Chen

1184




1184





bumped to the homepage by Community yesterday


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community yesterday


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.














  • Please check folder and files owner/group
    – Jugal Kishor
    Aug 1 '18 at 8:33


















  • Please check folder and files owner/group
    – Jugal Kishor
    Aug 1 '18 at 8:33
















Please check folder and files owner/group
– Jugal Kishor
Aug 1 '18 at 8:33




Please check folder and files owner/group
– Jugal Kishor
Aug 1 '18 at 8:33










1 Answer
1






active

oldest

votes


















0














More likely than issue with with bin/magento (even though actually there is no executable bit on any level of access) there is an issue with generated folder. As you can read in documentation for v2.2 compiled files changed theirs paths to /generated/*



I assume that you have properly set privileges bits for previous version but maybe you missed setgid/uid bits and therefore user executing php script do not have access to this file (all is a file in unix, also dirs).






share|improve this answer





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "479"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f205367%2fcommand-line-user-does-not-have-read-and-write-permissions-on-generated-director%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    More likely than issue with with bin/magento (even though actually there is no executable bit on any level of access) there is an issue with generated folder. As you can read in documentation for v2.2 compiled files changed theirs paths to /generated/*



    I assume that you have properly set privileges bits for previous version but maybe you missed setgid/uid bits and therefore user executing php script do not have access to this file (all is a file in unix, also dirs).






    share|improve this answer


























      0














      More likely than issue with with bin/magento (even though actually there is no executable bit on any level of access) there is an issue with generated folder. As you can read in documentation for v2.2 compiled files changed theirs paths to /generated/*



      I assume that you have properly set privileges bits for previous version but maybe you missed setgid/uid bits and therefore user executing php script do not have access to this file (all is a file in unix, also dirs).






      share|improve this answer
























        0












        0








        0






        More likely than issue with with bin/magento (even though actually there is no executable bit on any level of access) there is an issue with generated folder. As you can read in documentation for v2.2 compiled files changed theirs paths to /generated/*



        I assume that you have properly set privileges bits for previous version but maybe you missed setgid/uid bits and therefore user executing php script do not have access to this file (all is a file in unix, also dirs).






        share|improve this answer












        More likely than issue with with bin/magento (even though actually there is no executable bit on any level of access) there is an issue with generated folder. As you can read in documentation for v2.2 compiled files changed theirs paths to /generated/*



        I assume that you have properly set privileges bits for previous version but maybe you missed setgid/uid bits and therefore user executing php script do not have access to this file (all is a file in unix, also dirs).







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Dec 11 '17 at 18:20









        Bartosz HerbaBartosz Herba

        93518




        93518






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Magento Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f205367%2fcommand-line-user-does-not-have-read-and-write-permissions-on-generated-director%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            An IMO inspired problem

            Management

            Investment