Operating texis/webinator on a sun 64-bit E-250 server with 2Gb ram running solaris 2.7.
Commercial Version 3.01.962147411 of Jun 27, 2000 (sparc-sun-solaris2.6)
Running webinator searches, this machine has produced errors from the beginning. Kai provided some phone support several months ago, and a portion of the problem was identified as dns error. The dns was corrected but errors persist.
Here is the string that is being executed:
nohup gw -d/database -noindex -a -R -r -O -fshtml -fasp -fcfm -fjsp -fxml -t7 -z5000 -v4 "&list" > nohup.a
After the todo list grows, then additional gw strings are executed:
nohup gw -d/database -noindex -a -R -r -O -fshtml -fasp -fcfm -fjsp -fxml -t7 -z5000 -v4 > nohup.b
When I run multiple strings of gw, almost all of them die within a few hours, giving the message
000 Got signal 11 - quitting now
or
000 Got signal 10 - quitting now
According to the manual "UNIX Unleashed" description of kill signals:
10 Bus Error. Usually caused by a programming error, a bus error can be caused only by a hardware fault or a binary program file.
11 Segment violation. Caused by a program reference to an invalid memory location; can only be caused by a binary program file.
I suspect bad ram.
Before I approach Sun tech support again, I would like to know if you have seen this before, and if there is any chance it could be a software error.
Texis has been re-installed on this machine several times and it has not solved the problem.
I am running commercial webinator on a linux machine, using the exact same gw strings, and never have any problem.
Commercial Version 3.01.962147411 of Jun 27, 2000 (sparc-sun-solaris2.6)
Running webinator searches, this machine has produced errors from the beginning. Kai provided some phone support several months ago, and a portion of the problem was identified as dns error. The dns was corrected but errors persist.
Here is the string that is being executed:
nohup gw -d/database -noindex -a -R -r -O -fshtml -fasp -fcfm -fjsp -fxml -t7 -z5000 -v4 "&list" > nohup.a
After the todo list grows, then additional gw strings are executed:
nohup gw -d/database -noindex -a -R -r -O -fshtml -fasp -fcfm -fjsp -fxml -t7 -z5000 -v4 > nohup.b
When I run multiple strings of gw, almost all of them die within a few hours, giving the message
000 Got signal 11 - quitting now
or
000 Got signal 10 - quitting now
According to the manual "UNIX Unleashed" description of kill signals:
10 Bus Error. Usually caused by a programming error, a bus error can be caused only by a hardware fault or a binary program file.
11 Segment violation. Caused by a program reference to an invalid memory location; can only be caused by a binary program file.
I suspect bad ram.
Before I approach Sun tech support again, I would like to know if you have seen this before, and if there is any chance it could be a software error.
Texis has been re-installed on this machine several times and it has not solved the problem.
I am running commercial webinator on a linux machine, using the exact same gw strings, and never have any problem.