Could not prefetch wls_setting provider 'yaml': undefined class/module file about biemond-orawls HOT 6 CLOSED

Hooo-kay... Stupid weblogic...
I got dns domain name incorrectly setup and dnsdomainname/host lookup was failing.
After fixing that all started to work... +1000 points to weblogic for "helpful" error mesages.
Sorry to bother you, seems to be working now.

G.

from biemond-orawls.

Hi,

Just to be sure can you restart all the PE services on the master ( because of module caching) and do a puppet run on the master ( this will load the easy_type module )

I know puppet changed the used internal yaml ruby gem, maybe the upgrade did not update gem.
Can you try it on a new PE 3.3.2 node and did you also upgrade the clients.

this is the wls_setting yaml type & provider

type load the yaml gem
https://github.com/biemond/biemond-orawls/blob/master/lib/puppet/type/wls_setting.rb

and this is the provider which is probably not found.
https://github.com/biemond/biemond-orawls/blob/master/lib/puppet/provider/wls_setting/yaml.rb

Thanks

from biemond-orawls.

Hi,

I deleted /etc/wls_setting.yaml and this error went away.
I noticed that it was a very big file (4-5 screens long?) (generated on PE 2.8.7) with lots of references. Looked a lot like duplicated sections. (unfortunately I no longer have that file)
When it was recreated on PE 3.3.2 it looks now like in your vagrant example (only order of lines is reversed).

Now I have another issue - when starting admin server I get following error:

<The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: java.lang.ExceptionInInitializerError.
weblogic.security.service.SecurityServiceException: java.lang.ExceptionInInitializerError
<The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: A failure occurred attempting to load LDIF for provider Authorizer from file /opt/oracle/middleware12c/wlserver/server/lib/XACMLAuthorizerInit.ldift

I have absolutely no idea what is wrong - it works on your vagrant example and I copied that configuration to my machine almost 1:1 - source file locations are different, but that would be all...

Regards,
G.

from biemond-orawls.

Ah ok

so probably in PE 2.7 this was not working well because you should have only 1 unique entry in wls_setting.yaml

Really strange you get this error, I have never seen this.
Maybe the domain creation when wrong. Can you find this file /opt/oracle/middleware12c/wlserver/server/lib/XACMLAuthorizerInit.ldift and does it have the right user & group permissions.

maybe in the vagrant box I override the default oracle user with wls, else it will use oracle as user and get some strange errors.

  puppet.facter = {
    "environment"            => "development",
    "vm_type"                => "vagrant",
    "override_weblogic_user" => "wls",
  }

from biemond-orawls.

Permissions on this file are the same as in your vagrant box:
-rw-r-----. 1 oracle dba 72797 May 21 18:56 /opt/oracle/middleware12c/wlserver/server/lib/XACMLAuthorizerInit.ldift

There is no user wls, what does that "override_weblogic_user" => "wls" do?

from biemond-orawls.

Great you found it.

Cheers

from biemond-orawls.