adweitzsacker Absent Member.
Absent Member.
1479 views

NW6.5 SP7 edir 8.7.3.9 -> 8.7.3.10b won't reboot

This is a real problem at this moment.

I went through all the normal prep work & tested out multiple times
applying a series of NW6.5 post SP7 updates for our main academic & root
partition server.

Now the after applying

TCP681K
iprntnw65sp7b
novpatch14261
wsock6o
nwlib6l
scsihd-sp7b
edir873sp10b

The server WILL NOT BOOT. I suspect a problem with eDir, but right now
I just want to bring it up far enough to get networker to reload so I
can do a full restore of the SYS volume & server specific info.

I will be looking for TIDs in the support site, but before I pull out my
credit card & call Novell - yes, I DID get a DSR_DIB (dsrepair -rc) backup prior to upgrade, I'm hoping someone is out there than can help me out. It is
5:25am EDT in Buffalo, NY, USA.

This is a NW6.5 SP7 which was running eDirectory 8.7.3.9.

On reboot after edir, it hung at httpstk - eventually it came up with
"...process will be set to a safe state" msg, then rebooted the
system. I stepped through with F8 (maintenance mode), and it appears
DS.NLM 10554.34 loaded OK, but then the system hung as it got to the
search add sys:\java\bin line (had to be just a timing thing).

I just mailed this msg to the Novell list out there (Joe Doupnik's realm), but I'm hoping to get an answer soon.

My main question at this late moment: How do I get the server to boot
to the point that I can load Legato Networker to do the restore.

--alan

Alan D Weitzsacker, System Administrator III Canisius College, Buffalo, NY
Labels (2)
0 Likes
7 Replies
adweitzsacker Absent Member.
Absent Member.

Re: NW6.5 SP7 edir 8.7.3.9 -> 8.7.3.10b won't reboot

Update: Ended up opening a service call. End result for fix
was to do a down server upgrade using the NW65 SP7
media. This ended up bringing this server up to eDirectory
8.8 SP2. The engineer I was working with checked with
an eDirectory engineer & this should not affect how things
work being in a tree with mostly 8.7.3.9 servers.

Initially I find that NRM is not working, but am running a
dsrepair on the local database.

PKIDIAG & SDIDIAG come up good for both. I still need to
look at what of my prior post-SP7 updates may need to be
reapplied, but the server seems to be usable at this point.

The recommendation from support was to NOT do a restore
after bringing the system back up, that this could potentially
cause other issues.

So much for the testing I did prior to scheduling these upgrades.
That coupled w/too few restarts when applying some of these
updates. Worked in testing, but not in reality.

--alan

Alan D Weitzsacker, System Administrator III Canisius College, Buffalo, NY
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NW6.5 SP7 edir 8.7.3.9 -> 8.7.3.10b won't reboot

Personally if I had trouble with 873x and a novell engineer said upgrade
to 882--I would ask to be transferred to another engineer.

Just be aware of the requirements for 882 now---ie netmail versions,
zenwork versions, etc.

On Mon, 28 Jul 2008 14:26:02 +0000, adweitzsacker wrote:

> Update: Ended up opening a service call. End result for fix was to do a
> down server upgrade using the NW65 SP7 media. This ended up bringing
> this server up to eDirectory 8.8 SP2. The engineer I was working with
> checked with an eDirectory engineer & this should not affect how things
> work being in a tree with mostly 8.7.3.9 servers.
>
> Initially I find that NRM is not working, but am running a dsrepair on
> the local database.
>
> PKIDIAG & SDIDIAG come up good for both. I still need to look at what
> of my prior post-SP7 updates may need to be reapplied, but the server
> seems to be usable at this point.
>
> The recommendation from support was to NOT do a restore after bringing
> the system back up, that this could potentially cause other issues.
>
> So much for the testing I did prior to scheduling these upgrades. That
> coupled w/too few restarts when applying some of these updates. Worked
> in testing, but not in reality.
>
> --alan


0 Likes
beelsr Frequent Contributor.
Frequent Contributor.

Re: NW6.5 SP7 edir 8.7.3.9 -> 8.7.3.10b won't reboot


well, it's bit late to try Jeff's method but i would ask for my $$$
back. and push the issue if you meet resistance.

Upgrading your tree to 8.8 is a pretty painless upgrade - lots of
threads over in the edir groups. Schema is always the big thing in an
edir upgrade, IMO.


--
Cheers!
Richard Beels
~ Network Consultant
~ Sysop, Novell Support Connection
~ MCNE, CNE*, CNA*, CNS*, N*LS



-- Cheers! Richard Beels ~ Network Consultant ~ MCNE, CNE*, CNA*, CNS*, N*LS
0 Likes
210768m11227 Absent Member.
Absent Member.

Re: NW6.5 SP7 edir 8.7.3.9 -> 8.7.3.10b won't reboot

hi, i didnt understand that. have you make on the defective server a downgrade by booting from nw65 sp7 overlay cdrom, and install the server new,
or did you start the defetive server, and stert the gui , and start the installation from the server gui with the nw65 sp7 overlay cd rom?

or have you installed a new server ? with the media NW65sp7overlay?

helge
0 Likes
Knowledge Partner
Knowledge Partner

Re: NW6.5 SP7 edir 8.7.3.9 -> 8.7.3.10b won't reboot

HI,

210768m11227 wrote:
>
> hi, i didnt understand that. have you make on the defective server a
> downgrade by booting from nw65 sp7 overlay cdrom, and install the
> server new,
> or did you start the defetive server, and stert the gui , and start the
> installation from the server gui with the nw65 sp7 overlay cd rom?


Neither. He booted from the SP7 overlay CD and did a "down server
upgrade". Which, oddly though, is officially not supported by Novell.

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
adweitzsacker Absent Member.
Absent Member.

Re: NW6.5 SP7 edir 8.7.3.9 -> 8.7.3.10b won't reboot

After determining that we could not identify which update caused
the startup problem, and still having an unbootable production server,
we first backed up & then deleted the registry files. Then went
through loadstage steps for startup. All looked OK, with the exception
of hanging, then abending, but writing NOTHING to the abend.log.

This is when the next step was to do a down server upgrade using
the SP7 overlay CDs. The engineer was convinced that using the SP7
overlay would not upgrade eDirectory. While I was doing this, he
had run through a similar test and had the results of only upgrading
to 8.7.3.9. Perhaps it was due to already having 8.7.3.10b on this
server at the time of upgrade that caused 8.8 SP2 to install.

The down server upgrade left most of what was out there still
working. I didn't need to reinstall ZDM, nor our backup software.
Our Netware servers are used for file and print primarily, not as
application servers. This actually helped in this case.

It was not intended to upgrade to eDir 8.8, least of all on
my root partition server. I have yet to check that we got a good
backup overnight.

IF something is broken, I'll be back on the phone to Novell on
figuring out how to downgrade.

Alan D Weitzsacker, System Administrator III Canisius College, Buffalo, NY
0 Likes
Knowledge Partner
Knowledge Partner

Re: NW6.5 SP7 edir 8.7.3.9 -> 8.7.3.10b won't reboot

Hi,

adweitzsacker wrote:
>
> This is when the next step was to do a down server upgrade using
> the SP7 overlay CDs. The engineer was convinced that using the SP7
> overlay would not upgrade eDirectory.


Oh great. And he also wasn't aware that doing a down server upgrade
isn't supported starting with SP7 overlays it seems. 😞

> While I was doing this, he
> had run through a similar test and had the results of only upgrading
> to 8.7.3.9. Perhaps it was due to already having 8.7.3.10b on this
> server at the time of upgrade that caused 8.8 SP2 to install.


No. A down server upgrade with unaltered SP7 overlays will always
install eDir 8.8. There's a possibility though to alter the overlay so
that it doesn't do that.

> The down server upgrade left most of what was out there still
> working. I didn't need to reinstall ZDM, nor our backup software.
> Our Netware servers are used for file and print primarily, not as
> application servers. This actually helped in this case.


It did, and in the end that is what counts, but you were really lucky.
The update to eDir 8.8 using this method tends to fail quite often so
that DS aftewards won't open at all.

> IF something is broken, I'll be back on the phone to Novell on
> figuring out how to downgrade.


You can't, unless you restore your whole eDir tree. eDir 8.8 is a
one-way road.

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.