That will certainly cause the problem. Pulling data from an external IP in
a report cycle can be problematic when the remote IP is not replying for
some reason. You (or the author if not you) might want to have a look at
the code and see if you can refactor it to gracefully handle no response
from the external IP. Of course that may entail not just the code that hits
the URL failing gracefully but also the report template that uses the data
from the external IP being able to execute without the external data.
On Thursday, 22 February 2018 23:58:36 UTC+10, Mauro Venturelli wrote:
> Hi Gary,
> thanks for the quick reply.
> extIP.py receives from a server the public IP address,
> looks like the server is down hence the problem.
> Thanks for finding it
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.