I upgraded from 1.9 to 1.9.1 via MagentoConnectManager. Everthing seems to work well and the site looks good. But the admin-page ist just a blank white page. I checked the .htaccess and the core_config_data table changed from http to https but nothing is working.
The exeption log shows (Links anonym):
xxxurlxxx ...app/Mage.php:595
Stack trace:
#0 xxxurlxxx ...app/code/core/Mage/Api/Model/Server.php(127): Mage::throwException('Invalid webserv...')
#1 xxxurlxxx ...api.php(78): Mage_Api_Model_Server->initialize(NULL)
#2 {main}
2015-02-28T00:31:47+00:00 ERR (3):
exception 'Mage_Core_Exception' with message 'Invalid webservice adapter specified.' in xxxurlxxx ...app/Mage.php:595
Stack trace:
#0 xxxurlxxx ...app/code/core/Mage/Api/Model/Server.php(127): Mage::throwException('Invalid webserv...')
#1 xxxurlxxx ...api.php(78): Mage_Api_Model_Server->initialize(NULL)
#2 {main}
2015-03-06T10:03:41+00:00 ERR (3):
exception 'Mage_Core_Exception' with message 'Invalid webservice adapter specified.' in xxxurlxxx ...app/Mage.php:595
Stack trace:
#0 xxxurlxxx ...app/code/core/Mage/Api/Model/Server.php(127): Mage::throwException('Invalid webserv...')
#1 xxxurlxxx ...api.php(78): Mage_Api_Model_Server->initialize(NULL)
#2 {main}
Can anybody please help and give me a hind what to do?
The page is h**p://....vinocada.de bye the way.
Best regards,
Markus
Related
Is yaska supported in Linux? I tried installing it on CentOS and getting below error.
[root#390f68c98d2b yasca]# sh yasca.sh ./resources/test
Fatal error: Uncaught exception 'LogicException' with message 'Class Yasca\Scanner could not be loaded' in /var/www/html/yasca/Yasca/Main.php:36
Stack trace:
#0 /var/www/html/yasca/Yasca/Main.php(36): spl_autoload('Yasca\\Scanner')
#1 [internal function]: {closure}()
#2 /var/www/html/yasca/Yasca/Main.php(357): call_user_func(Object(Closure))
#3 /var/www/html/yasca/Yasca/Start.php(14): include('/var/www/html/y...')
#4 {main}
thrown in /var/www/html/yasca/Yasca/Main.php on line 36
Can someone please help in this?
I have a magneto based web shop with a custom template. The webshop works at first side fine except that during the loading of a page (every page) the following exception (see below) is thrown and Magento tries to load something that is not present: undefined?1479491943475 Anybody an idea how to fix this? I use Magento 1.9.2.4
16-11-05T22:04:46+00:00 ERR (3):
exception 'Exception' with message 'Error during unserialization' in /home/fossilshop/public_html/lib/Unserialize/Parser.php:60
Stack trace:
#0 /home/fossilshop/public_html/app/code/core/Mage/Core/Helper/UnserializeArray.php(44): Unserialize_Parser->unserialize(Object(Mage_Core_Model_Config_Element))
#1 /home/fossilshop/public_html/app/code/core/Mage/Adminhtml/Model/System/Config/Backend/Serialized.php(37): Mage_Core_Helper_UnserializeArray->unserialize(Object(Mage_Core_Model_Config_Element))
#2 /home/fossilshop/public_html/app/code/core/Mage/Core/Model/Config/Data.php(78): Mage_Adminhtml_Model_System_Config_Backend_Serialized->_afterLoad()
#3 /home/fossilshop/public_html/app/code/core/Mage/Adminhtml/Block/System/Config/Form.php(334): Mage_Core_Model_Config_Data->afterLoad()
#4 /home/fossilshop/public_html/app/code/core/Mage/Adminhtml/Block/System/Config/Form.php(229): Mage_Adminhtml_Block_System_Config_Form->initFields(Object(Varien_Data_Form_Element_Fieldset), Object(Mage_Core_Model_Config_Element), Object(Mage_Core_Model_Config_Element))
#5 /home/fossilshop/public_html/app/code/core/Mage/Adminhtml/Block/System/Config/Form.php(164): Mage_Adminhtml_Block_System_Config_Form->_initGroup(Object(Varien_Data_Form), Object(Mage_Core_Model_Config_Element), Object(Mage_Core_Model_Config_Element))
#6 /home/fossilshop/public_html/app/code/core/Mage/Adminhtml/Block/System/Config/Edit.php(92): Mage_Adminhtml_Block_System_Config_Form->initForm()
#7 /home/fossilshop/public_html/app/code/core/Mage/Adminhtml/controllers/System/ConfigController.php(107): Mage_Adminhtml_Block_System_Config_Edit->initForm()
#8 /home/fossilshop/public_html/app/code/core/Mage/Core/Controller/Varien/Action.php(418): Mage_Adminhtml_System_ConfigController->editAction()
#9 /home/fossilshop/public_html/app/code/core/Mage/Core/Controller/Varien/Router/Standard.php(254): Mage_Core_Controller_Varien_Action->dispatch('edit')
#10 /home/fossilshop/public_html/app/code/core/Mage/Core/Controller/Varien/Front.php(172): Mage_Core_Controller_Varien_Router_Standard->match(Object(Mage_Core_Controller_Request_Http))
#11 /home/fossilshop/public_html/app/code/core/Mage/Core/Model/App.php(365): Mage_Core_Controller_Varien_Front->dispatch()
#12 /home/fossilshop/public_html/app/Mage.php(684): Mage_Core_Model_App->run(Array)
#13 /home/fossilshop/public_html/index.php(83): Mage::run('', 'store')
#14 {main}
2016-11-05T22:04:46+00:00 ERR (3):
> Blockquote
I recently ran into this issue too and found this fix
https://www.atwix.com/magento/supee-7405-cart-merge-error-fix/
After adding my own module with the above fix, the exception stopped logging.
Hope it helps
I am using the poste.io mail server. While trying to issue the SSL cert using lets encrypt, it throws below error. Anyone has observed it already and could fix it?
[2016-11-08 00:12:44] LEScript.INFO: Account already registered. Continuing.
[2016-11-08 00:12:44] LEScript.INFO: Starting certificate generation process for domains
[2016-11-08 00:12:44] LEScript.INFO: Requesting challenge for mail.domain.ltd
[2016-11-08 00:12:45] LEScript.INFO: Sending signed request to /acme/new-authz
[2016-11-08 00:12:45] LEScript.INFO: Got challenge token for mail.domain.ltd
[2016-11-08 00:12:45] LEScript.INFO: Token for mail.domain.ltd saved at /opt/www//.well-known/acme-challenge/UEyhta88fiS_E5WTn-SOxKI-lqbsK1-eTOceiE_UnTQ and should be available at http://mail.domain.ltd/.well-known/acme-challenge/UEyhta88fiS_E5WTn-SOxKI-lqbsK1-eTOceiE_UnTQ
[2016-11-08 00:12:47] LEScript.ERROR: Please check http://mail.domain.ltd/.well-known/acme-challenge/UEyhta88fiS_E5WTn-SOxKI-lqbsK1-eTOceiE_UnTQ - token not available
[2016-11-08 00:12:47] LEScript.ERROR: #0 /opt/mailserver-admin/src/Analogic/LetsEncryptBundle/Handler/LeHandler.php(55): Analogic\ACME\Lescript->signDomains(Array)
[2016-11-08 00:12:47] LEScript.ERROR: #1 /opt/mailserver-admin/src/Analogic/LetsEncryptBundle/Controller/LeController.php(74): Analogic\LetsEncryptBundle\Handler\LeHandler->renew(true)
[2016-11-08 00:12:47] LEScript.ERROR: #2 [internal function]: Analogic\LetsEncryptBundle\Controller\LeController->issueAction(Object(Symfony\Component\HttpFoundation\Request))
[2016-11-08 00:12:47] LEScript.ERROR: #3 /opt/mailserver-admin/var/bootstrap.php.cache(3040): call_user_func_array(Array, Array)
[2016-11-08 00:12:47] LEScript.ERROR: #4 /opt/mailserver-admin/var/bootstrap.php.cache(2995): Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object(Symfony\Component\HttpFoundation\Request), 1)
[2016-11-08 00:12:47] LEScript.ERROR: #5 /opt/mailserver-admin/var/bootstrap.php.cache(2335): Symfony\Component\HttpKernel\HttpKernel->handle(Object(Symfony\Component\HttpFoundation\Request), 1, true)
[2016-11-08 00:12:47] LEScript.ERROR: #6 /opt/mailserver-admin/web/app.php(19): Symfony\Component\HttpKernel\Kernel->handle(Object(Symfony\Component\HttpFoundation\Request))
[2016-11-08 00:12:47] LEScript.ERROR: #7 {main}
Have posted in https://bitbucket.org/analogic/mailserver/issues/139/lets-encrypt-certificate-issue-exception but seems they only respond to pro customers. :(
Problem solved. My firewall disabled the port 25. Once the port is open, it started to work.
I have been searching and searching for any information regarding this redis error, but so far have not found any information. Any help would be greatly appreciated.
Here is my setup:
Laravel with 2 redis connections, 6379 for cache, and 6380 for a datastore.
Every couple of requests to the datastore, I get this error in my logs:
exception 'Predis\Protocol\ProtocolException' with message 'Unknown prefix: '1' [tcp://MY_SERVER_ADDRESS:6380]
This just started within the last few days, and I have not changed anything in the redis config or laravel redis config.
A little more info:
I do not have a prefix set in laravel anywhere.. laravel, predis, or redis is adding it itself.
The "prefix" that gets added changes, yesterday it was 'O', today it is '1'.
This is happening on two separate instances of laravel. The instances share an encryption key, but do not share any files or configs. They both connect to this redis server
Here is the full stack trace:
[2015-02-02 22:19:13] production.ERROR: exception 'Predis\Protocol\ProtocolException' with message 'Unknown prefix: '1' [tcp://MY_SERVER_ADDRESS:6380]' in /var/www/html/vendor/predis/predis/lib/Predis/Connection/AbstractConnection.php:151
Stack trace:
#0 /var/www/html/vendor/predis/predis/lib/Predis/Connection/StreamConnection.php(274): Predis\Connection\AbstractConnection->onProtocolError()
#1 /var/www/html/vendor/predis/predis/lib/Predis/Connection/StreamConnection.php(262): Predis\Connection\StreamConnection->read()
#2 /var/www/html/vendor/predis/predis/lib/Predis/Connection/AbstractConnection.php(130): Predis\Connection\StreamConnection->read()
#3 /var/www/html/vendor/predis/predis/lib/Predis/Connection/AbstractConnection.php(122): Predis\Connection\AbstractConnection->readResponse()
#4 /var/www/html/vendor/predis/predis/lib/Predis/Client.php(246): Predis\Connection\AbstractConnection->executeCommand()
#5 /var/www/html/vendor/predis/predis/lib/Predis/Client.php(228): Predis\Client->executeCommand()
#6 /var/www/html/app/interfaces/RedisRepository.php(47): Predis\Client->__call()
#7 /var/www/html/app/controllers/TrackingController.php(239): RedisRepository->registerNodeEventStatsGlobal()
#8 (): TrackingController->saveTrackerUserData()
#9 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Controller.php(231): call_user_func_array()
#10 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(93): Illuminate\Routing\Controller->callAction()
#11 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(62): Illuminate\Routing\ControllerDispatcher->call()
#12 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Router.php(962): Illuminate\Routing\ControllerDispatcher->dispatch()
#13 (): {closure}()
#14 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Route.php(109): call_user_func_array()
#15 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Router.php(1028): Illuminate\Routing\Route->run()
#16 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Router.php(996): Illuminate\Routing\Router->dispatchToRoute()
#17 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(775): Illuminate\Routing\Router->dispatch()
#18 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(745): Illuminate\Foundation\Application->dispatch()
#19 /var/www/html/vendor/laravel/framework/src/Illuminate/Session/Middleware.php(72): Illuminate\Foundation\Application->handle()
#20 /var/www/html/vendor/laravel/framework/src/Illuminate/Cookie/Queue.php(47): Illuminate\Session\Middleware->handle()
#21 /var/www/html/vendor/laravel/framework/src/Illuminate/Cookie/Guard.php(51): Illuminate\Cookie\Queue->handle()
#22 /var/www/html/vendor/stack/builder/src/Stack/StackedHttpKernel.php(23): Illuminate\Cookie\Guard->handle()
#23 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(641): Stack\StackedHttpKernel->handle()
#24 /var/www/html/public/index.php(49): Illuminate\Foundation\Application->run()
#25 {main} [] []
Help plz :(
The issue turned out to be specific to HHVM. Once I switched back to PHP-FPM the errors stopped.
HHVM does still have its quirks.
I haven't done any work on my Joomla site in a while- no new changes. I just visited the home page and it returns this error. Any ideas on what this may be?
Fatal error: Uncaught exception 'InvalidArgumentException' with message 'Could not find template "yoo_avenue".' in /hermes/bosweb25b/b905/ipg.stokestackbbqcom/avenue/libraries/cms/application/site.php:510 Stack trace: #0 /hermes/bosweb25b/b905/ipg.stokestackbbqcom/avenue/libraries/legacy/error/error.php(778): JApplicationSite->getTemplate() #1 /hermes/bosweb25b/b905/ipg.stokestackbbqcom/avenue/plugins/system/redirect/redirect.php(130): JError::customErrorPage(Object(InvalidArgumentException)) #2 [internal function]: PlgSystemRedirect::handleError(Object(InvalidArgumentException)) #3 {main} thrown in /hermes/bosweb25b/b905/ipg.stokestackbbqcom/avenue/libraries/cms/application/site.php on line 510