Difference between revisions of "Check GUI log"

From Kolmisoft Wiki
Jump to navigationJump to search
Line 1: Line 1:
When you get error on the GUI:
When you get this error on the GUI:


  We're sorry, but something went wrong.
  We're sorry, but something went wrong.
  We've been notified about this issue and we'll take a look at it shortly.
  We've been notified about this issue and we'll take a look at it shortly.


or something else is not working (e.g Graphs), you need to check RoR log. It has info what is wrong.
or something else is not working (e.g Graphs), you need to check the RoR log. It has info on what is wrong.
.
It can be done accessing file ''/home/mor/log/production.log''.


Starting from MOR v0.5.0.5 it is possible to do that online using address '''http://<YOUR IP>/billing/debug/show_log.php'''.
This can be done by accessing file ''/home/mor/log/production.log''.


It shows last 100 lines (usually it is enough) to find the cause of the problem.
Starting from MOR v0.5.0.5, it is possible to do this online using the address '''http://<YOUR IP>/billing/debug/show_log.php'''.
 
It shows the last 100 lines (usually this is enough) to find the cause of the problem.


==Errors==
==Errors==
Line 18: Line 18:
  Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 48372783 bytes) in /home/mor/public/debug/show_log.php on line 8
  Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 48372783 bytes) in /home/mor/public/debug/show_log.php on line 8


That means file is too huge. Login to server over SSH and do:
That means file is too large. Login to server over SSH and do:


  cp /home/mor/log/test.log /home/mor/log/production.log
  cp /home/mor/log/test.log /home/mor/log/production.log

Revision as of 12:27, 27 April 2010

When you get this error on the GUI:

We're sorry, but something went wrong.
We've been notified about this issue and we'll take a look at it shortly.

or something else is not working (e.g Graphs), you need to check the RoR log. It has info on what is wrong.

This can be done by accessing file /home/mor/log/production.log.

Starting from MOR v0.5.0.5, it is possible to do this online using the address http://<YOUR IP>/billing/debug/show_log.php.

It shows the last 100 lines (usually this is enough) to find the cause of the problem.

Errors

You can get:

Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 48372783 bytes) in /home/mor/public/debug/show_log.php on line 8

That means file is too large. Login to server over SSH and do:

cp /home/mor/log/test.log /home/mor/log/production.log