Author: paul.deluca

How to Configure IIS SMTP Server to relay with authentication

The following KB article describes how to use Microsoft’s SMTP engine in IIS.  It is intended to lay out guidelines for how to send email off your existing externally hosted email server.  You will need to obtain the following email settings before this can be setup.  Your mail server may require certain encryption settings that the SMTP service will not work with.  You should contact your mail provider for assistance with the following information.

–          Your company specific outbound email server (for example mail.customer.com)

–          Your company specific outbound email account (for example ecl@customer.com)

–          Your company specific outbound email password (for example eclmail123)

–          Your company specific outbound email port (usually tcp port 25 by default).

Screenshots below are for illustration purposes only and should be used as en example.

Install the SMTP Service

  • Click Start
  • Go to Server Manager
  • Click Features
  • Select Add Features
  • Select SMTP Server and continue through wizard

Configure the SMTP Service

  • Go to Start
  • Select Internet Information Services (IIS) 6.0 Manager
  • Right-click on SMTP Virtual Server #1
  • Select Properties
    • Click on the Access tab
    • Click on Relay – add your local network, then select OK
  • Click on the Delivery tab
    • Click on Outbound security…
      • Under Basic authentication, enter your outbound username and password for your email account and click OK (this information may vary based on your mail servers requirements).
    • Click On Advanced…
      • Fill in Fully-qualified domain name
      • Set Smart host to the main SMTP server’s address
      • Masquerade domain (optional)
      • Click OK
    • Click on Outbound connections… (optional)
      •  Only select this option If your outbound port needs to be adjusted from port 25 (you will need to ask your email provider). 
      • Click OK

How do I suspend or quiesce the UniVerse database?

To perform valid backups of your database, it is important to suspend the database. This prevents modifications of files during the backup process. Our standard backup script uses database suspension with snapshots to create point-in-time images of your database files, but it is also possible to perform the suspension procedure manually:

Do not forget to remove the suspension after you have completed the backup, or users will be unable to use Eclipse.
  • Log in as root
  • Run the following command to suspend the database:
uv -admin -L
  • Run the following command to validate the status of the database:
uv -admin -R
  • Run the following command to sync any cached data to disk:
sync
  • At this point, the database files are ready for backup
  • When the backup is completed, run the following command to release the database:
uv -admin -U

How do I reboot or shut down my Linux server?

To reboot or shut down from the shell (command line):

  • log out all Eclipse Eterm or Solar users
  • Log in as root using the terminal client of your choice (Eterm, PuTTY, etc.)
  • Run the following command to reboot your system:
reboot
  • Run the following command to shut down your system:
halt

To reboot or shut down your server via the GUI (console or DRAC only):

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

To schedule a reboot to happen at say 4AM, you could type:

at 0400
reboot

Press [CTRL-D] to submit the job

Extended Reboot/shutdown Procedure

If you encountered the “Not all UniVerse processes were successfully terminated” message during a shutdown or reboot, please follow this procedure as root to perform an extended, clean reboot/shutdown of UniVerse:

  • log out all Eclipse Eterm or Solar users
  • Stop SYSTEM.ADMIN, phantoms, JBoss:

RHEL 5 and RHEL 6:

service monit stop
service eclipse-jboss stop
service eclipse-system-admin stop

RHEL 7:

systemctl stop eclipse-jboss 
systemctl stop eclipse-system-admin
For secondary accounts (play, train, stage, etc.), substitute “eclipse” for the account name. For example, a “train” account services would be referred to as train-jboss and train-system-admin.
  • Stop UV processes:
cd /u2/uv
bin/uv
#ESC
MASTER OFF ALL
Q
  • Stop remaining phantoms, UV processes:
pkill -4 -f phantom
  • Stop UV:

RHEL 5 and RHEL 6:

service uv.rc stop

RHEL 7:

systemctl stop universe
  • If UV complains that there are open processes, find any “uv” or “phantom” processes and kill them:
ipcs -mp|grep 0xaceb
kill -15 cpid

uv -admin -stop -force
  • Run the following command to reboot your system:
reboot
  • Run the following command to shut down your system:
halt

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 is my PostgreSQL database being backed up?

PostgreSQL is a secondary database used by many of our newer products, including Job Management.

The default method of backing up the postgresql database is by dumping the entire database to an archive file that is captured as part of the regular Eclipse database backup. On Linux, the backup script is located at /u2/pgsql/pgsql_backup by default. On AIX, the backup script is located at /u2/pgsql/bin/backup.sh by default.

This backup script is scheduled to run daily via crontab. On Linux, this is accomplished via a symlink in /etc/cron.daily:

ln -s /u2/pgsql/pgsql_backup /etc/cron.daily/pgsql_backup

On AIX, this is accomplished via a crontab entry similar to the following:

0 0 * * * /u2/pgsql/bin/backup.sh  >/dev/null 2>&1