dear list,
as i am quite new to mysql-issues and the database, i don't know how to put my site to life again..
as i had troubles with the installation of the views-module (all the other first 7 modules did install with no problems) i wanted to deactivate it.
because i couldn't access my /admin/modules-frontend anymore, i used instructions on
http://www.drupalcenter.de/handbuch/11551 (german language)
to deactivate the views-module(s) in the database using phpmyadmin. (open phpmyadmin, select system, find the views-moulde-entries, deactivate it with setting status to 0)
after that, the site is down completely (drupal error-site is showing "site down" 'because of technical issues - please check your database settings in the settings.php file and ensure that your hosting provider's database server is running')
so, what to do now?
i already posted a forum-topic and followed the hint of one member with no results and even a complete confixx-restore with a backup of all files and the database i did one week ago when all was running well doesn't change anything.
could it be, i should have taken the site down with my admin-frontend, before changing something in the database?
thank you for reading anyhow
:-jo
On Wed, Dec 3, 2008 at 7:31 AM, jo joinkemel@yahoo.de wrote:
dear list,
as i am quite new to mysql-issues and the database, i don't know how to put my site to life again..
as i had troubles with the installation of the views-module (all the other first 7 modules did install with no problems) i wanted to deactivate it.
because i couldn't access my /admin/modules-frontend anymore, i used instructions on
http://www.drupalcenter.de/handbuch/11551 (german language)
to deactivate the views-module(s) in the database using phpmyadmin. (open phpmyadmin, select system, find the views-moulde-entries, deactivate it with setting status to 0)
Let's assume for the moment that the implementation of this advanced admin procedure did something wrong to the database, and that that left Drupal in an undefined state.
But a restore to the database should have left things as they were.
Try this:
1. Drop all the tables in the database. 2. Then restore from last week.
If that doesn't work then something is amiss in the file system or on the server configuration. In that case, try a fresh Drupal install on the same database. If that works then restore again.
Victor Kane http://awebfactory.com.ar
after that, the site is down completely (drupal error-site is showing "site down" 'because of technical issues - please check your database settings in the settings.php file and ensure that your hosting provider's database server is running')
so, what to do now?
i already posted a forum-topic and followed the hint of one member with no results and even a complete confixx-restore with a backup of all files and the database i did one week ago when all was running well doesn't change anything.
could it be, i should have taken the site down with my admin-frontend, before changing something in the database?
thank you for reading anyhow
:-jo
-- [ Drupal support list | http://lists.drupal.org/ ]
thank you very much for your hints, now i am at least stuck at another point ;-)
i tried your option 1 (deleting all tables and restore) with no positive results.
then i tried option 2 (reinstalling drupal by replacing all files with fresh drupal 6.6 files and a databank-restore, but also there was the same 'site down' errorpage.
which i read again and remembered that it says i should have a look at settings.php.
so next thing i did was renaming the settings.php with uglysettings.php and renaming default.settings.php with settings.php, so i would use the default settings from a fresh install - now i really was able to see the drupal installation-page where now i have problems with the database-configuration-step:
with the name of my existing database and the user and password i enter in phpmyadmin to come in, drupal doesn't go to the next step, but also it doesn't create any errormessage, just all fields are empty again. when i enter any adequate fantasy-names, it tells that this is the wrong password or username..why is that?
and what should i do now, especially in case i would love to avoid creating all nodes again - is there any possibility to recreate the nodes from the old database when i do a fresh-install and the backup is faulty?
:-jo
--- Victor Kane victorkane@gmail.com schrieb am Mi, 3.12.2008:
Von: Victor Kane victorkane@gmail.com Betreff: Re: [support] site down after i deactivated views via phpmyadmin An: support@drupal.org Datum: Mittwoch, 3. Dezember 2008, 11:05 On Wed, Dec 3, 2008 at 7:31 AM, jo joinkemel@yahoo.de wrote:
dear list,
as i am quite new to mysql-issues and the database, i
don't know how to put my site to life again..
as i had troubles with the installation of the
views-module (all the other first 7 modules did install with no problems) i wanted to deactivate it.
because i couldn't access my
/admin/modules-frontend anymore, i used instructions on
language)
to deactivate the views-module(s) in the database
using phpmyadmin. (open phpmyadmin, select system, find the views-moulde-entries, deactivate it with setting status to 0)
Let's assume for the moment that the implementation of this advanced admin procedure did something wrong to the database, and that that left Drupal in an undefined state.
But a restore to the database should have left things as they were.
Try this:
- Drop all the tables in the database.
- Then restore from last week.
If that doesn't work then something is amiss in the file system or on the server configuration. In that case, try a fresh Drupal install on the same database. If that works then restore again.
Victor Kane http://awebfactory.com.ar
after that, the site is down completely (drupal error-site is showing "site down" 'because of technical issues - please check your
database settings in the settings.php file and ensure that your hosting provider's database server is running')
so, what to do now?
i already posted a forum-topic and followed the hint
of one member with no results and even a complete confixx-restore with a backup of all files and the database i did one week ago when all was running well doesn't change anything.
could it be, i should have taken the site down with my
admin-frontend, before changing something in the database?
thank you for reading anyhow
:-jo
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
Once settings.php is pointed to the correct database with the correct username and password, and your fresh install is working, you can restore the database with your previous version, and you should be good to go.
You can do this either by installing Drupal anew, and filling in the correct database and user info during the installation, or else by directly editing settings.php.
The line you need to edit is the following (about half-way down):
$db_url = 'mysql://your-real-db-user-name:your-real-db-user-password@localhost/your-real-databasename';
Hope that helps,
Victor Kane http://awebfactory.com.ar
On Wed, Dec 3, 2008 at 5:54 PM, jo joinkemel@yahoo.de wrote:
thank you very much for your hints, now i am at least stuck at another point ;-)
i tried your option 1 (deleting all tables and restore) with no positive results.
then i tried option 2 (reinstalling drupal by replacing all files with fresh drupal 6.6 files and a databank-restore, but also there was the same 'site down' errorpage.
which i read again and remembered that it says i should have a look at settings.php.
so next thing i did was renaming the settings.php with uglysettings.php and renaming default.settings.php with settings.php, so i would use the default settings from a fresh install - now i really was able to see the drupal installation-page where now i have problems with the database-configuration-step:
with the name of my existing database and the user and password i enter in phpmyadmin to come in, drupal doesn't go to the next step, but also it doesn't create any errormessage, just all fields are empty again. when i enter any adequate fantasy-names, it tells that this is the wrong password or username..why is that?
and what should i do now, especially in case i would love to avoid creating all nodes again - is there any possibility to recreate the nodes from the old database when i do a fresh-install and the backup is faulty?
:-jo
--- Victor Kane victorkane@gmail.com schrieb am Mi, 3.12.2008:
Von: Victor Kane victorkane@gmail.com Betreff: Re: [support] site down after i deactivated views via phpmyadmin An: support@drupal.org Datum: Mittwoch, 3. Dezember 2008, 11:05 On Wed, Dec 3, 2008 at 7:31 AM, jo joinkemel@yahoo.de wrote:
dear list,
as i am quite new to mysql-issues and the database, i
don't know how to put my site to life again..
as i had troubles with the installation of the
views-module (all the other first 7 modules did install with no problems) i wanted to deactivate it.
because i couldn't access my
/admin/modules-frontend anymore, i used instructions on
language)
to deactivate the views-module(s) in the database
using phpmyadmin. (open phpmyadmin, select system, find the views-moulde-entries, deactivate it with setting status to 0)
Let's assume for the moment that the implementation of this advanced admin procedure did something wrong to the database, and that that left Drupal in an undefined state.
But a restore to the database should have left things as they were.
Try this:
- Drop all the tables in the database.
- Then restore from last week.
If that doesn't work then something is amiss in the file system or on the server configuration. In that case, try a fresh Drupal install on the same database. If that works then restore again.
Victor Kane http://awebfactory.com.ar
after that, the site is down completely (drupal error-site is showing "site down" 'because of technical issues - please check your
database settings in the settings.php file and ensure that your hosting provider's database server is running')
so, what to do now?
i already posted a forum-topic and followed the hint
of one member with no results and even a complete confixx-restore with a backup of all files and the database i did one week ago when all was running well doesn't change anything.
could it be, i should have taken the site down with my
admin-frontend, before changing something in the database?
thank you for reading anyhow
:-jo
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
success!
thank you so much for your clear and great support!
now i know what happenend: i simply changed passwords in confixx without knowing that it would also change the database-password..
what i do not understand yet: why is it secure to have the mysql-password stored in plaintext?
many greetings from the snowy winterhills of the taunus
:-jo
--- Victor Kane victorkane@gmail.com schrieb am Mi, 3.12.2008:
Von: Victor Kane victorkane@gmail.com Betreff: Re: [support] site down after i deactivated views via phpmyadmin An: support@drupal.org Datum: Mittwoch, 3. Dezember 2008, 21:00 Once settings.php is pointed to the correct database with the correct username and password, and your fresh install is working, you can restore the database with your previous version, and you should be good to go.
You can do this either by installing Drupal anew, and filling in the correct database and user info during the installation, or else by directly editing settings.php.
The line you need to edit is the following (about half-way down):
$db_url = 'mysql://your-real-db-user-name:your-real-db-user-password@localhost/your-real-databasename';
Hope that helps,
Victor Kane http://awebfactory.com.ar
On Wed, Dec 3, 2008 at 5:54 PM, jo joinkemel@yahoo.de wrote:
thank you very much for your hints, now i am at least
stuck at another point ;-)
i tried your option 1 (deleting all tables and
restore) with no positive results.
then i tried option 2 (reinstalling drupal by
replacing all files with fresh drupal 6.6 files and a databank-restore, but also there was the same 'site down' errorpage.
which i read again and remembered that it says i
should have a look at settings.php.
so next thing i did was renaming the settings.php with
uglysettings.php and renaming default.settings.php with settings.php, so i would use the default settings from a fresh install - now i really was able to see the drupal installation-page where now i have problems with the database-configuration-step:
with the name of my existing database and the user and
password i enter in phpmyadmin to come in, drupal doesn't go to the next step, but also it doesn't create any errormessage, just all fields are empty again.
when i enter any adequate fantasy-names, it tells that
this is the wrong password or username..why is that?
and what should i do now, especially in case i would
love to avoid creating all nodes again - is there any possibility to recreate the nodes from the old database when i do a fresh-install and the backup is faulty?
:-jo
--- Victor Kane victorkane@gmail.com schrieb
am Mi, 3.12.2008:
Von: Victor Kane victorkane@gmail.com Betreff: Re: [support] site down after i
deactivated views via phpmyadmin
An: support@drupal.org Datum: Mittwoch, 3. Dezember 2008, 11:05 On Wed, Dec 3, 2008 at 7:31 AM, jo joinkemel@yahoo.de wrote:
dear list,
as i am quite new to mysql-issues and the
database, i
don't know how to put my site to life again..
as i had troubles with the installation of
the
views-module (all the other first 7 modules did
install with
no problems) i wanted to deactivate it.
because i couldn't access my
/admin/modules-frontend anymore, i used
instructions on
(german
language)
to deactivate the views-module(s) in the
database
using phpmyadmin. (open phpmyadmin, select system,
find the
views-moulde-entries, deactivate it with setting
status to
Let's assume for the moment that the
implementation of
this advanced admin procedure did something wrong to the
database, and
that that left Drupal in an undefined state.
But a restore to the database should have left
things as
they were.
Try this:
- Drop all the tables in the database.
- Then restore from last week.
If that doesn't work then something is amiss
in the
file system or on the server configuration. In that case, try a
fresh Drupal
install on the same database. If that works then restore
again.
Victor Kane http://awebfactory.com.ar
after that, the site is down completely (drupal error-site is showing "site
down"
'because of technical issues - please
check your
database settings in the settings.php file and
ensure that
your hosting provider's database server is
running')
so, what to do now?
i already posted a forum-topic and followed
the hint
of one member with no results and even a complete confixx-restore with a backup of all files and the
database
i did one week ago when all was running well
doesn't
change anything.
could it be, i should have taken the site
down with my
admin-frontend, before changing something in the
database?
thank you for reading anyhow
:-jo
-- [ Drupal support list |
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
Quoting jo joinkemel@yahoo.de:
what i do not understand yet: why is it secure to have the mysql-password stored in plaintext?
Hopefully you're using a user for the DB that can only affect the site DB and you have regular backups.
-- Earnie http://r-feed.com Make a Drupal difference and review core patches.
with the name of my existing database and the user and password i enter in phpmyadmin to come in, drupal doesn't go to the next step, but also it doesn't create any errormessage, just all fields are empty again. when i enter any adequate fantasy-names, it tells that this is the wrong password or username..why is that?
Hard to say. Can you ask your host support? Is there an error log to look at?
and what should i do now, especially in case i would love to avoid creating all nodes again - is there any possibility to recreate the nodes from the old database when i do a fresh-install and the backup is faulty?
Depends on the backup--if the data is there, then it's probably possible to re-instate it. May have to do it manually however, which can be difficult.
-
Earnie Boyd -
Fred Jones -
jo -
Victor Kane