Home   Help Search Login Register  
You are not logged in. To get the full experience of these forums, we recommend you log in or register
Plusnet Usergroup » All Users - The Open Forum » Plusnet Network and Technical Issues » CGI clocks, ccgi03 an hour slow
Pages: [1]
  Print  
Author Topic: CGI clocks, ccgi03 an hour slow  (Read 1166 times)
phugoid

Posts: 18

WWW
« on: May 20, 2007, 06:38:43 pm »

Apologies if this has already been posted, but could someone sync the clocks across the CGI server – ccgi03 looks to be an hour slow.

phugoid

Posts: 18

WWW
« Reply #1 on: May 21, 2007, 11:47:52 am »

*BUMP*  Is anyone going to re-sync the clocks on the CGI server and get ccgi03 in step with the others? 

Having one node that’s an hour slow produces a spectacularly schizophrenic set of logfile entries and obviously plays havoc with any server-side caching.
jelv1

Posts: 1967


« Reply #2 on: May 21, 2007, 12:00:42 pm »

I suggest you have a look at the following topic which details the measures put in place to make sure the ccgi servers have the correct time:

http://usergroup.plus.net/forum/index.php/topic,3798.0.html

There's a link in that script to http://ccgi.csogilvie.plus.com/uptimes.php which shows the output from uptime for each of the 4 servers - that confirms the time on ccgi03 is wrong.

jelv
jelv1

Posts: 1967


« Reply #3 on: May 21, 2007, 02:13:08 pm »

Have you actually raised a ticket or rung in to report this?

jelv
jelv1

Posts: 1967


« Reply #4 on: May 21, 2007, 02:50:34 pm »

I think the answer to that question was obviously not.

I raised a ticket myself at 3:12pm.

At 3:38pm I was sent a response saying
Quote
I have made our networks team aware of this issue. We hope to have this resolved shortly.

I've just checked (3:45pm) and the time on ccgi03 has been reset.

jelv
lmartin

Posts: 1404


Comms Team

« Reply #5 on: May 21, 2007, 02:56:12 pm »

Was just about to raise a problem and it's back to normal smiley

Sorry I didn't spot this one earlier, guys.

Liam Martin
PlusNet Comms Team
jelv1

Posts: 1967


« Reply #6 on: May 21, 2007, 03:07:38 pm »

A think this demonstrates a good lesson: If you see something wrong raise a ticket - forums are not a route for reporting faults.

jelv
phugoid

Posts: 18

WWW
« Reply #7 on: May 21, 2007, 04:22:54 pm »

Cheers lmartin.  smiley I must admit, I didn’t so much see this as a request for help or technical support, more like flagging up something that PN could note and sort out as appropriate. But reading back over the posts, I think it probably was worth a ticket.  embarassed
Matt_2k34

Posts: 387

« Reply #8 on: May 21, 2007, 04:48:36 pm »

A think this demonstrates a good lesson: If you see something wrong raise a ticket - forums are not a route for reporting faults.

Could someone look at the time on ccgi04 please - it's an hour out!

Edit: You can check by going to http://ccgi.elvin.plus.com/misc/whichccgi.php keep refreshing and eventually you'll get each of the servers.


try not to contradict yourself too much jelv m8, if its "so bad" to report a fault to the forum, why do it yourself? - Forums i find Are better, as they rule out single issues that the person might be having, Or if its a PN or vISP fault.

-----------
=)
jelv1

Posts: 1967


« Reply #9 on: May 21, 2007, 05:04:47 pm »

try not to contradict yourself too much jelv m8, if its "so bad" to report a fault to the forum, why do it yourself?

Where?

If you are referring to this topic, I didn't raise a ticket because I hoped the OP had done so in the correct manner - thus avoiding an duplication of tickets. When it looked like he hadn't I raised one myself and the problem was quickly resolved.

Forums i find Are better, as they rule out single issues that the person might be having, Or if its a PN or vISP fault.

I quite agree - if you are not sure if it is a fault, or if it is a fault with your connection/account only. But the time being wrong is pretty blatantly a fault. The OP's first post was fine, maybe someone else had picked this up. When he made his second post, perhaps he should have asked himself if it had been properly reported and then did as I did.

jelv
phugoid

Posts: 18

WWW
« Reply #10 on: May 21, 2007, 06:14:36 pm »

I noticed that the CGI clocks had first diverged slightly before 9:01:24 on Sunday - it didn’t seem particularly important at the time, and I didn’t think it merited a formal fault report, so the next day I posted an observation on the forum. Oddly, it had attracted no replies by lunchtime on the following day so I considered making a fault report, but as the thread was already there it seemed far less confusing to just bump it. Luckily, jelv1 was at hand to sort out the mess. 
« Last Edit: May 21, 2007, 06:16:41 pm by phugoid »
Pages: [1]
  Print  
 
Jump to: