![]() |
![]() HP OpenVMS Systemsask the wizard |
![]() |
The Question is: Dear Wizard, I am working for a customer, who has a five node VAX cluster. (One MicroVAX 3400 Series ,two VAX 4000-300 and two VAX 4000-200 connected in DSSI cluster (RF72). All the nodes are running VAX/VMS 5.5 I am experiencing a serious problem with the UCX SMTP mail (which is enabled only on one node). The UCX mail server dies and the all the SMTP queues get stopped. The SYMBIONT processes eats up all the memory, and if un-attended, crashes the system. Generic server queue UCX$SMTP_NODE_00 Server queue UCX$SMTP_NODE_01, stopped, on NODE::, mounted form DEFAULT Server queue UCX$SMTP_NODE_02, stopped, on NODE::, mounted form DEFAULT Server queue UCX$SMTP_NODE_03, stopped, on NODE::, mounted form DEFAULT We used to restart the mail, if the symbiont is eating up the memory. $UCX STOP MAIL $UCX START MAIL and then... $UCX ANAL MAIL */REPAIR The operator log shows these errors.... *************** Message from user QUEUE_MANAGE on NODE %QMAN-E-SYMDEL, unexpected symbiont process termination %%%%%%%%%%% OPCOM 2-JUL-1999 10:04:08.73 %%%%%%%%%%% Message from user QUEUE_MANAGE on NODE -SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000, P0 3C00000 UCX version: ------------- UCX> show ver DEC TCP/IP Services for OpenVMS VAX Version V3.2 on a MicroVAX 3400 Series running OpenVMS V5.5 Any help will be very much appreciated! Thanks in advance Regards, Ganga The Answer is : Please seriously consider an OpenVMS and a TCP/IP Services upgrade, as neither OpenVMS VAX V5.5 nor TCP/IP Servces V3.2 have any support available at present. You will want to apply ECO 8 for TCP/IP Services V3.2, as a start. If this ECO kit fails to resolve your reported problems, you may well be required to perform an upgrade at least as far as OpenVMS VAX V5.5-2 and to TCP/IP Services V4.0 ECO 5. ECO kits are available at: http://search.service.digital.com/ As of 26-Jul-1999, the curreht OpenVMS VAX release is V7.2, and the current TCP/IP Services version is (now or very soon to be) V5.0A.
|