Magento 2 error 500 after adding a module












0















I added a module by these command



php bin/magento module:status
php bin/magento module:enable module


Everything was fine then I run this



php bin/magento setup:upgrade


After this everything messed up,
The output of this command is



php bin/magento setup:upgrade
Cache cleared successfully
File system cleanup:
/home/xyz/public_html/var/generation/Composer
/home/xyz/public_html/var/generation/Magento
/home/xyz/public_html/var/generation/Symfony
The directory '/home/xyz/public_html/var/di/' doesn't exist - skipping cleanup
Updating modules:
Schema creation/updates:


And after the execution of this command My site returning HTTP ERROR 500.



Any Idea how to solve this ??










share|improve this question
















bumped to the homepage by Community 4 mins ago


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




















    0















    I added a module by these command



    php bin/magento module:status
    php bin/magento module:enable module


    Everything was fine then I run this



    php bin/magento setup:upgrade


    After this everything messed up,
    The output of this command is



    php bin/magento setup:upgrade
    Cache cleared successfully
    File system cleanup:
    /home/xyz/public_html/var/generation/Composer
    /home/xyz/public_html/var/generation/Magento
    /home/xyz/public_html/var/generation/Symfony
    The directory '/home/xyz/public_html/var/di/' doesn't exist - skipping cleanup
    Updating modules:
    Schema creation/updates:


    And after the execution of this command My site returning HTTP ERROR 500.



    Any Idea how to solve this ??










    share|improve this question
















    bumped to the homepage by Community 4 mins ago


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


















      0












      0








      0








      I added a module by these command



      php bin/magento module:status
      php bin/magento module:enable module


      Everything was fine then I run this



      php bin/magento setup:upgrade


      After this everything messed up,
      The output of this command is



      php bin/magento setup:upgrade
      Cache cleared successfully
      File system cleanup:
      /home/xyz/public_html/var/generation/Composer
      /home/xyz/public_html/var/generation/Magento
      /home/xyz/public_html/var/generation/Symfony
      The directory '/home/xyz/public_html/var/di/' doesn't exist - skipping cleanup
      Updating modules:
      Schema creation/updates:


      And after the execution of this command My site returning HTTP ERROR 500.



      Any Idea how to solve this ??










      share|improve this question
















      I added a module by these command



      php bin/magento module:status
      php bin/magento module:enable module


      Everything was fine then I run this



      php bin/magento setup:upgrade


      After this everything messed up,
      The output of this command is



      php bin/magento setup:upgrade
      Cache cleared successfully
      File system cleanup:
      /home/xyz/public_html/var/generation/Composer
      /home/xyz/public_html/var/generation/Magento
      /home/xyz/public_html/var/generation/Symfony
      The directory '/home/xyz/public_html/var/di/' doesn't exist - skipping cleanup
      Updating modules:
      Schema creation/updates:


      And after the execution of this command My site returning HTTP ERROR 500.



      Any Idea how to solve this ??







      magento2 setup-script http-error-500






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited May 3 '18 at 13:01









      7ochem

      5,74293668




      5,74293668










      asked Jan 25 '17 at 21:13









      Sumit KumarSumit Kumar

      213




      213





      bumped to the homepage by Community 4 mins ago


      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 4 mins ago


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
























          2 Answers
          2






          active

          oldest

          votes


















          0














          For the unexpected 500 error, we should enable error reporting on the bootstrap. Should enable error reporting with -1 value. That will report all PHP errors.



          app/bootstrap.php



          ini_set('display_errors', -1) // Should enable error reporting with -1 value.





          share|improve this answer































            0














            Enable the developer mode. By running the below commend.



            php bin/magento deploy:mode:set developer


            after that you can see the errors trace in frontend.






            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%2f156475%2fmagento-2-error-500-after-adding-a-module%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              0














              For the unexpected 500 error, we should enable error reporting on the bootstrap. Should enable error reporting with -1 value. That will report all PHP errors.



              app/bootstrap.php



              ini_set('display_errors', -1) // Should enable error reporting with -1 value.





              share|improve this answer




























                0














                For the unexpected 500 error, we should enable error reporting on the bootstrap. Should enable error reporting with -1 value. That will report all PHP errors.



                app/bootstrap.php



                ini_set('display_errors', -1) // Should enable error reporting with -1 value.





                share|improve this answer


























                  0












                  0








                  0







                  For the unexpected 500 error, we should enable error reporting on the bootstrap. Should enable error reporting with -1 value. That will report all PHP errors.



                  app/bootstrap.php



                  ini_set('display_errors', -1) // Should enable error reporting with -1 value.





                  share|improve this answer













                  For the unexpected 500 error, we should enable error reporting on the bootstrap. Should enable error reporting with -1 value. That will report all PHP errors.



                  app/bootstrap.php



                  ini_set('display_errors', -1) // Should enable error reporting with -1 value.






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jan 25 '17 at 23:40









                  Khoa TruongDinhKhoa TruongDinh

                  21.3k64086




                  21.3k64086

























                      0














                      Enable the developer mode. By running the below commend.



                      php bin/magento deploy:mode:set developer


                      after that you can see the errors trace in frontend.






                      share|improve this answer




























                        0














                        Enable the developer mode. By running the below commend.



                        php bin/magento deploy:mode:set developer


                        after that you can see the errors trace in frontend.






                        share|improve this answer


























                          0












                          0








                          0







                          Enable the developer mode. By running the below commend.



                          php bin/magento deploy:mode:set developer


                          after that you can see the errors trace in frontend.






                          share|improve this answer













                          Enable the developer mode. By running the below commend.



                          php bin/magento deploy:mode:set developer


                          after that you can see the errors trace in frontend.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Jan 26 '17 at 3:17









                          MeenakshiSundaram RMeenakshiSundaram R

                          8,03942551




                          8,03942551






























                              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.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function () {
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f156475%2fmagento-2-error-500-after-adding-a-module%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

                              Magento 2 controller redirect on button click in phtml file

                              Polycentropodidae