Drupal not upgrading

Okay. I cannot get more tired than this. In the last three days I just worked on this problem.

All my backups are corrupted. I cannot get a dump of this version running currently because the dump corrupts the database. I cannot upgrade.

It’s fucked. I cannot do nothing, I passed an insane amount of hours on all this and the result is just my site completely broken and unrecoverable.

Thank you.

If you want to have an idea about what’s wrong look here. It’s a freshly installed version of drupal with the database set to utf8. As you can see it’s all completely broken, I even added a dump of the db.

I have no clue if it’s Drupal to be fucked up, or Dreamhost or mysql. I just know that I’m wasting my time in an unprecedented way.

Please shoot me in the head.

Before going to sleep:
mysqldump -uuser -ppass -h hostname dbname –default-character-set=latin1 | perl -pe ‘s/\),\(/),\n(/og’ | gzip > dumpforthewin.gz

mysql -uuser -ppass -h hostname dbname < dumpforthewin.sql The perl part is to have break lines in the database to have it readable, since I need to mess with it manually. Goodnight.

Posted in: Uncategorized | Tagged:

2 thoughts on “Drupal not upgrading

  1. I had a SimpleMachines forum up and running until my server was under DDOS attack. Unfortunately, after that the partition table was corrupted and it seems that there is no hope to restore.

    Before that incident, I have backed up my database throught DirectAdmin interface that I think it use mysqldump as usual.

    After restoring the database, the forum is up and running again but some of character (utf8) is not displayed correctly like before the incident.

    I know that all of the data of my forum is stored in latin1-based table but almost my data is utf8 encoded. I read somewhere and learn that in the database that single utf8 character is encoded as three latin1 characters

    By exploring the database backup file (which is a zipped file, gz format, that contains a text file without file extention), the text file is encoded in utf8. I learn that by opening it in Editplus and use Save As. Of cource, I do not save it in that manner. I use that option to find out what it is encoded.

    I guess that as I dump the database, mysqldump set charset default to utf8. This means that he believes my database data is ALREADY in utf8 so it dumps in a utf8 file. It is my guess only.

    Therefore, I can not import my backup as usual to make the utf8 data displayed correctly.

    How can I resolve that problem? How can I import a utf-8 file that contains latin1 characters encoded incorrectly as utf8 ones to make my forum work as previous times.

    I use MySQL 4.1
    DirectAdmin, instead of CPanel
    SimpleMachines 1.1RC1

    SHOW VARIABLES on phpMyAdmin

    character_set_client utf8
    character_set_connection utf8
    character_set_database latin1
    character_set_results utf8
    character_set_server latin1
    character_set_system utf8
    character_sets_dir /usr/share/mysql/charsets/
    collation_connection utf8_general_ci
    collation_database latin1_swedish_ci
    collation_server latin1_swedish_ci

    Thanks a lot


Leave a Reply