By anr on

I just upgraded from 4.6 to 4.7 and now I'm not able to administer the modules.
When clicking on administer->modules nothing happens.

I'm totally stuck, and I have not been using drupal for more that a few months, so I have no idea what to do now.
I really hope someone is able to help me.

⋅ Categories: Drupal 4.7.x

Comments

pobster’s picture

pobster commented

Do you still have any 4.6 modules in your modules/ folder? They may be stopping Drupal from displaying whats in the folder.

Pobster

anr’s picture

anr commented

My upgrade procedure was like this:

* I unpacked drupal 4.7 in a new folder
* Updated the site settings file to point to the 4.6 database
* Modified the virtual host entry in apache to point to the new directory (lucky me, I have root access)
* Restarted apache
* Ran update.php (I had to disable access rights checking while doing this)

/anr

pobster’s picture

pobster commented

Did you remember to disable all the modules before doing all this? It's possible that Drupal is having trouble because it's looking for modules which aren't there?

Pobster

anr’s picture

anr commented

I did not do anything before the above procedure.

I am not aware of any pre upgrade steps.

anr’s picture

anr commented

I tried to manually disable the modules by issueing
update system set status=0 where type like 'module';
To the database. My guess was that this would disable the modules.
That did not make any difference though.

heine’s picture

heine commented

Check your Apache logs for errors. The white screen of death is caused by a fatal error that should be logged by Apache.

The most common fatal error on the administer » modules page is due to an out of memory error. See for more information the My admin > modules page is blank in the Troubleshooting FAQ.
--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.

anr’s picture

anr commented

Ok. I was thought that I had been sufficiently excact in my error description. Here's another go

When clicking administer->modules *nothing* happens. The browser sends a request but stays at whatever page I'm on.

Checking the error log as suggested did not give any clue about the error, so I looked in the access log. This is strange:

If I hit the page www.example.com/admin/modules without being logged in, I get a nice error page and an entry in the apache access log.
If I hit the same page when I'm logged in, the above behavior occurs and NOTHING is logged in the apache access log!?!

This I REALLY dont get. Maybe someone with knowledge about drupal internals can get a clue out of this.

/anr

heine’s picture

heine commented

Strange indeed.

Can you do the following?:
- delete cookies in your browser (which browser?)
- clear the browser cache
- execute the query 'DELETE FROM `cache`;
- execute the query 'DELETE FROM `sessions';

It's especially very strange that nothing is logged in the access log.
Can you
- confirm that the virtual host settings are ok?
- follow the browser - server conversation with a sniffer?

--
Getting Fatal error: Call to undefined function: form_*() on Drupal 4.7 ?
When your problem is solved, please post a follow-up to the thread you started.

anr’s picture

anr commented

I cleared cahce and cookies (in mozilla, also tried with epiphany).
executed delete from ...
Fired up tcpmon

This is my request:

GET /admin/modules HTTP/1.1
Host: 192.168.1.3:8080
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051013
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://localhost:8080/admin
Cookie: PHPSESSID=9dd1c8771087a4fdbd87537231214f09

The response is ... well nothing

Damn this is wierd

pobster’s picture

pobster commented

What modules did you have enabled in the 4.6 version?

Pobster

anr’s picture

anr commented

Only default modules:

    name    | status
------------+--------
 queue      |      0
 aggregator |      1
 watchdog   |      1
 archive    |      1
 drupal     |      0
 forum      |      1
 legacy     |      0
 locale     |      0
 menu       |      1
 node       |      1
 page       |      1
 upload     |      1
 system     |      1
 comment    |      1
 ping       |      0
 poll       |      1
 profile    |      0
 search     |      1
 statistics |      1
 story      |      1
 taxonomy   |      1
 throttle   |      0
 tracker    |      0
 block      |      1
 blog       |      1
 blogapi    |      0
 book       |      1
 help       |      1
 filter     |      1
 path       |      0
 contact    |      0
 user       |      1
heine’s picture

heine commented

In the mean time I've tried to mess with several (development) installs, but I can only reproduce similar behaviour by getting system_modules() in an infinite loop. This times out after 60 seconds with the error

Fatal error: Maximum execution time of 60 seconds exceeded in [path]\modules\system.module on line 893

(Line 893 starts the infinite loop)

This does show up in the access.log after a while.

Can you check what happens to the Apache processes during the request?

--
Getting Fatal error: Call to undefined function: form_*() on Drupal 4.7 ?
When your problem is solved, please post a follow-up to the thread you started.

anr’s picture

anr commented

It seems to die.....

I can se that every time i hit the url, an apache process disappears from the list.
If it never finishes the request, then it explains why it never logs anything.

anr’s picture

anr commented

I'm beginning to think that this could be a bug in php.
I'm running:

php5-5.0.4_2
php5-gd-5.0.4_2
php5-pcre-5.0.4_2
php5-pgsql-5.0.4_2
php5-session-5.0.4_2
php5-xml-5.0.4_2
php5-pgsql-5.0.4_2

anr’s picture

anr commented

I give up.
I have a backup of the old database so I'll roll back to 4.6

bugger.

pobster’s picture

pobster commented

Why don't you try going into the 4.6 version, disabling all the modules and then try re-upgrading? Admittedly it's a pain, but I can't see any reason why your upgrade shouldn't work - I have a similar set up and I can't replicate your problem...

Pobster

anr’s picture

anr commented

Yes. Sure. If I have to rollback anyway. I'll give it a shot. If not tommorow, then in a few days.
I'll make sure to post a followup whatever happens.
/anr

lambert-1’s picture

lambert-1 commented

DELETE FROM 'cache' and DELETE FROM 'sessions' worked for me (with Drupal 5.1).

alboyd’s picture

alboyd commented

I'm using latest 4.7.

This is the exact same problem which happened to me. Not after an upgrade however, but after installing latest TinyMCE dirs and unpacked contents into the modules dir - nothing happens. I cannot access the admin module page to change attributes of modules. IT just does nothing when I click the link.

Some folk seem to suggest manually installing the msql file from the previous version of TinyMCE. But this doesn't seem to work either.

All I get is a similar effect as the above query. A module link that will not load....

Once I delete the tinymce folder from the modules folder - the problem is fixed. But obviously no TinyMCE.

Hmmm.

ckclarke’s picture

ckclarke commented

In the past when I've had trouble accessing the modules page it's because locally PHP hasn't been allotted enough memory to load all the modules on that page.

You might try adding a line like

php_value memory_limit 20M

To your htaccess file

----
http://www.whatdoesthatmean.com
http://www.ponderfodder.com
http://www.scribendi.com

docker’s picture

docker commented

I tired to search in loads of topics, and i was absolutely hopeless.
Many thanks and respect for you. That was the solution for my problem.

maureen’s picture

maureen commented

this solved my headache of the day.

peace.

sepeck’s picture

sepeck commented

Many solutions to common issues are in the http://drupal.org/Troubleshooting-FAQ

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

anr’s picture

anr commented

Hi. I just restored the database from a backup and downgraded the drupal installation to 4.6.6.
During this process, I got this bad feeling: I might not have been running the version of drupal that I thought i where...
I'll give the upgrade one more shot when I have some spare time, and post a followup.