Ggtkuk

Is it improper etiquette to ask your opponent what his/her rating is before the game?

Rising and falling intonation

How to implement a feedback to keep the DC gain at zero for this conceptual passive filter?

Does Doodling or Improvising on the Piano Have Any Benefits?

What will be next at the bottom row and why?

Aragorn's "guise" in the Orthanc Stone

Infinite dials to reset ever?

Fear of getting stuck on one programming language / technology that is not used in my country

Why electric field inside a cavity of a non conducting not zero

Redundant comparison & "if" before assignment

Has any country ever had 2 former presidents in jail simultaneously?

Creepy dinosaur pc game identification

How to create ADT in Haskell?

What should you do if you miss a job interview (deliberately)?

What does "Scientists rise up against statistical significance" mean? (Comment in Nature)

Is there any references on the tensor product of presentable (1-)categories?

How does a computer interpret real numbers?

Terse Method to Swap Lowest for Highest?

Are paving bricks differently sized for sand bedding vs mortar bedding?

Why should universal income be universal?

A social experiment. What is the worst that can happen?

Removing files under particular conditions (number of files, file age)

Yosemite Fire Rings - What to Expect?

Did arcade monitors have same pixel aspect ratio as TV sets?

Error log not created

What problem does this Magento Stack Trace report show?Magento Error Log file is not createedError log - 'PHP Fatal error: Class 'Mage_Catalog_Model_Product' not found in'Magento 1.9.01 update to 1.9.1.0 results in ''There has been an error processing your request'' LOG FILES uploadedException Error: “Memory limit has been reached.”“There has been an error processing your request” while moving to serverThere has been an error processing your request magento 1.9.0.1Page Refresh issueWarning in production mode stops executionError log record number: 813600142036

2

After Magento 2.2.1 CE upgrade I ended up situation that error report file is not created to /var/report directory.

There has been an error processing your request
Exception printing is disabled by default for security reasons.

Error log record number: xxxxxxx"

Is there a developer mode which can show the error directly in browser? All advises are welcome.

magento2.2 log error-log magento-2.2.1

share|improve this question

edited Nov 23 '17 at 15:27

Abhishek Panchal

3,5973929

asked Nov 23 '17 at 14:32

user61125user61125

111

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  what are the permissions on the folders?
  
  – treyBake
  Nov 23 '17 at 14:33
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Full, It It has been working in old versions....
  
  – user61125
  Nov 23 '17 at 15:25
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  hmm so 777? that's a risk xD ok, if it's 777 then that shouldn;'t be the cause, how about the owners?
  
  – treyBake
  Nov 23 '17 at 15:27
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  it has been 775 and 777 for the test. It didn't help
  
  – user61125
  Nov 23 '17 at 15:34
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I mean the owner, not permissions :) should be something like user : webdev
  
  – treyBake
  Nov 23 '17 at 15:38
  

  
  
  
  

 | 
show 2 more comments

2

After Magento 2.2.1 CE upgrade I ended up situation that error report file is not created to /var/report directory.

There has been an error processing your request
Exception printing is disabled by default for security reasons.

Error log record number: xxxxxxx"

Is there a developer mode which can show the error directly in browser? All advises are welcome.

magento2.2 log error-log magento-2.2.1

share|improve this question

edited Nov 23 '17 at 15:27

Abhishek Panchal

3,5973929

asked Nov 23 '17 at 14:32

user61125user61125

111

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  what are the permissions on the folders?
  
  – treyBake
  Nov 23 '17 at 14:33
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Full, It It has been working in old versions....
  
  – user61125
  Nov 23 '17 at 15:25
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  hmm so 777? that's a risk xD ok, if it's 777 then that shouldn;'t be the cause, how about the owners?
  
  – treyBake
  Nov 23 '17 at 15:27
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  it has been 775 and 777 for the test. It didn't help
  
  – user61125
  Nov 23 '17 at 15:34
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I mean the owner, not permissions :) should be something like user : webdev
  
  – treyBake
  Nov 23 '17 at 15:38
  

  
  
  
  

 | 
show 2 more comments

After Magento 2.2.1 CE upgrade I ended up situation that error report file is not created to /var/report directory.

There has been an error processing your request
Exception printing is disabled by default for security reasons.

Error log record number: xxxxxxx"

Is there a developer mode which can show the error directly in browser? All advises are welcome.

magento2.2 log error-log magento-2.2.1

share|improve this question

edited Nov 23 '17 at 15:27

Abhishek Panchal

3,5973929

asked Nov 23 '17 at 14:32

user61125user61125

111

share|improve this question

edited Nov 23 '17 at 15:27

Abhishek Panchal

3,5973929

asked Nov 23 '17 at 14:32

user61125user61125

111

share|improve this question

edited Nov 23 '17 at 15:27

Abhishek Panchal

3,5973929

asked Nov 23 '17 at 14:32

user61125user61125

111

edited Nov 23 '17 at 15:27

Abhishek Panchal

3,5973929

edited Nov 23 '17 at 15:27

Abhishek Panchal

3,5973929

asked Nov 23 '17 at 14:32

user61125user61125

111

asked Nov 23 '17 at 14:32

user61125user61125

111

1 Answer
1

active

oldest

votes

0

To answer your question, yes, yes there is. To enable the developer mode you need access to your terminal, in the magento root run this command:

php bin/magento deploy:mode:set developer

this sets Magento to developer mode, which displays errors in the browser for the "developer" to see. You can also achieve this (if the screen is just white) with the below code added into index.php:

ini_set('display_errors', 1);
ini_set('display_startup_errors', 1);
error_reporting(-1);

ini_set('error_reporting', E_ERROR);
register_shutdown_function('fatal_handler');
function fatal_handler()

 $error = error_get_last();
 echo ('<pre>');

 var_dump($error);

this should be enough to get the error on screen. If not, check your server error logs as opposed to Magento's to see if it's added there.

share|improve this answer

answered Nov 23 '17 at 15:46

treyBaketreyBake

120118

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  So far , No success.
  
  – user61125
  Nov 23 '17 at 17:27
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @user61125 what does going to a page look like after setting mode to developer?
  
  – treyBake
  Nov 24 '17 at 12:27
  

  
  
  
  

add a comment | 

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

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f202948%2ferror-log-not-created%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

0

To answer your question, yes, yes there is. To enable the developer mode you need access to your terminal, in the magento root run this command:

php bin/magento deploy:mode:set developer

this sets Magento to developer mode, which displays errors in the browser for the "developer" to see. You can also achieve this (if the screen is just white) with the below code added into index.php:

ini_set('display_errors', 1);
ini_set('display_startup_errors', 1);
error_reporting(-1);

ini_set('error_reporting', E_ERROR);
register_shutdown_function('fatal_handler');
function fatal_handler()

 $error = error_get_last();
 echo ('<pre>');

 var_dump($error);

this should be enough to get the error on screen. If not, check your server error logs as opposed to Magento's to see if it's added there.

share|improve this answer

answered Nov 23 '17 at 15:46

treyBaketreyBake

120118

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  So far , No success.
  
  – user61125
  Nov 23 '17 at 17:27
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @user61125 what does going to a page look like after setting mode to developer?
  
  – treyBake
  Nov 24 '17 at 12:27
  

  
  
  
  

add a comment | 

0

To answer your question, yes, yes there is. To enable the developer mode you need access to your terminal, in the magento root run this command:

php bin/magento deploy:mode:set developer

this sets Magento to developer mode, which displays errors in the browser for the "developer" to see. You can also achieve this (if the screen is just white) with the below code added into index.php:

ini_set('display_errors', 1);
ini_set('display_startup_errors', 1);
error_reporting(-1);

ini_set('error_reporting', E_ERROR);
register_shutdown_function('fatal_handler');
function fatal_handler()

 $error = error_get_last();
 echo ('<pre>');

 var_dump($error);

this should be enough to get the error on screen. If not, check your server error logs as opposed to Magento's to see if it's added there.

share|improve this answer

answered Nov 23 '17 at 15:46

treyBaketreyBake

120118

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  So far , No success.
  
  – user61125
  Nov 23 '17 at 17:27
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @user61125 what does going to a page look like after setting mode to developer?
  
  – treyBake
  Nov 24 '17 at 12:27
  

  
  
  
  

add a comment | 

To answer your question, yes, yes there is. To enable the developer mode you need access to your terminal, in the magento root run this command:

php bin/magento deploy:mode:set developer

this sets Magento to developer mode, which displays errors in the browser for the "developer" to see. You can also achieve this (if the screen is just white) with the below code added into index.php:

ini_set('display_errors', 1);
ini_set('display_startup_errors', 1);
error_reporting(-1);

ini_set('error_reporting', E_ERROR);
register_shutdown_function('fatal_handler');
function fatal_handler()

 $error = error_get_last();
 echo ('<pre>');

 var_dump($error);

this should be enough to get the error on screen. If not, check your server error logs as opposed to Magento's to see if it's added there.

share|improve this answer

answered Nov 23 '17 at 15:46

treyBaketreyBake

120118

php bin/magento deploy:mode:set developer

ini_set('display_errors', 1);
ini_set('display_startup_errors', 1);
error_reporting(-1);

ini_set('error_reporting', E_ERROR);
register_shutdown_function('fatal_handler');
function fatal_handler()

 $error = error_get_last();
 echo ('<pre>');

 var_dump($error);

share|improve this answer

answered Nov 23 '17 at 15:46

treyBaketreyBake

120118

answered Nov 23 '17 at 15:46

treyBaketreyBake

120118

answered Nov 23 '17 at 15:46

treyBaketreyBake

120118