Notifications ceased (FCM Issue?)

[gfro84]

Hi,

I've stopped receiving zmninja push notifications as of last night, this despite zm logs indicating FCM message has been sent following successful object detection.

Has asker's FCM server stopped operating, or is it an issue specific to me which warrants further debugging? I know there are plans afoot for a new zmes with an updated FCM server.

Many thanks

[tsp84]

I received and fcm a cpl hours ago via the zmNinja notifications.

Sometimes fcm goes down and when things work again some queued notifications are received.

Can you say itize and post your logs? Also try deleting tokens.txt and let zmes recreate it for you.

[tsp84]

I received and fcm a cpl hours ago via the zmNinja notifications.

Sometimes fcm goes down and when things work again some queued notifications are received.

Can you say itize and post your logs? Also try deleting tokens.txt and let zmes recreate it for you.

[gfro84]

Thanks TSP84,

I followed your suggestions to no avail. Using the eventserver instructions, I stopped zmes, set 'console_logs=yes' and did 'sudo -u www-data /usr/bin/zmeventnotification.pl --debug', which revealed the following;

Code: Select all

DBG-2:2022-01-26,09:17:53 PARENT: There are 1 active child forks & 0 zm_detect processes running...
DBG-2:2022-01-26,09:17:53 PARENT: checkEvents() new events found=0
DBG-2:2022-01-26,09:17:53 PARENT: There are 0 new Events to process
DBG-2:2022-01-26,09:17:53 PARENT: ---------->Tick END (active forks:1, total forks:2, active hooks: 0)<--------------
DBG-1:2022-01-26,09:17:54 |----> FORK:Front Main (2), eid:8794 fcmv1: FCM push message error Can't connect to 
us-central1-ninja-1105.cloudfunctions.net:443 (Temporary failure in name resolution)

Temporary failure in name resolution at /usr/share/perl5/LWP/Protocol/http.pm line 50.

DBG-3:2022-01-26,09:17:54 |----> FORK:Front Main (2), eid:8794 child finished writing to parent
DBG-3:2022-01-26,09:17:54 |----> FORK:Front Main (2), eid:8794 For 2 (Front Main), SHM says: state=0, eid=8794

So I'm left thinking it could either be i) I can't access all of a sudden (unlikely) or ii) the server is down.

Your reply makes ii) seem unlikely, so fingers crossed it is just temporary issues which will sort itself out. Google firebase service status is good though. Anyone else having issues?

Thanks

[tsp84]

Have you tried pinging it? I just did from termux on my phone and the name resolved to an IP.

Code: Select all

ping us-central1-ninja-1105.cloudfunctions.net
PING us-central1-ninja-1105.cloudfunctions.net (216.239.36.54) 56(84) bytes of data.
64 bytes from 216.239.36.54: icmp_seq=1 ttl=118 time=31.1 ms
64 bytes from 216.239.36.54: icmp_seq=2 ttl=118 time=39.8 ms
64 bytes from 216.239.36.54: icmp_seq=3 ttl=118 time=41.5 ms
64 bytes from 216.239.36.54: icmp_seq=4 ttl=118 time=31.6 ms
64 bytes from 216.239.36.54: icmp_seq=5 ttl=118 time=42.0 ms
^C
--- us-central1-ninja-1105.cloudfunctions.net ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4013ms
rtt min/avg/max/mdev = 31.191/37.267/42.089/4.835 ms

[gfro84]

A non-issue. My firewall rules were my issue.

I'll try delete this.

Thanks.

[tsp84]

No worries, I recently purged my CloudFlare MX DNS records and spent 30 mins troubleshooting with Google support about why I wasn't receiving emails anymore.

(Sh)It happens!