Maintenance Notice

  • Thread starter Thread starter JLBowler
  • 623 comments
  • 51,737 views
SpeedyishOlly
And looping bug.. and I still have trouble with sounds but I doubt they'll ever fix that properly.

Sucks people are still having that problem.


They may never fix some of it.

For example they never fixed that glitch with the acura/Honda DN-X concept.

The one where on a wheel with a clutch and H-Pattern when you let the car die and hit the gas. Your screen goes black your wheel turns full lock to the left.

And on everyone else's screen you lag and fly into the wall and disappear hahaha.

It is funny to mess with people with that glitch though
 
:lol: No California and a GTO :D. But it's a strange world.:crazy:


On topic: It just be the PP fix people think is coming? I have not noticed anything yet myself.
 
Server maintenance ≠ update.

I'm aware of that. I just meant that we usually get a rundown of what's happened after every maintenance session.

Question ≠ Wishful thinking. :)
 
Have there been a lot of maintenances without an update?

Yes.

I would like i if they told us whats happening BEFORE the maintenance has finished.

Why? They are probably doing usual server maintenance this time (or preparing something for something, whatever). Whatever they are doing, it is necessary because of something related to network. What would we have from information what are they fixing/updating? And why on earth would they share that information outside of the company before they think they should?
 
Why? They are probably doing usual server maintenance this time (or preparing something for something, whatever). Whatever they are doing, it is necessary because of something related to network. What would we have from information what are they fixing/updating? And why on earth would they share that information outside of the company before they think they should?

Excatly, haha. :sly:
 
Why? They are probably doing usual server maintenance this time (or preparing something for something, whatever). Whatever they are doing, it is necessary because of something related to network. What would we have from information what are they fixing/updating? And why on earth would they share that information outside of the company before they think they should?

I'm saying that they should release a statement saying if it is server maintenance, update or what have you, they don't need to release everything, I'd just like some generalities, something to lead me one way or another.
 
Sucks people are still having that problem.

They may never fix some of it.

For example they never fixed that glitch with the acura/Honda DN-X concept.

The one where on a wheel with a clutch and H-Pattern when you let the car die and hit the gas. Your screen goes black your wheel turns full lock to the left.

And on everyone else's screen you lag and fly into the wall and disappear hahaha.

It is funny to mess with people with that glitch though

Does that glitch work offline & online, or only online ? I've never heard of it.
 
I'm saying that they should release a statement saying if it is server maintenance, update or what have you, they don't need to release everything, I'd just like some generalities, something to lead me one way or another.

They already told you it's maintenance, what more do you want? It's not their fault people make assumptions. They said maintenance, it was maintenance.
 
They already told you it's maintenance, what more do you want? It's not their fault people make assumptions. They said maintenance, it was maintenance.
It's the sole fact that maintenance can mean anything, I'd like it a bit more specific.

My biggest problem is when I use the DFGT, sometimes the pointer randomly jams itself to the right, it's not unbearable, just irritating. Also we need a "Buy All" button.
 
They already told you it's maintenance, what more do you want? It's not their fault people make assumptions. They said maintenance, it was maintenance.

But what if there is an update tomorrow? Nice suprise I suppose, I have no problem not knowing what they're doing to be honest, as long as they're doing something :)
 
It's the sole fact that maintenance can mean anything, I'd like it a bit more specific.

Maintenance to me means they will go into the server side of things, make sure everything is running 100% and there are no issues. If so, they'll take that time to fix said issues. Nobody should expect anything.
 
Maintenance to me means they will go into the server side of things, make sure everything is running 100% and there are no issues. If so, they'll take that time to fix said issues. Nobody should expect anything.

But they've been so vague in calling everything "Maintenance" I do not know what to expect anymore.
 
TrdScionxB2
Does that glitch work offline & online, or only online ? I've never heard of it.

Everywhere. Both online and offline. But you have to have a Logitech G25/G27 or Thrustmaster or Fanatec wheels with a clutch and H-Pattern shifter
 
But they've been so vague in calling everything "Maintenance" I do not know what to expect anymore.

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
 
That cleared that up then! If you scroll up and down quick, it's like the opening scene from The Matrix.
 
Thank you...I appreciate it...except I only know very basic coding. Most of it was total mind:censored:

But seriously...that cannot be real. PD would publish anything like that. Besides is its the 14th, how could they predict the error.
 
Back