Environment
Products:
Novell Teaming 1
Novell Teaming 2
Novell Vibe OnPrem 3
Novell Vibe OnPrem 3.1
Configuration:
SuSE Linux Enterprise Server
Novell Open Enterprise Server
Novell Teaming 1
Novell Teaming 2
Novell Vibe OnPrem 3
Novell Vibe OnPrem 3.1
Configuration:
SuSE Linux Enterprise Server
Novell Open Enterprise Server
Situation
Email notifications sent out from Teaming contain a Teaming URL and the port number is incorrect. When recipients click on the link in the email message, the link does not work.
Resolution
- Locate the directory in which Teaming is installed. By default, this
will be /opt/novell/teaming/
If it is different from those locations, a system administrator will need to ascertain where Teaming was installed. The remaining steps are then performed relative to the teaming install directory. - As root, locate
the file
apache-tomcat-6.0.18/webapps/ssf/WEB-INF/classes/config/ssf-ext.properties
relative to the teaming directory. - Locate the line that reads:
ssf.port=nnnn
where nnnn is a number other than port 8080. - Change this line to read:
ssf.port=8080 - Stop and restart the Teaming process using these commands:
/etc/init.d/teaming stop
/etc/init.d/teaming start
Additional Information
Root Cause:
The default configuration when installing Teaming is to have the Apache web server listen on port 8080 but to use port 80 for connections because port 80 is what web browsers use by default, and hence the port number can be omitted. However, this will only work when clicking on a link in a mail message if the Teaming server has enabled port forwarding. Without port forwarding enabled, the links will appear to be broken.
Details:
Linux by convention reserves all port numbers less than 1024 for processes running as root. The Apache web server built into Teaming does not run as root, so it must listen on a port number greater than 1024. The Teaming installer makes this port number 8080 by default.
The system administrator can set port forwarding so that any packets coming to port 80 are forwarded to port 8080 and the web server will get the requests successfully. However, if port forwarding is not turned on, email links that do not explicitly reference port 8080 will fail. The port number used in email notifications is set at installation and written to the file ssf-ext.properties. In order to cause port 8080 to be used in Teaming links in outgoing email notifications, this value must be changed to 8080. The port number is contained in the attribute ssf.port.
Note that editing this attribute in the file ssf-ext.properties is equivalent to running the Teaming installer again, choosing the "Reconfigure settings" option, and then changing the value of HTTP Port on the Network Information form to be 8080. The installer will then rewrite the file ssf-ext.properties with the correct value of ssf.port. Either approach can be used to fix this problem.
The default configuration when installing Teaming is to have the Apache web server listen on port 8080 but to use port 80 for connections because port 80 is what web browsers use by default, and hence the port number can be omitted. However, this will only work when clicking on a link in a mail message if the Teaming server has enabled port forwarding. Without port forwarding enabled, the links will appear to be broken.
Details:
Linux by convention reserves all port numbers less than 1024 for processes running as root. The Apache web server built into Teaming does not run as root, so it must listen on a port number greater than 1024. The Teaming installer makes this port number 8080 by default.
The system administrator can set port forwarding so that any packets coming to port 80 are forwarded to port 8080 and the web server will get the requests successfully. However, if port forwarding is not turned on, email links that do not explicitly reference port 8080 will fail. The port number used in email notifications is set at installation and written to the file ssf-ext.properties. In order to cause port 8080 to be used in Teaming links in outgoing email notifications, this value must be changed to 8080. The port number is contained in the attribute ssf.port.
Note that editing this attribute in the file ssf-ext.properties is equivalent to running the Teaming installer again, choosing the "Reconfigure settings" option, and then changing the value of HTTP Port on the Network Information form to be 8080. The installer will then rewrite the file ssf-ext.properties with the correct value of ssf.port. Either approach can be used to fix this problem.