Problem Description

 

Please refer this article if you face any permission related issues while accessing Infoworks logs


Workaround/ Resolution

 

By default, Infoworks ships log directories with permissions of 755. Any new directories and files under this will have permissions based on the system's umask settings. The system’s umask default value is 022 so that new files will have 755 permissions.


Infoworks Service log locations:


Service logs
Location
Service info for UI
$IW_HOME/logs/apricot/apricot-out.log
Service info for Governor
$IW_HOME/logs/governor/governor.log
Service info for Hangman
$IW_HOME/logs/hangman/hangman.log
Service info for Rest API
$IW_HOME/logs/rest-api/iw-rest-api.log
Service info for Scheduler Service
$IW_HOME/RestAPI/apache-tomcat-7.0.63/logs/catalina.out
Service info for Data Transformation
$IW_HOME/df/apache-tomcat-8.0.33/logs/catalina.out
Service info for Cube Engine
$IW_HOME/cube-engine/logs/kylin.log
Service info for HA Service
$IW_HOME/logs/ha/ha.log
Service info for Monitoring Service
$IW_HOME/logs/mongod.log
Service info for Postgres
$IW_HOME/logs/pgsql.log
Service info for Orchestrator Webserver
$IW_HOME/logs/orchestrator/orchestrator.log
Service info for Orchestrator Engine Webserver
$IW_HOME/orchestrator-engine/airflow-webserver.log
Service info for Orchestrator Engine Scheduler
$IW_HOME/orchestrator-engine/airflow-scheduler.log
Service info for Orchestrator Engine Worker
$IW_HOME/orchestrator-engine/airflow-worker.log
Service info for RabbitMQ
$IW_HOME/logs/rabbit*.log
Service info for Nginx
$IW_HOME/resources/nginx-portable/logs/*.log
Service info for MongoDB
$IW_HOME/logs/mongod.log

 

 

IMPORTANT: Infoworks user must have write permissions to the logs directory.