Author: paul.deluca

How do I check the status of my EVault backup?

To manually check the status of your EVault backup:

  • If it’s not already installed, download and install the EVault CentralControl client from EVault’s support website or using this direct link.
  • If you’re using CentralControl for the first time, you’ll need to add connections to each server being backed up by EVault:
    • File -> New Agent
    • Fill in the Description, Network address, and root/Administrator user name and password fields
    • Press OK
  • Click the “+” sign next to the server you wish to check to expand and display the backup job(s)
  • Click the “+” sign next to the backup job you wish to check to expand and display the Logs folder
  • Select the Logs folder and double-click the most recent log to display the log. A successful backup will have no errors with output similar to the following:
06-Sep 21:03 SSET-I-04131 disconnect from the Vault at 06-Sep-2010 21:03:24 -0700
06-Sep 21:03 BKUP-I-00001 errors encountered:                        0
06-Sep 21:03 BKUP-I-00002 warnings encountered:                      0
06-Sep 21:03 BKUP-I-00003 files/directories examined:                280,340
06-Sep 21:03 BKUP-I-00004 files/directories filtered:                0
06-Sep 21:03 BKUP-I-00006 files/directories deferred:                0
06-Sep 21:03 BKUP-I-00007 files/directories backed-up:               280,340
06-Sep 21:03 BKUP-I-00008 files backed-up:                           267,837
06-Sep 21:03 BKUP-I-00009 directories backed-up:                     12,503
06-Sep 21:03 BKUP-I-00010 data stream bytes processed:               14,782,268,676 (13.76 GB)
06-Sep 21:03 BKUP-I-00011 all stream bytes processed:                14,782,268,676 (13.76 GB)
06-Sep 21:03 BKUP-I-00012 pre-delta bytes processed:                 651,912,316 (621.71 MB)
06-Sep 21:03 BKUP-I-00013 deltized bytes processed:                  118,090,710 (112.62 MB)
06-Sep 21:03 BKUP-I-00014 compressed bytes processed:                34,164,618 (32.58 MB)
06-Sep 21:03 BKUP-I-00015 approximate bytes deferred:                0 (0 bytes)
06-Sep 21:03 BKUP-I-00016 reconnections on recv fail:                0
06-Sep 21:03 BKUP-I-00017 reconnections on send fail:                0
06-Sep 21:03 SYST-I-07035 send e-mail: OK
06-Sep 21:03 BKUP-I-04128 job completed at 06-Sep-2010 21:03:26 -0700
06-Sep 21:03 BKUP-I-04129 elapsed time 00:03:11

Here’s a screencast showing an overview of the process:

How do I check disk usage on my Linux server?

View a step-by-step screencast of this process:

Log into the RHEL server as root via PuTTY, or shell out from Eterm.

The “df” command is used to determine overall filesystem usage. The “vgs” command will show you any space available in the volume group that has not yet been allocated to a specific filesystem.

To see the total size of each filesystem:

df -h

The standard Eclipse filesystems are located under /u2. Add the “Used” column for each of these filesystems, plus any non-standard Eclipse filesystems that you may have (/train, /backup, etc.).

[root@firestorm ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/rootvg-root
                       20G   18G  1.1G  95% /
/dev/mapper/datavg-u2
                      3.9G  2.1G  1.6G  57% /u2
/dev/mapper/datavg-uvtmp
                      3.9G  137M  3.6G   4% /u2/uvtmp
/dev/mapper/rootvg-esupport
                      5.9G  3.4G  2.3G  60% /esupport
/dev/sda1              99M   26M   69M  28% /boot
tmpfs                 3.9G     0  3.9G   0% /dev/shm
/dev/mapper/datavg-eclipse
                       26G   17G  7.6G  69% /u2/eclipse
/dev/mapper/datavg-ereports
                      992M   34M  908M   4% /u2/eclipse/ereports
/dev/mapper/datavg-lvol0
                      3.9G  2.1G  1.6G  57% /snap/u2
/dev/mapper/datavg-lvol4
                      3.9G  137M  3.6G   4% /snap/u2/uvtmp
/dev/mapper/datavg-lvol6
                       26G   17G  7.6G  69% /snap/u2/eclipse

If you would like to identify which files or subdirectories are using the most space in a particular filesystem or directory, you may use the “du” command. For example, to list the disk usage of top files and directories under /u2/eclipse in megabytes:

[root@firestorm ~]# cd /u2/eclipse
[root@firestorm eclipse]# du -sm * | sort -rn | head
3780    modules-linux
2856    modules
1568    ZIP4
859     jsdata
740     PHANTOM.LOG
740     modules-test
450     8.6.9.00.16-aix.zip
447     8.6.9.00.99-aix.zip
446     8.6.9.00.11-aix.zip
428     8.6.9.00.13-aix.zip

If you would like to see how much space is available for allocation within the volume group:

vgs

For more detail on this process, see: How do I expand a Linux file system?

Alternatively, if you prefer a graphical tool, you may log into the server’s GUI, and use the Disk Usage Analyzer tool:

  • Log into the server’s GUI (see also How do I access the GUI of my Linux server?)
  • Applications -> System Tools -> Disk Usage Analyzer
  • Click the Filesystem button to begin storage analysis of your entire system
  • Use the controls to drill down into each subdirectory for a graphical picture of storage utilization

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

What is Logwatch?

Logwatch is a log-monitoring system built into Red Hat Enterprise Linux. By default, it sends a daily email to the root user that contains potentially important entries from the system logs, such as kernel errors, user authentication failures, sudo commands, and disk utilization.

The output of the logwatch report is sent to the root user by default, but can easily be forwarded to any email address by adding an alias for the root user: How do I configure an email alias for my root account on Linux?

How do I obtain Red Hat Enterprise Linux media?