Good morning.
I've been having this issue for some days and have been lokking for a solution, but I haven't found one yet.
The problem is, I have this Magento store and some grids can be exported to CSV files, while others shows:
Error 503 Service Unavailable
Service Unavailable
Guru Meditation:
XID: 853411302
Varnish cache server
The Magento version I'm using is 1.6.2. I guess the problem is not about PHP code, since the error shown is this generic error, instead of a PHP one (I even found the code used for exporting files and it seems to be ok).
I would like to know why is this error being showed to me.
This is a Varnish Cache related error, I would suggest following the guide below on how to identify what the XID is returning for more insight on how to fix the issue:
https://www.varnish-cache.org/docs/trunk/tutorial/troubleshooting.html#varnish-gives-me-guru-meditation
Related
Yesterday my site suddenly stopped working and after investigating I found out that Midphase upgraded the PHP to 8.1 and MariaDB (says from 10.3 to 10.5). I got them to roll back PHP to 7.4 for the time being, although it sounds like it was already on 7.4, which is good as they couldn't go back further.
My live site is on 3.10.1 (http://www.scifivision.com) and after running an upgrade on a backup, assuming I did it right I have a version on 3.10.11. (http://www.thejfiles.com/sfv2023). Both are giving me the same errors other than the database name is different.
The frontend gives me white page with the error "1146 - Table 'thejrub4_joomfin.joom_fields_values' doesn't exist" and backend gives me a warning "Error loading module Table 'thejrub4_joomfin.joom_modules_menu' doesn't exist" and it lets me log in but I can't do anything.
Just wanted to mention, in case it's relevant, I have an earlier backup (I'm at the point if anything is fixed I'll be happy) that is also giving me two warnings:
session_name(): Session name cannot be changed after headers have already been sent in /home/thejrub4/public_html/sfvclon/libraries/joomla/session/handler/native.php on line 128
ession_cache_limiter(): Session cache limiter cannot be changed after headers have already been sent in /home/thejrub4/public_html/sfvclon/libraries/joomla/session/handler/native.php on line 235
Error: Failed to start application: Failed to start the session because headers have already been sent by "/home/thejrub4/public_html/sfvclon/libraries/vendor/joomla/input/src/Input.php" at line 41.
Since I am not seeing them on the newer backup, I'm assuming that is probably not the issue and was something I previously fixed, as I do have maximum on for debug
I have used forum post assistance for joomla.org if that helps and I will post the code below. This is for the 3.10.11 install, as the FPA wouldn't work on the older one. It says it should work without any issues, but clearly that's not true. I didn't know if that would help on this forum, but if you need it please let me know.
I've been modifying a module and for some reason prestashop does not take into consideration the code modifications in module.php.
I've made modifications a while back and I need to modify it again due to an update that raises an error, the problem is that I get the error even if I remove said line.
I get this type of error: PHP message: PHP Notice: Undefined index: ordersorderFilter!active in /modules/module/module.php on line 104
I've commented first than removed that line but I still get the error.
It seems like there is a cache somewhere that I can't find, I've deactivated all possible cache in prestashop, activated debug mode, deleted the dev and prod folders in /var/cache/ but I still get the error.
I've used grep on the server to try to find that line, and when I delete it from the file I can not find it anywhere else on the server (but can find it if I add it).
Anybody has any idea?
Thanks a lot!
Prestashop does not perform any kind of caching on the modules PHP files so the problem lies elsewhere or at "lower level" (webserver / proxy ie.).
So check your environment for server-side caching, proxies or PHP accelerators such as opCache that may not serve changes from the source server.
Also try renaming or deleting the offending file altogether and see if the error changes, if not you might simply be looking at the wrong file :)
I cant seem to find the error log of authorize.net api.
I have Laravel application which uses "authorizenet/authorizenet" package and the code where I try to create a customer profile, I get following error:
"Error getting valid response from API. Check log file for error details"
Can anyone tell me whereto find these logs? and what it's name?
I tried in /var/logs folder but i cant seem to find it.
if someone else has this issue, here is the solution.
The authorize.net has changed their endpoints from https://api.authorize.net to https://api2.authorize.net which is one of the possible reasons that you might get this error.
So if you are hardcoding these endpoints in your code then update it to the new one or if you are using library constant for it, same as me:
\net\authorize\api\constants\ANetEnvironment::SANDBOX
\net\authorize\api\constants\ANetEnvironment::PRODUCTION
Then simply update your library by running:
composer update authorizenet/authorizenet
This is how I resolved it and it seems to be the best way so far because it will update their library to take everything up to date if they have changes something else and you started experiencing this issue.
I hope it helps
My goal: I'd like to use an image from commons.mediawiki.org within a MediaWiki installation.
First I was trying to debug my InstantCommons configuration: Referring to files on commons.mediawiki.org failed for some reason. After activating various debugging options I learned that though general image download succeeded some kind of thumbnail followup request issued by the MediaWiki installation failed, which resulted into an overall error from the ForeignAPIRepo-Module.
As I can not deal with this error right now I thought I'd try something else as some kind of fallback: Download the MediaWiki image by specifiying the image URL in the upload image web page. The idea is to let MediaWiki download the image and include this image as regular wiki content. This way I would require to add license details manually and add a few comments, but this would be better than having no image.
But trying this I strangely get an error: It says "Fehler beim Senden der Anfrage" which means "Error while sending the request". But the internal request seems succeed in the logs. Here is what MediaWiki was logging:
[fileupload] Temporary file created "/tmp/URLdafce5345aa3-1"
[fileupload] Starting download from "https://upload.wikimedia.org/wikipedia/commons/c/c7/Broccoli%2C_Champignons%2C_Karotten_%2810581663524%29.jpg" <followRedirects>
[fileupload] <Error, collected 1 error(s) on the way, integer value set>
+------+---------------------------+------------------------------------------+
| 1 | http-request-error | |
+------+---------------------------+------------------------------------------+
[fileupload] Download by URL completed with HTTP status 200
Comment: All other log messages do not indicate anything that looks like an error or is related to the task of downloading the image, so I skipped them here.
The URL is correct, the image can be downloaded from the URL, MediaWiki receives a response code of 200, but instead of processing the response it indicates an error. Why? For http and https URLs I get the same result in the log.
Has anybody encountered this problem before in MediaWiki installations? Does anyone have any idea what the reason for this behaviour could be?
Comment: The wiki is of version 1.25.2 and a standard installation including SWM on an up to date standard Ubuntu Linux OS. Nothing exotic, nothing modified in any way.
Comment: Yes, I could upgrade to the latest version but, I'm not sure if this really solves the problem: I know that this featured did work in some other MediaWiki installations I have set up some time ago. Does anyone have a clue why this feature could fail here? Has anyone encountered something like this before?
Edit: I experimented with downloading from another MediaWiki instance of exactly the same version - 1.25.2 - in my local network. This did not succeed as well. But I get a different error message (translated): "The file .... could not be stored at ...". The "funny part": Though the error message indicated otherwise the file has been downloaded successfully and stored as expected. It has the correct user rights as one would expect, but log messages indicate that there are bugs in MediaWiki regarding this part: ("PHP Notice: Undefined property: UploadFromUrl::$nbytes") Maybe the uploading implementation is buggy somehow and the problems I am running into are typical?
There are multiple bugs with HTTPS support in MediaWiki, php-curl etc. See https://www.mediawiki.org/wiki/InstantCommons#HTTPS for debugging information, there is no magic bullet.
I 've installed magento and it seems to work, but if I want to save a new Catalog_product_set with different attributes then I get Internal Error Message with Status Code 500
Does anyone have the same problem?
Thanks in advance
cheers tabaluga
Your screenshot (and from the looks of it Magento's error page) clips the edge of the error off. Seeing the rest of the error message might be important. Regardless, it looks like Magento is trying to load a config file w/ simplexml, and cannot find that file.