I was looking everywhere if I can find an answer to this issue but I was not able.
So my issue is with Redis server, every night at random hour my website simply shut down due to the issue above.
To get my website up I just need to reboot my AWS Instance.
Thank you so much for your help !
PHP Fatal error: Uncaught exception 'CredisException' with message ' operation not permitted' in /var/www/lib/Credis/Client.php:704\n
Stack trace:
#0 /var/www/lib/Credis/Client.php(538): Credis_Client->read_reply('select')
#1 /var/www/lib/Credis/Client.php(440): Credis_Client->__call('select', Array)
#2 /var/www/app/code/community/Cm/Cache/Backend/Redis.php(135): Credis_Client->select(0)
#3 /var/www/lib/Zend/Cache.php(153): Cm_Cache_Backend_Redis->__construct(Array)
#4 /var/www/lib/Zend/Cache.php(94): Zend_Cache::_makeBackend('Cm_Cache_Backen...', Array, true, true)\n
#5 /var/www/app/code/core/Mage/Core/Model/Cache.php(137): Zend_Cache::factory('Varien_Cache_Co...', 'Cm_Cache_Backen...', Array, Array, true, true, true)
#6 /var/www/app/code/core/Mage/Core/Model/Config.php(1348): Mage_Core_Model_Cache->__construct(Array)
#7 /var/www/app/Mage.php(463): Mage_Core_Model_Config->getModelInstance('core/cache', Array)
#8 /var/www/app/code/core/Mage/Core/Model/App.php(401): Mage::getModel('core/cache', Array)\n#9 /var/www/app/code/core/Mag in /var/www/lib/Credis/Client.php on line 704
This sounds like your redis instance is left open on the internet and you've been hacked.
Make sure you secure correctly your instance.
Gist explaining the problem
Related
When Cron with "newsletter_send_all" this job code execute then its status became missed and pass message like below. currently using magento's defalt cron settings with UTC time. My Cron.php executed in every 5 minute. Please help me out on this curios issue.
exception 'Mage_Core_Exception' with message 'Too late for the schedule' in /home/test/public_html/app/Mage.php:595
Stack trace:
#0 /home/test/public_html/app/code/core/Mage/Cron/Model/Observer.php(293): Mage::throwException('Too late for th...')
#1 /home/test/public_html/app/code/core/Mage/Cron/Model/Observer.php(72): Mage_Cron_Model_Observer->_processJob(Object(Mage_Cron_Model_Schedule), Object(Mage_Core_Model_Config_Element))
#2 /home/test/public_html/app/code/core/Mage/Core/Model/App.php(1338): Mage_Cron_Model_Observer->dispatch(Object(Varien_Event_Observer))
#3 /home/test/public_html/app/code/core/Mage/Core/Model/App.php(1317): Mage_Core_Model_App->_callObserverMethod(Object(Mage_Cron_Model_Observer), 'dispatch', Object(Varien_Event_Observer))
#4 /home/test/public_html/app/Mage.php(448): Mage_Core_Model_App->dispatchEvent('default', Array)
#5 /home/test/public_html/cron.php(75): Mage::dispatchEvent('default')
#6 {main}
Also made below modification in newslatter module's observer in core for testing purpose but still its not working
public function scheduledSend($schedule)
{
$countOfQueue = 1; // default 3 Modified on 14 Nov 17
$countOfSubscritions = 1; //default 20 Modified on 14 Nov 17
$collection = Mage::getModel('newsletter/queue')->getCollection()
->setPageSize($countOfQueue)
->setCurPage(1)
->addOnlyForSendingFilter()
->load();
$collection->walk('sendPerSubscriber', array($countOfSubscritions));
}
This happens when the scheduler finds pending jobs that were supposed
to be scheduled longer than the time configured in
'system/cron/schedule_lifetime'. By default this value is set to 15
minutes.
There are two different problems the may result in you seeing this
error:
Cron isn't configured to run often enough: If you don't trigger cron
often enough then the tasks start piling up and most likely tasks
will be too late for schedule at the point when they're being
executed by the scheduler. Instead of increasing the
scheduler_lifetime settings you should increase the frequency cron
is being called to */5 * * * * (every 5 minutes) or even * * * * *
(every minute).
You have long running cron jobs that will block the execution of
other jobs: In case you're importing data, indexing products,
generating reports or doing other long-running jobs via cron (which
is generally a good idea) other jobs will not be run in parallel
(unless you're running cron.php instead of cron.sh). This will
result in these jobs not being executed. Find out which jobs are
preventing others from running (by looking at the timeline view) and
run them in a different cron group. (look at this for more
information and check the features added to version >0.5.0 for an
easier way to configure and manage cron groups.
source https://github.com/AOEpeople/Aoe_Scheduler/blob/master/doc/faq.md
Lately we get these exceptions after user finishes checkout in Magento and uses PayPal Plus as payment method. Customer gets error page but payment is made and Magento order status is set to "payed".
exception 'Mage_Core_Exception' with message 'Order not found.' in app/Mage.php:595
Stack trace:
#0 app/code/community/Iways/PayPalPlus/Model/Webhook/Event.php(254): Mage::throwException('Order not found...')
#1 app/code/community/Iways/PayPalPlus/Model/Webhook/Event.php(70): Iways_PayPalPlus_Model_Webhook_Event->getOrder(Object(PayPal\Api\WebhookEvent))
#2 app/code/community/Iways/PayPalPlus/controllers/IndexController.php(171): Iways_PayPalPlus_Model_Webhook_Event->processWebhookRequest(Object(PayPal\Api\WebhookEvent))
#3 app/code/core/Mage/Core/Controller/Varien/Action.php(418): Iways_PayPalPlus_IndexController->webhooksAction()
#4 app/code/core/Mage/Core/Controller/Varien/Router/Standard.php(254): Mage_Core_Controller_Varien_Action->dispatch('webhooks')
#5 app/code/community/BalkeTechnologies/StoreMaintenance/Controller/Router/Standard.php(91): Mage_Core_Controller_Varien_Router_Standard->match(Object(Mage_Core_Controller_Request_Http))
#6 app/code/core/Mage/Core/Controller/Varien/Front.php(172): BalkeTechnologies_StoreMaintenance_Controller_Router_Standard->match(Object(Mage_Core_Controller_Request_Http))
#7 app/code/core/Mage/Core/Model/App.php(365): Mage_Core_Controller_Varien_Front->dispatch()
#8 app/Mage.php(684): Mage_Core_Model_App->run(Array)
#9 index.php(83): Mage::run('', 'store')
#10 {main}
What's the problem and how can I solve it? Any hints appreciated!
Please check table sales_payment_transaction. order_id entry inserted properly or not (It's error because of order not found from current transaction).
When you find some keywords on my Magento store sometimes not appear anything but if you continue searching the same keyword finally results appear.
Variable 'innodb_lock_wait_timeout' was 50 and now is 100. Nothing happens.
Sometimes I get this error:
a:5:{i:0;s:91:"SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction";i:1;s:3666:"#0 /home/nginx/www/includes/src/Varien_Db_Statement_Pdo_Mysql.php(110): Zend_Db_Statement_Pdo->_execute(Array)
#1 /home/nginx/www/includes/src/__default.php(64796): Varien_Db_Statement_Pdo_Mysql->_execute(Array)
#2 /home/nginx/www/includes/src/__default.php(54128): Zend_Db_Statement->execute(Array)
....
I need help!
I have Swiftmailer set up to set emails via turbo-smtp, and have just started getting a 566 SMTP limit exceeded error. Is this turbo-smtp telling me I've sent too many emails, or my server's ISP, or is there something else in that error that needs to be addressed?
I'm not sending any more emails than I normally do via the day to day operation of the site.
Here's the error:
[09-Feb-2016 01:34:02 UTC] PHP Fatal error: Uncaught exception 'Swift_TransportException' with message 'Expected response code 354 but got code "566", with message "566 SMTP limit exceeded
"' in /usr/local/lib/php/Swift/Transport/AbstractSmtpTransport.php:386
Stack trace:
#0 /usr/local/lib/php/Swift/Transport/AbstractSmtpTransport.php(281): Swift_Transport_AbstractSmtpTransport->_assertResponseCode('566 SMTP limit ...', Array)
#1 /usr/local/lib/php/Swift/Transport/EsmtpTransport.php(245): Swift_Transport_AbstractSmtpTransport->executeCommand('DATA\r\n', Array, Array)
#2 /usr/local/lib/php/Swift/Transport/AbstractSmtpTransport.php(321): Swift_Transport_EsmtpTransport->executeCommand('DATA\r\n', Array)
#3 /usr/local/lib/php/Swift/Transport/AbstractSmtpTransport.php(432): Swift_Transport_AbstractSmtpTransport->_doDataCommand()
#4 /usr/local/lib/php/Swift/Transport/AbstractSmtpTransport.php(449): Swift_Transport_AbstractSmtpTransport->_doMailTransaction(Object(Swift_Message), 'support#songboo...', Array, Array)
#5 /usr/local/lib/php/Swift/Transport/Abstra in /usr/local/lib/php/Swift/Transport/AbstractSmtpTransport.php on line 386
My Swift code:
$transport = Swift_SmtpTransport::newInstance('pro.turbo-smtp.com', 25)
I also tried
$transport = Swift_SmtpTransport::newInstance('pro.turbo-smtp.com', 465, 'ssl')
Thanks for your time and help.
Turned out I'd hit my turbo-smtp limit. I hadn't looked at it for a couple of years, so had forgotten how it all worked. Upgraded my account, and it's working again. Ideally, they'd send you a simple email saying - "hey, you've hit your email limit, and emails aren't getting out - you should upgrade to fix the problem" for us dummies.
my magneto version is 1.9 suddenly i saw this error:
files are OK because when i change to another database Site working correctly
could you help me,please?
There has been an error processing your request
Front controller reached 100 router match iterations
Trace:
0 /home/user/domains/domain.com/public_html/app/code/core/Mage/Core/Controller/Varien/Front.php(179): Mage::throwException('Front controlle...')
1 /home/diamo/domains/domain.com/public_html/app/code/core/Mage/Core/Model/App.php(354): Mage_Core_Controller_Varien_Front->dispatch()
2 /home/user/domains/domain.com/public_html/app/Mage.php(684): Mage_Core_Model_App->run(Array) 3 /home/user/domains/domain.com/public_html/index.php(71): Mage::run('', 'store') 4 {main}