[ 
https://issues.apache.org/jira/browse/RANGER-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hisham Ismail updated RANGER-3217:
----------------------------------
    Summary: Ranger's Atlas plugin throws unexpected errors  (was: Ranger's 
Atlas plugin throught unexpected errors)

> Ranger's Atlas plugin throws unexpected errors
> ----------------------------------------------
>
>                 Key: RANGER-3217
>                 URL: https://issues.apache.org/jira/browse/RANGER-3217
>             Project: Ranger
>          Issue Type: Bug
>          Components: plugins
>    Affects Versions: 2.1.0
>            Reporter: Hisham Ismail
>            Priority: Blocker
>             Fix For: 2.1.0
>
>
> After deploying atlas with ranger plugin enabled, we receive the following 
> errors in the logs:
>  2021-03-22 08:10:26,633 ERROR - [main:] ~ 
> addResourceIfReadable(ranger-atlas-policymgr-ssl.xml): couldn't find resource 
> file location (RangerConfiguration:63)                                        
>                                                                      │
> │ 2021-03-22 08:10:26,643 ERROR - [main:] ~ 
> addResourceIfReadable(ranger-atlas-atlas-audit.xml): couldn't find resource 
> file location (RangerConfiguration:63)                                        
>                                                                        │
> │ 2021-03-22 08:10:26,644 ERROR - [main:] ~ 
> addResourceIfReadable(ranger-atlas-atlas-security.xml): couldn't find 
> resource file location (RangerConfiguration:63) 
>  
> In our install.properties file we used service_name = atlas and this error 
> changes on different values of service_name. On the ranger webui the plugin 
> is green with 200 and if i reinstall and use an invalid service name atlas 
> crashes. Therefore, i assume that the plugin is somehow working (I also 
> tested a simple feature) but i am not sure if these errors are causing harm 
> or making the plugin not fully functional. Can you please advise?
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to