Hello to everyone,

I've just installed ErrorLog Manager and the concept is awesome.

I'm wondering why I have some errors in my OC error log but those errors are not displayed.

Facts:

1. I can see them in errors list

2. I can see them in the database table "errorlog_manager"

My installation is a multistore:

- OC 2.0.3.1

- 3 themes and a big chunk of extension both commercial and free.

- ErrorLog Manager 1.2

Best regards,

José

Please,

Someone?

Hello

Same Thing is happening with me .

error.log has errors but not showing in the error log manager . Have you found the solution to this problem . 

Regards 

Saurabh Karangutkar

saurabh12222@gmail.com

Hi Saurabh,

No, I did not. Because there was no support whatsoever from the developers I've just deleted the extension.

That's it.

Regards,

Jose

Hi guys,

Apologies for not replying to this earlier. Since this is a community support, our staff is not replying here regularly. You can always open a support ticket in our support system to get a timely response.

As for the issue - most likely there are more than one log files in the logs directory and you need to select the error log you would like to parse from ErrorLogManager's Options menu.

Hope this helps.

(first let me say sorry for bringing this OLD topic) ... i just couldnt resist to not respond @Jose Antonio

there are allot of variables that can cause this. How big is the error log file it self ? ErrorLog Manager is a script that parse that text and push the parsed content as a more readable readable output. + while doing so(the script) it tries to analyze some of the errors based on pre-defined rules and offer fix suggestions. It all sound wonderful. .. BUT all those action above require .... some resources and proper server settings. The script to be able to parse a large file it will require some tweaks.

just for starters higher your max_execution_time / max_input_vars  if you run CSF set PT_USERTIME little bit higher (for example a 4MB error log took more than a minute on a 8 cpu server) then check your mod_sec and what rules you are using as they tend to mess up with the ErrorLog Manager. If you are on shared host .. then you are out of control... your option is to delete the error log

and while its fresh to analyze it with the iSence mod.  

This is not exactly true @Idle Stoev. The idea behind ErrorLog Manager is to allow you to examine large error log files, so it works with big files without a problem. @Jose Antonio says that he can see the errors in the module's database table, so the file has been parsed successfully. Please note that ErrorLog Manager takes into account the max execution time setting, so it doesn't time out. We have also made some database layout changes in the latest version which make the module work really fast even with large error log files. We have used a 1GB file in our tests. The issue Jose has had must have been due to a bug in the UI (which is fixed in the latest version), or he has been looking at a report for another file, since ErrorLog Manager allows you to parse any file in the logs directory of OpenCart.

Hi to Idle Stoev and to Ivailo Hristov.

First and foremost thank you very much for your inputs they were very helpful and insightful. I just hope it may help others with the same issue.

What I'm certain of is that "error file size" as nothing to do it, because it was a small file in a fresh install.

I think, in my opinion, this problem was either a bug or probably a PHP extension or Server Resources related issue.

Can someone tell me what PHP extensions does it require?

Regards

Hi Jose,

No special extensions are required for the module to run. Can you please try the latest version and let us know how it works for you?

Hi Ivailo,

I've installed the latest OC2.3.0.2 with Error log Manager 1.2.4 but the "issue" is still happening.

I'm not sure if this is a defect or feature, lol. Does it ignore old errors or already sorted out errors?

I've got a bunch of errors present in the log file but it's not showing up.

https://cl.ly/0R1w3F1P021b

Best regards

Hi Jose,

This does not seem normal. Can you please open a support ticket, so we can take a closer look?

I will do that.

Thank you very much

Hello everybody,

The issue was resolved and a fix will be applied to versions 1.2.5 and above.

It turned out that it was due to server security config, which was blocking the AJAX requests of ErrorLog Manager for getting the list of errors. We had to switch the request type from GET to POST.