How do I change a printer’s IP address in AIX?

The mappings of IP addresses to “lp” names are contained in the /etc/hosts configuration file. To change the IP address:

    Log into your server as root user via Eterm or PuTTY
    Edit the /etc/hosts file using vi:
vi /etc/hosts
    Locate the entry for the printer(s) you wish to change
    Make the change
    Save the file and quit

How do I view my Eclipse rsync backup logs on Linux?

The standard tape backup script keeps a number of log files that are accessible to the system administrator. To view the log files, log into your server as root and run the following commands. You may also configure the backup script to send an email every time the backup is run.

/tmp/snapsave.log contains the output from the last successful rsync backup

more /tmp/snapsave.log

The log for a successful rsync backup will show output similar to the following:

Copy done - status=0

Number of files: 2248894
Number of files transferred: 6519
Total file size: 181.30G bytes
Total transferred file size: 135.72G bytes
Literal data: 135.72G bytes
Matched data: 0 bytes
File list size: 82.91M
File list generation time: 0.001 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 135.82G
Total bytes received: 152.13K

sent 135.82G bytes  received 152.13K bytes  14.44M bytes/sec
total size is 181.30G  speedup is 1.33

/tmp/snapsave.rsync-local.log contains the files that were backed up or updated by rsync backup operation

/tmp/snapsave.log logs database suspension and snapshot operations:

less /tmp/snapsave.log

The following log file shows a successful backup and details the database and snapshot operations taking place. This is very useful for troubleshooting backup issues.

--------------------------------------------------------------------------------
Tue Sep  7 21:00:05 CDT 2010: Current snapshot status
Snapshots for /u2
Current  Location          512-blocks        Free Time
*        /dev/fslv00           163840       50432 Mon Sep  6 21:01:32 CDT 2010
Snapshots for /u2/eclipse
Current  Location          512-blocks        Free Time
*        /dev/fslv01          2818048     1512448 Mon Sep  6 21:01:39 CDT 2010
Snapshots for /u2/eclipse/ereports
Current  Location          512-blocks        Free Time
*        /dev/fslv02            32768       32000 Mon Sep  6 21:01:44 CDT 2010
Snapshots for /u2/pdw
Current  Location          512-blocks        Free Time
*        /dev/fslv03          1835008     1833984 Mon Sep  6 21:01:48 CDT 2010
--------------------------------------------------------------------------------
Tue Sep  7 21:00:16 CDT 2010: Releasing and unmounting previous snapshots
Tue Sep  7 21:00:18 CDT 2010: Unmounting /snap/u2/pdw
Tue Sep  7 21:00:23 CDT 2010: Removing snapshot(s) of /u2/pdw
rmlv: Logical volume fslv03 is removed.
Tue Sep  7 21:00:31 CDT 2010: Unmounting /snap/u2/eclipse/ereports
Tue Sep  7 21:00:32 CDT 2010: Removing snapshot(s) of /u2/eclipse/ereports
rmlv: Logical volume fslv02 is removed.
Tue Sep  7 21:00:39 CDT 2010: Unmounting /snap/u2/eclipse
Tue Sep  7 21:00:40 CDT 2010: Removing snapshot(s) of /u2/eclipse
rmlv: Logical volume fslv01 is removed.
Tue Sep  7 21:00:47 CDT 2010: Unmounting /snap/u2
Tue Sep  7 21:00:47 CDT 2010: Removing snapshot(s) of /u2
rmlv: Logical volume fslv00 is removed.
--------------------------------------------------------------------------------
Tue Sep  7 21:00:53 CDT 2010: Suspending database
--------------------------------------------------------------------------------
Tue Sep  7 21:00:59 CDT 2010: Performing snapshots:
Tue Sep  7 21:00:59 CDT 2010: Taking snapshot of /u2
Snapshot for file system /u2 created on /dev/fslv00
Tue Sep  7 21:01:04 CDT 2010: Taking snapshot of /u2/eclipse
Snapshot for file system /u2/eclipse created on /dev/fslv01
Tue Sep  7 21:01:11 CDT 2010: Taking snapshot of /u2/eclipse/ereports
Snapshot for file system /u2/eclipse/ereports created on /dev/fslv02
Tue Sep  7 21:01:16 CDT 2010: Taking snapshot of /u2/pdw
Snapshot for file system /u2/pdw created on /dev/fslv03
--------------------------------------------------------------------------------
Tue Sep  7 21:01:21 CDT 2010: Database suspend released.
--------------------------------------------------------------------------------
Tue Sep  7 21:01:21 CDT 2010: Mounting snapshot filesystems
Tue Sep  7 21:01:23 CDT 2010: Mounting snapshot: /snap/u2
Tue Sep  7 21:01:25 CDT 2010: Mounting snapshot: /snap/u2/eclipse
Tue Sep  7 21:01:27 CDT 2010: Mounting snapshot: /snap/u2/eclipse/ereports
Tue Sep  7 21:01:30 CDT 2010: Mounting snapshot: /snap/u2/pdw
rmt0 changed
Tue Sep  7 21:02:05 CDT 2010: Starting backup from /snap
--------------------------------------------------------------------------------
Tue Sep  7 22:40:15 CDT 2010: Mailing backup report
--------------------------------------------------------------------------------

How to find the serial number of your Synology NAS

You will need the serial number of the NAS to contact technical support.   It should be located on the unit but if you’d like to validate that or find it remotely.

1. Login to the NAS http://NASipaddress:5000 (the default username is admin with no password).

2. Click on the icon in the top right corner

nasicon

3.  Click on System Information nasscreenshot

4. You should see the serial number listed under the “General” Tab

serialNAS

New Relic Monitoring

There are many monitoring solutions available, and many of them work well with Eclipse servers, but we recommend the New Relic monitoring solution for customers interested in setting up monitoring quickly and easily.

We’ve prepared the following guide to help customers implement New Relic monitoring on their Eclipse servers, but Eclipse does not provide technical support for New Relic. If you have any questions, please contact New Relic support directly.

Sign up for a New Relic account

Before you can install the New Relic software, you’ll need to sign up for an account. They have a free option for customers that need basic monitoring and 24 hours of historical data, or you can upgrade to one of the more advanced tiers.

To sign up for an account, go to the New Relic website and follow the instructions.

Install the server monitoring agents

The server monitoring agents will track things like processor utilization and disk usage.

Linux

Enable the New Relic repository:

rpm -Uvh http://download.newrelic.com/pub/newrelic/el5/i386/newrelic-repo-5-3.noarch.rpm

Install New Relic’s server monitoring daemon:

yum install newrelic-sysmond

Configure the daemon with your license key (which you can obtain the Account Settings page):

nrsysmond-config --set license_key=27c16493aa50f89546b3caed34e3ee81880ab786

Start the daemon:

/etc/init.d/newrelic-sysmond start

Windows

Download the installer appropriate for your system:

Double click the installer file and follow the prompts to start the installation — generally you can click “Next” and the installer will try to pick smart defaults for you.

Enter your New Relic license key (which you can obtain the Account Settings page) when prompted, and click “OK”.

Install the application server agent

Note: installing the application server agent requires restarting JBoss, which will be disruptive to Solar and Job Management users.

Go to the Applications page and click Add more.

Choose the “Java” language

Click “Reveal your license key”

Click “Download New Relic Java agent”

Transfer the .zip file to the application server’s JBoss directory (e.g. /u2/eclipse/modules/jboss) via the method of your choice (e.g. FTP, SCP)

Log into the server as root, then extract and install the agent:

cd /u2/eclipse/modules/jboss
unzip newrelic*.zip

Set permissions:

chown -R jboss:jboss newrelic

Backup the current JBoss configuration:

cp /u2/eclipse/modules-conf/jboss.conf /u2/eclipse/modules-conf/jboss.conf.`date +%Y%m%d.%H%M%S`

Change the name of the application (the name that will be displayed on the New Relic web interface) from “My Application” to something more descriptive (e.g. companyname-Solar)

Add a line for New Relic to the end of the JBoss configuration file:

vim /u2/eclipse/modules-conf/jboss.conf
JAVA_OPTS="$JAVA_OPTS -javaagent:/u2/eclipse/modules/jboss/newrelic/newrelic.jar"

Restart JBoss

service eclipse-jboss halt
service eclipse-jboss start

Uninstalling New Relic

To uninstall the application server agent:

vim /u2/eclipse/modules-conf/jboss.conf

Remove the following line:

JAVA_OPTS="$JAVA_OPTS -javaagent:/u2/eclipse/modules/jboss/newrelic/newrelic.jar"

Restart JBoss to undeploy the agent.

Remove the New Relic agent files:

rm -rf /u2/eclipse/modules/jboss/newrelic

To remove the Linux server monitoring agent:

yum remove newrelic-sysmond