To configure SSL browsing in the up.time web interface, you must generate a server certificate, which identifies that server is using SSL for security, and perform some platform-specific configuration. The following steps will cover this process.
Alternately, you can generate your own non-recognized certificate. A non-recognized certificate is one that does not come from a certificate-issuing authority. To generate a non-recognized certificate, download and install the OpenSSL software. OpenSSL binaries for Windows can be obtained from Shining Light Productions.
Once OpenSSL is installed, enter the following commands (changing <openssl_dir> to the proper path for the OpenSSL installation directory) at the command line to generate the certificate key. The example uses 1024 bit encryption; if required, you can increase to your preferred value:
cd <openssl_dir>/bin openssl genrsa -des3 -out uptime_ssl_server.key 1024 openssl req -new -key uptime_ssl_server.key -out uptime_ssl_server.csr openssl x509 -req -days 365 -in uptime_ssl_server.csr -signkey uptime_ssl_server.key -out uptime_ssl_server.crt
Create a passphrase file containing your SSL server password specified in the previous step. The up.time Web Server will require the password each time it restarts but a passphrase file will automate the request, so user intervention is not necessary.
Save the file as passphrase.cmd.
Save the file as passphrase.cmd.
Make the file executable.
chmod +x passphrase.cmd
Copy the following files to the <uptime_dir>/apache/conf directory where <uptime_dir> is the installation directory of up.time (the default installation directory is C:\Program Files\uptime software\uptime on Windows and /usr/local/uptime on Linux).
The following changes to the web server configuration file (httpd.conf) will allow it to use SSL.
Open <uptime_dir>/apache/conf/httpd.conf for editing. Where <uptime_dir> appears below, change it to reflect the directory where you have up.time installed (ex. c:/Program Files/uptime software/uptime). All path slashes in httpd.conf need to be forward slashes (rather than the usual backslash that is used in Windows).
To make browsing to the up.time UI easy for users, have it listen on the default up.time UI port, 9999, as well as the typical HTTP and HTTPS ports, 80 and 443.
To handle requests on each of these ports, 80, 443, and 9999, and redirect (actually rewrite) them properly, we will leverage the mod_rewrite.so module, so we need to enable it. In the httpd.conf file, uncomment the following two lines.
LoadModule rewrite_module modules/mod_rewrite.so
NOTE: On Linux installations of up.time 7.2 and earlier, the mod_rewrite.so file is not bundled with up.time, so it is necessary to download it from the bottom of this article and copy it to the <uptime_dir>/apache/modules directory.
Finally, the last part is to add entries in httpd.conf that will rewrite the requests as HTTPS. At the bottom of the httpd.conf file, add these lines, changing <uptime_dir> to the directory of your up.time installation:
Open the <uptime_dir>/uptime.conf file for editing and change the httpContext parameter (which begins with "httpContext=http://") to reflect the use of SSL:
For the changes to take effect, restart the up.time Data Collector and up.time Web Server on Windows or uptime_core and uptime_httpd on Linux.
service uptime_core restart service uptime_httpd restart
mod_rewrite.so (Size: 59.0 KB - Downloads: 531)
If you have recently changed the hostname of your monitoring station and receive the message "Database Not Responding" in the monitoring station web interface, you must make the following...
By: uptime Support | Date Created: 10-1-2009 | Last Modified: 10-18-2013 | Index: 379
There are no agent settings to enable it to be bound to a specific network interface. By default, the up.time agent is designed to listen on all interfaces on the desired agent port (default...
By: uptime Support | Date Created: 10-14-2009 | Last Modified: 8-13-2011 | Index: 427
If you are seeing a Database Not Responding message in up.time GUI, with something similar to the following error: =================== Database is not responding ...
By: uptime Support | Date Created: 10-14-2009 | Last Modified: 8-13-2011 | Index: 436
To modify the session timeout value for the up.time User Interface: 1. Open the following file: //apache/php/php.ini 2. Edit the following line: session.cache_expire = 180 (note that the value is...
By: uptime Support | Date Created: 7-7-2011 | Last Modified: 8-11-2011 | Index: 535
Yes, up.time utilizes the information provided by pmi in order to produce performance graphs so it is required to be installed on the target WebSphere server.
By: uptime Support | Date Created: 8-20-2010 | Last Modified: 8-10-2011 | Index: 492