maven-weblogic-plugin : list-apps doesn't work on adminport - weblogic12c
I have a maven project,with weblogic-maven-plugin (groupid com.oracle.weblogic , version 12.1.3-0-0).
When I run weblogic:list-apps through HTTP protocoll it works fine:
[DEBUG] Configuring mojo 'com.oracle.weblogic:weblogic-maven-plugin:12.1.3-0-0:list-apps' with basic configurator -->
[DEBUG] (f) adminurl = t3://host:port
[DEBUG] (f) advanced = false
[DEBUG] (f) debug = true
[DEBUG] (f) examples = false
[DEBUG] (f) failOnError = true
[DEBUG] (f) noversion = false
[DEBUG] (f) password = password
[DEBUG] (f) remote = false
[DEBUG] (f) timeout = -1
[DEBUG] (f) user = username
[DEBUG] (f) verbose = true
[DEBUG] (f) version = false
[DEBUG] -- end configuration --
[INFO] Command flags are: -adminurl t3://host:port
weblogic.Deployer invoked with options: -noexit -listapps -user weblogic -debug -verbose -adminurl t3://host:port
app1
app2
Number of Applications Found : 2
Today I've set domain-wide admin port (and managed server's local admin ports overrided also)
Running the same commands including authorization details and turn into HTTPS protocoll. Changes:
Switched to t3s://host:adminport
added
-Dweblogic.security.SSL.ignoreHostnameVerification=true
-Dweblogic.security.TrustKeyStore=CustomTrust
-Dweblogic.security.CustomTrustKeyStoreFileName=trust.jks
-Dweblogic.security.CustomTrustKeyStoreType=JKS
-Dweblogic.security.CustomTrustKeyStorePassPhrase=password
nothing else changed.
Debug logs:
[ServerConnectionImpl.getMBeanServer():246] : Connecting to MBeanServer at service:jmx:t3s://host:adminport/jndi/weblogic.management.mbeanservers.domainruntime
[ServerConnectionImpl.getMBeanServer():246] : Connecting to MBeanServer at service:jmx:t3s://host:adminport/jndi/weblogic.management.mbeanservers.runtime
[DomainManager.resetDomain():36] : Getting new domain
[DomainManager.resetDomain():39] : Using pending domain: false
[MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache#6e03db1f
[MBeanCache.addNotificationListener():107] : Disabling mbean caching due to: java.io.InvalidClassException: weblogic.deploy.api.spi.deploy.mbeans.TargetCache; local class incompatible: stream classdesc serialVersionUID = -355364455225633633, local class serialVersionUID = -6063846258165761631
[MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache#38b3f208
[MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache#38b3f208
[ServerConnectionImpl.initialize():178] : Connected to WLS domain: ProjectName
[ServerConnectionImpl.init():168] : Initializing ServerConnection : weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl#65a9ea3c
[WebLogicDeploymentManagerImpl.getTargets():519] : Return target AdminServer_ProjectName
[WebLogicDeploymentManagerImpl.getTargets():519] : Return target ProjectName-auth-1
[WebLogicDeploymentManagerImpl.getTargets():519] : Return target ProjectName-auth-2
[WebLogicDeploymentManagerImpl.getTargets():519] : Return target ProjectName-pub-1
[WebLogicDeploymentManagerImpl.getTargets():519] : Return target ProjectName-pub-2
[WebLogicDeploymentManagerImpl.getTargets():519] : Return target ProjectName-auth-cluster
[WebLogicDeploymentManagerImpl.getTargets():519] : Return target ProjectName-pub-cluster
[WebLogicDeploymentManagerImpl.getAvailableModules():576] : getting all available modules of type ear
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Auth#1.9.2-SNAPSHOT-145, 0
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Public#1.9.2-SNAPSHOT-145, 0
[WebLogicDeploymentManagerImpl.getAvailableModules():576] : getting all available modules of type ejb
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Auth#1.9.2-SNAPSHOT-145, 1
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Public#1.9.2-SNAPSHOT-145, 1
[WebLogicDeploymentManagerImpl.getAvailableModules():576] : getting all available modules of type car
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Auth#1.9.2-SNAPSHOT-145, 2
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Public#1.9.2-SNAPSHOT-145, 2
[WebLogicDeploymentManagerImpl.getAvailableModules():576] : getting all available modules of type rar
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Auth#1.9.2-SNAPSHOT-145, 3
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Public#1.9.2-SNAPSHOT-145, 3
[WebLogicDeploymentManagerImpl.getAvailableModules():576] : getting all available modules of type war
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Auth#1.9.2-SNAPSHOT-145, 4
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Public#1.9.2-SNAPSHOT-145, 4
[WebLogicDeploymentManagerImpl.getAvailableModules():576] : getting all available modules of type unknown
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Auth#1.9.2-SNAPSHOT-145, 323
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Public#1.9.2-SNAPSHOT-145, 323
[WebLogicDeploymentManagerImpl.getAvailableModules():576] : getting all available modules of type jms
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Auth#1.9.2-SNAPSHOT-145, 324
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Public#1.9.2-SNAPSHOT-145, 324
[WebLogicDeploymentManagerImpl.getAvailableModules():576] : getting all available modules of type jdbc
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Auth#1.9.2-SNAPSHOT-145, 325
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Public#1.9.2-SNAPSHOT-145, 325
[WebLogicDeploymentManagerImpl.getAvailableModules():576] : getting all available modules of type intercept
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Auth#1.9.2-SNAPSHOT-145, 326
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Public#1.9.2-SNAPSHOT-145, 326
[WebLogicDeploymentManagerImpl.getAvailableModules():576] : getting all available modules of type config
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Auth#1.9.2-SNAPSHOT-145, 327
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Public#1.9.2-SNAPSHOT-145, 327
[WebLogicDeploymentManagerImpl.getAvailableModules():576] : getting all available modules of type submodule
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Auth#1.9.2-SNAPSHOT-145, 328
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Public#1.9.2-SNAPSHOT-145, 328
[WebLogicDeploymentManagerImpl.getAvailableModules():576] : getting all available modules of type wldf
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Auth#1.9.2-SNAPSHOT-145, 329
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Public#1.9.2-SNAPSHOT-145, 329
[WebLogicDeploymentManagerImpl.getAvailableModules():576] : getting all available modules of type webservice
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Auth#1.9.2-SNAPSHOT-145, 330
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Public#1.9.2-SNAPSHOT-145, 330
[WebLogicDeploymentManagerImpl.getAvailableModules():576] : getting all available modules of type sca composite
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Auth#1.9.2-SNAPSHOT-145, 331
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Public#1.9.2-SNAPSHOT-145, 331
[WebLogicDeploymentManagerImpl.getAvailableModules():576] : getting all available modules of type sca java
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Auth#1.9.2-SNAPSHOT-145, 332
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Public#1.9.2-SNAPSHOT-145, 332
[WebLogicDeploymentManagerImpl.getAvailableModules():576] : getting all available modules of type sca spring
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Auth#1.9.2-SNAPSHOT-145, 333
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Public#1.9.2-SNAPSHOT-145, 333
[WebLogicDeploymentManagerImpl.getAvailableModules():576] : getting all available modules of type sca bpel
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Auth#1.9.2-SNAPSHOT-145, 334
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Public#1.9.2-SNAPSHOT-145, 334
[WebLogicDeploymentManagerImpl.getAvailableModules():576] : getting all available modules of type sca extension
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Auth#1.9.2-SNAPSHOT-145, 335
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Public#1.9.2-SNAPSHOT-145, 335
[WebLogicDeploymentManagerImpl.getAvailableModules():576] : getting all available modules of type coherence cluster
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Auth#1.9.2-SNAPSHOT-145, 336
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Public#1.9.2-SNAPSHOT-145, 336
[WebLogicDeploymentManagerImpl.getAvailableModules():576] : getting all available modules of type gar
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.validateTargets():561] : Validating targets
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Auth#1.9.2-SNAPSHOT-145, 337
[ServerConnectionImpl.getModulesForTargets():630] : checking tmid, ProjectName-Public#1.9.2-SNAPSHOT-145, 337
[WebLogicDeploymentManagerImpl.getTargets():519] : Return target AdminServer_ProjectName
[WebLogicDeploymentManagerImpl.getTargets():519] : Return target ProjectName-auth-1
[WebLogicDeploymentManagerImpl.getTargets():519] : Return target ProjectName-auth-2
[WebLogicDeploymentManagerImpl.getTargets():519] : Return target ProjectName-pub-1
[WebLogicDeploymentManagerImpl.getTargets():519] : Return target ProjectName-pub-2
[WebLogicDeploymentManagerImpl.getTargets():519] : Return target ProjectName-auth-cluster
[WebLogicDeploymentManagerImpl.getTargets():519] : Return target ProjectName-pub-cluster
java.lang.NullPointerException
at weblogic.deploy.api.tools.deployer.ListappsOperation.getActiveState(ListappsOperation.java:83)
at weblogic.deploy.api.tools.deployer.ListappsOperation.report(ListappsOperation.java:60)
at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:140)
at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
at weblogic.Deployer.run(Deployer.java:74)
at weblogic.Deployer.mainWithExceptions(Deployer.java:63)
at weblogic.tools.maven.plugins.deploy.ListAppsMojo.execute(ListAppsMojo.java:165)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
[ServerConnectionImpl.close():341] : Closing DM connection
[ServerConnectionImpl.close():361] : Unregistered all listeners
[ServerConnectionImpl.closeJMX():381] : Closed JMX connection
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15.906 s
[INFO] Finished at: 2019-01-30T16:43:08+01:00
[ServerConnectionImpl.closeJMX():393] : Closed Runtime JMX connection
[ServerConnectionImpl.closeJMX():405] : Closed Edit JMX connection
[INFO] Final Memory: 23M/274M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.oracle.weblogic:weblogic-maven-plugin:12.1.3-0-0:list-apps (default-cli) on project ProjectName: java.lang.NullPointerException
[ERROR] at weblogic.deploy.api.tools.deployer.ListappsOperation.getActiveState(ListappsOperation.java:83)
[ERROR] at weblogic.deploy.api.tools.deployer.ListappsOperation.report(ListappsOperation.java:60)
[ERROR] at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:140)
[ERROR] at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
[ERROR] at weblogic.utils.compiler.Tool.run(Tool.java:158)
[ERROR] at weblogic.utils.compiler.Tool.run(Tool.java:115)
[ERROR] at weblogic.Deployer.run(Deployer.java:74)
[ERROR] at weblogic.Deployer.mainWithExceptions(Deployer.java:63)
[ERROR] at weblogic.tools.maven.plugins.deploy.ListAppsMojo.execute(ListAppsMojo.java:165)
[ERROR] at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
[ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
[ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
[ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
[ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
[ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
[ERROR] at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
[ERROR] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
[ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
[ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
[ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
[ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
[ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
[ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ERROR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[ERROR] at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
[ERROR] -> [Help 1]
Other goals running fine,without any problem. If I deactivate the admin port (mode) the command start working again.
And why I need admin port? Currently creating online deployment with the following steps: distribute app -> start adminmode -> test -> start / undeploy. But after a few iterations when started the new version, the old ones will be retired state. And want to delete/undeploy them automatically. (Purge tasks does not do this).
Thanks for help.
Related
Failing to start up HazelCast on AWS ECS
I'm trying to start up Hazelcast on AWS ECS. I have gone through the tutorial and have enabled all the permissions on the task role i.e decribeTasks, lisTasks etc. I have have a very simple configuration file
hazelcast:
cluster-name: hs-dcom-hazelcast
network:
join:
multicast:
enabled: false
aws:
enabled: true
interfaces:
enabled: true
interfaces:
- 10.106.*.*
However when the container tries to start it throws the following error
2023-01-23T14:47:16.975Z INFO 835 --- [ main] com.hazelcast.instance.impl.Node : [10.106.139.69]:5701 [hs-dcom-hazelcast] [5.0-BETA-1] Shutting down node engine...
7467 2023-01-23T14:47:17.004Z INFO 835 --- [ main] c.hazelcast.instance.impl.NodeExtension : [10.106.139.69]:5701 [hs-dcom-hazelcast] [5.0-BETA-1] Destroying node NodeExtension.
7468 2023-01-23T14:47:17.004Z INFO 835 --- [ main] com.hazelcast.instance.impl.Node : [10.106.139.69]:5701 [hs-dcom-hazelcast] [5.0-BETA-1] Hazelcast Shutdown is completed in 35 ms.
! 7469 2023-01-23T14:47:17.006Z WARN 835 --- [ main] o.s.w.c.s.GenericWebApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hazelcastInstance' defined in class path resource [org/springframework/boot/autoconfigure/hazelcast/HazelcastServerConfiguration$HazelcastServerConfigFileConfiguration.class]: Failed to instantiate [com.hazelcast.core.HazelcastInstance]: Factory method 'hazelcastInstance' threw exception with message: Failure executing: POST at: https://ecs.eu-west-1.amazonaws.com. Message: {"__type":"InvalidParameterException","message":"Identifier is for 570169269855. Your accountId is 531465454359"}. HTTP Error Code: 400
7470 2023-01-23T14:47:17.021Z INFO 835 --- [ main] .s.b.a.l.ConditionEvaluationReportLogger :
7471
7472 Error starting ApplicationContext. To display the condition evaluation report re-run your application with 'debug' enabled.
7473 2023-01-23T14:47:17.052Z ERROR 835 --- [ main] o.s.boot.SpringApplication : Application run failed
7474
7475 org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hazelcastInstance' defined in class path resource [org/springframework/boot/autoconfigure/hazelcast/HazelcastServerConfiguration$HazelcastServerConfigFileConfiguration.class]: Failed to instantiate [com.hazelcast.core.HazelcastInstance]: Factory method 'hazelcastInstance' threw exception with message: Failure executing: POST at: https://ecs.eu-west-1.amazonaws.com. Message: {"__type":"InvalidParameterException","message":"Identifier is for 570169269855. Your accountId is 531465454359"}. HTTP Error Code: 400
7476 at org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:657) ~[spring-beans-6.0.3.jar:6.0.3]
7477 at
I have tried looking on the forum, however can't seem to find anyone that has had this issue before.
Can't get version of the global server state file '/var/state/haproxy/global'
I have installed HAProxy-Ingress into my Kubernetes, I keep getting error 404 when trying to resolve paths, the reason is certainly this error, logged in the controller : 2022/11/22 23:49:18 INFO controller.go:165 HAProxy reloaded [NOTICE] (275) : haproxy version is 2.6.6-274d1a4 [WARNING] (275) : config : config: Can't get version of the global server state file '/var/state/haproxy/global'. [WARNING] (345) : Proxy healthz stopped (cumulated conns: FE: 8, BE: 0). [WARNING] (345) : Proxy http stopped (cumulated conns: FE: 0, BE: 0). [WARNING] (345) : Proxy https stopped (cumulated conns: FE: 0, BE: 0). [WARNING] (345) : Proxy stats stopped (cumulated conns: FE: 0, BE: 0). [NOTICE] (275) : New worker (356) forked [NOTICE] (275) : Loading success. [NOTICE] (275) : haproxy version is 2.6.6-274d1a4 [WARNING] (275) : Former worker (345) exited with code 0 (Exit) I tried copy/pasting the file from docker zone into /var/state/haproxy/ but this doesn't help...
Socket Hang up issue
Below are the logs: [debug] [35m[W3C][39m Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: Could not proxy command to the remote server. Original error: socket hang up [debug] [35m[W3C][39m at UIA2Proxy.command (C:\Users\aarif\AppData\Roaming\npm\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13) [debug] [35m[W3C][39m at processTicksAndRejections (node:internal/process/task_queues:96:5) [debug] [35m[W3C][39m at AndroidUiautomator2Driver.commands.getDevicePixelRatio (C:\Users\aarif\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-driver\lib\commands\viewport.js:14:10) [debug] [35m[W3C][39m at AndroidUiautomator2Driver.fillDeviceDetails (C:\Users\aarif\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-driver\lib\driver.js:244:28) [debug] [35m[W3C][39m at AndroidUiautomator2Driver.createSession (C:\Users\aarif\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-driver\lib\driver.js:230:7) [debug] [35m[W3C][39m at AppiumDriver.createSession (C:\Users\aarif\AppData\Roaming\npm\node_modules\appium\lib\appium.js:387:35) [35m[HTTP][39m [37m<-- POST /wd/hub/session [39m[31m500[39m [90m12195 ms - 1315[39m [35m[HTTP][39m [90m[39m [debug] [35m[Instrumentation][39m io.appium.uiautomator2.server.test.AppiumUiAutomator2Server: Test case skipped Test case skipped Test case skipped =============================================== Suite Total tests run: 3, Passes: 0, Failures: 0, Skips: 3 Configuration Failures: 1, Skips: 5 ===============================================
Tableau-cluster-linux Cloudformation template failing while creating bastion autoscaling group
The following resource(s) failed to create: [BastionAutoScalingGroup].
BastionAutoScalingGroup CREATE_FAILED Received 1 FAILURE signal(s) out of 1. Unable to satisfy 100% MinSuccessfulInstancesPercent requirement
log from bastionHost:-
grep -ni 'error\|failure' $(sudo find /var/log -name cfn* -or -name cloud-init*)
/var/log/cloud-init.log:458:Apr 22 08:19:08 cloud-init[3012]: main.py[DEBUG]: Ran 13 modules with 0 failures
/var/log/cloud-init.log:560:Apr 22 08:19:19 cloud-init[3208]: main.py[DEBUG]: Ran 10 modules with 0 failures
/var/log/cloud-init.log:594:ProcessExecutionError: Unexpected error while running command.
/var/log/cloud-init.log:615:RuntimeError: Runparts: 1 failures in 1 attempted commands
/var/log/cloud-init.log:651:Apr 22 08:20:09 cloud-init[3415]: main.py[DEBUG]: Ran 9 modules with 1 failures
/var/log/cloud-init-output.log:212:--> Processing Dependency: perl(Error) for package: perl-Git-2.23.1-1.amzn2.0.2.noarch
/var/log/cloud-init-output.log:215:---> Package perl-Error.noarch 1:0.17020-2.amzn2 will be installed
/var/log/cloud-init-output.log:230: perl-Error noarch 1:0.17020-2.amzn2 amzn2-core 32 k
/var/log/cloud-init-output.log:249: Installing : 1:perl-Error-0.17020-2.amzn2.noarch 3/8
/var/log/cloud-init-output.log:261: Verifying : 1:perl-Error-0.17020-2.amzn2.noarch 7/8
/var/log/cloud-init-output.log:272: perl-Error.noarch 1:0.17020-2.amzn2
/var/log/cloud-init-output.log:842:Error occurred during build: Command b-bootstrap failed
/var/log/cfn-init.log:20:2020-04-22 08:20:08,653 [ERROR] Command b-bootstrap (./bastion_bootstrap.sh --banner https://aws-quickstart.s3.us-east-1.amazonaws.com/quickstart-linux-bastion/scripts/banner_message.txt --enable false --tcp-forwarding false --x11-forwarding false) failed
/var/log/cfn-init.log:35:2020-04-22 08:20:08,654 [ERROR] Error encountered during build of config: Command b-bootstrap failed
/var/log/cfn-init.log:42: raise ToolError(u"Command %s failed" % name)
/var/log/cfn-init.log:43:ToolError: Command b-bootstrap failed
/var/log/cfn-init.log:44:2020-04-22 08:20:08,656 [ERROR] -----------------------BUILD FAILED!------------------------
/var/log/cfn-init.log:45:2020-04-22 08:20:08,660 [ERROR] Unhandled exception during build: Command b-bootstrap failed
/var/log/cfn-init.log:58: raise ToolError(u"Command %s failed" % name)
/var/log/cfn-init.log:59:ToolError: Command b-bootstrap failed
/var/log/cfn-init.log:61:2020-04-22 08:20:08,882 [DEBUG] Signaling resource BastionAutoScalingGroup in stack Tableau-ubuntu-BastionHost-1FMT6T80AVICN with unique ID i-0ba02ad1171cdc569 and status FAILURE
/var/log/cfn-wire.log:3:2020-04-22 08:20:08,938 [DEBUG] Response: 200 https://cloudformation.us-east-2.amazonaws.com/?Status=FAILURE&ContentType=JSON&StackName=Tableau-ubuntu-BastionHost-1FMT6T80AVICN&Version=2010-05-15&UniqueId=i-0ba02ad1171cdc569&Action=SignalResource&LogicalResourceId=BastionAutoScalingGroup [headers: {'x-amzn-requestid': '9a5ea98d-c6bb-49c9-a6d1-0b663848c9f3', 'date': 'Wed, 22 Apr 2020 08:20:08 GMT', 'content-length': '100', 'content-type': 'application/json'}]
/var/log/cfn-init-cmd.log:23:2020-04-22 08:20:08,653 P12339 [ERROR] Exited with error code 6
logs from primary:-
grep -ni 'error\|failure' $(sudo find /var/log -name cfn* -or -name cloud-init*)
/var/log/cloud-init-output.log:2099:There are 1 topology validation errors/warnings.
/var/log/cloud-init-output.log:2113:There are 1 topology validation errors/warnings.
/var/log/cloud-init-output.log:2127:There are 1 topology validation errors/warnings.
/var/log/cloud-init-output.log:2141:There are 1 topology validation errors/warnings.
/var/log/cloud-init-output.log:2155:There are 1 topology validation errors/warnings.
/var/log/cloud-init-output.log:2169:There are 1 topology validation errors/warnings.
/var/log/cloud-init-output.log:2183:There are 1 topology validation errors/warnings.
/var/log/cloud-init-output.log:2197:There are 1 topology validation errors/warnings.
/var/log/cloud-init-output.log:2211:There are 1 topology validation errors/warnings.
/var/log/cloud-init-output.log:2225:There are 1 topology validation errors/warnings.
/var/log/cloud-init-output.log:2239:There are 1 topology validation errors/warnings.
/var/log/cloud-init-output.log:2254:There are 1 topology validation errors/warnings.
/var/log/cloud-init-output.log:2268:There are 1 topology validation errors/warnings.
/var/log/cloud-init-output.log:2281:There are 2 topology validation errors/warnings.
/var/log/cloud-init-output.log:2305:There are 3 topology validation errors/warnings.
/var/log/cloud-init-output.log:2475:There are 3 topology validation errors/warnings.
/var/log/cloud-init-output.log:2485:Error: This configuration is invalid. Configuring Backgrounder node roles for
/var/log/cloud-init-output.log:2496:Error: This configuration is invalid. Configuring Backgrounder node roles for
/var/log/cloud-init.log:856:2020-04-22 08:18:10,148 - main.py[DEBUG]: Ran 15 modules with 0 failures
/var/log/cloud-init.log:981:2020-04-22 08:18:23,213 - main.py[DEBUG]: Ran 14 modules with 0 failures
/var/log/cloud-init.log:1078:cloudinit.util.ProcessExecutionError: Unexpected error while running command.
/var/log/cloud-init.log:1105:RuntimeError: Runparts: 1 failures in 1 attempted commands
/var/log/cloud-init.log:1141:2020-04-22 08:39:47,298 - main.py[DEBUG]: Ran 20 modules with 1 failures
Maven build failure: Read time out
I have tried all the possible solutions found here, including:
find ~/.m2 -name "*.lastUpdated" -exec grep -q "Could not transfer" {} \; -print -exec rm {} \;
mvn -U clean
It does not work anyway, the specific log is as below:
btw: I was trying to run a struts2 sample code from mkyong site
[DEBUG] =======================================================================
[DEBUG] com.mkyong.common:Struts2Example:war:com.mkyong.common
[DEBUG] junit:junit:jar:3.8.1:test
[DEBUG] org.apache.struts:struts2-core:jar:2.1.8:compile
[DEBUG] com.opensymphony:xwork-core:jar:2.1.6:compile
[DEBUG] org.springframework:spring-test:jar:2.5.6:compile
[DEBUG] commons-logging:commons-logging:jar:1.1.1:compile
[DEBUG] org.freemarker:freemarker:jar:2.3.15:compile
[DEBUG] ognl:ognl:jar:2.7.3:compile
[DEBUG] commons-fileupload:commons-fileupload:jar:1.2.1:compile
[DEBUG] commons-io:commons-io:jar:1.3.2:compile
[DEBUG] com.sun:tools:jar:1.5.0:system
[DEBUG] org.apache.struts:struts2-convention-plugin:jar:2.1.8:compile
[DEBUG] Using connector WagonRepositoryConnector with priority 0 for http://repo
.maven.apache.org/maven2
Downloading: http://repo.maven.apache.org/maven2/org/apache/struts/struts2-core/
2.1.8/struts2-core-2.1.8.jar
[DEBUG] Writing resolution tracking file D:\ProgramData\apache-maven-repo\.m2\re
pository\org\apache\struts\struts2-core\2.1.8\struts2-core-2.1.8.jar.lastUpdated
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 52:31.162s
[INFO] Finished at: Fri Jan 18 20:16:49 CST 2013
[INFO] Final Memory: 2M/5M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project Struts2Example: Could not resolve depe
ndencies for project com.mkyong.common:Struts2Example:war:com.mkyong.common: Cou
ld not transfer artifact org.apache.struts:struts2-core:jar:2.1.8 from/to centra
l (http://repo.maven.apache.org/maven2): GET request of: org/apache/struts/strut
s2-core/2.1.8/struts2-core-2.1.8.jar from central failed: Read timed out -> [Hel
p 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal o
n project Struts2Example: Could not resolve dependencies for project com.mkyong.
common:Struts2Example:war:com.mkyong.common: Could not transfer artifact org.apa
che.struts:struts2-core:jar:2.1.8 from/to central (http://repo.maven.apache.org/
maven2): GET request of: org/apache/struts/struts2-core/2.1.8/struts2-core-2.1.8
.jar from central failed
at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDe
pendencies(LifecycleDependencyResolver.java:210)
at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resol
veProjectDependencies(LifecycleDependencyResolver.java:117)
at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAr
eResolved(MojoExecutor.java:258)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:201)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
ct(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
ct(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBu
ild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl
eStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun
cher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav
a:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La
uncher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
352)
Caused by: org.apache.maven.project.DependencyResolutionException: Could not res
olve dependencies for project com.mkyong.common:Struts2Example:war:com.mkyong.co
mmon: Could not transfer artifact org.apache.struts:struts2-core:jar:2.1.8 from/
to central (http://repo.maven.apache.org/maven2): GET request of: org/apache/str
uts/struts2-core/2.1.8/struts2-core-2.1.8.jar from central failed
at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(D
efaultProjectDependenciesResolver.java:189)
at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDe
pendencies(LifecycleDependencyResolver.java:185)
... 22 more
Caused by: org.sonatype.aether.resolution.DependencyResolutionException: Could n
ot transfer artifact org.apache.struts:struts2-core:jar:2.1.8 from/to central (h
ttp://repo.maven.apache.org/maven2): GET request of: org/apache/struts/struts2-c
ore/2.1.8/struts2-core-2.1.8.jar from central failed
at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDepe
ndencies(DefaultRepositorySystem.java:375)
at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(D
efaultProjectDependenciesResolver.java:183)
... 23 more
Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Could not
transfer artifact org.apache.struts:struts2-core:jar:2.1.8 from/to central (htt
p://repo.maven.apache.org/maven2): GET request of: org/apache/struts/struts2-cor
e/2.1.8/struts2-core-2.1.8.jar from central failed
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(Def
aultArtifactResolver.java:538)
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArti
facts(DefaultArtifactResolver.java:216)
at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDepe
ndencies(DefaultRepositorySystem.java:358)
... 24 more
Caused by: org.sonatype.aether.transfer.ArtifactTransferException: Could not tra
nsfer artifact org.apache.struts:struts2-core:jar:2.1.8 from/to central (http://
repo.maven.apache.org/maven2): GET request of: org/apache/struts/struts2-core/2.
1.8/struts2-core-2.1.8.jar from central failed
at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(W
agonRepositoryConnector.java:951)
at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(W
agonRepositoryConnector.java:941)
at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.
run(WagonRepositoryConnector.java:669)
at org.sonatype.aether.util.concurrency.RunnableErrorForwarder$1.run(Run
nableErrorForwarder.java:60)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.maven.wagon.TransferFailedException: GET request of: org/a
pache/struts/struts2-core/2.1.8/struts2-core-2.1.8.jar from central failed
at org.apache.maven.wagon.AbstractWagon.getTransfer(AbstractWagon.java:3
49)
at org.apache.maven.wagon.AbstractWagon.getTransfer(AbstractWagon.java:3
10)
at org.apache.maven.wagon.AbstractWagon.getTransfer(AbstractWagon.java:2
87)
at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:97)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.
run(WagonRepositoryConnector.java:601)
... 4 more
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at org.apache.maven.wagon.providers.http.httpclient.impl.io.AbstractSess
ionInputBuffer.read(AbstractSessionInputBuffer.java:187)
at org.apache.maven.wagon.providers.http.httpclient.impl.io.ContentLengt
hInputStream.read(ContentLengthInputStream.java:176)
at org.apache.maven.wagon.providers.http.httpclient.conn.EofSensorInputS
tream.read(EofSensorInputStream.java:138)
at org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:493)
at org.apache.maven.wagon.AbstractWagon.getTransfer(AbstractWagon.java:3
39)
... 9 more
Read timed out means you have a network problem. Either repo.maven.apache.org is down (very unlikely) or you have connectivity issues on your end.
Read Timeout errors can also happen with big dependency resolution on slow networks (that you may not be able to fix by yourself). You may also want to consider this other thread, here you will find how to increase the Maven Wagon timeout which will help you in such cases. Also check the official documentation for more details.
But using wget I am able to download instance. It is almost halt here..waited more than 15 mins.. INFO] [INFO] --- maven-checkstyle-plugin:2.13:check (validate-checkstyle) # onos --- [DEBUG] Using connector WagonRepositoryConnector with priority 0.0 for http://repo.maven.apache.org/maven2 Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-module-xhtml/1.2/doxia-module-xhtml-1.2.pom 2/2 KB Regards, Bala