Something has gone VERY wrong with my Drupal site
www.skivermontqr.com
I can no longer login th the site and sometimes when it loads in firefox all I get is a directory listing.
The site has always been taking a long time to load and the server is set for 90 seconds to get some pages to load.
When I do log in in Firefox ( cannot log in in IE8 and my mac user on safari cannot log out)
and attempt to clear the cashe I get the following error:
The requested page "/?q=admin_menu/flush-cache/admin_menu&token=JWc3QDnkH9svFTzrhzmur8_WgZ3gY-SVHtbWUUXEdW8&destination=node" could not be found.
Most of my tool bar is missing as well.
I had made some formatting changes to the page portfolio, but I uploaded the CSS file from before the changes so that should not be an issue. Also put pag=ck the old style-less.less file
I had also added an image field to the basic page and an image type for it.
If I could get into the admin I would undo that and put it back.
My hosting company says they already do the suggestions made to make the site faster.
Here was their last post to me:
Something is weird with the database. The problem is cookie related we think because try to logout does it give you connection reset on the logout. You would want a drupal person to take a look.
I am unfamiliar with posting on message boards and really like the concept of Drual and would like to get it working properly.
My customer is really mad at me because the site is down and I do not know what to do. Can you help me?
Thanks!
-B
Comments
=-=
As you are not writing a module, this question belongs in the post installation forum. Please edit the opening post and move it. Thanks.
In Firefox it looks fine to
In Firefox it looks fine to me. Maybe you need to clear your browser cache.
Yes
Yes it does look fine. However if you look at the top right hand corner I can no longer login.
I can get here: http://skivermontqr.com/?q=user/login
But when I attempt to use my user name and password I get this error message:
The connection has timed out
The server at skivermontqr.com is taking too long to respond.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
My hosting Company has upped the time out to 90 seconds. and their reply to me was:
Something is weird with the database. The problem is cookie related we think because try to logout does it give you connection reset on the logout. You would want a drupal person to take a look.
=-=
clear your browser cache and cookies
check settings.php, is a cookie set?
cookie.php
I have cleared cache and cookies in my browser ( In firefox now)
Can open settings.php but am not a coder. What do I look for to see ig the cookie is set?
I found code here in setting.php
/**
* Set session cookie lifetime (in seconds), i.e. the time from the session is
* created to the cookie expires, i.e. when the browser is expected to discard
* the cookie. The value 0 means "until the browser is closed".
*/
ini_set('session.cookie_lifetime', 2000000);
/**
* If you encounter a situation where users post a large amount of text, and
* the result is stripped out upon viewing but can still be edited, Drupal's
* output filter may not have sufficient memory to process it. If you
* experience this issue, you may wish to uncomment the following two lines
* and increase the limits of these variables. For more information, see
* http://php.net/manual/en/pcre.configuration.php.
*/
# ini_set('pcre.backtrack_limit', 200000);
# ini_set('pcre.recursion_limit', 200000);
/**
* Drupal automatically generates a unique session cookie name for each site
* based on its full domain name. If you have multiple domains pointing at the
* same Drupal site, you can either redirect them all to a single domain (see
* comment in .htaccess), or uncomment the line below and specify their shared
* base domain. Doing so assures that users remain logged in as they cross
* between your various domains.
*/
# $cookie_domain = 'example.com';
=-=
looks fine.
clear your sessions table in the database and test
Done
OK, that is done and the home page loads much faster, pages still taking a long time to load
Log in still missing from shortcuts in both ie and firefox
Firefox after entering login and password:http://www.skivermontqr.com/?q=user/login
The connection was reset
The connection to the server was reset while the page was loading.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
IE after entering login and password:http://www.skivermontqr.com/?q=user/login
Internet Explorer cannot display the webpage
=-=
at this point, I'd download a copy of the sites files and database into a development machine and see if the issue is the site itself or the environment it's running in.
If all works well on local machine you can nearly rule out anything drupal related.
out of curiosity what happens what you use the correct username but the wrong password?
errors
I get the same error, but I did notice after I put in
http://www.skivermontqr.com/?q=user/login it goes to
http://www.skivermontqr.com/?q=user
=-=
and if you use the wrong username and password?
I get the standard drupal $message "Sorry, unrecognized username or password"
any error.log in your root?
anything in your watchdog log? you can export the table from the DB if needed
errors
Sorry, unrecognized username or password. Have you forgotten your password?
From my hosting Company
Here is a message from my hosting company. Unfortunately we are getting into stuff that I do not understand at all. I don't know what this means or what to do with it.
There is no error.log file in your root but watchdog log has 1218 rows of data.. We exported it to watchdog.csv in your main FTP folder.
It is a big file. Looks like db problem
PDOException\";s:8:\"!message\";s:35879:\"SQLSTATE[23000]
: Integrity constraint violation: 1062 Duplicate entry 'map' for key 1:
There is a lot more but hard to cut and paste it.
=-=
now that the watchdog has been copied, empty the table so that only new errors are recorded.
the file sent can be copied to pastebin.com and linked here.
it's complaining (at least based on the error you pasted) about a duplicate for 'map'. are you using a module for maps? if so, which one?
K - emailing my hosting
I have sent your message to my hosting company.
I thought I had the map turned off
Google had changed the software so that the API code no longer worked and we don't need a map on out contact page.
I had removed it from the body of the contact page.
Can I just remove the module through ftp since I can't get in to the admin?
Paste bin to line 10
http://pastebin.com/iygFyBn2
11-20
http://pastebin.com/GsDcBk38
21-31
http://pastebin.com/5BzuLuza
32-44
http://pastebin.com/NYeS3cyh
45-62
http://pastebin.com/x3D0UN2n
There are 1148 lines, should I keep going? Definitely looks like some type of DB thing, and it definitely does not like the map.
=-=
you can disable the module by setting its status to 0 in the system table of the database. note, it and anything dependent on it will need to be disabled.
desperation
We did that and I still get in. I was asking my hosting company to wipe out the whole thing and go back to a point where the admin worked. They asked me to ask this:
What about truncating or clearing out all the cache tables?
Ask the forums about how to do a reset on the cache from outside the admin manually.
We also cleared the sessions table again for you.
=-=
all cache tables can be safely emptied (truncated), this would be accomplished from inside the database.
don't know how
My hosting company was asking where to do that.
Do you have any clue?
=-=
as stated, within the database. If they/you aren't familiar with a drupal database they/you may use phpmyadmin to view the database tables. They/you will want to empty all tables marked cache, cache_ and _cache (there are multiple). That said make sure they/you backup the existing database first.
If your hosting company does not know how to work within the database using the tools they put on the server, you should seek a new host.
Maybe
Maybe I am not asking for the information they are looking for. They are not failiar with Drupal and recommend WordPress instead. I HAVE to get some things fixed on the site before 9AM tomorrow in order to keep my job. I cannot do them if I cannot get into the admin. There is no one else but me to do this task and this is all over my head. I am not used to posting on message boards and am doing the best I can.
I had asked them if we could just restore the site to a time when It was working and I would do everything all over again, but becuase we cleared the session files? this would be a problem.
Clearing the sessions tables
Clearing the sessions tables (not files) would make no difference if backing up from a backup prior to the changes.
=-=
you asked how to manually clear the cache. It's been explained how to do that. If they were able to truncate (empty) the sessions table in the database, the process is exactly the same though the table names are different.
Thank-you
Thank-you for your help. I have asked them to just restore the site back to when I could get into the admin.
The next issue which I will be dealing with tomorrow, is to find out why the site is working so slowly.
Should I fill out a new ticket for that or can you make a suggestion here?
=-=
There is no way to determine the causation of the slowness of your site based on this discussion.
I must admit that it is disturbing to have learned that you took on a client site and manipulated that site without backing it up before you started the work. There also seems to have been little to no evaluation of the existing site with reference to possible errors in watchdog before the job began. Therefore, you have no idea what state the site was really in before you touched it. This put you in a position to have to accept that any and all issues the site is experiencing are now yours. I can only hope that you've learned something from this experience that prompts you to work out a workflow for the future that provides protection for both you and the client.
Obviously the errors need to be dealt with. the more time errors are occurring, the more time the errors need to be recorded by drupal. Full disclosure should occur in a separate thread. Version of php, mysql, apache, how much memory, how many modules, which ones, are they all updated to the lastest release and so on. What transpired between the time the site was working as expected and wasn't is also helpful information.
There are also a great many already existing threads that deal with performance that should be sought out and read through.
Uninstall the module
This is very old thread, So I doubt whether anybody is still facing this issue or not.
But, I faced same issue recently.
I googled about the issue and tried all solutions but none of them worked.
Finally, i un-installed module from module listing page and re-installed it.
Ta-da, everything worked fine.