It's hard to say what exactly happened. Perhaps you have some odd custom module which caused the problem on hook_cron?

In Drupal 6, when users are deleted using user_delete(), any nodes authored by that user are set to be authored by "Anonymous" (user uid=0). See http://api.drupal.org/api/drupal/modules--node--node.module/function/node_user/6


On Wed, Feb 23, 2011 at 10:21 AM, Pat Newberry <drupal@gypsyfarm.com> wrote:

Well I got the page back up. After reading thru several blogs and logs, found one fellow that mentioned that the UID (user id)  on a node did not have a corresponding record in the USER table.  I checked and sure enough the UID in the NODE table did not have a USER record. So I change to my UID for the node having problems and sure enough I  got my form back.

 Of course the $64 question is why did it change?  Why would running a drupal cron job either remove a user record (assuming that is what happened) or change the UID on a node records?  … Still working on that one.

 

Pat




On 2/21/2011 12:49 PM, Pat Newberry wrote:
I have a webform that is pretty long. Been working just fine. I pressed 
the cron update (manual) button today from the reports link on one of 
the admin screens in  drupal.

Suddenly my web form  (node/3) was displaying the  page not found error 
messsage.

<snip>

Pat




--
[ Drupal support list | http://lists.drupal.org/ ]