Drupal 5.12 - logged-in admin sees only first teaser on frontpage, "n\a" for all others, basic blocks missing.

Hello everyone,

I am running a quite large community-like portal based on drupal 5.12, integrated with G2, much SEO oriented, and with currently oer 20000 nodes of content. The installation runs on a VPS with 640 mb of guaranteed ram and the mysql database is on a 2nd machine, called via remote connections, with 1gb of RAM available. It has worked very well for several months, until the original all-on-one-machine configuration has been modified in favor of a multi-server solution for hardware resources issues.

This accomodation on two machines has been chosen to be sure to liberate as many resources as possible on the first VPS for Apache processes; for the same purposes of sparing resources for heavy traffic, several modules of caching kind have been properly installed, significantly speeding up and smoothening the navigation, especialy for anonymous users. On this regard, no large problems experienced.

Unfortunately, since when this separation between Apache VPS and Mysql machine has been performed, transferring the DB on a 2nd server, I have experienced the following problem: as logged-in admin (UID1 I guess) I see "n\a" for all teasers on frontpage, page=1, page=2, page=n etc. As logged in admin seeing my frontpage, I see only the first teaser of the ten visible on each page (first teaser on frontpage, first teaser on page=1 etc; all the rest are N/A). Moreover, most standard blocks, such as "who is online", "who is new", "navigation", "search", when logged in as admin, don't show on the frontpage to administrator nor on other public pages.

Finally, if let's say I go to a page via an old bookmark, where there is a node of content, then I do see the item of content, but no other node at all is shown aside primary links. The ISSUE SEEMS TO AFFECT ALL CONTENT AND ALL TEASERS displayed when the user is ADMIN. Other users are apparently NOT affected.

NOTE that Administrative pages [eg, modules, logs, update, etc] accessed as UID1 seem to work correctly - as admin on administration pages, I see everything that I should, and everything seems to work correctly. Likewise, when I am logged out as anonymous, or logged-in as test user, the frontpage, the successive pages and the individual nodes work perfectly. The problem is thus indeed present only as admin who visits the pages usually available to the general public.

As I said, the problem emerged after an otherwise perfectly successful database transfer to a 2nd machine reached through apparently fast and safe connections. When I transferred the mySql database, for space reasons I truncated the classic expendable tables (Watchdog logs, cumulated search data etc). I am 101% sure to have not truncated nor deleted any essential table. In all cases, I have obviously several backups from the previous mysql, which is actually still on the first vps and seems to work (but as I said, running mysql & apache on the same machine is in my case unsuitable).

Facts that I guess may help the generous
reader who feels like helping:
1) there is a table called
NODE_TYPE_ in the database (sic). This
seems strange. But I may be wrong.

2) In some cases, checking user visits,
it seems that the administrator
resulted as "latest visitor" of himself;
it may be a hint of some sort of dublicate
entry in the DB of which i am not aware of,
regarding the uid1. If so, I wonder where
this may have been inserted.

If you are kindly going to help, I would like you
to notice the already tried solutions that didn't
clear the issue:

--controlled, analyzed, repaired all tables in the db with success;

--ensured that the node_access is perfectly functuional and configured;

--emptied all possible caches, including the VIEWS one;

--uninstalled/updated any module that seemed to interfere;

--until the issue is solved THROTTLE IS DISABLED, so this is NOT
an effect of that module in case of heavy traffic.

--addressed & rectified any kind of problem causing warnings
present in watchdog, in case they could indirectly lead to
solve also the problem described here.

--CAC_LITE is not installed and not active.

THANKS in advance for the help and
ing eneral for mantaining and expanding
the best OSS CMS available today on the web,
hand down.