December 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6915) Mod cluster not working with non-root user

by Rafael Pereira (JIRA)

[ https://issues.jboss.org/browse/WFLY-6915?page=com.atlassian.jira.plugin.... ] Rafael Pereira commented on WFLY-6915: -------------------------------------- Thank you. Thats great news. Great effort. > Mod cluster not working with non-root user > ------------------------------------------ > > Key: WFLY-6915 > URL: https://issues.jboss.org/browse/WFLY-6915 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 10.0.0.Final > Environment: OS's tested: > # Red Hat Enterprise Linux Server release 6.5 (Santiago) > # CentOS Linux release 7.2.1511 (Core) > *SELINUX*: Disabled > *IPTABLES/FIREWALLD: *disabled with no rules > #wildfly: 10.0.0.Final > #httpd: > httpd-2.2.15-31.el6_5.x86_64 > httpd-tools-2.2.15-31.el6_5.x86_64 > httpd-devel-2.2.15-31.el6_5.x86_64 > #modcluster/httpd version: 1.2.6 > Reporter: Rafael Pereira > Assignee: Radoslav Husar > Fix For: 11.0.0.Alpha1 > > > When I run wildfly with a non-root user(wildfly) mod_cluster won't work. I got this error: > 14:09:06,327 ERROR [org.jboss.modcluster] (UndertowEventHandlerAdapter - 1) MODCLUSTER000043: Failed to send INFO command to relatorios.sistemafieg.org.br/11.12.13.14:6666: Permission denied > This happens when I use port-offset>0 and run wildfly service. > However, if I run with root user, this error won't happen > Steps to reproduce > 1. Adding user > {code:shell} > groupadd -r wildfly > useradd -r -g wildfly -d /opt/wildfly -s /sbin/nologin wildfly > {code} > 2. use init.d or systemd script > {code:shell} > wildfly-10.0.0.Final/docs/contrib/scripts/init.d/wildfly-init-redhat.sh > {code} > 3. start wildfly and register proxy list and socket binding > {code:shell} > /socket-binding-group=ha-sockets/remote-destination-outbound-socket-binding=mod_cluster:add(port=6666,host=11.12.13.14) > /profile=ha/subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=proxies,value=[mod_cluster]) > {code} > 4. edit wildfly.conf > {code:shell} > JBOSS_HOME="/opt/wildfly/server" > JBOSS_USER=wildfly > JBOSS_MODE=domain > JBOSS_HOST_CONFIG=host.xml > JBOSS_CONSOLE_LOG="/var/log/wildfly/console.log" > JBOSS_OPTS="-Djboss.domain.base.dir=/opt/wildfly/config/domain -Djboss.bind.address.management=11.12.13.10 -Djboss.bind.address=11.12.13.10" > {code} > 5. edit httpd.conf > {code} > LoadModule slotmem_module modules/mod_slotmem.so > LoadModule manager_module modules/mod_manager.so > LoadModule proxy_cluster_module modules/mod_proxy_cluster.so > LoadModule advertise_module modules/mod_advertise.so > Listen 6666 > <VirtualHost *:6666> > <Location /> > Order deny,allow > Deny from all > Allow from 11.12.13 > </Location> > <Location /mcm> > SetHandler mod_cluster-manager > Order deny,allow > Allow from all > </Location> > KeepAliveTimeout 300 > MaxKeepAliveRequests 0 > Timeout 5400 > ProxyTimeout 5400 > EnableMCPMReceive On > ManagerBalancerName myCluster > ServerAdvertise Off > ErrorLog logs/cluster-error.log > CustomLog logs/cluster-access.log INFO > </VirtualHost> > {code} > 6. Run with service or systemctl command: *service wildfly start* > *Environment:* > OS's tested: > # Red Hat Enterprise Linux Server release 6.5 (Santiago) > # CentOS Linux release 7.2.1511 (Core) > *SELINUX*: Disabled > *IPTABLES/FIREWALLD: * disabled and no rules set > *wildfly:* 10.0.0.Final > *httpd:* > httpd-2.2.15-31.el6_5.x86_64 > httpd-tools-2.2.15-31.el6_5.x86_64 > httpd-devel-2.2.15-31.el6_5.x86_64 > *modcluster/httpd version:* 1.2.6 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-822) Move MechanismConfiguration from SecurityFactory<Credential> to CredentialSource

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-822?page=com.atlassian.jira.plugin.sy... ] David Lloyd commented on ELY-822: --------------------------------- +1 this is a good idea also because it also means that the server can present credentials based on algorithm/parameters (think TLS/entity with different certificates for example). > Move MechanismConfiguration from SecurityFactory<Credential> to CredentialSource > -------------------------------------------------------------------------------- > > Key: ELY-822 > URL: https://issues.jboss.org/browse/ELY-822 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta17 > > > This will make it consistent with client side configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6915) Mod cluster not working with non-root user

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6915?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-6915: --------------------------------- Fix Version/s: 11.0.0.Alpha1 (was: 10.2.0.Final) > Mod cluster not working with non-root user > ------------------------------------------ > > Key: WFLY-6915 > URL: https://issues.jboss.org/browse/WFLY-6915 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 10.0.0.Final > Environment: OS's tested: > # Red Hat Enterprise Linux Server release 6.5 (Santiago) > # CentOS Linux release 7.2.1511 (Core) > *SELINUX*: Disabled > *IPTABLES/FIREWALLD: *disabled with no rules > #wildfly: 10.0.0.Final > #httpd: > httpd-2.2.15-31.el6_5.x86_64 > httpd-tools-2.2.15-31.el6_5.x86_64 > httpd-devel-2.2.15-31.el6_5.x86_64 > #modcluster/httpd version: 1.2.6 > Reporter: Rafael Pereira > Assignee: Radoslav Husar > Fix For: 11.0.0.Alpha1 > > > When I run wildfly with a non-root user(wildfly) mod_cluster won't work. I got this error: > 14:09:06,327 ERROR [org.jboss.modcluster] (UndertowEventHandlerAdapter - 1) MODCLUSTER000043: Failed to send INFO command to relatorios.sistemafieg.org.br/11.12.13.14:6666: Permission denied > This happens when I use port-offset>0 and run wildfly service. > However, if I run with root user, this error won't happen > Steps to reproduce > 1. Adding user > {code:shell} > groupadd -r wildfly > useradd -r -g wildfly -d /opt/wildfly -s /sbin/nologin wildfly > {code} > 2. use init.d or systemd script > {code:shell} > wildfly-10.0.0.Final/docs/contrib/scripts/init.d/wildfly-init-redhat.sh > {code} > 3. start wildfly and register proxy list and socket binding > {code:shell} > /socket-binding-group=ha-sockets/remote-destination-outbound-socket-binding=mod_cluster:add(port=6666,host=11.12.13.14) > /profile=ha/subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=proxies,value=[mod_cluster]) > {code} > 4. edit wildfly.conf > {code:shell} > JBOSS_HOME="/opt/wildfly/server" > JBOSS_USER=wildfly > JBOSS_MODE=domain > JBOSS_HOST_CONFIG=host.xml > JBOSS_CONSOLE_LOG="/var/log/wildfly/console.log" > JBOSS_OPTS="-Djboss.domain.base.dir=/opt/wildfly/config/domain -Djboss.bind.address.management=11.12.13.10 -Djboss.bind.address=11.12.13.10" > {code} > 5. edit httpd.conf > {code} > LoadModule slotmem_module modules/mod_slotmem.so > LoadModule manager_module modules/mod_manager.so > LoadModule proxy_cluster_module modules/mod_proxy_cluster.so > LoadModule advertise_module modules/mod_advertise.so > Listen 6666 > <VirtualHost *:6666> > <Location /> > Order deny,allow > Deny from all > Allow from 11.12.13 > </Location> > <Location /mcm> > SetHandler mod_cluster-manager > Order deny,allow > Allow from all > </Location> > KeepAliveTimeout 300 > MaxKeepAliveRequests 0 > Timeout 5400 > ProxyTimeout 5400 > EnableMCPMReceive On > ManagerBalancerName myCluster > ServerAdvertise Off > ErrorLog logs/cluster-error.log > CustomLog logs/cluster-access.log INFO > </VirtualHost> > {code} > 6. Run with service or systemctl command: *service wildfly start* > *Environment:* > OS's tested: > # Red Hat Enterprise Linux Server release 6.5 (Santiago) > # CentOS Linux release 7.2.1511 (Core) > *SELINUX*: Disabled > *IPTABLES/FIREWALLD: * disabled and no rules set > *wildfly:* 10.0.0.Final > *httpd:* > httpd-2.2.15-31.el6_5.x86_64 > httpd-tools-2.2.15-31.el6_5.x86_64 > httpd-devel-2.2.15-31.el6_5.x86_64 > *modcluster/httpd version:* 1.2.6 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6546) jms-queue metrics appears in the profile in domain mode

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-6546?page=com.atlassian.jira.plugin.... ] Jeff Mesnil resolved WFLY-6546. ------------------------------- Fix Version/s: 11.0.0.Alpha1 Resolution: Done Fixed through WFCORE-1513 > jms-queue metrics appears in the profile in domain mode > ------------------------------------------------------- > > Key: WFLY-6546 > URL: https://issues.jboss.org/browse/WFLY-6546 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Minor > Fix For: 11.0.0.Alpha1 > > > Metrics associated to jms-queue resource are displayed in the profile in domain mode (under /profile=full/subsystem=messaging-activemq/server=artemis/jms-queue=XXX). > These metrics have no meaning in the domain controller and should only be exposed on the server (under /host=master/server=server-one/subsystem=messaging-activemq/server=default/jms-queue=XXX:read-resource(include-runtime=true) ) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6915) Mod cluster not working with non-root user

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6915?page=com.atlassian.jira.plugin.... ] Radoslav Husar resolved WFLY-6915. ---------------------------------- Fix Version/s: 10.2.0.Final Resolution: Done Fixed with wildfly-core:3.0.0.Alpha13 upgrade. > Mod cluster not working with non-root user > ------------------------------------------ > > Key: WFLY-6915 > URL: https://issues.jboss.org/browse/WFLY-6915 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 10.0.0.Final > Environment: OS's tested: > # Red Hat Enterprise Linux Server release 6.5 (Santiago) > # CentOS Linux release 7.2.1511 (Core) > *SELINUX*: Disabled > *IPTABLES/FIREWALLD: *disabled with no rules > #wildfly: 10.0.0.Final > #httpd: > httpd-2.2.15-31.el6_5.x86_64 > httpd-tools-2.2.15-31.el6_5.x86_64 > httpd-devel-2.2.15-31.el6_5.x86_64 > #modcluster/httpd version: 1.2.6 > Reporter: Rafael Pereira > Assignee: Radoslav Husar > Fix For: 10.2.0.Final > > > When I run wildfly with a non-root user(wildfly) mod_cluster won't work. I got this error: > 14:09:06,327 ERROR [org.jboss.modcluster] (UndertowEventHandlerAdapter - 1) MODCLUSTER000043: Failed to send INFO command to relatorios.sistemafieg.org.br/11.12.13.14:6666: Permission denied > This happens when I use port-offset>0 and run wildfly service. > However, if I run with root user, this error won't happen > Steps to reproduce > 1. Adding user > {code:shell} > groupadd -r wildfly > useradd -r -g wildfly -d /opt/wildfly -s /sbin/nologin wildfly > {code} > 2. use init.d or systemd script > {code:shell} > wildfly-10.0.0.Final/docs/contrib/scripts/init.d/wildfly-init-redhat.sh > {code} > 3. start wildfly and register proxy list and socket binding > {code:shell} > /socket-binding-group=ha-sockets/remote-destination-outbound-socket-binding=mod_cluster:add(port=6666,host=11.12.13.14) > /profile=ha/subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=proxies,value=[mod_cluster]) > {code} > 4. edit wildfly.conf > {code:shell} > JBOSS_HOME="/opt/wildfly/server" > JBOSS_USER=wildfly > JBOSS_MODE=domain > JBOSS_HOST_CONFIG=host.xml > JBOSS_CONSOLE_LOG="/var/log/wildfly/console.log" > JBOSS_OPTS="-Djboss.domain.base.dir=/opt/wildfly/config/domain -Djboss.bind.address.management=11.12.13.10 -Djboss.bind.address=11.12.13.10" > {code} > 5. edit httpd.conf > {code} > LoadModule slotmem_module modules/mod_slotmem.so > LoadModule manager_module modules/mod_manager.so > LoadModule proxy_cluster_module modules/mod_proxy_cluster.so > LoadModule advertise_module modules/mod_advertise.so > Listen 6666 > <VirtualHost *:6666> > <Location /> > Order deny,allow > Deny from all > Allow from 11.12.13 > </Location> > <Location /mcm> > SetHandler mod_cluster-manager > Order deny,allow > Allow from all > </Location> > KeepAliveTimeout 300 > MaxKeepAliveRequests 0 > Timeout 5400 > ProxyTimeout 5400 > EnableMCPMReceive On > ManagerBalancerName myCluster > ServerAdvertise Off > ErrorLog logs/cluster-error.log > CustomLog logs/cluster-access.log INFO > </VirtualHost> > {code} > 6. Run with service or systemctl command: *service wildfly start* > *Environment:* > OS's tested: > # Red Hat Enterprise Linux Server release 6.5 (Santiago) > # CentOS Linux release 7.2.1511 (Core) > *SELINUX*: Disabled > *IPTABLES/FIREWALLD: * disabled and no rules set > *wildfly:* 10.0.0.Final > *httpd:* > httpd-2.2.15-31.el6_5.x86_64 > httpd-tools-2.2.15-31.el6_5.x86_64 > httpd-devel-2.2.15-31.el6_5.x86_64 > *modcluster/httpd version:* 1.2.6 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1365) directory of images for drools-docs is not where it should be

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1365?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer resolved DROOLS-1365. -------------------------------------------- Resolution: Won't Fix > directory of images for drools-docs is not where it should be > ------------------------------------------------------------- > > Key: DROOLS-1365 > URL: https://issues.jboss.org/browse/DROOLS-1365 > Project: Drools > Issue Type: Bug > Components: docs > Affects Versions: 6.5.0.Final > Reporter: Michael Biarnes Kiefer > Assignee: Geoffrey De Smet > > I see that the images 1.png, 2.png and 3.png are not anymore available under: > https://docs.jboss.org/drools/release/6.5.0.Final/drools-docs/html/images... (where they normally are supposed to be) > I saw on filemgmt.jboss.org, that these images are now in: > https://docs.jboss.org/drools/release/6.5.0.Final/drools-docs/html/images... > Maybe the URL si not constructed good, so "community/docbook" is missing? > What to do here? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7752) Clustering XML readers are loaded eagerly

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7752?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-7752: --------------------------------- Description: [5:02 PM] Radoslav Husar: org.jboss.as.controller.parsing.ExtensionParsingContext#setSubsystemXmlMapping(java.lang.String, java.lang.String, java.util.function.Supplier<org.jboss.staxmapper.XMLElementReader<java.util.List<org.jboss.dmr.ModelNode>>>) [5:02 PM] Radoslav Husar: I mean we want to be using^ [5:02 PM] Radoslav Husar: but we are using org.jboss.as.controller.parsing.ExtensionParsingContext#setSubsystemXmlMapping(java.lang.String, java.lang.String, org.jboss.staxmapper.XMLElementReader<java.util.List<org.jboss.dmr.ModelNode>>) > Clustering XML readers are loaded eagerly > ----------------------------------------- > > Key: WFLY-7752 > URL: https://issues.jboss.org/browse/WFLY-7752 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > [5:02 PM] Radoslav Husar: org.jboss.as.controller.parsing.ExtensionParsingContext#setSubsystemXmlMapping(java.lang.String, java.lang.String, java.util.function.Supplier<org.jboss.staxmapper.XMLElementReader<java.util.List<org.jboss.dmr.ModelNode>>>) > [5:02 PM] Radoslav Husar: I mean we want to be using^ > [5:02 PM] Radoslav Husar: but we are using org.jboss.as.controller.parsing.ExtensionParsingContext#setSubsystemXmlMapping(java.lang.String, java.lang.String, org.jboss.staxmapper.XMLElementReader<java.util.List<org.jboss.dmr.ModelNode>>) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7752) Clustering XML readers are loaded eagerly

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-7752: ------------------------------------ Summary: Clustering XML readers are loaded eagerly Key: WFLY-7752 URL: https://issues.jboss.org/browse/WFLY-7752 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.1.0.Final Reporter: Radoslav Husar Assignee: Radoslav Husar -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-822) Move MechanismConfiguration from SecurityFactory<Credential> to CredentialSource

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-822: ------------------------------------ Summary: Move MechanismConfiguration from SecurityFactory<Credential> to CredentialSource Key: ELY-822 URL: https://issues.jboss.org/browse/ELY-822 Project: WildFly Elytron Issue Type: Enhancement Components: API / SPI Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta17 This will make it consistent with client side configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7746) Upgrade to a version of Infinispan that depends on JBoss Marshalling 2.0.0.Beta3

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-7746?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFLY-7746: ------------------------------------ [~fjuma] Hi Farah - can you post the stacktrace containing the ClusteredSingleSignOnTestCase failure? Best case scenario, Infinispan upgrades to JBM2 for 9.0. WF cannot integrate Infinispan 9 until WF12 at the earliest. > Upgrade to a version of Infinispan that depends on JBoss Marshalling 2.0.0.Beta3 > -------------------------------------------------------------------------------- > > Key: WFLY-7746 > URL: https://issues.jboss.org/browse/WFLY-7746 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Reporter: Farah Juma > Assignee: Paul Ferraro > > As part of the wildfly-naming-client integration work, we need to upgrade to JBoss Marshalling 2.0.0.Beta3 (see WFCORE-2044 and WFLY-7675). This upgrade currently results in testsuite failures in {{org.jboss.as.test.clustering.cluster.sso.ClusteredSingleSignOnTestCase}} since Infinispan is still on JBoss Marshalling 1.4.x. > ISPN-3391 was created a while back to upgrade Infinispan to JBoss Marshalling 2.0.0 but it seems this issue was waiting on a JBoss Marshalling release that adds back some classes that had previously been removed. JBoss Marshalling 2.0.0.Beta3 contains these classes so it should be possible now to upgrade Infinispan to this new version. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2016