I saw
this one time in the past, it was because $DBDIR/odb.adj was
missing.
If you
untar the managed node file from a recent ODB backup, and then restore the
odb.adj from there it should resolve the problem.
James Bale
Lead
Noctambulist
EDS
- Americas Tools & Automation
Auburn Hills, MI
Hi;
I have one gateway that is
failing to start oserv after installing 4.1.1-TMF-0010
There are only 2
hits from the the IBM support site and none from the list archive.
All
indications lead to re-install the managed node. Does anybody have any
pointers
to recover this managed node before I spend the time to rebuild
it ?
Thanks
Scot
2005/01/26 09:43:39 +05:
!WARNING: oserv_boot_info returned error 30
2005/01/26 09:43:39 +05:
!oserv: could not set configured network security
2005/01/26 09:43:39
+05: netsec_flags=0xffffffff,
comm_error=25, netsec_e
rror=0