unable to access modules from admin menu - error detail

The other module I deleted, right after seeing this error, was google analytics. I had just uploaded this module and had not enabled it. I was about to enable and activate it when the error occurred. Then I saw the items in the "page not found" list, requested by "anonymous" (the site is still in early stages of dev, so there aren't that many users).

Thanks again. Hope to find a solution here.

Peter

I got another error just now while logged in as admin:

this time "fatal error" is "(drupal)/includes/theme.inc on line 972"

that last error message was the same form as the others only with a different line number. The difference was that I was not trying to access "modules" but was on another page in admin and the error message appeared in pieces around the right side of the page - while the page otherwise appeared and functioned normally.

I will look into increasing PHP memory, but I am unfamiliar with doing this. Is the 32M normally not enough for Drupal? The site is young and there is not that much content nor many modules installed. And, of course, everything was fine up until last night.

I still get this error on a blank screen when I click on "modules" in the admin menu. I tried switching themes, to basic Garland, and it made no change in the error message:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 888370 bytes) in /(drupal)/includes/database.mysql-common.inc on line 41

Thanks!
Peter

I went to "performance" in the admin menu and clicked "clear cache" - I got the following error:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 86 bytes) in /(drupal)/includes/menu.inc on line 2347

I went back to the "performance" menu and changed minimum times for cache to "1 minute." That was ok, but when I tried to access "modules" I got the following error again:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 3512 bytes) in (drupal)/includes/database.mysql-common.inc on line 41

I went to phpmyadmin on my hosting server - but, before touching anything, I googled the situation and found this similar problem on drupal.org:

http://drupal.org/node/253948

So, it seems that others are having this problem too, but no definite solution yet - and it looks like it happens even with a lot more memory allocated.

I looked at "statue" in phpmyadmin. I found several items highlighted in red. I am listing them here as it may help drupal core developers. I am still not sure what to do next with the problem of not being able to access "modules" in the admin menu.

Handler_read_rnd | 285 k | The number of requests to read a row based on a fixed position. This is high if you are doing a lot of queries that require sorting of the result. You probably have a lot of queries that require MySQL to scan whole tables or you have joins that don't use keys properly.


Handler_read_rnd_next | 1,927 k | The number of requests to read the next row in the data file. This is high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have.

Created_tmp_disk_tables | 15 k | The number of temporary tables on disk created automatically by the server while executing statements. If Created_tmp_disk_tables is big, you may want to increase the tmp_table_size value to cause temporary tables to be memory-based instead of disk-based.

Select_full_join | 327 | The number of joins that do not use indexes. If this value is not 0, you should carefully check the indexes of your tables.

Opened_tables | 405 | The number of tables that have been opened. If opened tables is big, your table cache value is probably too small.