Since yesterday I have been seeing a lot of these errors in my logs:
Operation timed out after 100001 milliseconds with 0 bytes received
File: /var/www/html/vendor/google/apiclient/src/Google/IO/Curl.php(126)
Trace: #0 /var/www/html/vendor/google/apiclient/src/Google/IO/Abstract.php(136): Google_IO_Curl->executeRequest(Object(Google_Http_Request))
#1 /var/www/html/vendor/google/apiclient/src/Google/Http/REST.php(60): Google_IO_Abstract->makeRequest(Object(Google_Http_Request))
#2 /var/www/html/vendor/google/apiclient/src/Google/Task/Runner.php(174): Google_Http_REST::doExecute(Object(Google_Client), Object(Google_Http_Request))
#3 /var/www/html/vendor/google/apiclient/src/Google/Http/REST.php(46): Google_Task_Runner->run()
#4 /var/www/html/vendor/google/apiclient/src/Google/Client.php(593): Google_Http_REST::execute(Object(Google_Client), Object(Google_Http_Request))
#5 /var/www/html/vendor/google/apiclient/src/Google/Service/Resource.php(240): Google_Client->execute(Object(Google_Http_Request))
#6 /var/www/html/vendor/google/apiclient/src/Google/Service/Drive.php(2000): Google_Service_Resource->call('update', Array, 'Google_Service_...')
#7 /var/www/html/app/lib/GoogleDriveHelper.php(185): Google_Service_Drive_Files_Resource->update('1jbLDzGVNNNigA...', Object(Google_Service_Drive_DriveFile), Array)
#8 /var/www/html/app/lib/GoogleDriveHelper.php(131): GoogleDriveHelper->updateFile('1jbLDzGVNNNigA...', '/tmp/tr-filesUI...')
#9 /var/www/html/app/lib/GoogleDriveHelper.php(66): GoogleDriveHelper->createOrUpdateFileOnce('Folder/Photo_...', 'Filen...', '/tmp/tr-filesUI...', 'image/jpeg', '', true)
#10 /var/www/html/app/jobs/worker/taskresult-photo-upload-to-gdrive.php(170): GoogleDriveHelper->createOrUpdateFile('Folder/Photo_...', 'Filen...', '/tmp/tr-filesUI...', 'image/jpeg')
#11 [internal function]: upload_photos_to_gdrive(Object(GearmanJob), NULL)
#12 /var/www/html/app/jobs/uploads-worker.php(5): GearmanWorker->work()
I have tried checking Google Services status page and there are no reported issues.
I haven't seen this exception occur before and nothing on my side has changed.
I should note that this only happens quite rarely and sometimes Google Drive responds with 502 error status code and the following message:
<p>The server encountered a temporary error and could not complete your request.<p>Please try again in 30 seconds. <ins>That’s all we know.</ins>
Maybe you have been tackling this issue and could point me to explanation of what is happening, is this preventable (if so - how) or are these issues on my side of services?
There is nothing you can do about 500 errors they are an error on googles side. As recommended in the documentation you should implement exponential backoff.
If you get a 500 error wait a few seconds and try again. If it still doesn't work wait double the amount of time if it still doesn't work wait three times the amount of time.
If after say 15 attempts it still doesn't work then something is probably down. exponential-backoff
The HyperText Transfer Protocol (HTTP) 502 Bad Gateway server error response code indicates that the server, while acting as a gateway or proxy, received an invalid response from the upstream server.
Related
I am trying to install Magento version 1.9.2.0 with the sample data in my local Apache server.
I have stumbled upon a problem that is tearing my heart appart and I need some help or guidance in this obscure path, for I get this error message:
Error in file: "/opt/lampp/htdocs/magento/app/code/core/Mage/Sendfriend
/sql/sendfriend_setup/mysql4-upgrade-1.6.0.0-1.6.0.1.php" - SQLSTATE[42S02]: Base table or view not found: 1146 Table 'db_magento_sample.sendfriend_log' doesn't exist, query was: DESCRIBE `sendfriend_log`
Trace:
#0 /opt/lampp/htdocs/magento/app/code/core/Mage/Core/Model/Resource/Setup.php(645): Mage::exception('Mage_Core', 'Error in file: ...')
#1 /opt/lampp/htdocs/magento/app/code/core/Mage/Core/Model/Resource/Setup.php(437): Mage_Core_Model_Resource_Setup->_modifyResourceDb('upgrade', '1.6.0.0', '1.6.0.1')
#2 /opt/lampp/htdocs/magento/app/code/core/Mage/Core/Model/Resource/Setup.php(320): Mage_Core_Model_Resource_Setup->_upgradeResourceDb('1.6.0.0', '1.6.0.1')
#3 /opt/lampp/htdocs/magento/app/code/core/Mage/Core/Model/Resource/Setup.php(235): Mage_Core_Model_Resource_Setup->applyUpdates()
#4 /opt/lampp/htdocs/magento/app/code/core/Mage/Core/Model/App.php(428): Mage_Core_Model_Resource_Setup::applyAllUpdates()
#5 /opt/lampp/htdocs/magento/app/code/core/Mage/Core/Model/App.php(354): Mage_Core_Model_App->_initModules()
#6 /opt/lampp/htdocs/magento/app/Mage.php(684): Mage_Core_Model_App->run(Array)
#7 /opt/lampp/htdocs/magento/index.php(83): Mage::run('', 'store')
#8 {main}
I have tried changing the directories permissions, I have already uploaded the sql sample data script to my local DB using PHPMyAdmin, erasing and reinstalling again, and restarting the process for more than 3 times but I got blocked here, I have searched for solutions in forums but haven't found none
Does anyone know how to proceed? I thank you for reading.
Best regards,
D.
We are having issues with Magento not sending emails out. The emails having issues are the sales email which are logged into core_email_queue. None of these are sending. All other emails send fine through my server.
I am aware that CE1.9.x send emails through cron and my cron.php is running fine. AOE scheduler shows the cron is running. Only the emails are not being sent. In exception.log I see this issue which is exactly when the emails stopped going out and it repeats.
How can I fix this? It's a fresh install of CE1.9.1.1 and I reinstalled just to be sure.
2015-04-30T01:35:03+00:00 ERR (3):
exception 'Zend_Mail_Transport_Exception' with message 'Unable to send mail. ' in /home/nli/catalog/lib/Zend/Mail/Transport/Sendmail.php:137
Stack trace:
#0 /home/nli/catalog/lib/Zend/Mail/Transport/Abstract.php(348): Zend_Mail_Transport_Sendmail->_sendMail()
#1 /home/nli/catalog/lib/Zend/Mail.php(1194): Zend_Mail_Transport_Abstract->send(Object(Zend_Mail))
#2 /home/nli/catalog/app/code/core/Mage/Core/Model/Email/Queue.php(241): Zend_Mail->send()
#3 [internal function]: Mage_Core_Model_Email_Queue->send(Object(Aoe_Scheduler_Model_Schedule))
#4 /home/nli/catalog/app/code/community/Aoe/Scheduler/Model/Observer.php(79): call_user_func_array(Array, Array)
#5 /home/nli/catalog/app/code/core/Mage/Core/Model/App.php(1338): Aoe_Scheduler_Model_Observer->dispatch(Object(Varien_Event_Observer))
#6 /home/nli/catalog/app/code/core/Mage/Core/Model/App.php(1317): Mage_Core_Model_App->_callObserverMethod(Object(Aoe_Scheduler_Model_Observer), 'dispatch', Object(Varien_Event_Observer))
#7 /home/nli/catalog/app/Mage.php(448): Mage_Core_Model_App->dispatchEvent('default', Array)
#8 /home/nli/catalog/cron.php(76): Mage::dispatchEvent('default')
#9 {main}
I think following post can help you.
Magento:exception 'Zend_Mail_Transport_Exception' with message 'Unable to send mail
There is a chance that your from address can have extra character that seems invalid.
you can check this link out.
http://www.appseconnect.com/magento/magento-1-9-bug-sales-order-emails-does-not-hit-instantly-it-sends-when-magento-cron-jobs-is-initiated/
This will help you to get rid of late sending emails.
i have used this website for years but this is my first time asking a question, so feel free to correct me if i don't do it right.
We are running into this problem a lot lately.
We have mongos running one multiple Centos5 servers connecting to sharded replicaset mongodb servers running 2.4.9.
Recently we did a lot of optimization which increased our throughput and while this problem used to happen a lot before, it's now become intolerable.
After certain number of successful read requests the php just errors out and throws same error over and over. After awhile it can recover. This seems to be on per-app server basis and does not affect all app servers at the same time.
If I pkill mongo and start a new mongos connection, this is usually fixed.
any idea on which direction to dig in or maybe pointers are appreciated, thanks.
this is the error we get:
Fatal error: Uncaught exception 'MongoCursorException' with message 'localhost:27017: DBClientBase::findN: transport error: internal-mongo-r1-d2-dev.myserver.com:27017 ns: admin.$cmd query: { setShardVersion: "", init: true, configdb: "internal-mongo-c1-dev.myserver.com:27019,internal-mongo-c2-dev.myserver.com:27019,internal-mongo-c3-dev.myserver.com:27019", serverID: ObjectId('52f57ce26ca6543144b077e5'), authoritative: true }' in /mnt/home/webapps/cgs-sys/releases/20140207163554/includes/db/mongo/mongo.inc:185
Stack trace:
#0 /mnt/home/webapps/cgs-sys/releases/20140207163554/includes/db/mongo/mongo.inc(185): MongoCursor->rewind()
#1 /mnt/home/webapps/cgs-sys/releases/20140207163554/includes/db/data.inc(62): MongoCG::get(Array)
#2 /mnt/home/webapps/cgs-sys/releases/20140207163554/includes/data/session/savedsession.inc(30): Data::select('mongo', 'coll_saved_sess...', '_id', 'updated_ss', Array, Array)
#3 /mnt/home/webapps/cgs-sys/releases/20140207163554/includes/data/session/savedsession.inc(20): SavedSession::select(Array)
#4 /mnt/home/webapps/cgs-sys/releases/20140207163554/includes/access/phpsession.inc(32): SavedSession::get_one('fl0uq0nqjbbo4iq...')
#5 [internal function]: PhpSession::read('fl0uq0nqjbbo4iq...')
#6 /mnt/home/webapps/cgs-sys/releases/20140207163554/includes/access/phpsession.inc(16): session_start()
#7 /mnt/home/webapps/cgs-sys/releases/20140207163554/includes/allinc.inc(15): PhpSession::start()
#8 /mnt/home/webapps/cgs-sys/releases/20140207163554/p.php(4): include_once('/mnt/home/webap...')
#9 {main}
thrown in /mnt/home/webapps/cgs-sys/releases/20140207163554/includes/db/mongo/mongo.inc on line 185
just wanted to do a quick follow up.
after digging in we found out that we had a low setting of "open files" on the mongod servers which was fixed, and these errors disappeared.
There are quite a few references around to similar errors and the general suggestion is the first thing to look at at TCP keepalive.
Apart from the other considerations you may also want to look at keepalive settings in your driver connection.
Some links as a place to start:
https://www.google.com.au/search?q=mongodb+transport+error
https://groups.google.com/forum/#!topic/mongodb-user/eod_QH9-VIY
https://jira.mongodb.org/browse/SERVER-3446
https://www.google.com.au/search?q=mongodb+transport+error
The error below only occurs when I upload my code to the server. When I'm on my local development environment works perfectly. My local is Windows and my Production is Linux.
What does this mean? What should I do to solve it?
Fatal error: Uncaught exception 'CloudKey_RPCException' with message 'You must provide an url for mp4_h264_aac' in /var/www/application/libraries/CloudKey.php:336 Stack trace: #0 /var/www/application/libraries/VideoUploader.php(56): CloudKey_Api->__call('create', Array) #1 /var/www/application/libraries/VideoUploader.php(56): CloudKey_Media->create(Array) #2 /var/www/application/controllers/Admin.php(519): VideoUploader->upload(Array, Array, '06d88cc1721cbe1...') #3 [internal function]: Admin->videos('upload') #4 /var/www/system/core/CodeIgniter.php(356): call_user_func_array(Array, Array) #5 /var/www/public/index.php(274): require_once('/var/www/system...') #6 {main} thrown in /var/www/application/libraries/CloudKey.php on line 336
Ok, in case anyone ever needs this. The problem is that, I was using the $_FILES['file']['tmp_name'] directly into DMCloud method. Turns out that on Windows, it's something like C:\temp\file.tmp and on linux is something like /tmp/file. DMCloud api requires that the file used for upload must have an extension.
So, it failed to upload the file, and when I tried to use the URL of the failed upload, it gaveme this exception.
I hope someone fin this hopeful in the future =)
The problem is.. that when I try to login the user and then get the user info, I get error from Facebook API. with error code: 1
The same code works for one server, but not another one. THe config and everything are the same, except the non-working one is hosted at RackSpace cloud environment. I don't know if that's the cuase.
Information is here:
Server: Nginx. PHP 5
Backend: running Zend framework
API: use FB's facebook.php and facebookapi_php5_restlib.php
fail at the call_method, post_request(), when calling " facebook.users.getInfo "
Here is the error message
Exception
Error Code: 1
Message: An unknown error occurred
#0 /home/www/entouraxyz-dev.sector3gamez.com/site_prod/_library/facebook/facebookapi_php5_restlib.php(956): FacebookRestClient->call_method('facebook.fql.qu...', Array)
#1 /home/www/entouraxyz-dev.sector3gamez.com/site_prod/app/facebook/controllers/FacebookController.php(375): FacebookRestClient->fql_query('SELECT uid, fir...')
#2 /home/www/entouraxyz-dev.sector3gamez.com/site_prod/app/facebook/controllers/FacebookController.php(114): Facebook_FacebookController->_facebook_login()
#3 /home/www/entouraxyz-dev.sector3gamez.com/site_prod/_library/Zend/Controller/Action.php(132): Facebook_FacebookController->init()
#4 /home/www/entouraxyz-dev.sector3gamez.com/site_prod/_library/Zend/Controller/Dispatcher/Standard.php(261): Zend_Controller_Action->__construct(Object(Zend_Controller_Request_Http), Object(Zend_Controller_Response_Http), Array)
#5 /home/www/entouraxyz-dev.sector3gamez.com/site_prod/_library/Zend/Controller/Front.php(945): Zend_Controller_Dispatcher_Standard->dispatch(Object(Zend_Controller_Request_Http), Object(Zend_Controller_Response_Http))
#6 /home/www/entourxyz-dev.sector3gamez.com/site_prod/_library/Zcms/Application.php(226): Zend_Controller_Front->dispatch()
#7 /home/www/entourxyz-dev.sector3gamez.com/site_prod/index.php(38): Zcms_Application::run('MainPlugin')
#8 {main}
I have tested the PHPInfo. exactly the same. Max Execute timeout is 60sec. and CURL timeout is increased to 60 too. so. it may not be the timeout issue.
I have found that the Facebook API will shut you out for a day or so (not tested how long exactly) when you've been testing your app and been sending a lot of invalid (?) requests.
Wait a while and it will likely work again. The reason it happens on one server only will likely be the IP address.
All of this is speculated since Facebook won't specify anything regarding limitation or blocking, for security reasons.