Hello to everyone.
I would like to thank everyone who responded to my plea for help. Most
especially, I would like to thank Daina, Rolf, Vlad, Jeff H., Tim, L.S.,
Brian, Bill, Eric, Sekar, Jerry, Pat, Jeff S. and Robert for all of the
help, kind support and insights.
In the end, I received a lot of really great suggestions that all headed in
the same direction - there was a hardware issue. After speaking with the
Technical Assistance Center at Varian, I received a new CPU board, and
Ethernet Board and a new Ethernet Cable. I installed them yesterday and
have been putting the system through the paces. I am VERY excited to report
that for the first time in a very long time, I was able to acquire 30K scans
and am now back up and running the 2D experiements.
Thank you again for the wonderful help and support.
Adrienne
Adrienne B. Hoeglund
NMR Specialist
AOC, LLC.
950 Highway 57 East
Collierville, TN 38017
(901) 854-2800 ext. 532 - work
(901) 853-1582 - fax
www.aoc-resins.com <
http://www.aoc-resins.com>
*******************************************
Original e-mail:
At 12:09 PM 6/9/2005, you wrote:
Hello to everyone.
Over the last several months, our Mercury system has been experiencing
problems with staying connected during carbon acquisitions. Regardless of
whether I run 256 scans or 1024 scans, the run does not complete the number
of scans. A perfect example was about 30-minutes ago I tried to run
256-scans. The system stopped acquiring at 112-scans. When it does that,
it looses connection with the console and I have to type su acqproc at least
two or three times to get the system to reconnect. When it finally does
connect, it takes it a few minutes to respond.
We are currently on a full service contract with Varian but the problem is,
we lost our service technician back around Christmas and now one of the guys
from up North is having to do not only his area, but ours. Needless to say,
he is very busy. So, before I hassle him and set up a service call, I
thought I would come to you all to see if you have any suggestions as to
what could be causing this.
I have included the set of error messages I got from today's run (these are
the same on every run that stops). Let me reiterate that this is ONLY
happening when carbon acquisitions are occurring.
Error messages:
Sun Microsystems Inc. SunOS 5.8 Generic Patch October 2001
Bucky:Adrienne 1>su acqproc
Jun 9 12:44:57 Bucky su: 'su acqproc' succeeded for Adrienne on /dev/pts/5
Starting 'Acqproc'
Bucky:Adrienne 2>Broadcast Message from root (console) on Bucky Thu Jun 9
12:44:58...
Acquisition Console Ready.
getACQstatus(): i=-1
acqhandler(): Pos6 getACQstatus error ... Rebooting console??: Connection
timed out
getACQstatus(): i=-1
acqhandler(): Pos6 getACQstatus error ... Rebooting console??: Connection
timed out
Bucky:Adrienne 2>sugetACQstatus(): i=-1
acqhandler(): Pos6 getACQstatus error ... Rebooting console??: Connection
timed out
acqproc
Killing 'Acqproc'.
AcqProc(): Termination Signal Received
Broadcast Message from root (console) on Bucky Thu Jun 9 12:45:38...
Acquisition Daemon Terminated.
Bucky:Adrienne 3>su acqproc
Starting 'Acqproc'
Bucky:Adrienne 4>Broadcast Message from root (console) on Bucky Thu Jun 9
12:45:57...
Acquisition Console Ready.
getACQstatus(): i=-1
acqhandler(): Pos6 getACQstatus error ... Rebooting console??: Connection
timed out
Jun 9 12:45:57 Bucky last message repeated 2 times
SendAsync(): Max trys Exceeded, aborting send
Problems sending message
Bucky:Adrienne 4>
Thank you in advance for your help.
Adrienne
Received on Tue Jun 14 2005 - 16:16:12 MST