T.R | Title | User | Personal Name | Date | Lines |
---|
1359.1 | | STAR::PARKE | True Engineers Combat Obfuscation | Mon Jan 13 1997 13:38 | 6 |
1359.2 | posix_init-f-init_error posix v3.0 vms vax 7.1 | VMSNET::K_DECOUX | | Mon Mar 03 1997 12:25 | 27 |
| Hi Bill,
I've got a customer seeing a problem after upgrading. He was okay at
Version 2.0 vms 6.2 vax, but saw this after upgrading to 3.0 vms 7.1 :
The call from POSIX$STARTUP to run sys$system:posix$init generates
this error:
%Posix_Init-F-INIT_ERROR, initialization routine failure
and then when POSIX$STARTUP attempts to invoke POSIX (with the command
$ posix posix$bin:sh. "-l /cont/etc/posix_start.rc") it fails with
this error:
%POSIX-F-CTXNOTINI, POSIX system initialization not completed -
see system manager
Does this have anything to do with fork problem you mentioned earlier or
is this something else.
Thanks in advance for your help.
Karen
vmsnet::k_decoux
CSC
|
1359.3 | VAX needs help with V3.0/V7.1 combination, Alpha OOK. | STAR::PARKE | Sometimes pigeon, Sometimes statue | Mon Mar 03 1997 14:00 | 14 |
| Posix V3.0, VAX only, currently (I'm working on it) has problems. I
would be interested in knowing the configuration of the customer system
(are they also running UCX and what version) as these results are a lot
less spectacular than mine (with the Raw V3.0 kit).
I suspect it has to do with the fork problem, but my system did not
survive the raw kit starting up. (It would install and crash in
startup).
There will be at least an image replacement kit needed to get it
working, and I will make it available as soon as I can.
Bill
|
1359.4 | VMS 7.0 w/UCX 4.0 | CSC32::M_MENKHUS | Mark Menkhus (719)531-5853 @home) | Thu Mar 06 1997 00:50 | 27 |
| The system having the problem reported in .0 is as follows:
UCX> show version
Digital TCP/IP Services for OpenVMS VAX Version V4.0
on a MicroVAX 3100 running OpenVMS V7.0
There are no other errors reported prior to the error message:
$ run sys$system:posix$init
%Posix_Init-F-INIT_ERROR, initialization routine failure
The next failure is:
$ posix posix$bin:sh. "-l
/cont/etc/posix_start.rc"
%POSIX-F-CTXNOTINI, POSIX system initialization not completed - see
system manag
er
$abort:
$ say "POSIX for OpenVMS startup aborted."
POSIX for OpenVMS startup aborted.
Do you recommend we IPMT the problem? This doesn't seem to be the
typical problem where we can delete the container and rerun
posix$config to fixup whatever went wrong :-)
I checked the release notes for 4.0, and any of the patches for 4.0,
doesn't seem to be too much changes in the CFS area. Do you think a
newer UCX would help?
-Mark Menkhus
|
1359.5 | 7.0/3.0 should work | MUCTEC::BECKER | Hartmut B., VMS & Languages, Munich | Thu Mar 06 1997 06:22 | 11 |
| > on a MicroVAX 3100 running OpenVMS V7.0
^^^^
That's different from .0. V7.0 and Posix 3.0 should work. It looks like a setup
problem. Unfortunately the error message isn't very descriptive. It was
mentioned that posix$config.com already ran. Did you change anything else
during the upgrade? The label of the system disk? Did you try to repair the
container? Are the posix loadable images loaded?
Hartmut Becker
|