HELIOS PCShare 3.1 User manual


7 Technical support
7.1 Standard UNIX utility programs
The following standard UNIX tools can help you when configuring PCShare and diagnosing network problems. Other UNIX tools, such as HELIOS' "swho" or "ifstat" commands are described in the HELIOS Base manual.

Important: Your UNIX host name must never include a slash ("/") character (for example "my_rs/6000"). It is best to use lower case characters only, no spaces, no underlines and no punctuation marks except hyphens. A slash causes problems with EtherShare, PCShare, etc. because "/" is also the directory path separator.

The following programs to determine the host's name and internet address are often available:
hostname,
uname
The "hostname" command (BSD systems) or the "uname" command (System V systems) can be used to determine a UNIX computer's host name. Call "uname" with the -n switch (uname -n). Use the -a switch instead to see your operating system version, too.
arp
"arp" is used to display and edit the UNIX host's "internet address/computer name" conversion table. If the "arp" command includes a computer name as a command line argument, it tries to get more information on the specified computer, including its internet address. Although the conversion table does normally not contain information on your own host, it is often still possible to determine its internet address in this way, for example:
$ <path>/arp helios
0021-237 arp: The entry helios (192.9.200.11) is
not present in the local arp table.
7.2 Error Messages
The following section lists and describes the most important error messages for all UNIX program modules.
All error messages are constructed the same way. They start with the name of the issuing program followed by the UNIX process ID [in brackets]. This is then followed by a verbose error message which may include variable strings and numbers, for example:
pcshare[12345]: %s: sendmsg to %s failed, %m
In the following, strings are abbreviated by "%s", numbers by "%d", UNIX system error messages by "%m", and long hexadecimals by "%lx". Refer to your UNIX documentation for more information on UNIX system error messages.
7.2.1 "license" error messages
All PCShare servers verify the integrity of the executable image by performing a checksum and verify the license by reading the license file "HELIOSDIR/var/conf/license".
Program file corrupted, please reinstall
The program checksum did not match. A common reason is that you have transferred your PCShare installation via FTP and you have forgotten to set FTP to image (binary) mode.
/usr/local/helios/var/conf/license: %m
The license file could not be opened, probably because it is missing.
No valid PCShare license found
The license file "HELIOSDIR/var/conf/license" contains no valid license for PCShare.
The demo license has expired
PCShare demo versions run for a limited time, and the license has now expired. Each user is warned at every login to the file server that he is using a demo version, and also for how many days the license will still be valid. Thus, the expiry should not take effect surprisingly.
The license checksum is invalid
The "Checksum" field in the license does not match the data in the other fields. This should not happen as the installation procedure verifies that a license is valid before entering it into the license file. However, this error message may appear e.g. if you have upgraded from PCShare 2.5 to PCShare 3 but still use the old key, or when you installed another version of the product to another directory and the data mix up.
The license is not valid on this machine
The "MachID" field of the license does not match the host's machine ID. This might happen if you transfer a complete installation to a new host or if you get a new machine due to a hardware replacement. Contact our license department for a license transfer.
Missing required base license %08lx
The user expansion license did not find the proper base serial number. Verify that you have specified the proper base serial number when requesting the user expansion license from our license department.
7.2.2 "generic" error messages
Most programs issue a generic error message when anything goes wrong for a simple system call.
syscall: %m
Various error messages from system calls are logged-in this form. "syscall" is one of the common system calls (fork, malloc, -) and "%m" gives the reason why the call failed. Common reasons like "No more processes" or "Not enough core" point to resource shortages, such as "not enough swap space", or "process table too small". Refer to your UNIX documentation for more details.
7.2.3 Printer interface errors and status messages
Since, under PCShare, printer interface programs are referenced by the logical (UNIX) printer name rather than their real name (such as "smbif" or "pcif") it is necessary to look up the real program name (e.g."epson" or "deskjet") in the "HELIOSDIR/var/spool/qmeta/" directory. The following section describes errors using the real program names.
7.2.4 Messages shared by all printer interfaces
The following messages can be issued by any of the printer interfaces, no matter if issued by PCShare or EtherShare:
Usage: %s [-n user] [-h host] [acctfile]
The interface program "%s" was called with missing or wrong parameters.
Cannot create an unique log filename: %m
A temporary file name for saving error output until the real error message file has been established could not be determined. System call failure.
Cannot open log file '%s': %m
The temporary file "%s" for saving error output until the real error message file has been established could not be created. System call failure.
Cannot initialize library libsched.
The "libsched" shared library could not be initialized. Mostly a system call failure.
Cannot initialize library libhelios: Error %d
The "libhelios" shared library could not be initialized. Error is given in "%d".
Cannot find product locations: %s
None of the locations (directories) of the HELIOS products were found. "%s" is an explanatory error message.
Cannot find HELIOS PCShare product location.
The HELIOS PCShare product location (directory) could not be found. Mostly an installation error.
Cannot find executable '%s'.
The executable program could not be found. Mostly an installation error.
Cannot open resource '%s': %s
The named resource "%s" could not be opened. "%s" is an explanatory error message.
Cannot initialize library libprint: %s
The print support library could not be initialized. "%s" is an explanatory error message.
Cannot initialize resource messages '%s': %s
The message string handling for the message block "%s" could not be initialized. "%s" is an explanatory error message.
License initialization failed
License code init failed. Mostly a lack of system resources.
License read failed
License file is seriously corrupted.
No valid license found
No valid license could be found in the license file.
Invalid license
The license found is not valid.
Printer not in printcap
The printer does not have an entry in the file
"HELIOSDIR/var/conf/printcap".
Missing spooldir entry in printcap
The printer has an entry in "HELIOSDIR/var/conf/printcap" but lacks the information about its spool directory.
Error while restarting lpd
A fatal error occurred while restarting the line printer daemon. Mostly a UNIX system failure caused by a lack of system resources or an already running "lpd".
No current control file
The current print job does not have a control file. This may occur in case a printer interface program is started manually and not by the "lpd".
No history information found
The current print job should have a history entry in its control file but none is found. This occurs with damaged control files either created while the system was out of resources or manipulated manually.
No such printer in cap
The printer requested has no entry in the file
"HELIOSDIR/var/conf/printcap".
No such value in cap
The capability requested is not listed in the printer's capabilities.
Output from lpd: %s
The line printer daemon process issued the output "%s" while starting or handling requests. This output normally is an error message and indicates a serious problem of the "lpd" system.
Allocation of %d bytes failed: %m
A memory block of "%d" bytes could not be allocated. This indicates a lack of virtual memory.
Cannot parse filename '%s'
The file name "%s" could not be parsed into its key and path parts. This indicates a configuration error of a preference value.
Cannot open file '%s'
The file "%s" could not be opened. This indicates an access problem either because the file does not exist or there are not enough privileges to open the file.
Cannot find spool directory for printer '%s': %s
The spool directory for printer "%s" does not exist. "%s" is an explanatory error message.
Cannot open printer queue '%s': %s
No information could be gathered for printer queue "%s". This indicates a configuration error. "%s" is an explanatory error message.
Cannot query status for queue '%s': %s
The status of the printer queue "%s" could not be determined. This indicates a configuration error. "%s" is an explanatory error message.
Cannot read control file for current job: %s
The control file of the current print job cannot be read. This indicates a damaged or missing control file. "%s" is an explanatory error message.
Cannot rewrite control file '%s': %s
The modified print job's control file could not be written. This indicates a UNIX system call failure. "%s" is an explanatory error message.
Cannot open job history file '%s': %m
The print job's history file could not be opened due to a UNIX system call failure.
Cannot seek in job history file '%s': %m
The print job's history file could not be sought due to a UNIX system call failure.
Cannot seek in job log file: %m
The print job's message log file could not be sought due to a UNIX system call failure.
Cannot write to job history file '%s': %m
Writing to a print job's history file failed due to a UNIX system call failure.
Cannot write to job log file: %m
Writing to a print job's message log file failed due to a UNIX system call failure.
Cannot add job history to control file: %s
The job history file entry could not be appended to a job's control file. "%s" is an explanatory error message.
Cannot find resource '%s': %s
The HELIOS resource "%s" could not be found. This indicates a corrupted program file. "%s" is an explanatory error message.
Cannot fstat() '%s': %m
Information on an open file could not be retrieved due to a UNIX system call failure.
Cannot disable queue after fatal error: %s
The status of the printer queue for the current job could not be changed. "%s" is an explanatory error message.
Cannot copy job to error queue: %s
The current print job could not be copied to the error queue after job completion. "%s" is an explanatory error message.
Cannot restart error queue: %s
The error queue could not be restarted after a job had been copied. "%s" is an explanatory error message.
Cannot mail to print job initiator: missing user name
A printer interface program could not send mail to a print job's originator because the originator is unknown.
No mailer program found
A printer interface program could not find the required program for delivering mail to a print job's originator. This is mostly caused by an inappropriate system installation.
Cannot read from job log file: %m
A UNIX system call error occurred while reading from the job's message log file.
Error while opening mailer: %m
A printer interface program could not start the required program for delivering mail to a print job's originator. This is mostly caused by an inappropriate system installation.
Error while writing to mailer
A UNIX system call failed while piping data to the mailer program. This is mostly caused by an unexpected abortion of the mailer program due to e.g. a lack of resources.
Cannot copy data to '%s': %m
A UNIX system call failure occurred while copying data to a file or location "%s".
Error while writing to '%s': %m
A UNIX system call failure occurred while writing data to the file "%s".
Cannot reopen file '%s': %m
A UNIX system call failed while trying to reopen the just created file "%s".
Cannot open file '%s': %m
A UNIX system call failed while trying to open the file "%s".
Cannot open pipe to '%s': %m
A UNIX system call failed while trying to open a pipe to the program "%s".
Error during read: %m
A UNIX system call failed while reading data from a file.
Error while writing: %m
A UNIX system call failed while writing data to a file.
Cannot parse PostScript: %s
An error occurred while parsing PostScript data. "%s" is an explanatory error message.
Cannot create temporary string stream: %m
A UNIX system call failed while creating a temporary stream.
Unknown or illegal option '%s'
The unknown or illegal option "%s" was supplied to a printer interface program.
Cannot read directory '%s': %m
The UNIX directory "%s" could not be enumerated due to a UNIX system call failure.
Missing version in procset file '%s'
The procset file "%s" does not contain a version string and therefore is ignored.
Cannot move font to fontlist: %s
An error occurred while moving font information between internal lists. "%s" is an explanatory error message.
Your print job has been interrupted.
A print job has been canceled by user request.
Printing disabled due to a fatal error. Please inspect system and printer logs.
A fatal error occurred while initializing a printer interface program. This error will be a persistent system failure and would cause the following print jobs also to fail. Therefore the printer queue has been stopped until the cause of the failure has been eliminated. The queue has to be restarted manually.
Error on printing device:
A serious error occurred on a printing device. More error output follows this message.
Cannot add execution op
An internal execution operation failed. This mostly occurs in case the system is low on virtual memory. More error output follows after this text.


© 2003 HELIOS Software GmbH