How does one get a detailed description of an error from the system.log file in Magento 2?
I'm only able to see
[2016-06-14 11:11:01] main.CRITICAL: Class tglssearch does not exist [] []
magento2 logs are handled by Monolog so that is default.
Magento Log Details resides under
<magento-root>/var/log/*
<magento-root>/var/report
You have check the detailed error in httpd logs(apache server logs). In httpd logs you can able to see the exact line of where the errors occur.
I am using apache with fedora, in my case httpd logs resides under /var/log/httpd/error_log
Related
Getting following exception in wildfly:
ERROR [org.jboss.modcluster] (UndertowEventHandlerAdapter - 1):
MODCLUSTER000042: Error MEM sending ENABLE-APP command to rod.de.mgg.dk/11.10.11.11:400, configuration will be reset: MEM: Can't update or insert host alias
Able to ping this server.
Deployed an application in server but even after undeploy and restart not able to fix it.
Wildfly server group has 3 nodes in it which balance load.
The only response to this i found is following on google:
The indicates a problem with the LB, please inspect apache/undertow logs for the cause.
But i am unable to deduce so. Could anyone please suggest more here?
You need to increase MaxHost in your httpd.conf as per your backend server requirement.
We have an api deployed on Azure that uses Google authentication. Over the weekend, the API started to throw 500 errors that were resolved after restarting the API. Is there a way to identify what the underlying cause for these errors might be?
Check if you have custom error mode in web.config file to “on” or “Remoteonly”. If
yes then turn it off. Add the following line to System.web element in web.config
Enable custom logging/instrumentation in the code which can help you in more
information.
ASP.NET applications can use the System.Diagnostics.Trace class to log information to
the application diagnostics log. For example
System.Diagnostics.Trace.TraceError("If you're seeing this, something bad happened");
Enable Detailed Error Messages - Detailed version of the html files produced when
your website responds with an error message. This is good to enable for debugging
some error responses in your website. It is stored in the website's file system.
Web Server Logging - Also known as HTTP logs or IIS logs, this will log all requests
to your website in W3C Extended Log File Format.
Failed Request Tracing - Also known as FREB, here you can get lots of information
from IIS through its different stacks for each failing request.
I have installed ICP CE 2.1.0 on a google cloud VM and the installation has gone well-no errors in installation process. When accessing the GUI I am able to see deployments and services but as soon as I access any part of the Catalog I get a blank white page with the text:
{"statusCode":401,"details":"Unexpected response code 401 from request:\nGET https://xx.xxx.xxx.xx:8443/console/api/v1/header?serviceId=catalog-ui&dev=false&accessUrl=https%3A%2F%2Fxx.xxx.xxx.xx%3A8443* ...... }
I have tried killing the individual pods but I get same error. When looking a the pod logs for the catalog-ui I have error 500 messages.
Has anyone experienced this or can tell my why this is the case? Understand that a cloud VM is not the best use case maybe but it should work?
Can you confirm the version level of ICP? Your post mentioned "ICP CE 2.1.0" but if you can check the user icon (top right corner) and click About, we should be able to see the full version details.
Reason for asking is that, at the 2100 level there was an intermittent catalog issue just like you describe. Generally it was caused by resource constraints on the k8s.
Details for ICP 2103, which is the latest available release:
https://www.ibm.com/support/knowledgecenter/SSBS6K_2.1.0.3/getting_started/whats_new.html
I see a 500 error when I hit my TYPO3 site in ddev.
ddev logs shows me what's going on:
2018/05/10 21:07:38 [error] 354#354: *45 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught UnexpectedValueException: The current host header value does not match the configured trusted hosts pattern! Check the pattern defined in $GLOBALS['TYPO3_CONF_VARS']['SYS']['trustedHostsPattern'] and adapt it, if you want to allow the current host header 'typo3-master.ddev.local:8000' for your installation. in /var/www/html/typo3/sysext/core/Classes/Utility/GeneralUtility.php:2728
I have ddev v0.18.0 and have run ddev config, and I've confirmed that the AdditionalConfiguration.php contains the generic $GLOBALS['TYPO3_CONF_VARS']['SYS']['trustedHostsPattern'] = '.*';, so that should match anything, right?
TYPO3 v9 seems to not be able to use a trustedHostsPattern that contains a port. You're running on port 8000, for TYPO3 v9 and ddev, please figure out how to get it on port 80. There are troubleshooting instructions on how to figure out what else might be using port 80 at https://ddev.readthedocs.io/en/latest/users/troubleshooting/#unable-listen
When I run command "shimmercat devlove" it gives following error:-
Please find devlove.yaml file:- https://www.dropbox.com/s/6xhk3lq497zw8y2/devlove.yaml?dl=0
Good question #Atul Rai. I'm not completely sure, but I think it could be related with what is written here. It says:
...ShimmerCat probes the port to determine if the application is using HTTP/1.1 or FastCGI. The probing operation shows in ShimmerCat's logs, and may also show in the error log of the application.
Of course if you are not using an API domain (you don't have a subkey port on your devlove.yaml config file) I don't think that ShimmerCat has to do these probes, but I can't see another explanation for these error logs. Perhaps it would be useful if you update your question with your devlove.yaml file?