[recommended scope: Support only]Client reports "Repository not accessible". repserver.log reports "File system error 0x1c, aborting".
book
Article ID: KB0086283
calendar_today
Updated On:
Products
Versions
TIBCO InConcert
-
Not Applicable
-
Description
Resolution: Description: ============ The client, usually the PC GUI, reports "Repository not accessible".
Environment: ========== Solaris 10. May apply to other UNIX variants.
Symptoms: ========= Besides the error message from the client look in $IC_HOME/logs/<server_name>_repserver.log. If you find "IcRepServer Error File system error 0x1c, aborting" then this solution would also apply.
Cause: ===== The RepServer is reporting a file system error. The code 0x1c (26 decimal) can be found in /usr/include/sys/errno.h which is ETXTBSY 26 /* Text file busy*/". This is a file system Operating System error. Look in /var/adm/messages for file system error messages. What was found with the first report of this error was" [ID 845546 kern.notice] NOTICE: alloc: /: file system full". This error was being reported even though sub directories on different file systems were reporting less than 50 per cent full.
Resolution: ========= Provide more disk space or free up space on the main hard drive.
References: ==========
See also SOL1-OF1Z. This solution has the more common error conditions.
Issue/Introduction
[recommended scope: Support only]Client reports "Repository not accessible". repserver.log reports "File system error 0x1c, aborting".