Category: FAQ

How do I contact CrashPlan for support?

If you have an active subscription to Epicor’s ABS Online Backup or ABS Local Backup services, you may contact Epicor for support.

If you have purchased CrashPlan PRO licenses for your organization, and are running your own CrashPlan PRO server, you may contact CrashPlan directly for support. Here are some helpful tips that will speed up problem resolution:

Before contacting CrashPlan for support, please gather the CrashPlan PRO client backup logs: How do I gather CrashPlan logs?

Also, you may wish to consult CrashPlan’s list of Frequently Asked Questions and search their Support Forum.

Once you have the logs, use one of the following methods to contact CrashPlan support:

How do I manually restart JBoss on Linux?

Basic Restart Procedure

Log into the server as root and run the following command
RHEL 5 and RHEL 6:

service eclipse-jboss restart

RHEL 7:

systemctl restart eclipse-jboss

The application server will immediately begin the restart procedure, and it should be back up and running within 2-3 minutes on most servers.

Extended Restart Procedure

If the application server crashes, and attempts to restart it using the basic restart procedure above, or at the direction of Eclipse support, please follow this procedure as root to perform an extended, clean restart of JBoss:

  • Stop the JBoss service:

RHEL 5 and RHEL 6:

service eclipse-jboss stop

RHEL 7:

systemctl stop eclipse-jboss
  • Kill any errant JBoss processes:
pkill -9 -f jboss
  • Kill any errant J2EE (connection pool) phantoms on the database server:
pkill -4 -f SOLAR.J2EE.CONNECTION
  • (Optional) Backup logs for diagnosis (releases 8.7.2 and below):
cd /u2/eclipse/modules/jboss/server/eclipse
tar czvf /esupport/jboss.logs.`date +%Y%m%d.%H%M%S`.tar.gz ./log
  • (Optional) Backup logs for diagnosis (releases 8.7.3 and above):
cd /u2/eclipse/modules/jboss/eclipse
tar czvf /esupport/jboss.logs.`date +%Y%m%d.%H%M%S`.tar.gz ./log
  • Remove JBoss temporary directories (releases 8.7.2 and below):
rm -rf /u2/eclipse/modules/jboss/server/eclipse/tmp
rm -rf /u2/eclipse/modules/jboss/server/eclipse/log
rm -rf /u2/eclipse/modules/jboss/server/eclipse/data
rm -rf /u2/eclipse/modules/jboss/server/eclipse/work
  • Remove JBoss temporary directories (release 8.7.3 and above):
rm -rf /u2/eclipse/modules/jboss/eclipse/tmp
rm -rf /u2/eclipse/modules/jboss/eclipse/log
rm -rf /u2/eclipse/modules/jboss/eclipse/data
  • Remove the CONNECTED.APP.SERVERS control record:
cd /u2/eclipse
/u2/uv/bin/uv
ed control connected.app.servers
fd
y
q
  • Start the JBoss service:

RHEL 5 and RHEL 6:

service eclipse-jboss start

RHEL 7:

systemctl start eclipse-jboss

How do I log out an Eclipse Eterm or Solar user?

To log out an Eterm user’s session:

  • Log into the server as root
  • Display a list of logged in users with the command: who -u
  • Locate the user’s numeric process ID (PID) in the table, as highlighted in the example below:
olivera     pts/95      May 15 10:55     0:55   1102010  (172.17.190.22)
  • Log out that user with the kill -4 command, as shown in the example below:
kill -4 1102010

To log out a Solar user’s session:

  • Open the Solar web start page (ex. http://192.168.1.100:2080/, where 192.168.1.100 is your Eclipse server’s IP address)
  • Click on the Session Manager link
  • If you are warned by your browser about a potentially unsafe https connection, you should select the appropriate option to proceed
  • Log in with your Eclipse username and password
  • You may now log out the user(s) by clicking the Logout Session button

Screencast:

How do I restart JBoss on AIX?

Basic Restart Procedure

Log into the server as root and run the following command

/u2/eclipse/modules/bin/services.sh -d jboss

The application server will immediately begin the restart procedure, and it should be back up and running within 2-3 minutes on most servers.

Extended Restart Procedure

If the application server crashes, and attempts to restart it using the basic restart procedure above, or at the direction of Eclipse support, please follow this procedure as root to perform an extended, clean restart of JBoss:

  • Stop the JBoss service:
/u2/eclipse/modules/bin/services.sh -d jboss
  • Kill any errant JBoss processes:
ps -ef|grep jboss|awk '{print $2}'|xargs -i kill -9 {}
  • Kill any errant J2EE (connection pool) phantoms on the database server:
ps -ef|grep SOLAR.J2EE.CONNECTION|awk '{print $2}'|xargs -i kill -4 {}
  • (Optional) Backup logs for diagnosis (releases 8.7.2 and below):
cd /u2/eclipse/modules/jboss/server/eclipse
tar cvf /esupport/jboss.logs.`date +%Y%m%d.%H%M%S`.tar ./log
  • (Optional) Backup logs for diagnosis (releases 8.7.3 and above):
cd /u2/eclipse/modules/jboss/eclipse
tar cvf /esupport/jboss.logs.`date +%Y%m%d.%H%M%S`.tar ./log
  • Remove JBoss temporary directories (releases 8.7.2 and below):
rm -rf /u2/eclipse/modules/jboss/server/eclipse/tmp
rm -rf /u2/eclipse/modules/jboss/server/eclipse/log
rm -rf /u2/eclipse/modules/jboss/server/eclipse/data
rm -rf /u2/eclipse/modules/jboss/server/eclipse/work
  • Remove JBoss temporary directories (release 8.7.3 and above):
rm -rf /u2/eclipse/modules/jboss/eclipse/tmp
rm -rf /u2/eclipse/modules/jboss/eclipse/log
rm -rf /u2/eclipse/modules/jboss/eclipse/data
rm -rf /u2/eclipse/modules/jboss/eclipse/work
  • Remove the CONNECTED.APP.SERVERS control record:
cd /u2/eclipse
/u2/uv/bin/uv
ed control connected.app.servers
fd
y
q
  • Start the JBoss service:
/u2/eclipse/modules/bin/services.sh -e jboss

How do I run standalone diagnostics on my IBM pSeries server?

Additional resources: