Tag: linux

How do I stop and start Eclipse services on Linux?

Stop Eclipse

  • Stop VSIFAX:
vfxsched stop
  • Stop samba:
service smb stop
  • Stop PostgreSQL:
service postgresql-8.4 stop

RHEL7

systemctl stop postgresql-9.5
  • Stop SYSTEM.ADMIN, phantoms, JBoss:
service monit stop
service eclipse-jboss stop
service eclipse-system-admin stop

RHEL7

systemctl stop eclipse-api-release
systemctl stop eclipse-jboss.service 
systemctl stop eclipse-system-admin.service
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:
ps -ef|grep phantom|awk '{print $2}'|xargs -i kill -4 {}
  • Stop UV:
service uv.rc stop

RHEL7

systemctl stop  universe
  • If UV complains that there are open processes, check:
lsof /u2
ipcs -mop|grep 0xaceb

Start Eclipse

  • Start UV:
service uv.rc start

RHEL7

systemctl start  universe
  • Start PostgreSQL:
service postgresql-8.4 start

RHEL7

systemctl start postgresql-9.5
  • Start SYSTEM.ADMIN, phantoms, JBoss:
service monit start
service eclipse-system-admin start
service eclipse-jboss start

RHEL7

systemctl start eclipse-system-admin.service 
systemctl start eclipse-jboss.service 
systemctl start eclipse-api-release
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.
  • Start samba:
service smb start

RHEL7

systemctl start smb
  • Start VSIFAX:
vfxsched start

Which directories should I backup on my Eclipse servers?

The following directories contain the most critical files necessary to recover your Eclipse systems:

  • Database server (AIX, RHEL):
    • /u2 (contains your Eclipse database, UniVerse, JBoss and VSIFAX)
    • /snap/u2 (if using snapshots, this contains the same data as above, but frozen in time)
    • /etc (contains your operating system configuration files)
    • /home (contains your users’ home directories)
    • /usr/spool/uv (contains your legacy UniVerse printer configuration files)
  • Forms server (Windows):
    • C:\Program Files\EclipseForms (contains your Eclipse Forms software)
    • C:\Users\All Users\Application Data\EclipseForms (contains your Eclipse Forms configuration files)
  • Internet Gateway (IGATE) server (Windows):
    • All shared directories containing Eclipse web sites (ex IIS shared directories, etc.)
  • Imaging server (Windows):
    • All shared directories containing Eclipse file shares (ex image attachments, signature scans, etc.)

The UniVerse database must be stopped or suspended during backup to ensure data consistency. The standard Eclipse backup scripts have been modified to use snapshots to allow backups to take place on active systems.

While backing up the directories below should be minimally sufficient to recreate your system in the event of a disaster, backing up the entire system is always recommended when possible. By backing up the entire system, you protect against the loss of miscellaneous files or those inadvertently placed outside of their standard locations.

How do I install or update the RealPort drivers for my Digi PortServer on Linux?

To use the Digi PortServer, you’ll need to install the appropriate RealPort drivers for your kernel.

Additionally, any time the kernel is upgraded, you’ll need to recompile and reinstall the drivers. As such, it is important to plan your kernel upgrades in advance and perform testing after the first boot using a new kernel.

Screencast

Installing or Upgrading the Digi RealPort Drivers

If the drivers are already installed, uninstall the existing drivers:

rpm -e dgrp

Download the latest drivers, for example:

mkdir -p /esupport/digi && cd /esupport/digi
wget -c http://ftp1.digi.com/support/driver/40002086_AA.src.rpm

Download and install the Red Hat kernel source:

yum -y install kernel-headers-`uname -r` kernel-devel-`uname -r` rpm-build gcc ncurses-devel

Compile the drivers:

rpmbuild --rebuild /esupport/digi/40002086_Z.src.rpm

Install the drivers:

rpm -Uvh /usr/src/redhat/RPMS/x86_64/dgrp-1.9-39.x86_64.rpm

OR

rpm -Uvh /root/rpmbuild/RPMS/x86_64/dgrp-1.9-39.x86_64.rpm

Edit udev to set permissions for tty devices:

vim /etc/udev/rules.d/10-dgrp.rules

Locate the “tty_dgrp” entry, and modify it as displayed below:

KERNEL=="tty_dgrp*", PROGRAM="/usr/bin/dgrp_udev %k", NAME="%c", GROUP="lp", MODE="0666", OPTIONS="last_rule"

Adding Digi Ports to Linux

If this is a new Digi, setup the ports in the following manner:

dgrp_cfg_node init (ttyid) (ip_address) (number_of_ports)

Example (change the IP address and number of ports to match your device):

dgrp_cfg_node init D 192.168.100.111 1

Starting the Digi Service

When the drivers have been installed, and the ports have been configured, start the Digi service to activate the serial ports:

service dgrp_daemon restart

Adding Digi Ports to VSI-FAX

If you are configuring VSI-FAX for the first time, or if you’re adding a new fax modem to your environment, you’ll need to make VSI-FAX aware of the new modem’s serial port location. For example, to create a new modem called modem1 at the serial port location /dev/ttyD00:

vfxadmin device -a -d -v /dev/ttyD00 modem1

After adding the modem to VSI-FAX, you will also need to add the modem to the default fax “pool” or class. To add the new modem1 to the default fax “pool” named fax1:

vfxadmin class -d -a modem1 fax1

How do I manage Linux print queues?

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

To administer print jobs, first log into the server as root before running any of the following commands.

UniVerse Spooler Commands

  • To view the status of a UV print queue:
usa -p lp1
  • To enable a UV print queue:
usa +o -p lp1
  • To manually start the UV spooler:
cd /u2/uv
bin/usd /usr/spool/uv -t
    • To cancel print jobs from the UV Spooler:

For a specific job number:

usm -k 12345

For an entire queue:

usm -k -p lp1

Linux (CUPS) Spooler Commands

  • To view the status of all print queues:
lpc status
  • To check the status of a single print queue and view a list of pending jobs:
lpc status lp1
lpstat -P lp1
lpstat -plp1
  • To remove a single print job:
cancel lp1-1234
  • To remove all print jobs in a queue:
cancel -a lp1
  • To enable  a queue:
cupsenable lp1
  • To disable a queue:
cupsdisable lp1
  • To enable all queues:
lpstat -p | grep disabled | awk '{print $2}' | xargs cupsenable
  • To print a test job:
echo test | lpr -P lp1
  • To restart/refresh the cups service:
service cups restart

Resources