Troubleshooting
If searches in a table are slow, ensure that the overnight/weekly maintenance is being run, in particular, Perform batch updates and Compact and re-index tables.
Use TexAdmin to determine the overflow record count:
- Open a command line session on the EMu server and log in with the username emu.
- Type
client client
to go to the required EMu client environment. - Type TexAdmin table name
For example,
TexAdmin eparties
- Select Batch>Size from the Menu bar.
The number of records in the overflow file displays. If the overflow is greater than 100 records, an index rebuild may be required.
If tables do not display consistent data for the same records, they may be out of sync. This may be due to a Background Load process failing to run:
- Check the status of the Background Loads processes.
- Restart the Background Load process for any table with a
dead
status.
If a user is unable to connect to a module, check whether it is off-line or closed:
- Open a command line session on the EMu server and log in with the username emu.
- Type
client client
to go to the required EMu client environment.
To check whether the table is off-line:
- Type
emustatus [name of table]
For example,
emustatus eparties
A message displays the status of the table, e.g.:
Cannot access database eparties. Database is offline
The table may be off-line because it is currently being re-indexed. Wait until the re-index is complete and then check the status again.
To check whether the table has been closed:
- Type
texstatus name of table
For example,
texstatus eparties
A message displays the status of the table, e.g.:
emu-mirror/izlive@kenya[30] texstatus eparties
Warning! "eparties" database is closed
- To open the table, type texopen name of table
For example,
texopen -q eparties
Note: Consult the installation documentation / release notes.
If a user is unable to connect to the server, check:
- The inetd.conf file is present and pointing to the correct emurun script.
- Mapping of the port numbers in the services file.
- Network connectivity.
- The inetd program is running.
- Open a command line session on the EMu server and log in with the username emu .
- Type
client [client]
to go to the required EMu client environment. - Type
cd /etc
- Type
vi inetd.conf
- Look for the line that invokes the server for your client environment. It will be similar to:
emugallery stream tcp nowait root /home/ke/emu/emugallery/bin/emurun emurun texserver -aemu -i -L -t60
Check that the path for emurun is correct.
- Open a command line session on the EMu server and log in with the username emu .
- Type
client [client]
to go to the required EMu client environment. - Type
cd /etc
- Type
vi services
- Look for the line that maps the service name to the port number. It will be similar to:
emugallery 20042/tcp # gallery
For Interix servers the line will be similar to:
emugallery 20042/tcp # gallery^m
- Check that the port number matches the correct alias used in the EMu client.
The services file on the client must match the services file on the server. To view and edit the services file, open it in Notepad (c:/WINNT/system32/drivers/etc/services).
- If the inetd.conf file or the mapping in the services file are incorrect, adjust them accordingly.
- Select Start>Programs>Accessories>Command Prompt.
The Command Prompt window displays.
- Type
ping [server name]
For example,
ping kent
- Open a command line session on the EMu server and log in as
root
. - In Linux, Solaris or Interix type
ps -ef | grep inet
In FreeBSD, type ps -axvuemu | grep inet
Something similar to the following will display:
root 322 1 0 Aug-01 ? 00:00:00 /etc/inetd
emu 10495 9623 0 12:33:00 ttyp7 00:00:00 grep inet
- If inetd is not running, restart it.