a reboot of the trac host fixed the problem. On Wednesday, September 13, 2017 at 8:31:11 AM UTC+1, David Roe wrote: > > I haven't been able to find a log and I need to go to sleep. Dima should > have access though.... > David > > On Wed, Sep 13, 2017 at 3:17 AM, Vincent Delecroix <20100.d...@gmail.com > <javascript:>> wrote: > >> >> >> On 13/09/2017 09:17, David Roe wrote: >> >>> On Wed, Sep 13, 2017 at 3:10 AM, Dima Pasechnik <dim...@gmail.com >>> <javascript:>> wrote: >>> >>> As I mentioned, this is not under our control which ports are blocked on >>>> GCE hosts, and which are not. >>>> >>>> >>> I think it is (see >>> https://cloud.google.com/compute/docs/vpc/using-firewalls), >>> but I'm still confused. If you look at our list of firewall rules, >>> there's >>> a line for explicitly allowing tcp:9418, so I don't know why this port >>> would be blocked by the server. >>> >> >> Does the firewall produces a log? >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sage-devel" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to sage-devel+...@googlegroups.com <javascript:>. >> To post to this group, send email to sage-...@googlegroups.com >> <javascript:>. >> Visit this group at https://groups.google.com/group/sage-devel. >> For more options, visit https://groups.google.com/d/optout. >> > >
-- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
