Log error after 3.0.1.3 update

[wxman]

The update went fine on one of my servers, but shows an err in the monitor. The ISPConfig Log has:

Unable to connect to the database Can't create database 'c2list'; database exists

c2list is one of the databases I had before the update, and I didn't change any permissions. I can't honestly say the error wasn't there before the update because I didn't check just before running it. I know it wasn't there a short time ago though.

[till]

The error just means that the database could not be created because it existed already. Just click on the delete button in the error lost to remove it as it will block the config queue otherwise.

[wxman]

Thanks Till that looks better now. After I removed it it showed up again though. I tried backing it up, and removing it. ISPC made a new one so I thought it would be happy now, but it keeps generating tha same error.
This was my first upgrade after moving to version 3.

[till]

This has nothing to do with a ispconfig update. Basically you can not create a database adain that exists already.

[wxman]

Originally Posted by till

This has nothing to do with a ispconfig update. Basically you can not create a database adain that exists already.

So how do I stop the error. It keeps coming back even if I delete the database. I don't see how we can ever upgrade again if it won't like the databases that are already there.

[till]

Which commands exactly did you execute as you updated?