Sybernet Installtion for UNIX

Install Sybernet

Sybernet on UNIX may now be installed with your web browser. The utility program was completely rewritten to make this installation as smooth as possible.

Sybernet.utility requires read and write permission on several directories used by your web server. If this is unacceptable, please refer to the file oldREADME in this directory. You may also want to password protect this utility with your web browser.

Ideally, you should have decompressed this tar file from the same username that your CGIs run under. Alternatively, you can change the permission on the Sybernet directory so that read, write and execute permission is allowed on all files and all directories.

chmod -R 777 Sybernet

When we installed Sybernet under an Apache server running on Linux, we experienced problems with relative path names. This was solved by replacing all occurences of Sybernet.cgi with /cgi-bin/Sybernet.cgi. With a NetScape server the problem is eliminated with the following in your obj.conf file:

    <Object name="cgi">
    ObjectType fn="force-type" type="magnus-internal/cgi"
    Service fn="send-cgi"
    </Object>
The latter is consistent with the current documentation and implies you do not need to qualify the name Sybernet.cgi in your stored procedures.

Starting a Server Manually

The Sybernet.cgi is started automatically by your web server. They connect to the Sybernet server with an internet stream socket so the servers must be up and running at all times.

It's the server that hold connections and state information between the CGI and Sybase. The servers get all their configuration parameters from the file Sybernet.config in your cgi-bin directory except for the socket number that they are suppose to listen at. The socket number is passed as a parameter to the Sybernet server. It is the only parameter that it accepts; for example,

Sybernet.server 5555

will start a Sybernet server that listens at socket 5555. Make sure that if you start the servers in this manner that the socket numbers are valid. Note: The utility program is the safest way to start the Sybernet servers because it will not start a server on an invalid socket number.

A non-zero return result indicates one of the following errors:

  1. CANTREADCONFIGFILE
  2. SYNTAXERROR
  3. CANTCREATESOCKET
  4. CANTBINDSOCKET
  5. CANTGETSOCKETNAME
  6. CANTOPENLOGFILE
  7. FORKFAILED
These errors are explained in more detail in the section on trouble shooting (below).


Let me know how you progress!

Denis

Denis D. Workman (denis@unix.sri.com)
SRI International
333 Ravenswood Avenue
Menlo Park, California 94025
USA

Trouble Shooting

Trouble Shooting the Sybernet CGI Servers

The following are error messages you might see when starting one or all of the servers. Once the servers have successfully initialized, future errors are written to the log file: Sybernet.sumlog. It is a good idea to always check this file when something has gone wrong.

CAN'T CREATE INTERNET STREAM SOCKET
CAN'T BIND TO INTERNET STREAM SOCKET
CAN'T GET SOCKET NAME
CAN'T OPEN LOG FILE
CAN'T READ THE CONFIGURATION FILE

Trouble Shooting the Sybernet CGI client

In all cases, see if there are any entries in the Sybernet CGI server's log file: Sybernet.sumlog in the cgi-bin directory. If there are none and the servers are alive, the problem usually points to the client: either the Sybernet CGI client or the browser.

CAN'T READ THE CONFIGURATION FILE
WRITING TO STREAM SOCKET FAILED
READING OK FROM STREAM SOCKET FAILED
UNABLE TO READ CONTENTS OF CONFIGURATION FILE
UNABLE TO OPEN INTERNET STREAM SOCKET
SERVER_NAME ENVIRONEMENT VARIABLE IS UNDEFINED
INVALID SERVER_NAME WHILE OPENING SOCKET
CONNECTING TO STREAM SOCKET FAILED
CONNECTION TIMED OUT WHILE PINGING SOCKET