Unable to communiucate to MongoosePush service due to pool_timeout

[rajeshkumar114433]

Hi , I am running MongoosePush from DockerHub and getting console log as :

$ sudo docker run -p 8443:8443 -v /home/tg-linux/priv:/opt/app/priv/ -e PUSH_FCM_APP_KEY="" -e PUSH_HTTPS_CERTFILE="/opt/app/priv/ssl/server.pem" -e PUSH_HTTPS_KEYFILE="/opt/app/priv/ssl/server.key" -e PUSH_APNS_ENABLED=0 -it --rm mongooseim/mongoose-push:latest

=INFO REPORT==== 20-Dec-2018::06:48:32 === msg: "Starting reporters with []\n" options: [] 06:48:32.122 [error] Supervisor 'Elixir.Logger.Supervisor' had child 'Elixir.Logger.ErrorHandler' started with 'Elixir.Logger.Watcher':start_link({error_logger,'Elixir.Logger.ErrorHandler',{false,false,500}}) at <0.1201.0> exit with reason normal in context child_terminated 06:48:32.144 [info] Application lager started on node 'mongoose_push@127.0.0.1' 06:48:32.145 [info] Application elixometer started on node 'mongoose_push@127.0.0.1' 06:48:32.145 [info] Application logger_lager_backend started on node 'mongoose_push@127.0.0.1' 06:48:32.145 [info] Application mime started on node 'mongoose_push@127.0.0.1' 06:48:32.145 [info] Application crypto started on node 'mongoose_push@127.0.0.1' 06:48:32.153 [info] Application plug started on node 'mongoose_push@127.0.0.1' 06:48:32.153 [info] Application asn1 started on node 'mongoose_push@127.0.0.1' 06:48:32.153 [info] Application public_key started on node 'mongoose_push@127.0.0.1' 06:48:32.154 [info] Application ssl started on node 'mongoose_push@127.0.0.1' 06:48:32.154 [info] Application ranch started on node 'mongoose_push@127.0.0.1' 06:48:32.154 [info] Application cowlib started on node 'mongoose_push@127.0.0.1' 06:48:32.154 [info] Application cowboy started on node 'mongoose_push@127.0.0.1' 06:48:32.154 [info] Starting Elixir.MongoosePush.Router with Cowboy on https://0.0.0.0:8443 06:48:32.199 [info] Starting FCM pool with API key 06:48:33.035 [warning] lager_error_logger_h dropped 90 messages in the last second that exceeded the limit of 50 messages/sec

and mongooseim.cfg file:

{outgoing_pools, [{http, global, mongoose_push_http, [{strategy, available_worker}], [{server, "https://localhost:8443"}]} ] }. {mod_event_pusher, [ {backends, [ {push, [{wpool, [{workers, 100}]}]} ]} ]}, {mod_pubsub, [ {plugins, [<<"push">>]} ]}, {mod_push_service_mongoosepush, [ {pool_name, mongoose_push_http}, {api_version, "v2"}]}

The issue i am facing is whenever MongooseIM server tries to communicate with MongoosePush service for offline messages, I am getting below log on MongooseIM console and not getting push notification to the android client:

13:31:10.234 [error] Unable to communicate to MongoosePush service due to pool_timeout

[rslota]

Hi @rajeshkumar114433 ,

Is the issue still present? My initial exploration of this topic resulted in the following conclusions:

Issue is probably not related to MongoosePush - pool_timeout error is used when there is no connection available in the MongooseIM HTTP pool. This may mean that all connections "hang" for some reason (connection issues?). It may be interesting to see what happens if MongoosePush is not available at all.

[pawlooss1]

Closing due to lack of activity.