XF 2.1 Push notification *errors* (not timeout errors)

rfc0001

Well-known member
Unrelated to the timeout errors in several other posts, I'm seeing these errors - any idea what these are caused by?
  • ErrorException: Push notification failure: {"success":false,"endpoint":{},"message":"cURL error 28: (see http:\/\/curl.haxx.se\/libcurl\/c\/libcurl-errors.html)"}
  • src/XF/Error.php:75
Stack trace
Code:
#0 src/XF.php(187): XF\Error->logError('Push notificati...', false)
#1 src/XF/Service/PushNotification.php(247): XF::logError('Push notificati...')
#2 src/XF/Service/PushNotification.php(167): XF\Service\PushNotification->handleResults(Array, Array)
#3 src/XF/Service/PusherTrait.php(159): XF\Service\PushNotification->sendNotifications()
#4 src/XF/Repository/UserAlert.php(147): XF\Service\Alert\Pusher->push()
#5 src/XF/Repository/UserAlert.php(98): XF\Repository\UserAlert->insertAlert(400, 754, 'user123', 'post', 96089, 'reaction', Array)
#6 src/XF/Reaction/AbstractHandler.php(181): XF\Repository\UserAlert->alertFromUser(Object(xenMade\ST404\XF\Entity\User), Object(xenMade\ST404\XF\Entity\User), 'post', 96089, 'reaction', Array)
#7 src/XF/Repository/Reaction.php(196): XF\Reaction\AbstractHandler->sendReactionAlert(Object(xenMade\ST404\XF\Entity\User), Object(xenMade\ST404\XF\Entity\User), 96089, Object(XFMG\XF\Entity\Post), 1)
#8 src/XF/Repository/Reaction.php(137): XF\Repository\Reaction->insertReaction(1, 'post', 96089, Object(xenMade\ST404\XF\Entity\User), true, false)
#9 src/XF/ControllerPlugin/Reaction.php(65): XF\Repository\Reaction->reactToContent(1, 'post', 96089, Object(xenMade\ST404\XF\Entity\User), true)
#10 src/XF/ControllerPlugin/Reaction.php(19): XF\ControllerPlugin\Reaction->actionToggleReaction(Object(XFMG\XF\Entity\Post), 'posts/reactions', 'posts')
#11 src/XF/ControllerPlugin/Reaction.php(12): XF\ControllerPlugin\Reaction->actionReact(Object(XFMG\XF\Entity\Post), 'posts', 'posts/react', 'posts/reactions')
#12 src/XF/Pub/Controller/Post.php(368): XF\ControllerPlugin\Reaction->actionReactSimple(Object(XFMG\XF\Entity\Post), 'posts')
#13 src/XF/Mvc/Dispatcher.php(321): XF\Pub\Controller\Post->actionReact(Object(XF\Mvc\ParameterBag))
#14 src/XF/Mvc/Dispatcher.php(244): XF\Mvc\Dispatcher->dispatchClass('XF:post', 'React', Object(XF\Mvc\RouteMatch), Object(Andy\ShowDeleted\XF\Pub\Controller\Post), NULL)
#15 src/XF/Mvc/Dispatcher.php(100): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), Object(Andy\ShowDeleted\XF\Pub\Controller\Post), NULL)
#16 src/XF/Mvc/Dispatcher.php(50): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#17 src/XF/App.php(2177): XF\Mvc\Dispatcher->run()
#18 src/XF.php(390): XF\App->run()
#19 index.php(20): XF::runApp('XF\\Pub\\App')
#20 {main}
 
Can be ignored for now. We do have it in mind to filter some of these out. I think timeout errors happen frequently enough that we don't need to log them.
 
So any idea when/why this would occur? The previous "timeout" erorrs (the word timeout literally in the server error message) were due to network conditions on my host causing severe inbound traffic contraints, which they since resolved, and were causing all sort of other timeouts system wide. Since I'm no longer having those issues, I'm trying to figure out the root cause of these issues and if I should be concerned. I see a few a day and somedays none. with about 100 active daily members.
 
Here is the error I was getting previously:
Clearly says timed out after 10 seconds:
ErrorException: Push notification failure: {"success":false,"endpoint":{},"message":"cURL error 28: Operation timed out after 10000 milliseconds with 0 out of -1 bytes received (see http:\/\/curl.haxx.se\/libcurl\/c\/libcurl-errors.html)"} src/XF/Error.php:75

Any idea under what conditions the previous error above happens compared to this one?
 
I'm not certain why the wording is different, but any error which is cURL error 28 is a timeout, whether it mentions that word or not. This error and the previous ones are all timeouts and the time limit is 10 seconds. So from what I can tell, despite the wording, they are exactly the same.

Certainly getting them with any frequency with 100 active daily users is unexpected so it does imply there are still issues.
 
Gotcha, good call - didn't even realize these were the same error. I'm not seeing any other inbound or outbound perf issues (and was seeing them everywhere previously), so I'm skeptical it's the same or related cause, but will keep an eye on it. Thanks.
 
Back
Top Bottom