| Summary | CFR logs to two different logs files, one with today's date and another with a date from the past which has logging from all days up to today. |
|---|---|
| Article Number | 36183 |
| Environment | Orbix 6.x All Supported Platforms |
| Question/Problem Description | Two log files are created for the CFR, both are being written to. |
| Clarifying Information | By default Orbix services will create a new log file each day with the date concatenated to the end. In this instance this is still done, but the first day to encounter this error will have logging from all days until the service is restarted. |
| Error Message | Fri, 01 Oct 2012 11:11:11.0000000 [host:] (IT_ATLI2_IP:101) E - could not write to '/IT_PRODUCT_DIR/var/DOMAIN_NAME/logs/config_rep_hostname.log.10012012', sending to stderr |
| Defect/Enhancement Number | |
| Cause | Unknown at this time, but it is suspected this may be caused due to faulty disk access. Ensure that all files for logging and databases for Orbix services are stored on a local disk, rather than an NFS mounted disk. It appears that once an Orbix service gets the write error a thread ends up holding on to this FD and will sometimes get the write error and will never create a new file. Meanwhile all other threads are able to write to the file and will create a new file each day as expected. Note this is speculation as the issue was only ever seen once and could not be reproduced or debugged as it was in a release environment. |
| Resolution | Restarting the configuration repository will release the bad FD and all logging will return to normal. |
| Workaround | |
| Notes | |
| Attachment |
| Created date: | 13 November 2012 |
|---|---|
| Last Modified: | 12 February 2013 |
| Last Published: | 13 November 2012 |
| First Published date: | 13 November 2012 |
#KnowledgeDocs
#Orbix