We're running Texis 3.01.971289085 of Oct 11, 2000 on our Tru64 Alphaserver. When building indexes on a table the monitor log is showing the above error. Can you shed any light on what might be happening? Is this something we should worry about? The indexes seem to be functioning correctly having been built.
Fork failed in the function Check Index
-
- Posts: 6
- Joined: Fri Jan 17, 2003 4:02 am
Fork failed in the function Check Index
Is there any further message as to why the fork failed? The Check Index is the process that makes sure the indexes are kept up to date. It will try again. If the message keeps happening then your indexes may become less efficient over time. If it only occurs once or twice it is probably not worth worrying about, although it may indicate that you were pushing the machine to its limits.
John Turnbull
Thunderstone Software
Thunderstone Software
-
- Posts: 6
- Joined: Fri Jan 17, 2003 4:02 am
Fork failed in the function Check Index
No. No other messages in the log to suggest why it has happened. However, since I posted my message, I've been doing a bit of digging. I think what's happening is that the maximum number of processes is being reached and that's what is causing the problem. I have our hosting service system admin looking into it as I'm seeing other messages (max_proc_per user) being displayed on the console.
Fork failed in the function Check Index
That would be the most likely cause. That will prevent the index being updated when a lot of other processes exist, but it should get updated later at a quieter time (assuming there is one).
John Turnbull
Thunderstone Software
Thunderstone Software