OJS OCS OMP OHS

You are viewing the PKP Support Forum | PKP Home Wiki



Unable to upgrade

Are you responsible for making OJS work -- installing, upgrading, migrating or troubleshooting? Do you think you've found a bug? Post in this forum.

Moderators: jmacgreg, btbell, michael, bdgregg, barbarah, asmecher

Forum rules
What to do if you have a technical problem with OJS:

1. Search the forum. You can do this from the Advanced Search Page or from our Google Custom Search, which will search the entire PKP site. If you are encountering an error, we especially recommend searching the forum for said error.

2. Check the FAQ to see if your question or error has already been resolved.

3. Post a question, but please, only after trying the above two solutions. If it's a workflow or usability question you should probably post to the OJS Editorial Support and Discussion subforum; if you have a development question, try the OJS Development subforum.

Re: Unable to upgrade

Postby asmecher » Wed Jan 09, 2008 9:28 am

Hi bernardforgues,

It's possible that some part of the first upgrade attempt is still causing trouble. Reload your database from backup, make sure your MySQL server is running, double-check that "Installed" is set to "Off" in your config.inc.php, and try again.

Regards,
Alec Smecher
Public Knowledge Project Team
asmecher
 
Posts: 9099
Joined: Wed Aug 10, 2005 12:56 pm

Re: Unable to upgrade

Postby bernardforgues » Wed Jan 09, 2008 9:34 am

Mmm,
That's exactly what I did before sending the previous post.
Let me try again: I'll be back in a couple of minutes.
Thanks again,
Bernard
bernardforgues
 
Posts: 13
Joined: Wed Mar 14, 2007 6:27 am
Location: France

Re: Unable to upgrade

Postby bernardforgues » Wed Jan 09, 2008 9:43 am

OK, that's what I feared...
I went back, dropped the 58 tables in my database, imported the backup and ended up with 58 tables again.
I cehcked that the config file was still with install=off and debug=on, then went to the website, clicked on upgrade, then "upgrade Open Journal Systems", and I got got the same error:
Errors occurred during installation:
* A database error has occurred: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
Any idea?
Thanks in advance,
Bernard
bernardforgues
 
Posts: 13
Joined: Wed Mar 14, 2007 6:27 am
Location: France

Re: Unable to upgrade

Postby asmecher » Wed Jan 09, 2008 10:12 am

Hi Bernard,

Are you sure that your MySQL server is running on a local UNIX domain socket? Try connecting manually by running the following from the command line:
Code: Select all
mysql -u mysql_username_here -p mysql_database_name_here
Regards,
Alec Smecher
Public Knowledge Project Team
asmecher
 
Posts: 9099
Joined: Wed Aug 10, 2005 12:56 pm

Re: Unable to upgrade

Postby bernardforgues » Thu Jan 10, 2008 7:00 am

Hi Alec,

I'm not so sure I understand your sentence 100%, but I suspect it is indeed running. Actually, I have tried to reinstall a previous version, and it (sort of works). More precisely, it works, although the interface is really ugly. But as far as the MySQL server is concerned, it proves it works anyway, I think.
As for your asking to run a command, unfortunately I don't have a CLI...

I have been thinking maybe I should use another route: install a fresh version from scratch and then copy the old database into the new one.
Is this reasonable?
If so, is there a document somewhere explaining the correspondence between the old and new databases?

Thanks again, and sorry for taking up your time.

Bernard
bernardforgues
 
Posts: 13
Joined: Wed Mar 14, 2007 6:27 am
Location: France

Re: Unable to upgrade

Postby asmecher » Thu Jan 10, 2008 9:34 am

Hi Bernard,

Hmm -- would you be willing to give me access to investigate personally? Please PM me.

Regards,
Alec Smecher
Public Knowledge Project Team
asmecher
 
Posts: 9099
Joined: Wed Aug 10, 2005 12:56 pm

Re: Unable to upgrade

Postby asmecher » Fri Jan 11, 2008 1:28 pm

Hi all,

FYI, the base problem appears to have been caused by duplicate entries in the public_issue_id column of the issues table, for which values where blank but not null. This can be worked around by running the following query prior to upgrading:
Code: Select all
UPDATE issues SET public_issue_id = NULL WHERE public_issue_id = '';
The relevant bugzilla entry is at http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=3219.

Regards,
Alec Smecher
Public Knowledge Project Team
asmecher
 
Posts: 9099
Joined: Wed Aug 10, 2005 12:56 pm

Previous

Return to OJS Technical Support

Who is online

Users browsing this forum: Bing [Bot] and 5 guests