[Owncloud] Buggered the update to 6.0.0a; password is wrong?

[~Stack~]

Greetings,

I was running 5.0.13 and life was good. I have a test VM that is
"similar" to my setup also running 5.0.13. I updated my test vm to
6.0.0a and everything seemed to go smoothly. Of course my test vm has a
single user and isn't really used at all.

I figured, alright time to update my Owncloud server! Well, it didn't go
so smoothly.

I am running Debian 6.0.8 Squeeze fully updated with Apache, Php5,  and
SQLite.

Here is what I did. I skimmed the installation guides, not a whole lot
different then the instructions that have been posted before, but there
were a few packages the install guides suggested that I needed so I
played along.

  520  cd /var/www/
  521  apt-get install apache2 php5 php5-gd php-xml-parser php5-intl
  522  apt-get install php5-sqlite php5-mysql smbclient curl libcurl3
php5-curl
  523  vim /etc/apache2/sites-enabled/000-default
  524  a2enmod rewrite
  525  a2enmod headers
  526  /etc/init.d/apache2 restart
  527  ls
  528  rm owncloud # Note this was a symlink to the old installation
  529  mkdir owncloud-6.0.0a
  530  ln -s owncloud-6.0.0a owncloud
  531  tar -jxvf owncloud-6.0.0a.tar.bz2
  532  cp owncloud-5.0.13/config/config.php owncloud/config/config.php
  533  chown -R www-data:www-data owncloud/config/config.php
  534  cd owncloud
  535  ln -s /home/owncloud_data/ data

So basically, I have a "fresh" install + config.php + symlink to my data
directory. All is good right? I fire up my owncloud installation and it
tells me it is in maintenance mode. Horray! It leaves maintenance mode
and I am at the login screen! Horray!

I log in with my admin account. Failed password. Huh? I try again. Nope.

I try again with my user account. Still won't let me in. What?

I try with a user whose password I know. Still no go.

Just for grins I try the client. Failed "405 Method Not Allowed"
whatever that means.

Errr....OK. Whatever. This is why I symlink the install directories.
Afterall, this isn't the first time I have had to roll back an update.
So I reset the symlink.

I still can't log in. Uh oh.

Then it dawns on me. I missed a step. I didn't backup the database
before hand...GAH! Ok. No worries. We use owncloud a LOT but there are
only a handful of users on the server. I can recreate them so long as
the data is still there....

So lets take a look at the logs and figure this out. Well under the
5.0.13 binaries I am getting this message:
{"app":"PHP","message":"SQLSTATE[HY000]: General error: 1 no such table:
oc_queuedtasks at
\/var\/www\/owncloud-5.0.13\/lib\/db.php#391","level":4,"time":"2013-12-29T20:22:24+00:00"}

Hrm. Ok. The database has been updated and changed (not really a
surprise). So maybe I can't go back to 5.0.13. Lets try going forward
and fixing 6.0.0a.

{"app":"core","message":"Login failed: user 'i.am.stack' , wrong
password, IP:set log_authfailip=true in
conf","level":2,"time":"2013-12-29T20:44:02+00:00"}

Huh. Well at least it seems the user is there (and hopefully the data!),
but the password seems to have gone missing/bad.

Suggestions on how to reset/fix it?

Thanks!
~Stack~

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 259 bytes
Desc: OpenPGP digital signature
URL: <http://mail.kde.org/pipermail/owncloud/attachments/20131229/4ddc6319/attachment.sig>