Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > ISPConfig 3 > Installation/Configuration

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Reply
 
Thread Tools Display Modes
  #1  
Old 4th June 2009, 03:24
wxman wxman is offline
Senior Member
 
Join Date: May 2007
Posts: 189
Thanks: 11
Thanked 2 Times in 2 Posts
Default Log error after 3.0.1.3 update

The update went fine on one of my servers, but shows an err in the monitor. The ISPConfig Log has:
Code:
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.
Reply With Quote
Sponsored Links
  #2  
Old 4th June 2009, 08:11
till till is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 35,964
Thanks: 825
Thanked 5,366 Times in 4,213 Posts
Default

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.
__________________
Till Brehm
--
Get ISPConfig support and the ISPConfig 3 manual from ispconfig.org.
Reply With Quote
  #3  
Old 4th June 2009, 16:30
wxman wxman is offline
Senior Member
 
Join Date: May 2007
Posts: 189
Thanks: 11
Thanked 2 Times in 2 Posts
Default

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.

Last edited by wxman; 4th June 2009 at 17:42.
Reply With Quote
  #4  
Old 5th June 2009, 11:40
till till is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 35,964
Thanks: 825
Thanked 5,366 Times in 4,213 Posts
Default

This has nothing to do with a ispconfig update. Basically you can not create a database adain that exists already.
__________________
Till Brehm
--
Get ISPConfig support and the ISPConfig 3 manual from ispconfig.org.
Reply With Quote
  #5  
Old 5th June 2009, 13:37
wxman wxman is offline
Senior Member
 
Join Date: May 2007
Posts: 189
Thanks: 11
Thanked 2 Times in 2 Posts
Default

Quote:
Originally Posted by till View Post
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.
Reply With Quote
  #6  
Old 5th June 2009, 14:06
till till is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 35,964
Thanks: 825
Thanked 5,366 Times in 4,213 Posts
Default

Which commands exactly did you execute as you updated?
__________________
Till Brehm
--
Get ISPConfig support and the ISPConfig 3 manual from ispconfig.org.
Reply With Quote
  #7  
Old 5th June 2009, 14:51
wxman wxman is offline
Senior Member
 
Join Date: May 2007
Posts: 189
Thanks: 11
Thanked 2 Times in 2 Posts
Default

From root I did "ispconfig_update.sh".
I've really messed things up now. My two servers are replicated/mirrored, and when I removed the DB on web1 it of course removed it on web2.
Reply With Quote
  #8  
Old 5th June 2009, 15:47
wxman wxman is offline
Senior Member
 
Join Date: May 2007
Posts: 189
Thanks: 11
Thanked 2 Times in 2 Posts
Default

It does seem that this was all because of DB replication. I guess I needed to shut off replication completely before I did any upgrade. Because I didn't, the upgrade of one got stuck in the DB logs so it kept trying to do the same on the other slave. The two databases just kept trying to sync each other, which kept messing them up. What I ended up doing was shut off the slaves, fixed the databases from back up, the completely redid the master/master replication setup so the all at the same point again. I won't make that mistake next time.
Reply With Quote
  #9  
Old 5th June 2009, 16:13
till till is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 35,964
Thanks: 825
Thanked 5,366 Times in 4,213 Posts
Default

Ok, this means you use mysql replication? This is not compatible with ispconfig 3, no wonder that the update failed. ISPConfig uses its own replication.
__________________
Till Brehm
--
Get ISPConfig support and the ISPConfig 3 manual from ispconfig.org.
Reply With Quote
  #10  
Old 6th June 2009, 01:48
wxman wxman is offline
Senior Member
 
Join Date: May 2007
Posts: 189
Thanks: 11
Thanked 2 Times in 2 Posts
 
Default

OK now I'm really confused. I asked that when I first started this project, but it sounded like because I was running this as a load balancer/fail over system, the built in replication wouldn't work.

I need both servers to be exactly the same in case of fail over to the second server. I even tried installing ISPC on the second server as a slave, but it didn't seem to work. Am I wrong, and I should reinstall it? If that's true, how should it be done?
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
The system is currently updating the configuration files. warlock General 8 21st February 2009 18:15
slow download through webserver problem snewp Technical 14 9th May 2008 05:25
Outlook does not Authenticates aberrio Server Operation 30 1st November 2007 19:21
No ftp login for ispconfig-webuser agri Installation/Configuration 12 19th March 2007 10:06
HotSaNIC domino Tips/Tricks/Mods 23 6th November 2006 05:19


All times are GMT +2. The time now is 05:43.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.