Data Server of Availability Manager V3.1 won't start on VMS 8.3 (Alpha)

[Jan van den Boogaard_1]

The Data Server of Availability Manager V3.1 won't start on VMS 8.3 (Alpha).

I have 2 test systems: a 7.3-2 system and a 8.3 system, both ES45. Both configurations are similar, all recent patches.

I start the Data Server in a batch proces, like this, on both machines:


$ set noon
$ SET PROCESS/NAME="AvailDataServer"
$ AVAIL/SERVER/PORT=9819

This works fine on 7.3-2, the log file displays this:


$ IF APP_OPTION .EQS. AM_ANALYZER
$ ELSE
$ JAVA_CMD = "JAVA ""-cp"" " + -
"""" + AM_CLASSES + """ " + -
JVM_QUALIFIERS + " " + -
"""" + JRE_MAIN_CLASS + """ " + -
"""-port"" 9819 "
$ ENDIF
$! SHOW SYMBOL JAVA_CMD
$ JAVA "-cp" "/amds$am_system/AvailMan.jar:/amds$am_system/AvailManImages.jar:/amds$am_system/AvailDocs.jar" "-Xms48m" "-Xmx64m" "com.compaq.am
.server.ServerMain" "-port" 9819
StatusLogger. - Opened log file AM_Server_20100825-0200.log for output
Wed, Aug 25th 02:00:41.354 Platform attributes, OS name and version = OpenVMS V7.3-2
Wed, Aug 25th 02:00:41.370 ** Log file opened for output **
Wed, Aug 25th 02:00:41.374
Wed, Aug 25th 02:00:41.379 HP Availability Manager Server V3.1 (build 1198)
Wed, Aug 25th 02:00:41.380 © 2009, Hewlett-Packard Development Company, L.P.
Wed, Aug 25th 02:00:41.393
Wed, Aug 25th 02:00:41.395 List of Data Server options:
Wed, Aug 25th 02:00:41.397 Arg[0] = -port
Wed, Aug 25th 02:00:41.401 Arg[1] = 9819
Wed, Aug 25th 02:00:41.415 Processing Data Server options:
Wed, Aug 25th 02:00:41.417 Found -port 9819 option
Wed, Aug 25th 02:00:41.419 Port 9819 processed
Wed, Aug 25th 02:00:41.524 Network adapters found on this system
Wed, Aug 25th 02:00:41.525 SYS$RMDRIVER - default Ethernet adapter
Wed, Aug 25th 02:00:41.525 [9819] Server mode is secure.


But on V8.3, the java command stopts without error, so the batch process terminates vey quickly and the logfile shows this:


$ IF APP_OPTION .EQS. AM_ANALYZER
$ ELSE
$ JAVA_CMD = "JAVA ""-cp"" " + -
"""" + AM_CLASSES + """ " + -
JVM_QUALIFIERS + " " + -
"""" + JRE_MAIN_CLASS + """ " + -
"""-port"" 9819 "
$ ENDIF
$! SHOW SYMBOL JAVA_CMD
$ JAVA "-cp" "/amds$am_system/AvailMan.jar:/amds$am_system/AvailManImages.jar:/amds$am_system/AvailDocs.jar" "-Xms48m" "-Xmx64m" "com.compaq.am.server.Server
Main" "-port" 9819
StatusLogger. - Opened log file AM_Server_20100825-1122.log for output
$! SHOW SYMBOL $STATUS
$ !
$ SAVE_VERIFY = F$VERIFY(SAVE_VERIFY)
$ !
$RESTORE_PRIVS:
$ ! Restore privs to input state
$ RESETPRIVS = F$SETPRIV(OLDPRIVS)
$ !
$ !
$ EXIT
$ EXIT
AVAIL_MGR job terminated at 25-AUG-2010 11:22:34.71


The job runs under a special account AVAIL_MGR:

Username: AVAIL_MGR Owner:
Account: UIC: [3770,100] ([AVAIL_MGR])
CLI: DCL Tables: DCLTABLES
Default: INFRA$DISK:[CLUSTER.AVAIL_MGR]
LGICMD:
Flags:
Primary days: Mon Tue Wed Thu Fri
Secondary days: Sat Sun
No access restrictions
Expiration: (none) Pwdminimum: 8 Login Fails: 0
Pwdlifetime: (none) Pwdchange: 24-AUG-2010 17:52
Last Login: 24-AUG-2010 17:53 (interactive), 25-AUG-2010 11:22 (non-interactive)
Maxjobs: 0 Fillm: 4096 Bytlm: 2000000
Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0
Maxdetach: 0 BIOlm: 150 JTquota: 4096
Prclm: 8 DIOlm: 150 WSdef: 4096
Prio: 4 ASTlm: 300 WSquo: 8192
Queprio: 4 TQElm: 100 WSextent: 16384
CPU: (none) Enqlm: 30000 Pgflquo: 2100000
Authorized Privileges:
NETMBX OPER SYSPRV TMPMBX
Default Privileges:
NETMBX OPER SYSPRV TMPMBX


The netwerk interfaces are all oke.
Any clues what might be wrong?

[H.Becker]

Is there any clue in the "Opened log file"? From what I see, Java starts up and runs the ServerMain, which very likely prints the "StatusLogger. ..." message.

With the AVAIL_MGR account being the same, I would check system resources. Java is known to use many of them. There may be some information on the required resources in the Availability Manager documentation.

I would start with "$ mc sysgen show channelcnt"

[Jan van den Boogaard_1]

Thanks for your reply.
The opened log files are complete empty on both nodes.
Also AMDS$AM_RUN_DEBUG and _VERIFY dont help.

The systems do apply to the requirements in the A.M. install.guide.

Also I ran
[HP.SVCTOOLS.COMMON.JRE.LIB]JAVA$CHECK_ENVIRONMENT.COM

Channelcnt is 4096 on both systems , this should be oke.

[abrsvc]

Check accounting for the process termination status. Also, if you can do this without major problems, turn on image accounting just before you launch the app and terminate it after it stops. Look at the accounting records for any error conditions. A crude but effective way to get a pointer to the problem, hopefully...

Dan

[H.Becker]

Which Java version[s]?

You can add a -verbose (default is class) to the Java command, it will generate a lot of output. But I'm not sure if it will get you any closer to the root of the problem.

I would still check the used resources with accounting, show proc/acc or anal/sys. I do remember an entry in this forum about a problem running java, which worked interactively but failed in batch. Unfortunately I can't find it at the moment. I think to remember it was a resource problem.

[Jan van den Boogaard_1]

First of all, I discovered that this problem is also with V3.0-2 and also with the Data Analyzer on both versions on VMS V8.3 !

I turned on accounting, see the appended file for the output.

Also -verbose doesnot give any extra output at all....

And i found out that there is no difference between interactive and batch. I begin to suspect that the Java version 1.5.0-3 is not supported on V8.3.....


$ !
$ JAVA -version
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition
Fast VM (build 1.5.0-3, build J2SDK.v.1.5.0:03/01/2007-21:16, native threads, jit_150)
$ JAVA -fullversion
java full version "1.5.0-3"

[Jan van den Boogaard_1]

The lastest version 1.5.0-6.p1 doenst solve anything.....

See all output in the attachment....


$ !
$ ! The following information is needed by the Java
$ !
$ JAVA -version
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition
Fast VM (build 1.5.0-6.p1, build J2SDK.v.1.5.0:11/16/2009-20:33, native threads, jit_150)
$ JAVA -fullversion
java full version "1.5.0-6.p1"

[Hoff]

The Availability Manager kits have tended to include their own JRE, and this version is no different, and the integrated Java stuff has definitely require specific patches to keep it from tipping over. The AMDS, err, sorry, my bad, AvailMan stuff wasn't using the system version of Java or the JRE.

I recall seeing some directions posted for swapping out the integrated JRE, but I'd only tend to try that as a last resort or at the direction of HP support.

Following a chain of URLs to get to the requisite list of ill-formatted and ill-named patches for Java5, you need to have these ECO kits loaded:

All Rating 1 ECO kits for OpenVMS Alpha V8.3
Whatever the TCP/IP Services V5.6 current ECO
VMS CRTL V5 or later
VMS PTHREAD V1 or later.

If you have software support and if you have the requisite patch kits installed, then call HP.

[Jan van den Boogaard_1]

Problem solved........

I started 3.0-2 data server on yet another node and this showed one extra very subtle line......

$ set noon
$ SET PROCESS/NAME="AvailDataServer"
$ AVAIL/SERVER/PORT=9819
$ GOTO START
$START:
$ IF F$TRNLNM("AMDS$AM_RUN_VERIFY")
$ ELSE
$ SAVE_VERIFY = F$VERIFY(0)
%AMDS-I-SERVERPORT, using port 9819 for Data Server
StatusLogger. - Opened log file AM_Server_20100826-1933.log for output
Thu, Aug 26th 19:33:58.993 Platform attributes, OS name and version = OpenVMS V7.3-2
Thu, Aug 26th 19:33:59.002 ** Log file opened for output **
Thu, Aug 26th 19:33:59.003
Thu, Aug 26th 19:33:59.004 HP Availability Manager Server V3.0-2 (build 1194)
Thu, Aug 26th 19:33:59.011 © 2009, Hewlett-Packard Development Company, L.P.
Thu, Aug 26th 19:33:59.012
Thu, Aug 26th 19:33:59.012 FATAL - Missing key file AM$KeyStore.jks
$ !
$RESTORE_PRIVS:
$ ! Restore privs to input state
$ RESETPRIVS = F$SETPRIV(OLDPRIVS)
$ !
$ !
$ EXIT
$ EXIT
AVAIL_MGR job terminated at 26-AUG-2010 19:33:59.14


So, no key in the key store, very easy to fix.

Thanx for tips and help.

[Jan van den Boogaard_1]

Thu, Aug 26th 19:33:59.012 FATAL - Missing key file AM$KeyStore.jks

So, no key in the key store, very easy to fix.

Thanx for tips and help.