Error message after restore

[Timbalu]

Thinking about the wild way, I would recommend doing the database thing first!
In these days trying to upgrade there might have been a process writing the serendipity root
file path into the serendipity_config database table with a value like /kunden/187871_90762/webseiten/serendipity/uploads/serendipity and so on.

If you know about an online database tool like PhpMyAdmin - which is recommended to have when using web accessible databases - we can check this easily.

[Timbalu]

Margret, I can imagine you are pestered by this damn upgrade process, but following your improvements via web...., I can see you are stuck now, since you have this

Code: Select all

Warning: mysql_query() [function.mysql-query]: Unable to save result set in /kunden/187871_90762/webseiten/serendipity/include/db/mysql.inc.php on line 84

Warning: mysql_query() [function.mysql-query]: Unable to save result set in /kunden/187871_90762/webseiten/serendipity/include/db/mysql.inc.php on line 84
Query failed:

Got error 127 from storage engine

error.

This means you should update the MySql Server too to something >= 5.0.xx.

Error 127 is a table based error and bug in some old mysql versions with very large database tables.

I dont know why you might have one of these, but it is recommendet to run a mysql command:

Code: Select all

repair Tables `yourTableName`

which might help, but the better way should be a mysql server upgrade to get around this limitation error.

First thing to do, is to control database access and corrupt files via PhpMyAdmin.

[Zirbelholz]

Thanks very much for all this, Ian. I have no doubt at all that the serendipity directory you named is where the weblog originally was, nor that I cannot see whatever other uploads must have occurred since then. I just have no overview of exactly what has gone wrong. And that I needed to update MySQL was new to me.

At all events, I have to do something else now! Will report back.

Margaret

[Timbalu]

I expect this is a very strange behaviour.

Updating the MySql server is recommended in some google search results when having this 127 error.
Thats why I came up with that. You might want to speak to domainfactory about this.

What is suspect, is your lang files don't speak and you only get the smarty constants in the login panel.
There may be some more unusual behaviour in the serendipity database config table.

When you find time again, please inspect the serendipity_config_local.inc.php file to have the right mysql connect data, then go to the phpmyadmin tool which is located in https://ihre-domain.tld/sqladmin and open the serendipity_config mysql table to see what kind of path settings are set there.

Then we will see how to proceed.

[Timbalu]

Maybe there are still some serendipity upload issues around, since you additionally have a

Code: Select all

Fatal error: Call to undefined function serendipity_mb() in /xxxx/serendipity/include/functions_comments.inc.php on line 326

when calling one of your old entries like
/index.php?/archives/3265-Unmistakeably-GermanUnverkennbar-Deutsch.html

Following this thread
http://board.s9y.org/viewtopic.php?f=1&t=11984&start=0
it means the lang directory with all needed items is (partially) missing or, as already said, the serendipity_config database table is missing the right path settings somewhere.

(And, as I am unsure about this ftp tool your are using, you might try another one like Filezilla, which is well maintained and hook up everything again)

[garvinhicking]

Hi!

Ich habe Zirbelholz kurzfristig helfen können und mich eingeloggt - auch dank der Hilfe von Timbalu ging die Problemanalyse dann recht schnell. Dabei habe ich die Datenbank von MySQL 3.2.28 (!!!) auf MYSQL5 umgestellt. Im DOmainfactory-Interface habe ich dazu eine neue Datenbank angelegt mit MySQL5, dann habe ich die alte im ISO-8859-1-Format via phpMyAdmin exportiert und die Datei in der neuen Datenbank importiert (die Rohdaten lagen als UTF-8 vor, sonst wäre es doppelt kodiert worden). Danach konnte ich den neuen Datenbanknamen in der serendipity_config_local.inc.php eintragen. Dann noch das hier genannte fixlogin.php hochgeladen, Passwort eingetragen, aufgerufen - und der Login klappte.

Zirbelholz hatte also alles am Ende korrekt hochgeladen, es scheiterte dann "nur" noch am sehr alten MySQL 3.2.28, das mit den Datenmengen so nicht mehr zurecht kam,

(Upps, ich habs jetzt auf Deutsch geschrieben und bin zu faul es zu übersetzen)

Grüße,
Garvin

[Zirbelholz]

Vielen Dank an Garvin.

Ich bin zwar Übersetzerin, aber das ist bekanntllich nicht meine Fachrichtung!

Garvin says: 'I was able to help Zirbelholz at short notice and logged into her account - with Timbalu's help, it didn't take long to analyse the problem. I updated the database from MySQL 3.2.28 (!!!) to MySQL5. In the domainfactory interface, I installed a new database in MySQL5, and then I used phpMyAdmin to export the old database in the format ISO 8859 1 and then imported the file into the new database (the raw data was in UTF-8, or else it would have been double coded). After that I entered the new database name in serendipity_config_local.inc.php. Then I uploaded the file fixlogin.php, discussed in this thread, and the login worked.

So Zirbelholz had actually uploaded everything correclty (hooray!), and the only reason it failed was because of the antique version MySQL 3.2.28, which was unable to handle the amount of data.'

(I recall that when I tried to make some changes after importing the weblog from Movable Type, domainfactory wouldn't let me have access to the database after a first attempt, and I suppose the MySQL5 has fewer problems).

Many thanks to Garvin for that. Now I can do some work.

Margaret

[Timbalu]

UNFASSBAR, MySQL 3.2.28 (!!!) und das 2011 (!!!) Domainfactory, ick hör dir trapsen (!!!)
bitte übersetzen

Margret, he said "...am Ende ..." which means at the end of our progress finding different installations...

[Zirbelholz]

I translated 'am Ende' as 'actually' because that's the way I read it. You might prefer 'it turned out that Z. had uploaded everything correctly'.
As for 'Nachtigall, ick hör dir trapsen', I don't think there's any single way of translating that - the suggestion 'I know which way the wind's blowing' doesn't work here. Possibly you mean 'domainfactory, I can see you have a crappy site'?

Margaret

[Timbalu]

I translated 'am Ende' as 'actually' because that's the way I read it. You might prefer 'it turned out that Z. had uploaded everything correctly'.

Did she? "at the end" is describing the progress from first error with double serendipity folders to the simple upgrade with the mysql error. But I am not argueing here, I just wanted to "give my senf" to it! (being happy you solved you issues last night)

As for 'Nachtigall, ick hör dir trapsen', I don't think there's any single way of translating that - the suggestion 'I know which way the wind's blowing' doesn't work here. Possibly you mean 'domainfactory, I can see you have a crappy site'?

More something in this direction, I presume. " Suggestion, that the intention was noticed "

Nachtrag: Was dem Amerikaner sin Mockingbird is dem Europäer sin Nachtigall („Was dem einen sin Uhl, ist dem andern sin Nachtigall“), beide singen sehr schön.