Anonymous_User Absent Member.
Absent Member.
2740 views

Apache Webserver for Administration not loading

I have an issue where my server is rebooting due to backup job issues.

However, I am concerned as it seems the Admin instance of apache is not loading
I cannot get to the server via NoRM https:server_ip:8009

Don't see any glaring reasons error or the like. I'm not sure what to look for.
As it always just loaded itself when the server started. I am unfamiliar
with loading it 'by hand'

what commands should i give to get it loaded? or to at least see errors
that might exisit when it does try to load.
Labels (2)
0 Likes
8 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Apache Webserver for Administration not loading

westmd2remove@nfis.com wrote:

> However, I am concerned as it seems the Admin instance of apache is not loading
> I cannot get to the server via NoRM https:server_ip:8009


NoRM doesn't use Apache. It uses it's on HTTP server, loaded via
httpstk.nlm. Depending on your version of NetWare, the "admin" instance
of apache is loaded via nvxadmup.ncf (nw 6.0) or admsrvup.ncf (nw 6.5)

> Don't see any glaring reasons error or the like. I'm not sure what to look for.
> As it always just loaded itself when the server started. I am unfamiliar
> with loading it 'by hand'


The most common reason for NoRM and/or Apache to not load are expired
certificates. Try running pkidiag on the server to see if your certs are
in good shape. If not, it will fix them.

--
Jim
NSC Sysop
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Apache Webserver for Administration not loading

I was able to get to SERVER1 via NoRM and Managed Servers link from SERVER2

Interstingly its on port 8008 (is that the non secure port? that is,
http:// vs https:// for port 8009?)

I used to be able to get directly to the SERVER1 with https://serverip:8009
but that seems broken at the moment. Yet I can get to NoRM via SERVER2 and
'make my way' to SERVER1 NoRM screen. It's there via http://servername:8008



My confusion on Apache stems from the following:
On My screens list I see
Apache 2.0.54 for Netware
*Apache2 Web Manager

I thought 1 was Apache for to host a website and the other was for Netware
's Administration. Since administration seems to have its own stack, why
the 2 instances?



> westmd2remove@nfis.com wrote:
>
> > However, I am concerned as it seems the Admin instance of apache is not

loading
> > I cannot get to the server via NoRM https:server_ip:8009

>
> NoRM doesn't use Apache. It uses it's on HTTP server, loaded via
> httpstk.nlm. Depending on your version of NetWare, the "admin" instance
> of apache is loaded via nvxadmup.ncf (nw 6.0) or admsrvup.ncf (nw 6.5)
>
> > Don't see any glaring reasons error or the like. I'm not sure what to

look for.
> > As it always just loaded itself when the server started. I am unfamiliar
> > with loading it 'by hand'

>
> The most common reason for NoRM and/or Apache to not load are expired
> certificates. Try running pkidiag on the server to see if your certs are
> in good shape. If not, it will fix them.
>
> --
> Jim
> NSC Sysop


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Apache Webserver for Administration not loading

westmd2remove@nfis.com wrote:

> Interstingly its on port 8008 (is that the non secure port? that is,
> http:// vs https:// for port 8009?)


Yep. NoRM listens on both ports.

> I used to be able to get directly to the SERVER1 with https://serverip:8009
> but that seems broken at the moment. Yet I can get to NoRM via SERVER2 and
> 'make my way' to SERVER1 NoRM screen. It's there via http://servername:8008


This would lend credence to my initial suspicion that your SSL
certificates are expired or otherwise corrupt, since you can get in via
non-SSL.

Again, run pkidiag to test/fix them.

> My confusion on Apache stems from the following:
> On My screens list I see
> Apache 2.0.54 for Netware
> *Apache2 Web Manager
>
> I thought 1 was Apache for to host a website and the other was for Netware
> 's Administration. Since administration seems to have its own stack, why
> the 2 instances?


You are correct that there are two instances of Apache on a normal NW6
box. Once is a general purpose instance that handles iManager and any
other additional things (like GroupWise webaccess). The other handles
some NetWare web-based management tasks, but that is NOT NoRM! Remote
Manager is it's own thing entirely. The reason for having a small,
special HTTP stack for it is that you wouldn't want to rely on Apache to
manage your server remotely... if Apache died, your access would be gone.
--
Jim
NSC Sysop
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Apache Webserver for Administration not loading

I ran PKIDIAG and it found 2 errors a fixed 2 errors.

I still have the same problem with NoRM.

I seem to have broken pkidaig. the Util doesn't require enter after
entering a menu number choice. The process run and want any key pressed to
continue, which it does by ending.

I went back into pkidiag, choose option 4(something about renaming if
neccessary) it showed what seemed to be 2 new option 5 & 6
I took 6 relazied that was not what i wanted. couldn't esc out of it.
cntrl c seem to end the process
but now pkidiag errors when trying to run

in CSS recovercode-1498
Error -1498 from CSS_Init
<press any key to continue>

Did I end up doing something real bad? Something a reboot would fix?



> westmd2remove@nfis.com wrote:
>
> > Interstingly its on port 8008 (is that the non secure port? that is,
> > http:// vs https:// for port 8009?)

>
> Yep. NoRM listens on both ports.
>
> > I used to be able to get directly to the SERVER1 with https://serverip:8009
> > but that seems broken at the moment. Yet I can get to NoRM via SERVER2 and
> > 'make my way' to SERVER1 NoRM screen. It's there via http://servername:8008

>
> This would lend credence to my initial suspicion that your SSL
> certificates are expired or otherwise corrupt, since you can get in via
> non-SSL.
>
> Again, run pkidiag to test/fix them.
>
> > My confusion on Apache stems from the following:
> > On My screens list I see
> > Apache 2.0.54 for Netware
> > *Apache2 Web Manager
> >
> > I thought 1 was Apache for to host a website and the other was for Netware
> > 's Administration. Since administration seems to have its own stack, why
> > the 2 instances?

>
> You are correct that there are two instances of Apache on a normal NW6
> box. Once is a general purpose instance that handles iManager and any
> other additional things (like GroupWise webaccess). The other handles
> some NetWare web-based management tasks, but that is NOT NoRM! Remote
> Manager is it's own thing entirely. The reason for having a small,
> special HTTP stack for it is that you wouldn't want to rely on Apache to
> manage your server remotely... if Apache died, your access would be gone.
> --
> Jim
> NSC Sysop


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Apache Webserver for Administration not loading

westmd2remove@nfis.com wrote:


> Did I end up doing something real bad? Something a reboot would fix?


I'd go for a reboot.

--
Cheers,
Edward
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Apache Webserver for Administration not loading

westmd2remove@nfis.com wrote:

> Did I end up doing something real bad? Something a reboot would fix?


I doubt you did anything bad.. most likely something of pkidiag is still
in memory and a reboot will fix it.

--
Jim
NSC Sysop
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Apache Webserver for Administration not loading

In the intrest of finality for anyone else with this problem.

I was able to reboot my server and all is well (as far as this problem is
concerned)

PKIDIAG is able to run again and I am able to get to my server via secure
NoRM (https://serverip:8009)

Now to learn about certificates and why this happened. My box is not truly
connected to the internet (we are a seconadry site to a 'headquarters' that
has the Internet connectivity and 'acts' as our ISP) so I think that might
be why I haven't had to concern myself with certificates being properly
configured.

Thanks for the help!

> I ran PKIDIAG and it found 2 errors a fixed 2 errors.
>
> I still have the same problem with NoRM.
>
> I seem to have broken pkidaig. the Util doesn't require enter after
> entering a menu number choice. The process run and want any key pressed to
> continue, which it does by ending.
>
> I went back into pkidiag, choose option 4(something about renaming if
> neccessary) it showed what seemed to be 2 new option 5 & 6
> I took 6 relazied that was not what i wanted. couldn't esc out of it.
> cntrl c seem to end the process
> but now pkidiag errors when trying to run
>
> in CSS recovercode-1498
> Error -1498 from CSS_Init
> <press any key to continue>
>
> Did I end up doing something real bad? Something a reboot would fix?
>
>
>
> > westmd2remove@nfis.com wrote:
> >
> > > Interstingly its on port 8008 (is that the non secure port? that is,
> > > http:// vs https:// for port 8009?)

> >
> > Yep. NoRM listens on both ports.
> >
> > > I used to be able to get directly to the SERVER1 with

https://serverip:8009
> > > but that seems broken at the moment. Yet I can get to NoRM via

SERVER2 and
> > > 'make my way' to SERVER1 NoRM screen. It's there via

http://servername:8008
> >
> > This would lend credence to my initial suspicion that your SSL
> > certificates are expired or otherwise corrupt, since you can get in via
> > non-SSL.
> >
> > Again, run pkidiag to test/fix them.
> >
> > > My confusion on Apache stems from the following:
> > > On My screens list I see
> > > Apache 2.0.54 for Netware
> > > *Apache2 Web Manager
> > >
> > > I thought 1 was Apache for to host a website and the other was for

Netware
> > > 's Administration. Since administration seems to have its own stack, why
> > > the 2 instances?

> >
> > You are correct that there are two instances of Apache on a normal NW6
> > box. Once is a general purpose instance that handles iManager and any
> > other additional things (like GroupWise webaccess). The other handles
> > some NetWare web-based management tasks, but that is NOT NoRM! Remote
> > Manager is it's own thing entirely. The reason for having a small,
> > special HTTP stack for it is that you wouldn't want to rely on Apache to
> > manage your server remotely... if Apache died, your access would be gone.
> > --
> > Jim
> > NSC Sysop

>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Apache Webserver for Administration not loading

westmd2@nfis.com wrote:

> Now to learn about certificates and why this happened. My box is not truly
> connected to the internet (we are a seconadry site to a 'headquarters' that
> has the Internet connectivity and 'acts' as our ISP) so I think that might
> be why I haven't had to concern myself with certificates being properly
> configured.


Just a clarification... certificates have nothing to do with your server
being connected (or not) to the Internet. NetWare uses several "self
signed" (meaning, they were signed by your own Novell certificate server
instead of a commercial certificate authority like Verisign)
certificates to enable core functionality. It is these certificates than
can expire and cause all sorts of things to break.. NRM being just one.


--
Jim
NSC Sysop
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.