Ttdfjt

Why is it faster to reheat something than it is to cook it?

Do wooden building fires get hotter than 600°C?

Can anything be seen from the center of the Boötes void? How dark would it be?

Significance of Cersei's obsession with elephants?

How to tell that you are a giant?

Why should I vote and accept answers?

How were pictures turned from film to a big picture in a picture frame before digital scanning?

Do I really need to have a message in a novel to appeal to readers?

Why is my ESD wriststrap failing with nitrile gloves on?

Is it possible for SQL statements to execute concurrently within a single session in SQL Server?

How to write the following sign?

Does the Weapon Master feat grant you a fighting style?

Localisation of Category

What was the first language to use conditional keywords?

Project Euler #1 in C++

Trademark violation for app?

What is the difference between globalisation and imperialism?

Is grep documentation about ignoring case wrong, since it doesn't ignore case in filenames?

How can I reduce the gap between left and right of cdot with a macro?

Sum letters are not two different

If windows 7 doesn't support WSL, then what does Linux subsystem option mean?

Maximum summed subsequences with non-adjacent items

How do I find out the mythology and history of my Fortress?

Should I use a zero-interest credit card for a large one-time purchase?

Magento log is not writing in log folder

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

2

Log files are not writing in the log folder but previously they are writing in the folder. Any idea about this?.

magento-1.9 log debugging

share|improve this question

edited Aug 30 '16 at 7:55

Anna Völkl

15.7k347134

asked Aug 29 '16 at 14:43

Akhil KurianAkhil Kurian

86212

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Is there a solution yet?
  
  – Black
  Jun 19 '18 at 14:00
  

  
  
  
  

add a comment | 

2

Log files are not writing in the log folder but previously they are writing in the folder. Any idea about this?.

magento-1.9 log debugging

share|improve this question

edited Aug 30 '16 at 7:55

Anna Völkl

15.7k347134

asked Aug 29 '16 at 14:43

Akhil KurianAkhil Kurian

86212

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Is there a solution yet?
  
  – Black
  Jun 19 '18 at 14:00
  

  
  
  
  

add a comment | 

Log files are not writing in the log folder but previously they are writing in the folder. Any idea about this?.

magento-1.9 log debugging

share|improve this question

edited Aug 30 '16 at 7:55

Anna Völkl

15.7k347134

asked Aug 29 '16 at 14:43

Akhil KurianAkhil Kurian

86212

share|improve this question

edited Aug 30 '16 at 7:55

Anna Völkl

15.7k347134

asked Aug 29 '16 at 14:43

Akhil KurianAkhil Kurian

86212

share|improve this question

edited Aug 30 '16 at 7:55

Anna Völkl

15.7k347134

asked Aug 29 '16 at 14:43

Akhil KurianAkhil Kurian

86212

edited Aug 30 '16 at 7:55

Anna Völkl

15.7k347134

edited Aug 30 '16 at 7:55

Anna Völkl

15.7k347134

asked Aug 29 '16 at 14:43

Akhil KurianAkhil Kurian

86212

asked Aug 29 '16 at 14:43

Akhil KurianAkhil Kurian

86212

3 Answers
3

active

oldest

votes

5

There are several possible options here:

1. Logs have been disabled under System > Configuration > Developer > Log Settings > Enabled
   


2. 
   Your server is full and thus can't write to the logs anymore.


3. Maybe there's nothing to log (which is a good thing as that means there's no error/warning to log on your website)


4. Maybe your var/log folder permissions have changed and thus Magento cannot write to this folder anymore.

share|improve this answer

edited 2 days ago

magefms

2,7702528

answered Aug 29 '16 at 14:45

Raphael at Digital PianismRaphael at Digital Pianism

55.2k22124280

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Is any possibility of hacking to prevent log writing?
  
  – Akhil Kurian
  Aug 29 '16 at 15:07
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @AkhilKurian well I don't see why someone would prevent log writing to hack your website. There's no reason behind that. I've added an extra reason
  
  – Raphael at Digital Pianism
  Aug 29 '16 at 15:08
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  PHP Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE[HY000] [2002] Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)' in /var/www/html/bluemountainorganics/lib/Zend/Db/Adapter/Pdo/Abstract.php:129 I got this error in yesterday on cron is any idea aboutthis ?
  
  – Akhil Kurian
  Aug 29 '16 at 15:12
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @AkhilKurian well it has nothing to do with the logs. It means Magento couldn't connect to MySQL, there's several reasons: maybe the Database server was down, the credentials have changed or you're out of space in your server
  
  – Raphael at Digital Pianism
  Aug 29 '16 at 15:16
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  Permissions. Check if logging is not going to /tmp/magento/var/log ( off the top of my head, so could be incorrect path)
  
  – ProxiBlue
  Aug 29 '16 at 15:40
  

  
  
  
  

 | 
show 3 more comments

2

I've found that if SELinux is not set properly for Magento, nothing gets written to the Magento logs, but instead goes to the /tmp location. Try 'setenforce Permissive' to disable SELinux. If the logs begin to receive output, then SELinux was to blame. Unfortunately, I do not know how to allow the Magento user (on CentOS it's apache) to write to the log files. With SELinux, even setting permissions on that file to 777 doesn't help.

So, by disabling SELinux with 'setenforce Permissive', just remember that after a reboot, it will be enabled again.

share|improve this answer

answered May 30 '18 at 18:20

S. BaranS. Baran

211

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This worked in my case, to keep it permanent edit /etc/sysconfig/selinux with SELINUX=permissive. Details here
  
  – George Irimiciuc
  Mar 14 at 9:33
  
  

  
  
  
  

add a comment | 

2

In 1.9.4.1 (or after applying SUPEE-11086 patch) if you delete "/var/log/system.log" log file becomes "not writeable" (even if directory is writeable), so Magento skips writing log.

Solution:

• make sure "/var/log/" is writeable


• create empty "/var/log/system.log" there


• and/or wait when it will be fixed by Magento devs

share|improve this answer

answered 2 days ago

user2504763user2504763

211

New contributor

user2504763 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

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%2f133629%2fmagento-log-is-not-writing-in-log-folder%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

5

There are several possible options here:

1. Logs have been disabled under System > Configuration > Developer > Log Settings > Enabled
   


2. 
   Your server is full and thus can't write to the logs anymore.


3. Maybe there's nothing to log (which is a good thing as that means there's no error/warning to log on your website)


4. Maybe your var/log folder permissions have changed and thus Magento cannot write to this folder anymore.

share|improve this answer

edited 2 days ago

magefms

2,7702528

answered Aug 29 '16 at 14:45

Raphael at Digital PianismRaphael at Digital Pianism

55.2k22124280

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Is any possibility of hacking to prevent log writing?
  
  – Akhil Kurian
  Aug 29 '16 at 15:07
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @AkhilKurian well I don't see why someone would prevent log writing to hack your website. There's no reason behind that. I've added an extra reason
  
  – Raphael at Digital Pianism
  Aug 29 '16 at 15:08
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  PHP Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE[HY000] [2002] Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)' in /var/www/html/bluemountainorganics/lib/Zend/Db/Adapter/Pdo/Abstract.php:129 I got this error in yesterday on cron is any idea aboutthis ?
  
  – Akhil Kurian
  Aug 29 '16 at 15:12
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @AkhilKurian well it has nothing to do with the logs. It means Magento couldn't connect to MySQL, there's several reasons: maybe the Database server was down, the credentials have changed or you're out of space in your server
  
  – Raphael at Digital Pianism
  Aug 29 '16 at 15:16
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  Permissions. Check if logging is not going to /tmp/magento/var/log ( off the top of my head, so could be incorrect path)
  
  – ProxiBlue
  Aug 29 '16 at 15:40
  

  
  
  
  

 | 
show 3 more comments

5

There are several possible options here:

1. Logs have been disabled under System > Configuration > Developer > Log Settings > Enabled
   


2. 
   Your server is full and thus can't write to the logs anymore.


3. Maybe there's nothing to log (which is a good thing as that means there's no error/warning to log on your website)


4. Maybe your var/log folder permissions have changed and thus Magento cannot write to this folder anymore.

share|improve this answer

edited 2 days ago

magefms

2,7702528

answered Aug 29 '16 at 14:45

Raphael at Digital PianismRaphael at Digital Pianism

55.2k22124280

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Is any possibility of hacking to prevent log writing?
  
  – Akhil Kurian
  Aug 29 '16 at 15:07
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @AkhilKurian well I don't see why someone would prevent log writing to hack your website. There's no reason behind that. I've added an extra reason
  
  – Raphael at Digital Pianism
  Aug 29 '16 at 15:08
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  PHP Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE[HY000] [2002] Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)' in /var/www/html/bluemountainorganics/lib/Zend/Db/Adapter/Pdo/Abstract.php:129 I got this error in yesterday on cron is any idea aboutthis ?
  
  – Akhil Kurian
  Aug 29 '16 at 15:12
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @AkhilKurian well it has nothing to do with the logs. It means Magento couldn't connect to MySQL, there's several reasons: maybe the Database server was down, the credentials have changed or you're out of space in your server
  
  – Raphael at Digital Pianism
  Aug 29 '16 at 15:16
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  Permissions. Check if logging is not going to /tmp/magento/var/log ( off the top of my head, so could be incorrect path)
  
  – ProxiBlue
  Aug 29 '16 at 15:40
  

  
  
  
  

 | 
show 3 more comments

There are several possible options here:

1. Logs have been disabled under System > Configuration > Developer > Log Settings > Enabled
   


2. 
   Your server is full and thus can't write to the logs anymore.


3. Maybe there's nothing to log (which is a good thing as that means there's no error/warning to log on your website)


4. Maybe your var/log folder permissions have changed and thus Magento cannot write to this folder anymore.

share|improve this answer

edited 2 days ago

magefms

2,7702528

answered Aug 29 '16 at 14:45

Raphael at Digital PianismRaphael at Digital Pianism

55.2k22124280

share|improve this answer

edited 2 days ago

magefms

2,7702528

answered Aug 29 '16 at 14:45

Raphael at Digital PianismRaphael at Digital Pianism

55.2k22124280

edited 2 days ago

magefms

2,7702528

edited 2 days ago

magefms

2,7702528

answered Aug 29 '16 at 14:45

Raphael at Digital PianismRaphael at Digital Pianism

55.2k22124280

answered Aug 29 '16 at 14:45

Raphael at Digital PianismRaphael at Digital Pianism

55.2k22124280

2

I've found that if SELinux is not set properly for Magento, nothing gets written to the Magento logs, but instead goes to the /tmp location. Try 'setenforce Permissive' to disable SELinux. If the logs begin to receive output, then SELinux was to blame. Unfortunately, I do not know how to allow the Magento user (on CentOS it's apache) to write to the log files. With SELinux, even setting permissions on that file to 777 doesn't help.

So, by disabling SELinux with 'setenforce Permissive', just remember that after a reboot, it will be enabled again.

share|improve this answer

answered May 30 '18 at 18:20

S. BaranS. Baran

211

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This worked in my case, to keep it permanent edit /etc/sysconfig/selinux with SELINUX=permissive. Details here
  
  – George Irimiciuc
  Mar 14 at 9:33
  
  

  
  
  
  

add a comment | 

2

I've found that if SELinux is not set properly for Magento, nothing gets written to the Magento logs, but instead goes to the /tmp location. Try 'setenforce Permissive' to disable SELinux. If the logs begin to receive output, then SELinux was to blame. Unfortunately, I do not know how to allow the Magento user (on CentOS it's apache) to write to the log files. With SELinux, even setting permissions on that file to 777 doesn't help.

So, by disabling SELinux with 'setenforce Permissive', just remember that after a reboot, it will be enabled again.

share|improve this answer

answered May 30 '18 at 18:20

S. BaranS. Baran

211

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This worked in my case, to keep it permanent edit /etc/sysconfig/selinux with SELINUX=permissive. Details here
  
  – George Irimiciuc
  Mar 14 at 9:33
  
  

  
  
  
  

add a comment | 

I've found that if SELinux is not set properly for Magento, nothing gets written to the Magento logs, but instead goes to the /tmp location. Try 'setenforce Permissive' to disable SELinux. If the logs begin to receive output, then SELinux was to blame. Unfortunately, I do not know how to allow the Magento user (on CentOS it's apache) to write to the log files. With SELinux, even setting permissions on that file to 777 doesn't help.

So, by disabling SELinux with 'setenforce Permissive', just remember that after a reboot, it will be enabled again.

share|improve this answer

answered May 30 '18 at 18:20

S. BaranS. Baran

211

share|improve this answer

answered May 30 '18 at 18:20

S. BaranS. Baran

211

answered May 30 '18 at 18:20

S. BaranS. Baran

211

answered May 30 '18 at 18:20

S. BaranS. Baran

211

2

In 1.9.4.1 (or after applying SUPEE-11086 patch) if you delete "/var/log/system.log" log file becomes "not writeable" (even if directory is writeable), so Magento skips writing log.

Solution:

• make sure "/var/log/" is writeable


• create empty "/var/log/system.log" there


• and/or wait when it will be fixed by Magento devs

share|improve this answer

answered 2 days ago

user2504763user2504763

211

New contributor

user2504763 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

2

In 1.9.4.1 (or after applying SUPEE-11086 patch) if you delete "/var/log/system.log" log file becomes "not writeable" (even if directory is writeable), so Magento skips writing log.

Solution:

• make sure "/var/log/" is writeable


• create empty "/var/log/system.log" there


• and/or wait when it will be fixed by Magento devs

share|improve this answer

answered 2 days ago

user2504763user2504763

211

New contributor

user2504763 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

In 1.9.4.1 (or after applying SUPEE-11086 patch) if you delete "/var/log/system.log" log file becomes "not writeable" (even if directory is writeable), so Magento skips writing log.

Solution:

• make sure "/var/log/" is writeable


• create empty "/var/log/system.log" there


• and/or wait when it will be fixed by Magento devs

share|improve this answer

answered 2 days ago

user2504763user2504763

211

New contributor

user2504763 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this answer

answered 2 days ago

user2504763user2504763

211

New contributor

user2504763 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

answered 2 days ago

user2504763user2504763

211

New contributor

user2504763 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

answered 2 days ago

user2504763user2504763

211