Stronghold Web Server 2.4 FAQ

My license block does not work

The license block consists of about seven or eight lines of text, starting with the line "*****BEGIN LICENSE BLOCK*****" and ending with the line "*****END LICENSE BLOCK*****". When you paste the license block during installation make sure you include these lines in the code you paste.

After installation, you can find the license block in the file sh2license in your installed Stronghold Web Server 2.4.1 or 2.4.2 directory. Look in this file and make sure it includes the start and end lines as given above.

Do not use a "license key" (as used for Stronghold Web Server 2.3 and earlier). If you have a license key you can convert it to a license block using our license key converter. See also "What is a License Block?" in the Stronghold Web Server 2.4 FAQ.

When I type the filename it says something like "Command not found"

When you type a command the system looks in the directories listed in your "path" or "PATH" environment variable for that program. You have probably downloaded the file into your current directory, but your path does not include the current directory (this is usually a good idea). To run the file, simply put "./" in front of the filename to tell the system that it is in your current directory. For example

 # % ./sh-241-mips-sgi-irix5.3.bc2409

What does the download filename mean?

Each download filename looks like this:

 sh-241-mips-sgi-irix5.3.bc2409 

This is followed by three parts which together make up the operating system that this file is intended for. This starts with a underlying hardware (processor) name, which is "mips" in this example. For Intel systems this will be "i386", which indicate it supports all Intel-compatable processors in the x86 range from the 386 upward. Then the manufacturer is given. In this example it is "sgi". On Intel-compatible systems this will be "unknown" because the system can come from any number of different manufacturers. Finally for this part comes the operating system name and version, which in the example above is "irix5.3". The version may include dots (periods) within the version number.

Finally the "build code" is given after the last dot in the filename. The "build code" is used to ensure that every release has a unique version, without having to update the product version number.

Installation is asking me to generate a keypair, but I already have one

If you already have a keypair for your server, you do not need to generate a new set. Press control-C to exit from the installation when asked to generate a new keypair. This will display an error and say that installation has not been completed, but it has.

Now you can simply copy your existing key and certificate files into your Stronghold Web Server 2.4.1 or 2.4.2 installation directory (in ssl/certs and ssl/private), and start the server with bin/start-server. See the next question for more details about upgrading an existing Stronghold Web Server 2.4 installation.

I can't paste the license block!

If you are on a console you may not be able to paste the license block when asked during installation. In this situation, press ^D (control-D) when asked to paste the license block, then answer "n" when asked whether you want to paste another license block. Installation will continue, but at the end the server will not be started (since it will not run without a license block). See the next question for how to install the license block after installation has finished.

When I type the filename it says "Permission denied"

This probably means that the file is not marked as executable. To run a file as a program, the file must have its "executable" bit set. To set the executable bit, run

 # % chmod u+x sh-241-mips-sgi-irix5.3.bc2409

I did not enter a license block during installation. How do I enter it now?

If you do not have a valid licence block during installation, or could not paste the block during installation, you may have answered "n" to the question "paste another licence block" during installation. Installation for Stronghold Web Server will have finished, but the server cannot be started because it does not have a license block. There are now two ways to install the license block.

If you cannot paste the license block (perhaps because your terminal does not allow pasting), you can simply place the text of the license block in the file sh2license in the directory where you installed Stronghold Web Server. To check the license block is valid, run the command ./httpd -s sh2license.

If you are able to cut and paste the license block, you may find it easier to run an interactive program which will accept, check and install the license block. To do this change to the directory where you installed Stronghold Web Server, and run bin/install_lb.

In either case, once you have installed the license block you can start the server running with bin/start-server.

Recompiling Stronghold Web Server fails

While there can be several other causes for this, the most common reason is that Stronghold Web Server 2.4.1 or 2.4.2 has been installed into the same directory that contains an earlier version of Stronghold Web Server or a version of Apache before 1.3. Stronghold Web Server 2.4.1 or 2.4.2 must not be installed over an existing installation. If you have done this but need to recompile, install it again this time to a new directory.

How do I upgrade an existing Stronghold Web Server 2.4 installation?

Stronghold Web Server 2.4.1 and 2.4.2 cannot automatically upgrade an Stronghold Web Server 2.4 installation. Instead you must install 2.4.1 or 2.4.2 into a new directory then copy across the configuration and other information from your 2.4 installation. A typical procedure is:

• Install Stronghold Web Server 2.4.1 or 2.4.2 into a new directory, and when asked for ports, use temporary (unused) port numbers. This means that your existing Stronghold Web Server server can continue running during the changeover. When you see the message about generating a new keypair ("You are now generating a new keypair which will be used to encrypt all SSL traffic to the server...") press control-C to exit, since you already have a keypair from your existing installation and do not need to generate a new one. This will cause the installation to exit with an error. Do not worry about this, installation has in fact finished correctly.

Now copy across all the localised information from your existing Stronghold Web Server 2.4 directory. The main things you will want to copy are:

• Copy any local changes to conf/httpd.conf to the new httpd.conf.
• Copy the whole htdocs directory.
• Copy the whole cgi-bin directory.
• Copy any other changed files (for example, any icons you have modified)
• Copy the key and certificate files from ssl/certs and ssl/private
• Copy any other local modifications. For example, if you have added any extra mime types to conf/mime.types.

Stop the old server. Start the new one.

How can I recompile Stronghold Web Server 2.4.2

Stronghold Web Server 2.4.2, build code 2410 must be manually patched in order to recompile. Later versions do not require this modification.

• cd into Stronghold Web Server's src directory.
• Edit the file /ServerRoot/src/main/Makefile.tmpl
• Change the line

     # $(CC) $(CFLAGS) $(LDFLAGS) -o gen_uri_delims gen_uri_delims.o $(LIBS)
  

  to

     # $(CC) $(CFLAGS) $(LDFLAGS) -o gen_uri_delims gen_uri_delims.o
  

• Change the line

     # $(CC) $(CFLAGS) $(LDFLAGS) -o gen_test_char gen_test_char.o $(LIBS)
  

  to

     # $(CC) $(CFLAGS) $(LDFLAGS) -o gen_test_char gen_test_char.o
  

• Save the file.
• In the file /ServerRoot/src/Configure, change the line

     # tmpstr=`echo $CFLAGS $TEXTRA_CFLAGS |\ 
     # sed -e 's;[^I ]]\([+-]\);!\1;g' -e 's/\\\"/\"/g' -e 's/\([^\\]\)"/\1/g'`
  

  to

     # tmpstr=`echo $CFLAGS $TEXTRA_CFLAGS |\
     # sed -e 's;[^I ]\([+-]\);!\1;g' -e 's/\([^\\]\)"/\1/g' -e 's/\\\"/\"/g'`
  

  (where ^I is a tab character)
• Save the file.