Maintenance Notice

  • Thread starter Thread starter JLBowler
  • 623 comments
  • 51,737 views
Well, I really hope that Sony and PD are preparing some good stuff and I hope this happens at the Sony Official Metting Show this Feb. 20. If not, PD will just get me so dawn angry with another upgrade with Chinese and Japanese cars in an different look from the others 100 that already exist in game.

But I'm sure that PD will not do it again.

Alright? :)
 
TrdScionxB2
It's fun lol & I also found some hacked civics. & If anybody is upset for me being off topic. Sorry

I got it to come back a few times then randomly disappear again. That really bleeding my friend's minds
 
I got it to come back a few times then randomly disappear again. That really bleeding my friend's minds

I've found out about the glitch. In a race, it says after you do it you need a oil change, your battery is drained, but the car is still taking from it (might not be a glitch), the wheels disappear, but sometimes come back, the car can make a weird noise sometimes, the car has a higher top speed before the glitch, before, under 190, after, over 205, some views work after the glitch, some don't, the driver & the camera in the car is messed up, & the G bar is messed up too.
 
TrdScionxB2
I've found out about the glitch. In a race, it says after you do it you need a oil change, your battery is drained, but the car is still taking from it (might not be a glitch), the wheels disappear, but sometimes come back, the car can make a weird noise sometimes, the car has a higher top speed before the glitch, before, under 190, after, over 205, some views work after the glitch, some don't, the driver & the camera in the car is messed up, & the G bar is messed up too.

Oh wow didn't know all of that. I have noticed the wheels disappearing in a replay before. And the HUD displays were all messed up
 
Here it is for you mate, just to be at peace ;)

Gran Turismo 5 Server Maintenance Report 14-02-2013

Tue Feb 14 13:54:10 2013: test1:check:INFO: The quick backup-type is supported only for snapshot backups. Setting backup-type to 'regular'
Tue Feb 14 13:54:10 2013: test1:check:INFO: Mail address: server1213@gran-turismo.com is ok
Tue Feb 14 13:54:10 2013: test1:check:INFO: Getting mysql variables
Tue Feb 14 13:54:10 2013: test1:check:INFO: "/usr/bin"/mysqladmin --user="backupuser" --password="*****" --host="xxx.xxx.xxx.xxx" --port="3306" variables
Tue Feb 14 13:54:10 2013: test1:check:INFO: datadir is /usr/local/mysql/data/
Tue Feb 14 13:54:10 2013: test1:check:INFO: mysql_version is 4.1.18-standard-log
Tue Feb 14 13:54:10 2013: test1:check:INFO: InnoDB data file are /usr/local/mysql/data/ibdata1
Tue Feb 14 13:54:10 2013: test1:check:INFO: InnoDB log dir is /usr/local/mysql/data/.
Tue Feb 14 13:54:10 2013: test1:check:INFO: License check successful
Tue Feb 14 13:54:10 2013: test1:check:INFO: Configuration check successful
Tue Feb 14 13:54:14 2013: test1:backup:INFO: START OF BACKUP
Tue Feb 14 13:54:14 2013: test1:backup:INFO: PHASE START: Initialization
Tue Feb 14 13:54:14 2013: test1:backup:INFO: The quick backup-type is supported only for snapshot backups. Setting backup-type to 'regular'
Tue Feb 14 13:54:14 2013: test1:backup:INFO: Mail address: server1213@gran-turismo.com is ok
Tue Feb 14 13:54:14 2013: test1:backup:INFO: ZRM Temporary configuration file = /etc/mysql-zrm/test1/tmp8djpt.conf
Tue Feb 14 13:54:14 2013: test1:backup:INFO: {
Tue Feb 14 13:54:14 2013: test1:backup:INFO: quiet=0
Tue Feb 14 13:54:14 2013: test1:backup:INFO: retention-policy=7D
Tue Feb 14 13:54:14 2013: test1:backup:INFO: verbose=1
Tue Feb 14 13:54:14 2013: test1:backup:INFO: backup-level=0
Tue Feb 14 13:54:14 2013: test1:backup:INFO: mysql-binpath=/usr/bin
Tue Feb 14 13:54:14 2013: test1:backup:INFO: mailto=server1214@gran-turismo.com
Tue Feb 14 13:54:14 2013: test1:backup:INFO: databases=123.12
Tue Feb 14 13:54:14 2013: test1:backup:INFO: port=3306
Tue Feb 14 13:54:14 2013: test1:backup:INFO: remote-mysql-binpath=/usr/local/mysql/bin
Tue Feb 14 13:54:14 2013: test1:backup:INFO: host=192.200.200.147
Tue Feb 14 13:54:14 2013: test1:backup:INFO: backup-mode=logical
Tue Feb 14 13:54:14 2013: test1:backup:INFO: password=******
Tue Feb 14 13:54:14 2013: test1:backup:INFO: backup-type=regular
Tue Feb 14 13:54:14 2013: test1:backup:INFO: user=backupuser
Tue Feb 14 13:54:14 2013: test1:backup:INFO: compress=
Tue Feb 14 13:54:14 2013: test1:backup:INFO: mysql-binlog-path=/urs/local/mysql/data
Tue Feb 14 13:54:14 2013: test1:backup:INFO: copy-plugin=/usr/share/mysql-zrm/plugins/ssh-copy.pl
Tue Feb 14 13:54:14 2013: test1:backup:INFO: }
Tue Feb 14 13:54:14 2013: test1:backup:INFO: Getting mysql variables
Tue Feb 14 13:54:14 2013: test1:backup:INFO: "/usr/bin"/mysqladmin --user="backupuser" --password="*****" --host="xxx.xxx.xxx.xxx" --port="3306" variables
Tue Feb 14 13:54:14 2013: test1:backup:INFO: datadir is /usr/local/mysql/data/
Tue Feb 14 13:54:14 2013: test1:backup:INFO: mysql_version is 4.1.18-standard-log
Tue Feb 14 13:54:14 2013: test1:backup:INFO: InnoDB data file are /usr/local/mysql/data/ibdata1
Tue Feb 14 13:54:14 2013: test1:backup:INFO: InnoDB log dir is /usr/local/mysql/data/.
Tue Feb 14 13:54:14 2013: test1:backup:INFO: License check successful
Tue Feb 14 13:54:14 2013: test1:backup:INFO: backup set being used is test1
Tue Feb 14 13:54:15 2013: test1:backup:INFO: backup-set=test1
Tue Feb 14 13:54:15 2013: test1:backup:INFO: backup-date=20130614135414
Tue Feb 14 13:54:15 2013: test1:backup:INFO: mysql-server-os=Linux/Unix
Tue Feb 14 13:54:15 2013: test1:backup:INFO: backup-type=regular
Tue Feb 14 13:54:15 2013: test1:backup:INFO: host=192.200.200.147
Tue Feb 14 13:54:15 2013: test1:backup:INFO: backup-date-epoch=1413700054
Tue Feb 14 13:54:15 2013: test1:backup:INFO: retention-policy=7D
Tue Feb 14 13:54:15 2013: test1:backup:INFO: mysql-zrm-version=ZRM for MySQL Enterprise Edition - version 2.2
Tue Feb 14 13:54:15 2013: test1:backup:INFO: mysql-version=4.1.18-standard-log
Tue Feb 14 13:54:15 2013: test1:backup:INFO: backup-directory=/var/lib/mysql-zrm/test1/20130614135414
Tue Feb 14 13:54:15 2013: test1:backup:INFO: backup-level=0
Tue Feb 14 13:54:15 2013: test1:backup:INFO: backup-mode=logical
Tue Feb 14 13:54:15 2013: test1:backup:INFO: PHASE END: Initialization
Tue Feb 14 13:54:15 2013: test1:backup:INFO: PHASE START: Running pre backup plugin
Tue Feb 14 13:54:15 2013: test1:backup:INFO: Executing pre-backup-plugin
Tue Feb 14 13:54:15 2013: test1:backup:INFO: PHASE END: Running pre backup plugin
Tue Feb 14 13:54:15 2013: test1:backup:INFO: PHASE START: Flushing logs
Tue Feb 14 13:54:15 2013: test1:backup:INFO: Flushing the logs
Tue Feb 14 13:54:15 2013: test1:backup:INFO: "/usr/bin"/mysqladmin --user="backupuser" --password="*****" --host="192.200.200.147" --port="3306" flush-logs
Tue Feb 14 13:54:15 2013: test1:backup:ERROR: Flush of logs failed
Tue Feb 14 13:54:15 2013: test1:backup:INFO: PHASE START: Cleanup
Tue Feb 14 13:54:15 2013: test1:backup:INFO: backup-status=Backup failed
Tue Feb 14 13:54:15 2013: test1:backup:INFO: Backup failed
Tue Feb 14 13:54:15 2013: test1:backup:INFO: mailing file /tmp/TQJ7Rlh5Tc
Tue Feb 14 13:54:15 2013: test1:backup:INFO: mail command is cat "/tmp/TQJ7Rlh5Tc"|mail -s "[ZRM for MySQL Report] ERROR during backup of backup-set test1" server1213@gran-turismo.com
Tue Feb 14 13:54:15 2013: test1:backup:INFO: PHASE END: Cleanup
Tue Feb 14 13:54:15 2013: test1:backup:INFO: END OF BACKUP


Hahaha.jpg



Jerome
 
Why did anybody even expect anything? Can PD not just perform maintenance anymore without everybody expecting something?
Why? Because PD has a history of scheduling maintenance which includes an unannounced update. Didn't the last "maintenance" included update 2.10?

PD should be up front and honest about their scheduled maintenance. If it includes a small update that only contains bugfixes then announce it as so. If it is a big update announce it announce it as a major update. And for goodness sake, please include a detailed change log if there is an update... Oh, one more thing. PD, please test the updates before releasing them to your paying customers 👍.

P.S. I also noticed the short password. Now which button makes the star :D.
 
Here it is for you mate, just to be at peace ;)

Gran Turismo 5 Server Maintenance Report 14-02-2013

Tue Feb 14 13:54:10 2013: test1:check:INFO: The quick backup-type is supported only for snapshot backups. Setting backup-type to 'regular'
Tue Feb 14 13:54:10 2013: test1:check:INFO: Mail address: server1213@gran-turismo.com is ok
Tue Feb 14 13:54:10 2013: test1:check:INFO: Getting mysql variables
Tue Feb 14 13:54:10 2013: test1:check:INFO: "/usr/bin"/mysqladmin --user="backupuser" --password="*****" --host="xxx.xxx.xxx.xxx" --port="3306" variables
Tue Feb 14 13:54:10 2013: test1:check:INFO: datadir is /usr/local/mysql/data/
Tue Feb 14 13:54:10 2013: test1:check:INFO: mysql_version is 4.1.18-standard-log
Tue Feb 14 13:54:10 2013: test1:check:INFO: InnoDB data file are /usr/local/mysql/data/ibdata1
Tue Feb 14 13:54:10 2013: test1:check:INFO: InnoDB log dir is /usr/local/mysql/data/.
Tue Feb 14 13:54:10 2013: test1:check:INFO: License check successful
Tue Feb 14 13:54:10 2013: test1:check:INFO: Configuration check successful
Tue Feb 14 13:54:14 2013: test1:backup:INFO: START OF BACKUP
Tue Feb 14 13:54:14 2013: test1:backup:INFO: PHASE START: Initialization
Tue Feb 14 13:54:14 2013: test1:backup:INFO: The quick backup-type is supported only for snapshot backups. Setting backup-type to 'regular'
Tue Feb 14 13:54:14 2013: test1:backup:INFO: Mail address: server1213@gran-turismo.com is ok
Tue Feb 14 13:54:14 2013: test1:backup:INFO: ZRM Temporary configuration file = /etc/mysql-zrm/test1/tmp8djpt.conf
Tue Feb 14 13:54:14 2013: test1:backup:INFO: {
Tue Feb 14 13:54:14 2013: test1:backup:INFO: quiet=0
Tue Feb 14 13:54:14 2013: test1:backup:INFO: retention-policy=7D
Tue Feb 14 13:54:14 2013: test1:backup:INFO: verbose=1
Tue Feb 14 13:54:14 2013: test1:backup:INFO: backup-level=0
Tue Feb 14 13:54:14 2013: test1:backup:INFO: mysql-binpath=/usr/bin
Tue Feb 14 13:54:14 2013: test1:backup:INFO: mailto=server1214@gran-turismo.com
Tue Feb 14 13:54:14 2013: test1:backup:INFO: databases=123.12
Tue Feb 14 13:54:14 2013: test1:backup:INFO: port=3306
Tue Feb 14 13:54:14 2013: test1:backup:INFO: remote-mysql-binpath=/usr/local/mysql/bin
Tue Feb 14 13:54:14 2013: test1:backup:INFO: host=192.200.200.147
Tue Feb 14 13:54:14 2013: test1:backup:INFO: backup-mode=logical
Tue Feb 14 13:54:14 2013: test1:backup:INFO: password=******
Tue Feb 14 13:54:14 2013: test1:backup:INFO: backup-type=regular
Tue Feb 14 13:54:14 2013: test1:backup:INFO: user=backupuser
Tue Feb 14 13:54:14 2013: test1:backup:INFO: compress=
Tue Feb 14 13:54:14 2013: test1:backup:INFO: mysql-binlog-path=/urs/local/mysql/data
Tue Feb 14 13:54:14 2013: test1:backup:INFO: copy-plugin=/usr/share/mysql-zrm/plugins/ssh-copy.pl
Tue Feb 14 13:54:14 2013: test1:backup:INFO: }
Tue Feb 14 13:54:14 2013: test1:backup:INFO: Getting mysql variables
Tue Feb 14 13:54:14 2013: test1:backup:INFO: "/usr/bin"/mysqladmin --user="backupuser" --password="*****" --host="xxx.xxx.xxx.xxx" --port="3306" variables
Tue Feb 14 13:54:14 2013: test1:backup:INFO: datadir is /usr/local/mysql/data/
Tue Feb 14 13:54:14 2013: test1:backup:INFO: mysql_version is 4.1.18-standard-log
Tue Feb 14 13:54:14 2013: test1:backup:INFO: InnoDB data file are /usr/local/mysql/data/ibdata1
Tue Feb 14 13:54:14 2013: test1:backup:INFO: InnoDB log dir is /usr/local/mysql/data/.
Tue Feb 14 13:54:14 2013: test1:backup:INFO: License check successful
Tue Feb 14 13:54:14 2013: test1:backup:INFO: backup set being used is test1
Tue Feb 14 13:54:15 2013: test1:backup:INFO: backup-set=test1
Tue Feb 14 13:54:15 2013: test1:backup:INFO: backup-date=20130614135414
Tue Feb 14 13:54:15 2013: test1:backup:INFO: mysql-server-os=Linux/Unix
Tue Feb 14 13:54:15 2013: test1:backup:INFO: backup-type=regular
Tue Feb 14 13:54:15 2013: test1:backup:INFO: host=192.200.200.147
Tue Feb 14 13:54:15 2013: test1:backup:INFO: backup-date-epoch=1413700054
Tue Feb 14 13:54:15 2013: test1:backup:INFO: retention-policy=7D
Tue Feb 14 13:54:15 2013: test1:backup:INFO: mysql-zrm-version=ZRM for MySQL Enterprise Edition - version 2.2
Tue Feb 14 13:54:15 2013: test1:backup:INFO: mysql-version=4.1.18-standard-log
Tue Feb 14 13:54:15 2013: test1:backup:INFO: backup-directory=/var/lib/mysql-zrm/test1/20130614135414
Tue Feb 14 13:54:15 2013: test1:backup:INFO: backup-level=0
Tue Feb 14 13:54:15 2013: test1:backup:INFO: backup-mode=logical
Tue Feb 14 13:54:15 2013: test1:backup:INFO: PHASE END: Initialization
Tue Feb 14 13:54:15 2013: test1:backup:INFO: PHASE START: Running pre backup plugin
Tue Feb 14 13:54:15 2013: test1:backup:INFO: Executing pre-backup-plugin
Tue Feb 14 13:54:15 2013: test1:backup:INFO: PHASE END: Running pre backup plugin
Tue Feb 14 13:54:15 2013: test1:backup:INFO: PHASE START: Flushing logs
Tue Feb 14 13:54:15 2013: test1:backup:INFO: Flushing the logs
Tue Feb 14 13:54:15 2013: test1:backup:INFO: "/usr/bin"/mysqladmin --user="backupuser" --password="*****" --host="192.200.200.147" --port="3306" flush-logs
Tue Feb 14 13:54:15 2013: test1:backup:ERROR: Flush of logs failed
Tue Feb 14 13:54:15 2013: test1:backup:INFO: PHASE START: Cleanup
Tue Feb 14 13:54:15 2013: test1:backup:INFO: backup-status=Backup failed
Tue Feb 14 13:54:15 2013: test1:backup:INFO: Backup failed
Tue Feb 14 13:54:15 2013: test1:backup:INFO: mailing file /tmp/TQJ7Rlh5Tc
Tue Feb 14 13:54:15 2013: test1:backup:INFO: mail command is cat "/tmp/TQJ7Rlh5Tc"|mail -s "[ZRM for MySQL Report] ERROR during backup of backup-set test1" server1213@gran-turismo.com
Tue Feb 14 13:54:15 2013: test1:backup:INFO: PHASE END: Cleanup
Tue Feb 14 13:54:15 2013: test1:backup:INFO: END OF BACKUP

SWEET!!!! We are getting all 2013 model of every manufactured automobile and motor vehicle, DTM, NASCAR, ALMS, Rolex, Le Mans, Ferrari Challenge, Porch-uh Cup, NHRA cars AND bikes, Paris to Dakkar Noir vehicles, hover craft, ALL race tracks used in and created for but not used in precious Gran Turismo games, and GTTV will feature a 24 hour feed of everyone PD employee fest with audio language translations!!!

Thank you so much Amar!!!!
 
Some server-maintenance must be going on at the moment...

Here in DK (Europe), I am getting booted out to GT Main menu, thrown out of on-line seasonals-menu with "network-errors". Also had "Error connecting to server" on startup of GT5.. And all loading of menu-screens is SO slow at the moment, like it is really having trouble communicating with the servers.

So even PD stated some well-defined hours for the maintenance, they seem to include the time between as well.. 👍

So what they really meant in their maintenance-notice must have been:
"We are starting maintenance from the 12th february around 18:00-21:00ish GMT until 14th february, 18:00-21:00ish GMT"
:crazy:
 
Yep..

Text from original maintenance notice:

----
GT5 INFORMATION
Maintenance Notice

Last Updated: Feb 08, 2013

The online service of Gran Turismo 5 will undergo maintenance during the following hours:

Start: 02/12/2013 11:00 EST
Finish: 02/12/2013 14:00 EST

Start: 02/14/2013 11:00 EST
Finish: 02/14/2013 14:00 EST

Please note that the online service may be unstable during the maintenance. Thank you in advance for your understanding.

*Please note that the exact time of the maintenance may slightly vary.
----

What we don't know, however, is if there HAS been done any maintenance in the first scheduled time-frame.. at least there hasn't been any report of server-downtime around it...
 
Oh wow didn't know all of that. I have noticed the wheels disappearing in a replay before. And the HUD displays were all messed up

Yea, I played around with it for a while. I wanted to try it on people online But it was a hacked civic room So I couldn't use the car
 
The second batch of maintenance is due to end in just under an hour. :dopey:

Then we can all enjoy the addition of.....;)
 
The second batch of maintenance is due to end in just under an hour. :dopey:

Then we can all enjoy the addition of.....;)

Its looking like nothing went on exactly like two days ago.
No interuption, no nothing once again. I'm starting to doubt anything will change.
As of now, 40 min. before estimated time expired, we gonna stay at current version.
Hope i'm wrong though.
 
Great :grumpy: I stopped the 24hrs of green hell on sunday when I faced the fact that I would not finish before tuesday's update!

Should of just stock with it!
 
...nothing.

Most likely. :lol:

Whilst it's easy to conjure up reasons why it'll be DLC/an Update etc. It's also just as easy to conjure up reasons why it'll be completely nothing.

I'm trying not to keep my hopes up.

25 minutes to go.....
 
Maybe I'm wrong? But generally we can't play through updates, we can maintenance.

I have not seen anything to lead us to believe, it's not just simple maintenance.
 
Back