SYSMGR

We're a bunch of Computers: Diana, Daphne, and Dido, called the 3D-cluster, running OpenVMS, Io running OpenVMS as well (in some obscure role in the network) Aphrodite, Athene and Irene running WindowsXP-Pro (SP2, of course) and Cerberus at the edge of the Network, with Charon, also running Linux, as standby. SYSMGR takes care of us.

Wednesday, February 8

08-Feb-2006

Error corrected
It seems the error was coreected, all was normal today.
Apache trouble since last reboot
Well, not really, just that Tomcat isn't running. But that's not new.

Diana's site-specific startup procedure (SYSTARTUP_VMS.COM) is devided in two: one part running in forefront, that is directly invoked by STARTUP.COM (the basic boot procedure that comes withn OpenVMS and should not be altered), taking part of the stuff that is considered "basic". The rest is submitted to batch at it's end, so as soon as this job is submitted, I have access to the system using the console while the rest is still being prepared. And: I get a log, regardless the SYSGEN settings (and on a predefined, self-defined location).

This batch procedure starts TCPIP, enables the usage of programming languages (likely: it just loads the privileged parts of compilers, SDK members and alike), starts databases, and will also start Apache the Diana way, using a commandprocedure. One more, indeed, but with a reason: It starts all Apache based stuff in the right order.
Starting Apache implies starting Tomcat beforehand, to be able to use Tomcat's facilities. In that proces, apache$tomcat.exe is startwed as a detached proces. However, in some way, this fails with an RMS error: File not found, or File protection violation... I have to check accounting and audit for the exact message, but I think it is an issue with SYS$OUTPUT, SYS$ERROR or SYS$OUTPUT, since the problem does not occur when started from the terminal.
Apache has no problem that Tomcat isn't running. It will come available.
So normally, I stop the webserver and run the startup procedure that is normally executed by the batch procedure.
But this time, I didn't.

Since Tomcat isn't started, Java cannot be started from the web, nor will .JSP-files be serviced. I have none so it is not really an issue. Even better: it frees resources: Tomcat is written in Java and consumes quite a lot of CPU, memory and IO even doing nothing at all.

So I decided to leave it for the moment.

0 Comments:

Post a Comment

<< Home