Troubleshooting And Support
- Communication programs initially write messages to the
syslog (/var/log/messages) until it is
possible to write log messages to its own specific log file.
- Look in file /var/log/messages, files in directory
webit/test/logs (test system), or files in directory
webit/prod/logs (prod system) for error messsages.
- Look in /var/log/httpd/access_log and /var/log/httpd/error_log
for messages generated by apache.
- The interface programs can be run standalone from the command line if no
logfile output is available. Look for error messages when running programs
form the command line. The -p option is used to pass a profile name to
- Many problems are attributable to incorrect access permissions.
Verify all files are assigned to the zwebit user id and zwebit group.
- cd /usr/local/zwebit
- chown -R zwebit.zwebit *
- The HSC zWebit programs utilize the PostgreSQL
relation database management system (RDBMS). The RDBMS must be operational
and running for any of the zWebit programs to function
|Stop and start options do not work on the View Interfaces menu
||Verify the script files in the webit/bin directory exist and
work correctly; verify the programs have the setuid bit set and are owned
by user zwebit, group zwebit in usr/local/bin
|Records appear to be sent but ACK/NAK not working
||Check framing characters
|Message "error opening logfile"
||Verify the directory exists and the program has write permission on the
|Delivery programs do not wake up or process new inbound data
||Verify the pipe path and name settings in the acquisition program profile
are set up to use the EXACT same pipe path and name as the delivery program.
Also verify directory exists with valid access permissions.
|On the web-based front end, selecting view log files does not
||Verify symbolic link to the test/logs and prod/logs directory into
the html directory. If it does not, create the symbolic link with the
- cd /usr/local/zwebit/html
- ln -s ../test/logs tlogs
- ln -s ../prod/logs plogs
||A bind error is a result of one side of a TCP/IP communication
remaining active and the other side of the interface is trying to reconnect.
A bind error is like a phone "busy signal", the other side must hang up
before the initiating program can restart the link. If both programs
(client and server) are inactive and this message still occurs, wait a couple
minutes. The problem is eventually cleaned up by the OS
Send an email to email@example.com for further
Visit the GNU home page.
FSF & GNU inquiries & questions to
Comments on these web pages to
Copyright (C) 2003 HealthCare Systems and Consulting
Verbatim copying and distribution of this entire article is
permitted in any medium, provided this notice is preserved.
Last updated: 07/21/2003