Revolution R FAQ

Other than the FAQ's on this site, you can find some troubleshooting steps in Appendix A of the RevoDeployR Installation Guide.

The common cause for this error is that one of the services RevoDeployR needs has not been launched.
You can launch the services related to deployr as follows:

For Linux:
----------
/etc/init.d/rserve start
/etc/init.d/tomcat7 start
/etc/init.d/httpd start
/etc/init.d/mysql start

You can use the command 'ps -aux' to check that these have been successfully launched.

If this doesn't resolve the issue, please email the following server-side log files to 'support@revolutionanalytics.com':

/usr/share/tomcat7/logs/catalina.out
/usr/share/tomcat7/bin/plogs/production.log

For Windows:
------------
Open 'Start ---> Control Panel ---> Administrative Tools ---> Services'
Verify that the services: RServe, Apache Tomcat 7.0, Apache 2.2 and MySQL are all installed and in the 'Status' field it shows them ALL as started.
If any services are not started, launch them by right-clicking on the Service and choosing 'Start'.
You can download any of these missing prerequisites from the following URL:
http://www.revolutionanalytics.com/products/deployr/install/2.0/win-server-prerequisites.php

The server-side log files we need for further troubleshooting are located in:
C:\Program Files\Apache Software Foundation\Tomcat 7.0\logs\catalina.out
c:\Program Files\Apache Software Foundation\Tomcat 7.0\plogs\production.log

Make sure that you set the 'Server web context' entry to: 'http://"myaddress"/deployr', where "myaddress" is equal to the IP address of your web server. This setting can be found under the 'Management Console Interface' under the 'Server Policies' tab.

This can happen if the incorrect IP address is defined for RevoDeployR.
This can be corrected by updating the Web Server Context IP Address:

1. Go to the RevoDeployR Management Console and perform the following:

Go to revodeployr_server_ip_address/revolution/

where revodeployr_server_ip_address is the IP of the main server machine.
Log in as the default administrator. If you have not yet changed the default password, use the following:

Username: admin Password: secret

In the Server Polices tab, make sure the public IP address you want to use is correctly shown in the “Web Server context” field. Refer to the Management Console User’s Guide for more information on how to edit server policies.

2. Open the Hello World sample using the newly defined IP address:

revodeployr_server_ip_address/revolution/sample1.html

and click Execute. The plot results should display.

To set Tomcat program to run as an administrator:

1. Right-click the file tomcat7w.exe and choose Properties from the shortcut menu. tomcat7w.exe is a GUI application for monitoring and configuring Tomcat services.
2. In the Properties dialog, select the checkbox Run this program as an administrator checkbox in the Privilege Level area.
3. Click OK.
4. Launch RevoDeployR again.

You can't have more than one active RevoDeployR login session at a time. Instead, you will need to login to the Management Console and API Explorer in separate browser windows.(e.g., open one in Google Chrome and the other in Firefox).

Most likely, there is a port conflict with another application or service on the server machine. To resolve this problem, change the Tomcat port numbers.

On Windows:

1. In the Tomcat 7.0 directory, open the file server.xml and make two changes:
2. Find the port=”8080” and change to a new port number such as port=”8090”
3. Find the port=”8008” and change to a new port number such as port=”8010”
4. Save the file.
5. In the Apache2.2/extra/ root directory, open the file httpd-vhosts.conf.
6. In the following line from httpd-vhosts.conf, update the port number with the one you used to replace 8008, which in our example is 8010:
ProxyPass /deployr ajp://localhost:8008/deployr timeout=1800
7. Restart Tomcat and then restart Apache HTTPD for the change to take effect.
   
   net stop tomcat7
   net start tomcat7
   
   net stop Apache2.2
   net start Apache2.2
   
   

On Linux:

Note: If you added lines to iptables during installation, you may need to change the port numbers listed there as well.

1. Edit the file /usr/share/tomcat6/conf/server.xml and make two changes: Find the port=”8080” in the lines:
   Connector port="8080" protocol="HTTP/1.1"
   connectionTimeout="20000"
   redirectPort="8443" />
   and change to a new port number, such as port=”8090”.
   Find the port=”8008” in the line:
   Connector port="8008" protocol="AJP/1.3" redirectPort="8443" /
   and change to a new port number, such as port=”8010”
   Save and exit the file.
   
2. Edit the file /etc/httpd/conf/httpd.conf to update the Connector AJP port number in the following line with the one you used to replace 8008, which in our example is 8010:

ProxyPass /deployr ajp://localhost:8008/deployr timeout=1800

3. Restart Tomcat and then restart Apache HTTPD for the changes to take effect.

/etc/init.d/tomcat7 stop
/etc/init.d/tomcat7 start
/etc/init.d/httpd stop
/etc/init.d/httpd start

4. Verify that the port changes are working as expected. At the prompt, type:

netstat -p --listening --numeric-ports --numeric-hosts | grep -i java