Unable to View Web Interface

  1. Check NexOSS is running

Issue the following commands to verify that the web interface of NexOSS is up and listening.

   [ossadmin@NexOSS]$ ps -ef|grep java
   ossadmin 15072 1 0 Feb28 ? 00:01:13 /home/ossadmin/OSS/nexoss/jdk/bin/java -DNexOSSWebServer -server -mx2500M -Djava.endorsed.dirs=/home/ossadmin/OSS/nexoss/nexoss/WebServer/common/endorsed -classpath /home/ossadmin/OSS/nexoss/jdk/lib/tools.jar:/home/ossadmin/OSS/nexoss/nexoss/WebServer/bin/bootstrap.jar -Dcatalina.base=/home/ossadmin/OSS/nexoss/nexoss/WebServer -Dcatalina.home=/home/ossadmin/OSS/nexoss/nexoss/WebServer -Djava.io.tmpdir=/home/ossadmin/OSS/nexoss/nexoss/WebServer/temp org.apache.catalina.startup.Bootstrap start
   [ossadmin@NexOSS]$ netstat -na|grep 7080
   tcp 0 0 :::7080 :::* LISTEN
  1. Check IP Tables

If port 7080 is not open in the operating system iptables (/etc/sysconfig/iptables), then the web interface to NexOSS will be blocked to all users. To fix this problem, configure the iptables of the operating system of the NexOSS host server to open port 7080. Below is an example iptables with port 7080 opened.

   # Firewall configuration written by system-config-securitylevel
   # Manual customization of this file is not recommended.
   :INPUT ACCEPT [0:0]
   :RH-Firewall-1-INPUT - [0:0]
   -A INPUT -j RH-Firewall-1-INPUT
   -A FORWARD -j RH-Firewall-1-INPUT
   -A RH-Firewall-1-INPUT -i lo -j ACCEPT
   -A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT
   -A RH-Firewall-1-INPUT -p 50 -j ACCEPT
   -A RH-Firewall-1-INPUT -p 51 -j ACCEPT
   -A RH-Firewall-1-INPUT -p udp --dport 5353 -d -j ACCEPT
   -A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT
   -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT
   -A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
   -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 21 -j ACCEPT
   -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
   -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 7080 -j ACCEPT
   -A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited

After editing the IP Tables file, restart the iptables.

   [root@sdreporter ossadmin]# /etc/init.d/iptables restart
   Flushing firewall rules: [ OK ]
   Setting chains to policy ACCEPT: filter [ OK ]
   Unloading iptables modules: [ OK ]
   Applying iptables firewall rules: [ OK ]
   Loading additional iptables modules: ip_conntrack_netbios_n[ OK ]ntrack_ftp
   [root@sdreporter ossadmin]#
  1. Insuffient Java Server Memory

If insufficient RAM is allocated to TrafficAnalyzer, reports will be generated more slowly as disk swap space is used and the the web interface will stop working. When this occurs the following TrafficAnalyzer log message will confirm the application needs additional memory.

   2011-04-04 20:17:03|Analyzer-QoS-Reporting |ERROR |There was a problem analyzing CDRs: Java heap space
   java.lang.OutOfMemoryError: Java heap space

Memory allocation to Java for the TrafficAnalyzer is defined by the JAVA_OPTS parameter in the $NexOSS_HOME/unix/run/start_web_server.sh . The default value for JAVA_OPTS is 6000 MB. The recommended guideline is to set JAVA_OPTS equal to 75% of the available RAM. For example, if available RAM is 16 GB, then JAVA_OPTS should be set to 12 GB (75%*16 GB).

NexOSS must be restarted for the change in JAVA_OPTS memory allocation to take effect.

  1. Clear Java Client Cache

Sometimes, a user’s Java cache can be too full of temporary files to view the NexOSS reports. The following steps will fix this problem.

Disable the “Keep temporary files on my computer” option in the Java Applet Viewer by doing the following.

  1. Open the “Java Control Panel” on the computer.

  2. Select the “General” tab.

  3. Click on “Settings” under the “Temporary Internet Files” section.

  4. Un-check the “Keep temporary files on my computer” check box.

  5. Close the control panel and all web browser windows.