Maintenance on th cp?

[somereseller]

The cp is unreachable again and I didn't get a message about any maintenance...

[jmbeach]

do you mean HSphere? If so, it's working for me right now.

No maintenance just a reboot.. Should be fine now.

[Wonderer]

Still broken.

I can get to http://cp.hsphere.cc:8080/psoft/serv...oft.hsphere.CP

But not to...

https://cp.wonderer.net:8443/psoft/s...oft.hsphere.CP

or

http://cp.wonderer.net:8080/psoft/se...oft.hsphere.CP

Forgot to mention, cp.hsphere.cc resolves to 65.57.231.120 while cp.wonderer.net resolves to 216.157.134.147

[somereseller]

Still unreachable for me

[Wonderer]

Tracing route to cp.hsphere.cc [65.57.231.120]

over a maximum of 30 hops:



1 <10 ms <10 ms 15 ms porom001.adidasus.com [10.1.92.2]

2 <10 ms <10 ms <10 ms porom006.adidasus.com [209.63.106.1]

3 <10 ms <10 ms <10 ms s5-0-0.gw03.ptld.eli.net [209.210.8.165]

4 <10 ms <10 ms <10 ms srp2-0.cr02.ptld.eli.net [208.186.20.132]

5 15 ms 16 ms 16 ms p9-0.cr01.rcrd.eli.net [207.173.115.42]

6 16 ms 15 ms 16 ms srp3-0.cr02.rcrd.eli.net [208.186.20.242]

7 16 ms 15 ms 16 ms p9-0.cr01.sntd.eli.net [207.173.114.57]

8 31 ms 16 ms 31 ms so-0-0-0--0.er01.plal.eli.net [207.173.114.138]

9 16 ms 15 ms 16 ms gig1-2.edge1.paix-sjo1.Level3.net [209.245.146.25]

10 16 ms 15 ms 16 ms GigabitEthernet3-0.core1.SanJose1.Level3.net [209.244.3.245]

11 16 ms 15 ms 32 ms ae0-53.mp1.SanJose1.Level3.net [64.159.2.65]

12 94 ms 93 ms 94 ms so-0-1-0.mp2.Orlando1.Level3.net [64.159.0.26]

13 93 ms 94 ms 94 ms gige11-2.hsa1.Orlando1.Level3.net [209.247.11.50]

14 94 ms 94 ms 93 ms 67.30.136.2

15 94 ms 94 ms 93 ms 66.103.132.6

16 94 ms 94 ms 94 ms ns1.hsphere.cc [65.57.231.120]



Trace complete.



Tracing route to cp.wonderer.net [216.157.134.147]

over a maximum of 30 hops:



1 <10 ms <10 ms <10 ms porom001.adidasus.com [10.1.92.2]

2 <10 ms <10 ms <10 ms porom006.adidasus.com [209.63.106.1]

3 <10 ms <10 ms <10 ms s5-0-0.gw03.ptld.eli.net [209.210.8.165]

4 <10 ms <10 ms <10 ms srp2-0.cr02.ptld.eli.net [208.186.20.132]

5 15 ms 16 ms 16 ms p9-0.cr01.rcrd.eli.net [207.173.115.42]

6 16 ms 15 ms 16 ms srp3-0.cr02.rcrd.eli.net [208.186.20.242]

7 16 ms 15 ms 32 ms p9-0.cr01.sntd.eli.net [207.173.114.57]

8 16 ms 16 ms 15 ms so-0-0-0--0.er01.plal.eli.net [207.173.114.138]

9 16 ms 16 ms 15 ms gig1-2.edge1.paix-sjo1.Level3.net [209.245.146.25]

10 31 ms 15 ms 16 ms GigabitEthernet3-1.core1.SanJose1.Level3.net [209.244.3.249]

11 32 ms 15 ms 16 ms ae0-51.mp1.SanJose1.Level3.net [64.159.2.1]

12 94 ms 94 ms 109 ms so-0-2-0.mp1.Orlando1.Level3.net [64.159.0.29]

13 94 ms 94 ms 94 ms gige10-0.hsa1.Orlando1.Level3.net [64.159.0.34]

14 94 ms 109 ms 94 ms 67.30.136.2

15 94 ms 109 ms 94 ms 66.103.132.6

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.




Tracing route to wonderer.net [216.157.134.122]

over a maximum of 30 hops:



1 <10 ms <10 ms <10 ms porom001.adidasus.com [10.1.92.2]

2 <10 ms <10 ms <10 ms porom006.adidasus.com [209.63.106.1]

3 15 ms <10 ms <10 ms s5-0-0.gw03.ptld.eli.net [209.210.8.165]

4 <10 ms <10 ms <10 ms srp2-0.cr02.ptld.eli.net [208.186.20.132]

5 16 ms 16 ms 15 ms p9-0.cr01.rcrd.eli.net [207.173.115.42]

6 15 ms 16 ms 15 ms srp3-0.cr02.rcrd.eli.net [208.186.20.242]

7 31 ms 16 ms 15 ms p9-0.cr01.sntd.eli.net [207.173.114.57]

8 15 ms 32 ms 15 ms so-0-0-0--0.er01.plal.eli.net [207.173.114.138]

9 15 ms 31 ms 16 ms gig1-2.edge1.paix-sjo1.Level3.net [209.245.146.25]

10 16 ms 16 ms 31 ms GigabitEthernet3-1.core1.SanJose1.Level3.net [209.244.3.249]

11 15 ms 16 ms 31 ms ae0-51.mp1.SanJose1.Level3.net [64.159.2.1]

12 94 ms 93 ms 94 ms so-0-1-0.mp2.Orlando1.Level3.net [64.159.0.26]

13 94 ms 110 ms 93 ms gige10-1.hsa1.Orlando1.Level3.net [64.159.0.42]

14 94 ms 109 ms 94 ms 67.30.136.2

15 94 ms 109 ms 94 ms 66.103.132.6

16 110 ms 94 ms 93 ms 216.157.134.122



Trace complete.

[somereseller]

ping cp.wonderer.net

Pinging cp.wonderer.net [216.157.134.147] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

etc.
etc.

[Wonderer]

Its a DNS problem. I sent in a TT and they got it fixed.

[Vixen]

Originally posted by somereseller
The cp is unreachable again and I didn't get a message about any maintenance...

Do you ever ASK a question before you decide to be accusatory and complaining?? Or do you not know how to inquire without being rude??

[bootNumlock]

vixen--

your ability to read emotion into text is simply remarkable see when i read his post is sounded more like--

hey, the cp is down again and i didn't get an email about maintenance

and then what i heard was--

so is it maintenance or is something just not right?

and then a little voice in my head said to collect every blue m&m that i could find and bury it in the field just south of my house and wait util magical fairies came to collect the candies....

[Vixen]

Well, it becomes easier and easier when someone never actually asks a question but addresses it an argumentative manner. (You don't get the joy of reading all the TTs that come in the same manner. Lucky you. LoL) I am talented. What can I say??

As for the M&Ms I am not sure about that. I just thought it rained Skittles. LoL

[bootNumlock]

that's why they never tasted like chocolate

[Vixen]

Originally posted by bootNumlock02
that's why they never tasted like chocolate

Exactly. LoL Skittles just try to pull your freakin fillings out.

[bootNumlock]

wouldn't know about that--never had a cavity [na, na, na, na, na]

[admin]

We found the problem, the reason it worked for some andnot others was for some reason the CP did not add the IPs when it rebooted.. After we got 2 tickets we thought hey something must be up.. We thought hey Psoft must of screwed up again..

Then got to really looking around and found the IPs were missing from the server.. Ran the script and all good again. Sorry about that.. First time I have ever seen the CP do that..