Helix Server License Renewal 2018-06-09

[Marty Stanquist]

Team,

I now have our new Perforce Helix server license file for the upcoming year.
The current license will expire on Saturday 2018-06-09. Once the service
terminates, I'll upload the new license file and restart the server. If you
have any issues going forward, please post them here.

Marty

[Marty Stanquist]

"Marty Stanquist" wrote in message news:pf4ei6$tdn$***@www.openwatcom.org...

Team,

I now have our new Perforce Helix server license file for the upcoming year.
The current license will expire on Saturday 2018-06-09. Once the service
terminates, I'll upload the new license file and restart the server. If you
have any issues going forward, please post them here.

Marty

The update has been completed. Let me know if there are any issues.

Marty

[Paul S. Person]

On Sun, 10 Jun 2018 14:16:03 -0500, "Marty Stanquist"

Post by Marty Stanquist
Team,
I now have our new Perforce Helix server license file for the upcoming year.
The current license will expire on Saturday 2018-06-09. Once the service
terminates, I'll upload the new license file and restart the server. If you
have any issues going forward, please post them here.
Marty
The update has been completed. Let me know if there are any issues.
Marty

Well, this is odd.

The other OW newgroups do nothing but record a failure to connect.

So did this one -- but it downloaded the message anyway! So I guess
the server was available briefly.

The web server and perforce are not available.

A while back, you asked me to to tracert:

C:\Users\Paul>tracert 70.165.27.117

Tracing route to wsip-70-165-27-117.pn.at.cox.net [70.165.27.117]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ControlPanel.Home [192.168.1.1]
2 13 ms 11 ms 10 ms
h-67-100-127-1.sttn.wa.dynamic.globalcapacity.com [67.100.127.1]
3 14 ms 11 ms 11 ms
h-67-103-216-25.sttn.wa.globalcapacity.com [67.103.216.25]
4 14 ms 11 ms 11 ms
h-68-167-191-98.sttn.wa.globalcapacity.com [68.167.191.98]
5 14 ms 11 ms 10 ms 173.205.55.197
6 * * * Request timed out.
7 85 ms 84 ms 83 ms ae-2-3513.edge1.Atlanta4.Level3.net
[4.69.150.161]
8 85 ms 86 ms 83 ms 4.53.232.58
9 106 ms 106 ms 106 ms pnschdrj02-ae0.0.rd.pn.cox.net
[68.1.1.111]
10 106 ms 107 ms 105 ms ip68-1-11-173.at.at.cox.net
[68.1.11.173]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Line 10 was the last hop before wsip-70-165-27-117.pn.at.cox.net
[70.165.27.117] on the result I recorded for future reference.

[Paul S. Person]

On Mon, 11 Jun 2018 09:32:13 -0700, Paul S. Person
<***@ix.netscom.com.invalid> wrote:

Further checking suggests that openwatcom.contributors, at least, is
available on eternal-september, hence the message activity.

In fact, all five are, so it looks like I can disable the openwatcom
server and avoid having to respond to the error messages. I will still
be able to check connectivity (which confirms that the ow usenet
server is timing out) when the other servers drop.