Very Computer

I'm having a mysterious problem with a netsite server on an Indy running
Irix 5.3.  The original installation went fine, and all seemed ok.  I got
the server up and running, and the administrative server worked peachy.  
However, mysteriously, one day the administrative server stopped working,
and despite much hair tearing and reinstalls of netsite, it still won't
works.  What happens, is when I connect to the administrative server, I
get the dread, "Document contains no data" error, and when I look in the
admin server's error log, I get the following

[28/Aug/1995:16:54:47] catastrophe: caught SIGSEGV or SIGBUS, trying to
dump core in admin/config

Now this is all fine and good, but I have no idea where to look for the
problem.  The documentation sucks, and trying to get support out of
Netscape has been useless.  Has anyone experienced this problem, and does
anyone have any idea what might be causing it?

--
     Matt Cable // Internet Technologies Group // Internet Eye Candy
---------------------------------------------------------------------------
#!/usr/local/bin/perl -s-- -export-a-crypto-system-sig -RSA-in-3-lines-PERL

Sa2/d0<X+d*La1=z\U$n%0]SX$k"[$m*]\EszlXx++p|dc`,s/^.|\W//g,print pack('H*'
,$_)while read(STDIN,$m,($w=2*$d-1+length($n||die"$0 [-d] k n\n")&~1)/2)
---------------------------------------------------------------------------

: I'm having a mysterious problem with a netsite server on an Indy running
: Irix 5.3.  The original installation went fine, and all seemed ok.  I got
: the server up and running, and the administrative server worked peachy.  
: However, mysteriously, one day the administrative server stopped working,
: and despite much hair tearing and reinstalls of netsite, it still won't
: works.  What happens, is when I connect to the administrative server, I
: get the dread, "Document contains no data" error, and when I look in the
: admin server's error log, I get the following

: [28/Aug/1995:16:54:47] catastrophe: caught SIGSEGV or SIGBUS, trying to
: dump core in admin/config

: Now this is all fine and good, but I have no idea where to look for the
: problem.  The documentation sucks, and trying to get support out of
: Netscape has been useless.  Has anyone experienced this problem, and does
: anyone have any idea what might be causing it?

to narrow down the above stated problems somewhat....i tried running
/usr/ns-home/bin/httpd/admin/bin/index by hand, which is what I believe
the admin server is trying to run, and I had no problem with it, it spits
out what appears to be perfectly parsable html.

Any ideas?

--
     Matt Cable // Internet Technologies Group // Internet Eye Candy
---------------------------------------------------------------------------
#!/usr/local/bin/perl -s-- -export-a-crypto-system-sig -RSA-in-3-lines-PERL

Sa2/d0<X+d*La1=z\U$n%0]SX$k"[$m*]\EszlXx++p|dc`,s/^.|\W//g,print pack('H*'
,$_)while read(STDIN,$m,($w=2*$d-1+length($n||die"$0 [-d] k n\n")&~1)/2)
---------------------------------------------------------------------------

You can have a look at http://www.mcom.com/assist/support/server-support/server-tnotes/unix/...

Here you can find a copy of this page

     Patch for "Document contains no data" when you access the admin server

 Technical note:20108
 Created:       07/24/95 by Brian
 Last modified: 08/18/95 by Brian
 Product:       Netscape Commerce and Communications Servers 1.1
-------------------------------------------------------------------------------

There is a bug in version 1.1 of the Netscape Commerce and
Communications Servers (on all Unix platforms, but it was fixed before
the release of our Windows NT web server) whereby every attempt to log
into the administration server will result in a "Document contains no
data" error and an empty page in your browser, and the following
message in your server error log:

    [18/Jul/1995:14:20:57] catastrophe: caught SIGSEGV or SIGBUS,
    trying to dump core in admin/config

The problem is that the admin server crashes when it tries to resolve
the hostname you're connecting from to see if you're allowed to access
the admin server from there.

There is a patch available for this problem:

    ftp://ftp.netscape.com/private/ns-admin/aix/patch.tar
    ftp://ftp.netscape.com/private/ns-admin/bsdi/patch.tar
    ftp://ftp.netscape.com/private/ns-admin/hp_ux/patch.tar
    ftp://ftp.netscape.com/private/ns-admin/irix/patch.tar
    ftp://ftp.netscape.com/private/ns-admin/osf_1/patch.tar
    ftp://ftp.netscape.com/private/ns-admin/solaris/patch.tar
    ftp://ftp.netscape.com/private/ns-admin/sunos4/patch.tar

There is a README file included in the tar which explains how to apply
the patch.  Also note that you should explicitly stop your admin
server before you apply the patch, and then start your admin server
again after you are finished.

You can also work around the problem by removing the "Hosts" line from
your "ns-admin.conf" file, then restarting your admin server.  If you
do this and you still want to restrict admin server access to only
specific sites, then you should put the numeric IP addresses of those
sites into the "Addresses" line of that file (create that line if it
doesn't already exist).

-------------------------------------------------------------------------------

             Copyright ? 1995 Netscape Communications Corporation

Hope that helps,

Laurent

Silicon Graphics France                  Voice Mail : 5-9787
                                              Phone : +33.1.34.88.80.88

: : I'm having a mysterious problem with a netsite server on an Indy running
: : Irix 5.3.  The original installation went fine, and all seemed ok.  I got
: : the server up and running, and the administrative server worked peachy.  
: : However, mysteriously, one day the administrative server stopped working,
: : and despite much hair tearing and reinstalls of netsite, it still won't
: : works.  What happens, is when I connect to the administrative server, I
: : get the dread, "Document contains no data" error, and when I look in the
: : admin server's error log, I get the following

: : [28/Aug/1995:16:54:47] catastrophe: caught SIGSEGV or SIGBUS, trying to
: : dump core in admin/config

: : Now this is all fine and good, but I have no idea where to look for the
: : problem.  The documentation sucks, and trying to get support out of
: : Netscape has been useless.  Has anyone experienced this problem, and does
: : anyone have any idea what might be causing it?

: to narrow down the above stated problems somewhat....i tried running
: /usr/ns-home/bin/httpd/admin/bin/index by hand, which is what I believe
: the admin server is trying to run, and I had no problem with it, it spits
: out what appears to be perfectly parsable html.

: Any ideas?

Your problem looks like an exact match for one which we have solved.  Here
is the description of the problem from
        http://home.netscape.com/assist/support/server-support/server-tnotes/...

--------------
There is a bug in version 1.1 of the Netscape Commerce and
Communications Servers (on all Unix platforms, but it was fixed before
the release of our Windows NT web server) whereby every attempt to log
into the administration server will result in a "Document contains no
data" error and an empty page in your browser, and the following
message in your server error log:

    [18/Jul/1995:14:20:57] catastrophe: caught SIGSEGV or SIGBUS,
    trying to dump core in admin/config

The problem is that the admin server crashes when it tries to resolve
the hostname you're connecting from to see if you're allowed to access
the admin server from there.

There is a patch available for this problem:

    ftp://ftp.netscape.com/private/ns-admin/aix/patch.tar
    ftp://ftp.netscape.com/private/ns-admin/bsdi/patch.tar
    ftp://ftp.netscape.com/private/ns-admin/hp_ux/patch.tar
    ftp://ftp.netscape.com/private/ns-admin/irix/patch.tar
    ftp://ftp.netscape.com/private/ns-admin/osf_1/patch.tar
    ftp://ftp.netscape.com/private/ns-admin/solaris/patch.tar
    ftp://ftp.netscape.com/private/ns-admin/sunos4/patch.tar

There is a README file included in the tar which explains how to apply
the patch.  Also note that you should explicitly stop your admin
server before you apply the patch, and then start your admin server
again after you are finished.

You can also work around the problem by removing the "Hosts" line from
your "ns-admin.conf" file, then restarting your admin server.  If you
do this and you still want to restrict admin server access to only
specific sites, then you should put the numeric IP addresses of those
sites into the "Addresses" line of that file (create that line if it
doesn't already exist).
--------------

Sorry for the bug- hope this helps.  Let us know if it doesn't work.

Mike

---
Mike Belshe