Stable is down since Feb. 28
Hi, I just noticed that the stable is down since Feb. 28. I'm relying on https://www.montastic.com to check demos availabilities but it's not reliable. Unfortunately there is no other free choices. I checked why this happened and found: Build file '/home/ofbizDemo/branch17.12/build.gradle' line: 1161 * What went wrong: A problem occurred evaluating root project 'ofbiz'. > Could not resolve all files for configuration ':runtime'. > Could not resolve org.opensaml:opensaml:1.1b. Required by: project : > project :plugins:ldap > org.jasig.cas:cas-server-core:3.3.5 > Could not resolve org.opensaml:opensaml:1.1b. > Could not get resource 'https://repo.spring.io/plugins-release/org/opensaml/opensaml/1.1b/opensaml-1.1b.pom'. > Could not GET 'https://repo.spring.io/plugins-release/org/opensaml/opensaml/1.1b/opensaml-1.1b.pom'. Received status code 401 from server: Unauthorized > Could not resolve org.inspektr:inspektr-core:0.7.0. Required by: project : > project :plugins:ldap > org.jasig.cas:cas-server-core:3.3.5 > Could not resolve org.inspektr:inspektr-core:0.7.0. > Could not get resource 'https://repo.spring.io/plugins-release/org/inspektr/inspektr-core/0.7.0/inspektr-core-0.7.0.pom'. > Could not GET 'https://repo.spring.io/plugins-release/org/inspektr/inspektr-core/0.7.0/inspektr-core-0.7.0.pom'. Received status code 401 from server: Unauthorized The 2 others demo (trunk and old - R16) are OK. Also R17 (stable) works locally. So we have an issue that exists only for the stable OFBiz demo. I have created https://issues.apache.org/jira/browse/INFRA-21543 for that Jacques
Re: Stable is down since Feb. 28
Looks like the plugins for 17.12 are not up-to-date on the server The dependency for org.jasig.cas:cas-server-core was changed toorg.apereo.cas:cas-server-support-ldap-core during the JCenter/Maven Central migration. Regards, Michael Brohl ecomify GmbH - www.ecomify.de Am 09.03.21 um 13:01 schrieb Jacques Le Roux: Hi, I just noticed that the stable is down since Feb. 28. I'm relying on https://www.montastic.com to check demos availabilities but it's not reliable. Unfortunately there is no other free choices. I checked why this happened and found: Build file '/home/ofbizDemo/branch17.12/build.gradle' line: 1161 * What went wrong: A problem occurred evaluating root project 'ofbiz'. > Could not resolve all files for configuration ':runtime'. > Could not resolve org.opensaml:opensaml:1.1b. Required by: project : > project :plugins:ldap > org.jasig.cas:cas-server-core:3.3.5 > Could not resolve org.opensaml:opensaml:1.1b. > Could not get resource 'https://repo.spring.io/plugins-release/org/opensaml/opensaml/1.1b/opensaml-1.1b.pom'. > Could not GET 'https://repo.spring.io/plugins-release/org/opensaml/opensaml/1.1b/opensaml-1.1b.pom'. Received status code 401 from server: Unauthorized > Could not resolve org.inspektr:inspektr-core:0.7.0. Required by: project : > project :plugins:ldap > org.jasig.cas:cas-server-core:3.3.5 > Could not resolve org.inspektr:inspektr-core:0.7.0. > Could not get resource 'https://repo.spring.io/plugins-release/org/inspektr/inspektr-core/0.7.0/inspektr-core-0.7.0.pom'. > Could not GET 'https://repo.spring.io/plugins-release/org/inspektr/inspektr-core/0.7.0/inspektr-core-0.7.0.pom'. Received status code 401 from server: Unauthorized The 2 others demo (trunk and old - R16) are OK. Also R17 (stable) works locally. So we have an issue that exists only for the stable OFBiz demo. I have created https://issues.apache.org/jira/browse/INFRA-21543 for that Jacques
Re: Stable is down since Feb. 28
>Looks like the plugins for 17.12 are not up-to-date on the server Actually they could not be. Because the call to pullAllPluginsSource task failed before (see below and [1]) I had to manually remove them, use pullAllPluginsSource manually, remove the ldap plugin, and then it worked. I tried again locally. Because there I don't use pullAllPluginsSource. I have the plugins cloned in a plugins sub-dir. So with another instance I used pullAllPluginsSource and again got no issue starting OFBiz So the stable instance is now running. But I'll now try again to see if I can reproduce the weird ldap issue there. [1] https://github.com/apache/ofbiz-tools/blob/master/demo-backup/stable-manual.sh Jacques Le 09/03/2021 à 15:27, Michael Brohl a écrit : Looks like the plugins for 17.12 are not up-to-date on the server The dependency for org.jasig.cas:cas-server-core was changed toorg.apereo.cas:cas-server-support-ldap-core during the JCenter/Maven Central migration. Regards, Michael Brohl ecomify GmbH - www.ecomify.de Am 09.03.21 um 13:01 schrieb Jacques Le Roux: Hi, I just noticed that the stable is down since Feb. 28. I'm relying on https://www.montastic.com to check demos availabilities but it's not reliable. Unfortunately there is no other free choices. I checked why this happened and found: Build file '/home/ofbizDemo/branch17.12/build.gradle' line: 1161 * What went wrong: A problem occurred evaluating root project 'ofbiz'. > Could not resolve all files for configuration ':runtime'. > Could not resolve org.opensaml:opensaml:1.1b. Required by: project : > project :plugins:ldap > org.jasig.cas:cas-server-core:3.3.5 > Could not resolve org.opensaml:opensaml:1.1b. > Could not get resource 'https://repo.spring.io/plugins-release/org/opensaml/opensaml/1.1b/opensaml-1.1b.pom'. > Could not GET 'https://repo.spring.io/plugins-release/org/opensaml/opensaml/1.1b/opensaml-1.1b.pom'. Received status code 401 from server: Unauthorized > Could not resolve org.inspektr:inspektr-core:0.7.0. Required by: project : > project :plugins:ldap > org.jasig.cas:cas-server-core:3.3.5 > Could not resolve org.inspektr:inspektr-core:0.7.0. > Could not get resource 'https://repo.spring.io/plugins-release/org/inspektr/inspektr-core/0.7.0/inspektr-core-0.7.0.pom'. > Could not GET 'https://repo.spring.io/plugins-release/org/inspektr/inspektr-core/0.7.0/inspektr-core-0.7.0.pom'. Received status code 401 from server: Unauthorized The 2 others demo (trunk and old - R16) are OK. Also R17 (stable) works locally. So we have an issue that exists only for the stable OFBiz demo. I have created https://issues.apache.org/jira/browse/INFRA-21543 for that Jacques
Re: Stable is down since Feb. 28
-4.5.1.jar:4.5.1] at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:128) [gradle-messaging-4.5.1.jar:4.5.1] at org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:404) [gradle-messaging-4.5.1.jar:4.5.1] at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63) [gradle-base-services-4.5.1.jar:4.5.1] at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46) [gradle-base-services-4.5.1.jar:4.5.1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_282] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_282] at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55) [gradle-base-services-4.5.1.jar:4.5.1] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_282] 2021-03-11 03:05:59,303 |Test worker |ControlFilter |W| The default error code will be used: 403 So OFBiz was somehow running, but ldap, and this explains the 403 error we got so far. So people using the same kind of config that we have on demos should care about that BTW I noticed that the ldap component documentation is not up to date it says: OFBiz disabled LDAP component as default, you can enable this component by take the comment out from plugins/component-load.xml file. That's only in no longer supported R16 branch. I'll fix that. Jacques Le 11/03/2021 à 09:36, Jacques Le Roux a écrit : >Looks like the plugins for 17.12 are not up-to-date on the server Actually they could not be. Because the call to pullAllPluginsSource task failed before (see below and [1]) I had to manually remove them, use pullAllPluginsSource manually, remove the ldap plugin, and then it worked. I tried again locally. Because there I don't use pullAllPluginsSource. I have the plugins cloned in a plugins sub-dir. So with another instance I used pullAllPluginsSource and again got no issue starting OFBiz So the stable instance is now running. But I'll now try again to see if I can reproduce the weird ldap issue there. [1] https://github.com/apache/ofbiz-tools/blob/master/demo-backup/stable-manual.sh Jacques Le 09/03/2021 à 15:27, Michael Brohl a écrit : Looks like the plugins for 17.12 are not up-to-date on the server The dependency for org.jasig.cas:cas-server-core was changed toorg.apereo.cas:cas-server-support-ldap-core during the JCenter/Maven Central migration. Regards, Michael Brohl ecomify GmbH - www.ecomify.de Am 09.03.21 um 13:01 schrieb Jacques Le Roux: Hi, I just noticed that the stable is down since Feb. 28. I'm relying on https://www.montastic.com to check demos availabilities but it's not reliable. Unfortunately there is no other free choices. I checked why this happened and found: Build file '/home/ofbizDemo/branch17.12/build.gradle' line: 1161 * What went wrong: A problem occurred evaluating root project 'ofbiz'. > Could not resolve all files for configuration ':runtime'. > Could not resolve org.opensaml:opensaml:1.1b. Required by: project : > project :plugins:ldap > org.jasig.cas:cas-server-core:3.3.5 > Could not resolve org.opensaml:opensaml:1.1b. > Could not get resource 'https://repo.spring.io/plugins-release/org/opensaml/opensaml/1.1b/opensaml-1.1b.pom'. > Could not GET 'https://repo.spring.io/plugins-release/org/opensaml/opensaml/1.1b/opensaml-1.1b.pom'. Received status code 401 from server: Unauthorized > Could not resolve org.inspektr:inspektr-core:0.7.0. Required by: project : > project :plugins:ldap > org.jasig.cas:cas-server-core:3.3.5 > Could not resolve org.inspektr:inspektr-core:0.7.0. > Could not get resource 'https://repo.spring.io/plugins-release/org/inspektr/inspektr-core/0.7.0/inspektr-core-0.7.0.pom'. > Could not GET 'https://repo.spring.io/plugins-release/org/inspektr/inspektr-core/0.7.0/inspektr-core-0.7.0.pom'. Received status code 401 from server: Unauthorized The 2 others demo (trunk and old - R16) are OK. Also R17 (stable) works locally. So we have an issue that exists only for the stable OFBiz demo. I have created https://issues.apache.org/jira/browse/INFRA-21543 for that Jacques
