Failed lookup on gcm on autoscale about uniqush-push HOT 11 CLOSED

Thank you so much for your report! I will work on this issue soon. It seems like the DNS is not working here. However, if it is only on GCM, then there might be a bigger problem. I will first do some googling and then try to reproduce it on my side. Mark it as MustFix for the next release.

from uniqush-push.

Thanks @monnand

from uniqush-push.

@cmabastar Sorry for the delay. I was working on other projects.

Some questions about this issue:

• Does the instance have an Internet connection? I mean, when uniqush-push is running, does it have an Internet connection?
• Did you try to log onto the instance and run host android.googleapis.com?
• Which DNS server are you using?
• You may add a line to your /etc/hosts file explicitly tells the system what is the IP address of android.googleapis.com. This is a dirty fix but may work if it is only the problem of the DNS.

from uniqush-push.

Yes it does have DNS server. yes we did try hosts. We didn't try the
/etc/hosts yet. DNS is default in AWS. I'll see if the /etc/hosts works.

Cheers,

Christopher Marlon S. Abastar

On Fri, Mar 14, 2014 at 2:46 AM, monnand [email protected] wrote:

@cmabastar https://github.com/cmabastar Sorry for the delay. I was
working on other projects.

Some questions about this issue:

• Does the instance have an Internet connection? I mean, when
  uniqush-push is running, does it have an Internet connection?
• Did you try to log onto the instance and run host
  android.googleapis.com?
• Which DNS server are you using?
• You may add a line to your /etc/hosts file explicitly tells the
  system what is the IP address of android.googleapis.com. This is a
  dirty fix but may work if it is only the problem of the DNS.

Reply to this email directly or view it on GitHubhttps://github.com//issues/43#issuecomment-37571661
.

This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error, please notify the system manager.
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee, you should not
disseminate, distribute or copy this email. Please notify the sender
immediately by email if you have received this email by mistake and delete
this email from your system. If you are not the intended recipient, you are
notified that disclosing, copying, distributing or taking any action in
reliance on the contents of this information is strictly prohibited.

from uniqush-push.

Thank you, @cmabastar. Let me double check: You mean that uniqush-push is unable to resolve the host name even if host android.googleapis.com works? This means after running host android.googleapis.com, uniqush-push can still not resolve the host name, am I correct?

My quick thought was: When the instance was started, it might not able to resolve host names for a short period somehow. During this period, uniqush-push is unable to resolve any host name. However, after a short period, it could work. However, it seems not the case.

My attempted approach is: Whenever there's a DNS error, I will let uniqush-push re-send the message after several seconds. I can quickly build a version like this. Will you be able to help me to test this version?

from uniqush-push.

Hi Monnand,

Yes i might be able to test the new build on my free time.

Cheers,

Christopher Marlon S. Abastar

On Sat, Mar 15, 2014 at 12:06 PM, monnand [email protected] wrote:

Thank you, @cmabastar https://github.com/cmabastar. Let me double
check: You mean that uniqush-push is unable to resolve the host name even
if host android.googleapis.com works? This means after running host
android.googleapis.com, uniqush-push can still not resolve the host name,
am I correct?

My quick thought was: When the instance was started, it might not able to
resolve host names for a short period somehow. During this period,
uniqush-push is unable to resolve any host name. However, after a short
period, it could work. However, it seems not the case.

My attempted approach is: Whenever there's a DNS error, I will let
uniqush-push re-send the message after several seconds. I can quickly
build a version like this. Will you be able to help me to test this version?

Reply to this email directly or view it on GitHubhttps://github.com//issues/43#issuecomment-37716704
.

This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error, please notify the system manager.
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee, you should not
disseminate, distribute or copy this email. Please notify the sender
immediately by email if you have received this email by mistake and delete
this email from your system. If you are not the intended recipient, you are
notified that disclosing, copying, distributing or taking any action in
reliance on the contents of this information is strictly prohibited.

from uniqush-push.

Hi @cmabastar

I just build a new version for you to test:

• .tar.gz
• .rpm
• .deb

Once you download the file, you may want to try uniqush-push -version to make sure it's the correct version.

Please let me know any problem you have. Thank you so much!

from uniqush-push.

Hi I haven't verified the GCM problem yet. but currently this build shows up an error for APNS
Failed: tls: either ServerName or InsecureSkipVerify must be specified in the tls.Config

from uniqush-push.

Hi @monnand ,

This build still fail on gcm.. Still getting the

[Push][Error] 2014/04/10 14:45:11 RequestID=53463df7-lK7qrhcFjdWy0gAZSzqrYg== Service=0839899613932562 Subscriber=532776d43dc9e15ffd38f36f PushServiceProvider=gcm:321c686a5eb5a03ef5d447d19182de600a69e65d DeliveryPoint=gcm:f8bc083e1d04a825f6309a871b4c490cd637fbb3 Failed: Post https://android.googleapis.com/gcm/send: dial tcp: lookup android.googleapis.com: no such host

from uniqush-push.

Thanks for your test!

I saw the error message from two users and it should not be a coincidence. I will dig into this problem this week.

from uniqush-push.

Hi @cmabastar,

I think now I have an (sort-of) answer to this problem: Because there are too many concurrent connections. This post may be useful. (tl;dr The system has a hard limit on how many number of sockets you could have. You could either increase this number, or decrease the number of concurrent connections.)

I'm working on a new version of uniqush-push and will address this problem in that version. Maybe I can provide a place somewhere in the config file so that you can set the max. number of fds.

from uniqush-push.