Re: [MRBS-general] Fatal Error unfortunately the database is not available at the moment
Brought to you by:
jberanek
From: Peter G. <p.g...@bb...> - 2015-11-26 23:13:20
|
Hi Campbell, Thanks for the feedback. Yes overnight I restored back to a good copy. This still leaves the original issue I was trying to solve which is that when trying to add a monthly repeat booking for a Thursday in 2016 it would suggest Wednesday in the tick box instead. Changing it back to Thursday then caused MRBS to attempt to do a booking on a Friday, so the days are out of sync somehow. WRT the upgrade I believe I have identified the duplicate table names, so at a quiet time I will re-attempt the upgrade again. Thanks [cid:image002.png@01D128FC.2CC458F0]Peter Griffiths From: Campbell Morrison [mailto:cam...@gm...] Sent: Thursday, 26 November 2015 7:44 PM To: 'General purpose list (support/developers/users)' Subject: Re: [MRBS-general] Fatal Error unfortunately the database is not available at the moment It looks like the upgrade to 1.5 has failed during the upgrade of the database at the point where a unique key constraint is added to the room table. It looks like you've got two rooms called "Being Active Eating Well" in the same area. It shouldn't be possible in MRBS to get into this state in the first place and the unique constraint is just being added as a precaution. The only thing I can think of is that a room name was changed manually, eg through phpMyAdmin. Having restored 1.4 that is failing with a database error because the database has been partially upgraded. It is now neither suitable for 1.4 or 1.5. So what you need to do is restore the database backup, assuming you have one. If you don't have a backup then there's going to be some manual work in undoing the changes that the upgrade process made before it failed. Campbell From: Peter Griffiths [mailto:p.g...@bb...] Sent: 26 November 2015 04:33 To: 'mrb...@li...' <mrb...@li...<mailto:mrb...@li...>> Subject: [MRBS-general] Fatal Error unfortunately the database is not available at the moment Hi, I am holding the fort while our IT person is being replaced, and I know almost nothing about this system. Our users found an issue with MRBS v1.4 where trying to do a recurring weekly for 2016 the system would try to make a booking the following day instead of the day selected. I noticed v1.5 was out so decided to try an upgrade. I copied all the files except the config file over the top of the 1.4 files (I made a backup first). This gave me the following error: ---------------------------------------------------------------- Upgrading to database version: 44 Tried: -- $Id$ -- Add some UNIQUE constraints ALTER TABLE mrbs_room ADD UNIQUE INDEX uq_room_name (area_id, room_name) and got error: Duplicate entry '10-Being Active Eating Well ' for key 'uq_room_name' ---------------------------------------------------------------- This error didn't mean anything to me so I thought it best to undo the changes. I deleted the v1.5 upgrade folder and reinstated the v1.4 backup folder. Now the system displays all the entries and bookings as before but gives the Fatal error message: "Fatal Error unfortunately the database is not available at the moment" I have tried to look for log files but I have no idea where they would be for this system. I have also logged into IIS and found the entry for the MRBS,. I have looked through different entries but I have no idea what I am looking for. My config file: * Database settings ******************/ // Which database system: "pgsql"=PostgreSQL, "mysql"=MySQL, // "mysqli"=MySQL via the mysqli PHP extension $dbsys = "mysqli"; // Hostname of database server. For pgsql, can use "" instead of localhost // to use Unix Domain Sockets instead of TCP/IP. For mysql/mysqli "localhost" // tells the system to use Unix Domain Sockets, and $db_port will be ignored; // if you want to force TCP connection you can use "127.0.0.1". $db_host = "localhost"; // If you need to use a non standard port for the database connection you // can uncomment the following line and specify the port number //$db_port = 3306 // Database name: $db_database = "rooms"; // Schema name. This only applies to PostgreSQL and is only necessary if you have more // than one schema in your database and also you are using the same MRBS table names in // multiple schemas. //$db_schema = "public"; // Database login user name: $db_login = "root"; // Database login password: $db_password = '*********'; // Prefix for table names. This will allow multiple installations where only // one database is available $db_tbl_prefix = "mrbs_"; // Uncomment this to NOT use PHP persistent (pooled) database connections: // $db_nopersist = 1; Any help would be appreciated. Thanks Peter |