08-11-05 10:46 PM
Some progress is being made. I did what the logger screen said :-). There was no RootCert.der fi
le in sys:public, so I re-exported, and ran tckeygen. So, tcadmup / tomcat4 now work w/o the erro
rs on the logger screen. I also am now able to get to https://ip_address:8009 and [url
]https://ipaddress:636[/url] to verify SSL and LDAP are working. However, I don't
think I'm getting Apache loaded.
I type AP2WEBUP and it seems to load on the logger screen - although under v2 I'm not s
ure what I'm supposed to see. It doesn't show any ports listening like 1.5 did. Also,
when I type AP2WEBDN, it says that APACHE2 is not loaded. I cannot get to the main we
b page http://servername either.
I also get an error on the logger screen when I attempt to unload Tomcat4 us
ing TC4STOP. Its main error is 'Connection Refused'. Not sure if this is c
osmetic or not or, if not, how to fix it.
Ideas where to start? I'm thinking I need to put Apache on the secondary IP
address I added like I did under 1.5 due to iPrint conflicts, but when I di
d that under 1.5 I modified the adminserv.conf file's SecureListen line and
the portal IP within iManager. My current sys:\adminserv\conf\ adminserv.co
nf file is 0 bytes. Could I possibly copy it from a 6.0 SP5 server since th
is one is my only OES/6.5 server? Or should I still go ahead and perform a
'down server upgrade' on this production server?
Thanks - April
"April Simmons" <aprilamey@cox.net> wrote in message news:AiwKe.2671$RK5.132
2@prv-forum2.provo.novell.com...
We did our first 6.0 Sp5 to OES SP3 (iso) upgrade and had some trouble. Bri
efly, we took the CD out when it did its initial reboot and we're thinking t
hat caused the problem. It just kept going in a circle on each reboot - bri
nging up the GUI, and when it started to install all the chosen products, it
said each one failed. It eventually came up to the dreaded colon prompt wi
th no server name. Called tech support and he had me delete the c:\nwserver
\config.nw file and it came back up. He suggested using the down server upg
rade to make sure all products were installed, but it was rather late and we
saw a server name and could login :-). Obviously, now I'm thinking that wa
sn't a very smart move.
The server has been up and running for a week fine though. The CA is a serv
er up at HQ - not this one. All other servers besides this one are at 6.0 S
P5. I'm wondering if I'm seeing Cert issues because I didn't do one of the
2 replica servers at Corporate first. The server we did does NOT hold a rep
lica of the root partition if that could be the problem. I ran deployment m
anager first - all steps - and received no errors.
I'm working on getting the web server to work and I'm seeing some weird issu
es with certificates, imanager, and apache. I'm also not sure which command
s belong with the old apache server as things weren't removed or remmed in a
utoexec due to the upgrade issues. Is portal still supposed to be loading?
- When I type tcadmup, the logger screen shows the following error:
Problems with Security Certificate. Re-export sys:\public\RootCert.dir and
then execute sys:system\tckeygen.ncf.
Load NLDAP (it is loaded by the way)
- \adminserv\conf\ The adminserv.conf is 0 bytes. -
Just when I had finally learned where all those config files were, Novell we
nt and moved them on me :-). Oh well.
I ran pkidiag with no errors. I went into the NDS IP and DNS objects and cl
icked validate and received no errors. No other servers are having Certific
ate issues.
- I see 636 listening
What is my best approach in this situation? Maybe bring it down and perform
a down server upgrade just like he suggested?
Thanks - April
[ Post a follow-up to this message ]
| 
