-
Notifications
You must be signed in to change notification settings - Fork 64
Problems with wls module #6
Comments
I can confirm the problem is related to copying of the file. I made a change in your module to use a symlink rather than making a copy (I have the installer in a network drive that I mount in the Vagrant machine) and that seems to work fine. Maybe this should also be added as an option, since there is no real need to copy the file if you have it in a common folder, and it is about 1GB large. |
Hi, Can you use this puppetDownloadMntPoint parameter and point this to the folder of the wls jar and this should copy this to /tmp else default it will look at the files folder of the wls module or you can add an location entry to fileserver.conf of the master puppet configuration
I use this in a masterless configuration. Thanks |
Hi, Both options (with Could the problem be arising because the copying of the file takes too long? (It's 1GB) Is there any timeout for puppet operations of something like that? Cheers |
Hi, The only thing I can think of that I use puppet enterprise and this uses passenger which can better handle downloads, are you using puppet opensource and what is the puppet version you are using. Thanks |
I'm using the free version of Puppet indeed. Well, at least you know there might be a problem with this. My |
Ok thanks, last weekend I made some changes to support puppet 3.0 but I will also check the latest opensource puppet edition. |
Is there enough space on your /tmp filesystem? Maybe that's why the copy fails. |
I am having a problem as well trying to get these modules to run under Vagrant. I can get the first module to install fine by itself. When I add the I am trying to install into include jdk7
jdk7::install7 { 'jdk1.7.0_40':
version => "7u40",
fullVersion => "jdk1.7.0_40",
alternativesPriority => 18000,
x64 => true,
downloadDir => "/install/jdk7",
urandomJavaFix => false,
sourcePath => "puppet:///modules/jdk7/"
}
include wls
wls::installwls { 'wls1036':
downloadDir => '/install/wls',
version => '1036',
fullJDKName => 'jdk1.7.0_40',
oracleHome => '/opt/Oracle',
mdwHome => '/opt/Oracle/Middleware',
} This is the output I get when I only run the Notice: /Stage[main]//Node[default]/Jdk7::Install7[jdk1.7.0_40]/Javaexec[jdkexec jdk1.7.0_40 7u40]/Exec[default java alternatives jdk1.7.0_40]/returns: executed successfully
Notice: Finished catalog run in 29.21 seconds And this is what I get by running the Notice: /Stage[main]//Wls::Installwls[wls1036]/Exec[installwls /install/wls/wls1036_generic.jar]/returns: executed successfully
Notice: Finished catalog run in 220.93 seconds I really would like to get this automated and working so I can upgrade when I need to without having to repackage my virtual machine from the ground up. |
hi, you can add a require in wls install which points to jdk . and please use the github puppet modules and not from force. ( github is the latest ) thanks |
Thanks for the quick response, I am using the github repo modules. I am trying to adapt that example to 1036 but not having much rapid progress. I am struggling with getting the domain configured now. |
Great, here some more info for vagrant and weblogic. what do you want for template? , I can make a custom demo file for you in a few minutes. Thanks |
I have gotten past those issues, now I am fighting with getting JDBC vagrant@sles11sp3x64:/install> sudo puppet apply --modulepath Here is the contents of the /install/gmomog11createJdbcDatasource.py wlsUser = 'weblogic' #dsName, jdbcDatasourceTargets, dsName = 'gmomm011' jdbcDatasourceTargets = 'AdminServer' dsJNDIName = 'jdbc/gmomm011' dsDriverName = 'oracle.jdbc.xa.client.OracleXADataSource' dsURL = 'jdbc:oracle:thin:@dbagent1.alfa.local:1521/ dsUserName = 'ordermp' dsPassword = 'stupid01' datasourceTargetType = 'Server' globalTransactionsProtocol = 'xxxx' useStoreConfig = 'false' if useStoreConfig != "true": print "datasource " +dsName datasourceTargets=String(jdbcDatasourceTargets).split(",") for datasourceTarget in datasourceTargets: print "dsJNDIName " +dsJNDIName edit() try:
'/JDBCDataSourceParams/' + dsName )
'/JDBCDriverParams/' + dsName )
'/JDBCConnectionPoolParams/' + dsName )
'/JDBCDriverParams/' + dsName + '/Properties/' + dsName +
'/JDBCDataSourceParams/' + dsName)
',Type='+datasourceTargetType) )
except: Jarrod Roberson |
Hi, I don't see an error, can you ping and connect to the dbagent1.alfa.local server and can you set logOuput parameter on the wlst manifest to true or try to create it manually in the weblogic console Thanks |
What if I am just trying to configure the connection pools and I don't On Fri, Oct 11, 2013 at 4:36 PM, Edwin Biemond notifications@github.comwrote:
Jarrod Roberson |
ok that explains , your py script looks ok |
Using your "example 3" template I have everything working except starting I am getting Stderr from the command: Error: java -Dweblogic.security.SSL.ignoreHostnameVerification=true I tried running this manually and it fails as well. What do I have to do to get my AdminServer up and running from the puppet attached is my manifest file On Fri, Oct 11, 2013 at 4:36 PM, Edwin Biemond notifications@github.comwrote:
Jarrod Roberson |
Hi, I can't see your file but for starting the adminserver I will connect to the nodemanager so please lookat the readme.md ( class wls1036osb_soa and wls_osb_soa_domain optionally remove the bsu, osb and soa part ) or example conf 2 cluster , that are the right steps. set the defaultsWls::Installwls { Wls::Nodemanager { Wls::Bsupatch { installwls::installwls{'11gPS5':} weblogic patch 10.3.6.0.5wls::bsupatch{'p16619891': #nodemanager configuration and starting |
I have gotten to the where I try and start the nodemanager and the admin Seems the nodemanager just doesn't start. if I do /opt/Oracle/Middleware/wlserver10.3/server/bin/startNodeManager.sh I can start the AdminServer from the domain bin/startWeblogic.sh just fine. I can't get the puppet stuff to act right ... Notice:
Stderr from the command: Error: java -Dweblogic.security.SSL.ignoreHostnameVerification=true On Tue, Oct 15, 2013 at 4:45 PM, Edwin Biemond notifications@github.comwrote:
Jarrod Roberson |
Hi, weblogic.nodemanager.NMConnectException: Connection refused. Could not connect to NodeManager. Check that it is running at localhost:7001. Or the nodemanager is not started or you are not connecting to port 5556 Ok can you paste your class configuration and paste this startAdminServerstartWlsServer2.py script this is my start script python script wls:wlscontrol
|
Thanks so much for the help, I finally have gotten things installing like I I will be sending you some pull requests when I get things tidied up a That said, the one thing I can't get to work is the I am trying to pass in osDomain and it just ignores what I trying to send I hope I don't have to directly edit the params.pp file? Here is the snippet from my site.pp file: orautils::parms { orautils::nodemanagerautostart{"autostart weblogic 1036": no matter what I set osDomain to, the startWeblogicAdmin.sh and Any advice? On Thu, Oct 10, 2013 at 2:47 PM, Edwin Biemond notifications@github.comwrote:
Jarrod Roberson |
Hi, first can you use this ( there is a difference between FMW 11g = 1111, nodemgr part of mdw home and FMW 12c = 1212, part of the domain ) so with version 1111 , no need for domain name etc.
and indeed you need to change the params.pp and add your own machines and their values. thanks |
and this I fixed it usage: change the params.pp class so the defaults match with your environment or add extra changes based on the hostname include orautils class{'orautils': |
Hi, This is working for me when installing WebLogic 10.3.6 with Vagrant and I also got download errors on some big soa files I put the wls jar in the vagrant shared folder set the permissions in vagrant when you need to extract zip files
in puppet set the swap file
and the weblogic install
hope this helps |
Hi,
I'm trying to use Vagrant to set up a machine with JRockit and Web Logic Server up and running. Vagrant allows provisioning using Puppet, which I'm trying to do using your Puppet modules. The jrockit module is working fine, but I'm having problems with the wls module.
Here's my Puppet manifest file:
The
wls-sysctl.pp
file contains thesysctl
setup you advise in the README (is it necessary BTW, or just advised?)Here's the vagrant log:
It looks to me like the problem is that the WLS installation file is not being properly copied somehow. Here are the contents of my
/tmp/
folder:As you can see the
wls1036_generic.jar
file is empty and has some temporary extension. Any clue what might be going wrong here?The text was updated successfully, but these errors were encountered: