I upgraded from 6.6 to 6.8 and now i can't access any of the admin pages. I get the message "Page not found", although the address is from the history. This goes on for hours now. I refresh again and again, no result.
It has happened before, but after a awhile it resolves itself. I can add nodes, see te front.
It critical that in the coming hours it will be working. What might be causing this?

Comments

keith.smith’s picture

keith.smith commented
Category: bug » support
Priority: Critical » Normal

Adjust category and priority.

From the release announcement:
It is important to run update.php to refresh the menu cache and other caches on the website. These releases changed .htaccess and robots.txt, so if you have custom changes in them, make sure to keep the changes after the upgrade.

Did you run update.php after updating, and are you sure that any custom changes to your .htaccess file were preserved?

hannesh’s picture

hannesh commented

Yes i did run it, even though there was nothing to update. And i therer were no changes in htaccess file.

gpk’s picture

gpk commented

Is there a folder "admin" in your Drupal folder?

hannesh’s picture

hannesh commented

No, there is no such folder.
As i've said, it has happened before. After some refreshing i get the pages's back, but this it has not happened in more than 16 hours.

gpk’s picture

gpk commented

Do you get a Drupal page not found page or a simple one from the Apache web serer?

Also note some webhosts "reserve" the path admin for their own control panel or somesuch.

What happens if you go to www.example.com/?q=admin

You might get some clues from the {watchdog} table, and the {accesslog} table if you have enabled statistics.module's recent hits functionality. Also the Apache error log and accesslog.

Bojhan’s picture

Bojhan commented
Component: usability » base system
hannesh’s picture

hannesh commented

i get the drupals "page not found"

on the ?q=admin i get same error message.

Accesslog is empty for some reason, but from Watchdogs table i get this message on the not found pages

type "page not found" message "500.shtml" severity "4" variables "N;"

gpk’s picture

gpk commented

Ah that's the vital clue.

Probably you are running on cPanel shared hosting or similar. If a 500 error occurs then it looks for a page 500.shtml to report the error to the user. But of course that doesn't exist.

500 = Internal server error http://en.wikipedia.org/wiki/List_of_HTTP_status_codes#5xx_Server_Error

You need to check your Apache error log to find out what the error was. Probably ran out of PHP memory.

hannesh’s picture

hannesh commented

Good, progress then.

yes, it's a shared hosting.
I have given 500mb for D.
i would probably need to get this error log from the provider?

gpk’s picture

gpk commented

>I have given 500mb for D.
?? Sorry don't follow.

>i would probably need to get this error log from the provider?
On my cPanel interface there is an option to view the account's portion of the Apache error log.

hannesh’s picture

hannesh commented

in the php.ini file there is a memory limit of 565M

In my cpanel i found only the error log for page errors, as "File does not exist" and such, but nothing for Apache

gpk’s picture

gpk commented

>in the php.ini file there is a memory limit of 565M
Do you know if the setting is actually being respected? What is reported for memory_limit if you run phpinfo() from within your Drupal site/a script in Drupal's root folder?

>In my cpanel i found only the error log for page errors, as "File does not exist" and such, but nothing for Apache
Hmm a 500 error does indicate a potentially significant problem, maybe your host can help track it down.

To check whether having "admin" in the URL is the cause of the problem (unlikely but worth ruling out) you could set up a URL alias for somthing like mypage pointing to Drupal path admin, then www.example.com/mypage would show whether the problem is occurring before or after Drupal takes over handling the page request. admin paths are not fundamentally different from any other paths/pages on the site, but they do tend to be more memory hungry/require more queries etc.

500 errors are also sometimes caused when the Apache config conflicts with the .htaccess; Drupal should "sort of" work without it (but clean URLs won't work so you must use the example.com/q=path form of URLs) - something else to troubleshoot.

hannesh’s picture

hannesh commented

>>in the php.ini file there is a memory limit of 565M
>Do you know if the setting is actually being respected? What is reported for memory_limit if you run phpinfo() from within your >Drupal site/a script in Drupal's root folder?
In PHP Core it says 565M for local and master value.

>>In my cpanel i found only the error log for page errors, as "File does not exist" and such, but nothing for Apache
>Hmm a 500 error does indicate a potentially significant problem, maybe your host can help track it down.
I've written to the host. They're usually very helpful.

>To check whether having "admin" in the URL is the cause of the problem (unlikely but worth ruling out) you could set up a >URL alias for somthing like mypage pointing to Drupal path admin, then www.example.com/mypage would show whether >the problem is occurring before or after Drupal takes over handling the page request. admin paths are not fundamentally >different from any other paths/pages on the site, but they do tend to be more memory hungry/require more queries etc.
I made the url alias in the table and going to this new address i still get the same error

>500 errors are also sometimes caused when the Apache config conflicts with the .htaccess; Drupal should "sort of" work >without it (but clean URLs won't work so you must use the example.com/q=path form of URLs) - something else to >troubleshoot.
should i try turning off clean url-s?

gpk’s picture

gpk commented

>should i try turning off clean url-s?
You could try turning them off and then temporarily rename .htaccess so that it isn't used.

The real error should be logged somewhere, your host may be able to help track it down or maybe PHP config needs altering slightly so that the error is reported/logged properly. BTW check for an error_log file in your Drupal root folder.

hannesh’s picture

hannesh commented

>>should i try turning off clean url-s?
>You could try turning them off and then temporarily rename .htaccess so that it isn't used.
Well, now i get to see some admin pages (the comment pages) but for other i get "Internal Server Error" page. When i renamed htaccess again, the problem comes back.

>The real error should be logged somewhere, your host may be able to help track it down or maybe PHP config needs altering >slightly so that the error is reported/logged properly. BTW check for an error_log file in your Drupal root folder.
my log file was 1gb, im waiting for the hosts answer.

gpk’s picture

gpk commented

All very odd, let's hope your help can shed some more light on the errors.

>my log file was 1gb
If that was an error_log file then the answer is probably in there somewhere. :D

hannesh’s picture

hannesh commented

>All very odd, let's hope your help can shed some more light on the errors.
Even after clearing the cache it would not show some pages, so now i reverted back to the clean url-s and htaccess.

>>my log file was 1gb
>If that was an error_log file then the answer is probably in there somewhere. :D
i think i need some magic to open it. i'll wait for the host's answer.

Thanks very much for you're help though. Got much clarity for about the issues.

gpk’s picture

gpk commented

>i think i need some magic to open it.
OR else rename it to error_log.0 and then generate some errors and have a look quick before it grows too big!!

hannesh’s picture

hannesh commented

>>i think i need some magic to open it.
>OR else rename it to error_log.0 and then generate some errors and have a look quick before it grows too big!!
yet was trying to do that, but the "error" is that i cant produce errors, this "page not found" action does not log into this log.

ainigma32’s picture

ainigma32 commented
Status: Active » Postponed (maintainer needs more info)

@hannesh: I just tried your site and although I can't understand any of the language it looks like you resolved this. Did you manage to find out what was causing the 500 errors?

- Arie

hannesh’s picture

hannesh commented

unfortunately no. the site you may have looked is my personal site, not the problem site i'm working on. The host said that they do not have any more information, so i dont know how to find the apache errors right now.
I'm planning on trying to upload the drupal files with a new database, taking the node, terms aso from the old database; making a "reinstall". That's a desperate option, that i've come up with.

ainigma32’s picture

ainigma32 commented

Sorry to hear that. Curious to hear that the ISP can't produce a log with the error in it (!)

If you are going to do the "reinstall" anyway you could try rebuilding the site in a test environment and see if you can reproduce the error.

Anyway good luck and please post back your progress.

- Arie

hannesh’s picture

hannesh commented

ok, thanks!
ISP could not give me any more, than was already available to me in cpanel. Maybe that's normal. Usually they have been good.

gpk’s picture

gpk commented

Re #15: getting to see just some admin pages but not others is really rather strange. I wonder if the host has some strict mod_security rules in place that are intercepting Drupal's admin URLs. In your situation I'd probably either 1) try a more Drupal-friendly host or 2) start adding debug code to bits of core to check whether the problem URLs are getting as far as being processed by Drupal, or whether the 500 error is thrown even before processing is handed off to Drupal, which is what I begin to suspect. Another way of testing this would be to create a URL alias for a problem URL e.g. create an alias for admin/problem called "news" or something innocuous. Then see if you can access the admin page via the "news" alias .

hannesh’s picture

hannesh commented

i did an alias for "admin" , but with no change.
Though the address changed only for the main page, but stayed the same for other pages like admin/content aso.

edit: turns out isp does not support php commands from .htaccess

ainigma32’s picture

ainigma32 commented

Marked #303876: after update from 6.3->6.4 admin section gone as a duplicate of this issue.

- Arie

gpk’s picture

gpk commented

@25, OK looks like it's probably not a problem with the path "admin" being blocked somewhere. Yes the alias would only affect the main admin page.

>edit: turns out isp does not support php commands from .htaccess
Yes directives in .htaccess can cause 500 errors if the server config does not allow them.

Is this fixed now?

ainigma32’s picture

ainigma32 commented
Status: Postponed (maintainer needs more info) » Fixed

Looks like hannesh won't be posting any feedback so I'm setting this to fixed.

Feel free to reopen if you think that is wrong.

- Arie

hannesh’s picture

hannesh commented

sorry for the delay.
the problem was the host does not support php funtions in .htaccess files. Although it did work mostly before, i removed them and it works fine now.
Thanks for the help!

gpk’s picture

gpk commented

Thanks for the update. Strange that the php directives in .htaccess only caused intermittent problems, but glad to hear all is working now.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

hannesh’s picture

hannesh commented
Version: 6.6 » 6.12
Status: Closed (fixed) » Active

seems that the issue is back. the removal of php commands from .htaccess is not a permament help.
But now i get a error report from the log file. Maybe someone can help interpret it for me. I can't get leads from it.
This one repeats often:

PHP Warning: MySQL server has gone away
query: INSERT INTO watchdog
(uid, type, message, variables, severity, link, location, referer, hostname, timestamp)
VALUES
(0, 'php', '%message in %file on line %line.', 'a:4:{s:6:\"%error\";s:12:\"user warning\";s:8:\"%message\";s:513802:\"MySQL server has gone away\nquery: UPDATE sessions SET uid = 0, cache = 0, hostname = '', session = '8kcAfSk3xtWEp0qVEVdfVmT9N17JFtgACEgWXKoIDZEALqyOm1peSdKZ3LMxIOR7ckSqfXQXsCykkb0l4pta6NPW6xDXjsKGpFOkZFTvSa4rl9icRtOP5JSbuTP6-WgoW7B8AxEyDD2ZwoMZdfEuc0j_Ls3m8VcOR_iE-RJHSTQP1NXgnx_ebxA5rhK-nYS7SNdTNFKw0bTmfqpv5ZjwA8VHzqEVk2DuZZdk383MuBRILNd66SkC1PUiCttKMnYM7cyiPGl3DXxrMq0epU4O6Hb7q9S1P2YLJTB_bzBABYrauB6zNdrc5JivWFUldNY4fm5ob7vufTKvpehflUmOoEV7QgER7IC9APQJ32RQyYt8FEro1omA3NtH1o4saVW9bOkk5KErcl2UAzHBoY1zLLEAZhSp8GRScTInN7xdoEiYQI7eEj-4fbGl_1UnahhUDfnHMigPY4kJ2hVaPrOHdqtS-s4GeH2CoEfsOMzz1Evd8OkEi8-67ja6R1Clkgm1N7ZTBYJLntSWXjHS4Ss104TjhHpGfKXXHHtxH_fCrH3v in public_html/includes/database.mysql.inc on line 128

And this one also reappears:

[14-May-2009 16:01:07] PHP Warning: MySQL server has gone away
query: INSERT INTO watchdog
(uid, type, message, variables, severity, link, location, referer, hostname, timestamp)
VALUES
(0, 'php', '%message in %file on line %line.', 'a:4:{s:6:\"%error\";s:12:\"user warning\";s:8:\"%message\";s:180:\"MySQL server has gone away\nquery: SELECT dst FROM url_alias WHERE src = 'admin/reports/updates/check' AND language IN('et', '') ORDER BY language DESC\";s:5:\"%file\";s:44:\"/public_html/includes/path.inc\";s:5:\"%line\";i:69;}', 3, '', 'http:///?//public_html/cron.php', '', '', 1242306067) in /public_html/includes/database.mysql.inc on line 128

int’s picture

int commented

your data base is offline sometimes, contact your administrator, or mysql logs

"MySQL server has gone away"

hannesh’s picture

hannesh commented

Thanks!
They say that database has not been away, but what about /includes/database.mysql.inc on line 128?

mdupont’s picture

mdupont
Primary language French
Location Switzerland
commented
Status: Active » Closed (works as designed)

It is likely to be fixed by now, and the latest issue is related to MySQL, not Drupal. Closing.