Best unofficial Apache Server developers community
Username
Forgot password?
Sign in with Twitter account
Sign in with Facebook account
List archives

User/Password management in 2.6

Can't get simplest client / server connection to work still
(420 lines)
storeconfigs stores wrong fact value in facts_values table
(50 lines)
Jul 27, 2010
Christian Casar
Christian Casar
Hey there,
I recently updated to 2.6.
Part of puppet's assignment is to manage users and their passwords.
Since the update every puppetrun reports that passwords for every user
were created although they've already been set in previous runs.

debug: User[root](provider=useradd): Executing '/usr/sbin/usermod -p
imagine-encrypted-password
root'
notice: /Stage[main]/Allgemein::User/User[root]/password: created
password

user {"root":
                ensure  => present,
                uid     =>
"0",
                password => 'imagine-encrypted-
password',
                gid     =>
"0",
                comment => "Root $hostname",
                home    => "/root",
                shell   => "/bin/bash"
        }

I don't know if it's default behaviour since 2.6 but in 0.25.4
passwords were only created once.
Is this worth a bug report or just a problem with my manifest?

I'm using OpenSuse 11.3 and as you can see the provider used is
useradd.





Reply
Tags: passwordsupdatedrunsset
Messages in this thread
User/Password management in 2.6
reply Re: User/Password management in 2.6
(24 lines) Jul 27, 2010 11:58
Similar Threads
Can't change user password
I tried on Archiva-1.2.2 and Archiva-1.3.1, both failed to change:



HTTP Status 500 -

type Exception report

message

descriptionThe server encountered an internal error () that prevented it 
from fulfilling this request.

exception

javax.servlet.ServletException: java.lang.IllegalArgumentException: 
fromIndex(0) > toIndex(-1)

root cause

java.lang.IllegalArgumentException: fromIndex(0) > toIndex(-1)

note The full stack traces of the exception and its root causes are 
available in the GlassFish Server Open Source Edition 3.0.1 logs.
GlassFish Server Open Source Edition 3.0.1






[#|2010-07-07T14:46:02.764+0000|WARNING|glassfish3.0.1|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=36;_ThreadName=Thread-1;|StandardWrapperValve[default]:

PWC1406: Servlet.service() for servlet default threw exception
java.lang.IllegalArgumentException: fromIndex(0) > toIndex(-1)
     at java.util.ArrayList.subListRangeCheck(ArrayList.java:887)
     at java.util.ArrayList.subList(ArrayList.java:877)
     at 
org.codehaus.plexus.redback.policy.DefaultUserSecurityPolicy.extensionChangePassword(DefaultUserSecurityPolicy.java:338)
     at 
org.codehaus.plexus.redback.users.jdo.JdoUserManager.updateUser(JdoUserManager.java:368)
     at 
org.codehaus.plexus.redback.users.cached.CachedUserManager.updateUser(CachedUserManager.java:229)
     at 
org.codehaus.plexus.redback.users.configurable.ConfigurableUserManager.updateUser(ConfigurableUserManager.java:174)
     at 
org.codehaus.plexus.redback.struts2.action.AccountAction.submit(AccountAction.java:191)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
     at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
     at java.lang.reflect.Method.invoke(Method.java:616)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:404)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:267)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:229)
     at 
org.codehaus.plexus.redback.struts2.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.java:173)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
org.codehaus.plexus.redback.struts2.interceptor.PolicyEnforcementInterceptor.intercept(PolicyEnforcementInterceptor.java:159)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
org.codehaus.plexus.redback.struts2.interceptor.AutoLoginInterceptor.intercept(AutoLoginInterceptor.java:167)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
org.codehaus.plexus.redback.struts2.interceptor.ForceAdminUserInterceptor.intercept(ForceAdminUserInterceptor.java:77)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
org.codehaus.plexus.redback.struts2.interceptor.EnvironmentCheckInterceptor.intercept(EnvironmentCheckInterceptor.java:97)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
com.opensymphony.xwork2.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:221)
     at 
com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
com.opensymphony.xwork2.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:150)
     at 
org.apache.struts2.interceptor.validation.AnnotationValidationInterceptor.doIntercept(AnnotationValidationInterceptor.java:48)
     at 
com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
                                                         at 
com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
com.opensymphony.xwork2.interceptor.ConversionErrorInterceptor.intercept(ConversionErrorInterceptor.java:123)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
com.opensymphony.xwork2.interceptor.ParametersInterceptor.doIntercept(ParametersInterceptor.java:184)
     at 
com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
com.opensymphony.xwork2.interceptor.StaticParametersInterceptor.intercept(StaticParametersInterceptor.java:105)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
org.apache.struts2.interceptor.CheckboxInterceptor.intercept(CheckboxInterceptor.java:83)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
org.apache.struts2.interceptor.FileUploadInterceptor.intercept(FileUploadInterceptor.java:207)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
com.opensymphony.xwork2.interceptor.ModelDrivenInterceptor.intercept(ModelDrivenInterceptor.java:74)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
com.opensymphony.xwork2.interceptor.ScopedModelDrivenInterceptor.intercept(ScopedModelDrivenInterceptor.java:127)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
org.apache.struts2.interceptor.ProfilingActivationInterceptor.intercept(ProfilingActivationInterceptor.java:107)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
org.apache.struts2.interceptor.debugging.DebuggingInterceptor.intercept(DebuggingInterceptor.java:206)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
com.opensymphony.xwork2.interceptor.ChainingInterceptor.intercept(ChainingInterceptor.java:115)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
com.opensymphony.xwork2.interceptor.I18nInterceptor.intercept(I18nInterceptor.java:143)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)

    at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
com.opensymphony.xwork2.interceptor.PrepareInterceptor.doIntercept(PrepareInterceptor.java:121)
     at 
com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
org.apache.struts2.interceptor.ServletConfigInterceptor.intercept(ServletConfigInterceptor.java:170)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
com.opensymphony.xwork2.interceptor.AliasInterceptor.intercept(AliasInterceptor.java:123)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
com.opensymphony.xwork2.interceptor.ExceptionMappingInterceptor.intercept(ExceptionMappingInterceptor.java:176)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:224)
     at 
com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:223)
     at 
com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
     at 
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
     at 
org.apache.struts2.impl.StrutsActionProxy.execute(StrutsActionProxy.java:50)
     at 
org.apache.struts2.dispatcher.Dispatcher.serviceAction(Dispatcher.java:504)
     at 
org.apache.struts2.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:422)
     at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256)
     at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:215)
     at 
com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
     at 
com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
     at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256)
     at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:215)
     at 
org.apache.struts2.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:99)
     at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256)
     at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:215)
     at 
org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96)
     at 
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
     at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256)
     at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:215)
     at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:277)
     at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:188)
     at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:641)
     at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:97)
     at 
com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:85)
     at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:185)
     at 
org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:325)
     at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:226)
     at 
com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:165)
     at 
com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:791)
     at
com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:693)
     at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:954)
     at 
com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:170)
     at 
com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135)
     at 
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102)
     at 
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88)
     at 
com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
     at 
com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53)
     at 
com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57)
     at com.sun.grizzly.ContextTask.run(ContextTask.java:69)

     at 
com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57)
     at com.sun.grizzly.ContextTask.run(ContextTask.java:69)
     at 
com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:330)
     at 
com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:309)
     at java.lang.Thread.run(Thread.java:636)
|#]



----

I would like to know if there is any workaround,

Thanks,
Lenik





Created: (AMQ-2794) javax.jms.JMSException: User name or password is invalid --> activemq-admin b
javax.jms.JMSException: User name or password is invalid -->
activemq-admin browse --amqurl tcp://localhost:61616 TEST.FOO

DO NOT REPLY access allowed if password matches first seven characters of real password
https://issues.apache.org/bugzilla/show_bug.cgi?id=46152

Nick Kew <nic### @webthing.com> changed:

           What    |Removed                     |Added

Instance management
Hi,

I have apache-tomcat-6.0.20 and jdk1.6.0_18 installed in one centos 5.5
with
three instances running using the CATALINA_BASE variable resource.
The developments can shutdown and run own applications with a PROBE
application. I would like to management(shutdown e run) all the instances
with an web application, someone knows a application java that does this?

Thanks,
Alex Carvalho


RDF data management in MonetDB/SQL
Hi MonetDB developers,
  I have a question about RDF data management in MonetDB/SQL. The comment
of sql.rdfshred says "shredding an RDF data file from location results in 7
new tables (6 permutations of SPO and a mapping) ... We can then query with
SQL queries the RDF triple store by quering tables gid_spo, gid_pso etc.,
...". In my option, if the spo table is considered the triples table, the
other 5 tables (sop, pso, pos, osp, ops) (except the mapping table) can be
viewed as indexes of the triples table spo.
  When I write SQL to query the shredded RDF data in the triples table, I
have two ways. The first way is to only use spo table to make self-joins.
The second way is to use all 6 tables to make joins. I noticed that
"MonetDB/SQL Reference Manual" says that "The heart is the MonetDB server,
which comes with the following innovative features. ... Index selection,
creation and maintenance is automatic". If I use 6 tables (as indexes)
explicitly to make joins, it seems that I write the query plan by myself.
However, I think this work should be done by the SQL optimizer using
statistics from the system catalog. I wondered if these tables have already
been specified as indexes in the internal code, or if there is a way to
specify it so that the optimizer can use them as indexes to generate query
plans. I am not sure if my understanding is correct. I will appreciate any
help from developers. Thank you in advance.

  Best regards,
          Xin Wang

Re: RDF data management in MonetDB/SQL
Dear Lefteris,

  Thank you for your reply. Your explanation will help me much.
In addition, would you give me some guidelines on how to make the
6 different indices of the triple table be understood by the SQL/SPARQL
query optimizer and used accordingly. If I want to implement this
feature by myself, in which files the code should be added or modified. 
BTW, in the future, will you implement the MonetDB/SPARQL as a new 
supported front-end language? Will you consider to translate SPARQL to MAL

directly, instead of through SQL to MAL (but this way you have to develop 
a SPARQL specific optimizer, instead of making use of the SQL optimizer)? 
Thank you so much.

Best regards, 
    Xin Wang

From: Lefteris <lsi### @gmail.com>
Reply-To: 
To: wangx <wa### @tju.edu.cn>
Subject: Re: [Monetdb-developers] RDF data management in MonetDB/SQL
Date:Fri, 16 Jul 2010 10:29:53 +0200

Hi,

your understanding is in general correct. The availability of the six
different indices of the triple table should be understood by the
SQL/SPARQL query optimizer and used accordingly. However, the
MonetDB/RDF module has not been announced yet, and that is because it
has not finished yet. You are using a piece of code which is
experimental and unfinished. As such, the only way to test Monet and
its capabilities on RDF data is to manually write the SQL query in
such a way that you use the correct order of the triple table on the
correct join.

In the future of course, this will be done by the optimizer and the
user will only have to write simple SPARQL queries referring to the
name of the graph, instead of the underlying storage schema, but until
then I am afraid you will have to do it by hand. The good news is that
if you are using RDF data and testing queries that have been published
previously on papers as benchmarks, most likely someone else will have
done already the translation to a correct SQL query (since most
experiments on newly build engines that do not support SPARQL use this
method).

Hope this helps you a bit,

lefteris

2010/7/15 wangx
:
> Hi MonetDB developers,
>  I have a question about RDF data management in MonetDB/SQL. The
comment of
> sql.rdfshred says "shredding an RDF data file from location
results in 7 new
> tables (6 permutations of SPO and a mapping) ... We can then
query with SQL
> queries the RDF triple store by quering tables gid_spo, gid_pso
etc., ...".
> In my option, if the spo table is considered the triples table,
the other 5
> tables (sop, pso, pos, osp, ops) (except the mapping table) can
be viewed as
> indexes of the triples table spo.
>  When I writeSQLto query the shredded RDF data in the triples
table, I
> have two ways.The first way is toonly use spo table tomake
self-joins.
> The second way is touse all 6 tables to make joins. I noticed
that
> "MonetDB/SQL Reference Manual" says that "The heart is the
MonetDB server,
> which comes with the following innovative features. ... Index
selection,
> creation and maintenance is automatic". IfI use6 tables (as
indexes)
> explicitly to make joins, it seems that I write the query plan by
myself.
> However, I think this work should be done by the SQL optimizer
using
> statistics from the system catalog. I wondered if these tables
have
> alreadybeen specified as indexes in the internal code, or if
there is a way
> to specify it so that the optimizer can use them as indexes to
generate
> query plans. I am not sure if my understanding is correct. I will
appreciate
> any help from developers. Thank you in advance.
>
>  Best regards,
> Xin Wang
> 
Proposed changes to Puppet's IP management
Hi all,

As discussed multiple times earlier, but most recently at [1], we're  
going to take the next step on managing the IP of Puppet and related  
projects.

This is currently a proposal, so please speak up if you have any  
concerns about this.

Basically, our plan is to stick to either GPL or MIT+GPL for all of  
our projects, and all contributors will need to either sign a CLA or  
contribute their code under the MIT.

Non-core tools like Facter will have MIT attached so that they can  
easily be used wherever you want, and the core projects like Puppet  
and Dashboard will be GPL'd.  Our goal is to have enhanced rights to  
all of the code in the projects we maintain so we can relicense to  
partners and customers.

Note I didn't say 'own' - we're using a form of the Apache CLA, which  
just gives us enhanced rights, not ownership.  If you're not  
comfortable with that, or if your contribution is small enough that  
it's not worth signing a CLA, you can submit your code under the MIT  
(or equivalent, I assume) license, which gives us (and everyone else)  
the right to relicense your code.

We've got a plugin ready for Redmine (written for us by Eric Davis of  
LittleStream Software) that will track who's signed a CLA, and it has  
a click-through agreement just like Google uses, so signing a CLA  
should be entirely easy.

We'll be working through the list of contributors in the next quarter  
or so.  If you're a contributor and haven't yet signed a CLA, you  
should expect to hear from Amy Hoang, who will be working through the  
list.  We'll be installing the Redmine plugin in the next week, at  
which point we'll send out another email.

Also - we know that nearly everyone is moving toward an Apache license  
rather than GPL.  We don't rule out such a move in the future, and  
doing so would still require that we get these enhanced rights, but  
from I can tell the GPL does a much better job of encouraging a  
profitable ecosystem.  This is something we'll be revisiting  
constantly, but it seems the right answer for now.

1 -
http://www.mail-archive.com/puppet-us...com/msg07284.html







Password Criterias Validators
Hi all,
       Could any one tell me if there is a common framework for Password
Criterias Validators.

Thanks,
Kalpa


Re: Management of MySQL grant tables?
Hi,
I tried the mysq-module (from http://github.com/camptocamp/puppet-mysql)
and it will install mysql but it won't create db's or users.
I had to create /usr/share/augeas/lenses/contrib, because the module
seems to expect it. Otherwise I get no error-logs, it just won't
create users or databases...

I'm running it on Ubuntu Lucid Lynx, puppet 25.4.


Somebody having the same problems?

Thanks!

btw, this is what I use to test:

node 'puppettest' {

include mysql::server

mysql::rights {"Set rights for puppet database":
  ensure   => present,
  database => "puppesdfsdft",
  user     => "puppesd### @localhost",
  password => "puppsdfsdfdsfet"
}

mysql::database{"mysdfsdfsdfdb":
  ensure   => present
}

}




On Jun 21, 5:51 pm, David Schmitt <da.### @dasz.at> wrote:
 On 5/19/2010 5:44 PM, Ken wrote:



 >> I found a github reference to a package that might do it
 >> (http://github.com/camptocamp/puppet-mysql) but I can't
understand
 >> what it is, how it works, or even what to do with it.

 > Hmm. How familiar are you with puppet modules? Not quite clear
how
 > detailed we need to be here :-). Here is a doc that outlines
them:
 >http://docs.puppetlabs.com/guides/modules.html

 > Ordinarily you would drop this code into your 'module path' (by
 > default this is often /etc/puppet/modules). This would make it
 > available then for use in other code/manifests.

 > Assuming you are already okay with these aspects of puppet -
here is
 > a sample manifest on how to use it for 1 system. I have a fork
of
 > that code (its been around - I'm not even clear who wrote it
first -
 > could have been David Schmidt:
 >http://git.black.co.at/?p=module-mysql;a=summary) so it may not
work
 > exactly the same :-).

 Indeed, the mysql_* types were originially written by me.

 Best Regards, David
 --
 dasz.at OG              Tel: +43 (0)664 2602670    
Web:http://dasz.at
 Klosterneuburg                                    
    UID: ATU64260999

         FB-Nr.: FN 309285 g          FB-Gericht: LG
Korneuburg





Re: Re: Management of MySQL grant tables?
David,

Curious on how you handle doing a grant of *.* (all attributes) I looked
through your puppet type and I see you are individually listing every type
out but you are missing event_priv and trigger_priv as grant types.

-Chris

On Mon, Jun 21, 2010 at 11:51 AM, David Schmitt <da### @dasz.at>
wrote:

 On 5/19/2010 5:44 PM, Ken wrote:

> I found a github reference to a package that might do it
>> (http://github.com/camptocamp/puppet-mysql) but I can't
understand
>> what it is, how it works, or even what to do with it.
>>
>
> Hmm. How familiar are you with puppet modules? Not quite clear
how
> detailed we need to be here :-). Here is a doc that outlines
them:
> http://docs.puppetlabs.com/guides/modules.html
>
> Ordinarily you would drop this code into your 'module path' (by
> default this is often /etc/puppet/modules). This would make it
> available then for use in other code/manifests.
>
> Assuming you are already okay with these aspects of puppet - here
is
> a sample manifest on how to use it for 1 system. I have a fork of
> that code (its been around - I'm not even clear who wrote it
first -
> could have been David Schmidt:
> http://git.black.co.at/?p=module-mysql;a=summary) so it may not
work
> exactly the same :-).
>


 Indeed, the mysql_* types were originially written by me.


 Best Regards, David
 --
 dasz.at OG              Tel: +43 (0)664 2602670     Web:
http://dasz.at
 Klosterneuburg                                         UID:
ATU64260999

       FB-Nr.: FN 309285 g          FB-Gericht: LG Korneuburg


 --
 
nginx virtual host management
Are there recipes in puppet to deal with configuring nginx virtual
host files?
Ideally they'd be parameterized..





Web Management Console / Configuration and Spring-DM
Hi everybody

What are the requirements for a service to show up in "Configurations" 
in the "Configuration" of the web management console?

I am using spring-osgi (spring DM) version 1.2.1 and Spring 3.0 in 
felix. According to their documentation 
(http://static.springsource.org/osgi/d...l/compendium.html)

I created a few test services that (I thought) should be configurable 
via the configuration admin service once deployed:


<bean id="TestService" class="com.example.TestService">
<osgix:managed-properties persistent-id="com.example.TestService" />
<property name="someProperty" value="test me" />
</bean>


<bean class="com.example.ConfigurableService" id="configurableService"
/>
<osgi:service ref="configurableService" 
interface="org.osgi.service.cm.ManagedService">
<osgi:service-properties>
<entry key="service.pid" value="com.example.ConfigurableService" />
<entry key="some.property">
<value>
                     /v1
                     /v2
                     /v3
</value>
</entry>
<entry key="some.integer.property" value="23" />
</osgi:service-properties>
</osgi:service>

The latter service being the "most simple" approach according to the 
before mentioned documentation, i.e. ConfigurableService simply 
implements org.osgi.service.cm.ManagedService.

I deployed the bundle and verified that the beans are created and the 
service is exported. Also, the spring compendium infrastructure detects 
and registers the <osgix...> declarations. The ConfigurableService
is 
also listed as a service in the felix console.

However, I cannot configure any of the properties using the Apache Felix 
Web Management Console Configuration, as nothing I declared shows up in 
the "Configurations" dropdown (and of course not int the Factory 
configurations). Also, the PIDs do not show up under Configuration 
status > Configurations.

Is the use of SCR required for this?

Regarding the Felix version I am using, here are the felix bundle
versions:


Apache Felix Bundle Repository  1.4.1    org.apache.felix.bundlerepository
Apache Felix Configuration Admin Service    1.2.4    
org.apache.felix.configadmin
Apache Felix EventAdmin    1.0.0    org.apache.felix.eventadmin
System Bundle    2.0.2    org.apache.felix.framework
Apache Felix Http Bridge    2.0.5.R901608    org.apache.felix.http.bridge
Apache Felix Metatype Service    1.0.4    org.apache.felix.metatype
Apache Felix Preferences Service    1.0.4    org.apache.felix.prefs
Apache Felix Declarative Services    1.4.1.R892241    org.apache.felix.scr
Apache Felix Web Management Console    2.0.6   
org.apache.felix.webconsole
Apache Felix Web Console Event Plugin    0.9.0    
org.apache.felix.webconsole.plugins.event


Thanks a lot,
Olaf


Re: Re: Management of MySQL grant tables?
On 7/28/2010 12:41 AM, Christopher Johnston wrote:
 David,

 Curious on how you handle doing a grant of *.* (all attributes) I
looked
 through your puppet type and I see you are individually listing every
 type out but you are missing event_priv and trigger_priv as grant
types.

I haven't worked on those types in a while and it is possible, that 
those privs only exist in a later version of mysql?


Best Regards, David


        FB-Nr.: FN 309285 g          FB-Gericht: LG Korneuburg





Resetting the admin password in derby
Hi,

After a forced reset of the admin password I am no longer able to log
in. I have seen some other posts relating to this, I have deleted
cookies for example and this doesn't help. I can't request a reset as
mail is not configured on the host system. I assumed it would be a
straight forward to just update the JDOUsers table with an updated
password, I can see the encoded_password field but I can't figure out
what encoding it's using and setting it to null doesn't help. Can anyone
let me know how the passwords in the encoded_password field are
computed?

Thanks,
 -Phil


changes to Authenticator interface for password policy
hello guys,

  Its been a while since I started working on implementing password
policy[1].

  Here are a few things I wanted to let you know about the implementation

   1. The PasswordPolicyInterceptor cannot be used to enforce this
policy cause we need access to the
       userpassword and other special attributes before the
authentication process starts, so am removing this
       interceptor

   2. Am planning to make some changes to the Authenticator interface
to inject the password policy configuration
       so that the authenticator can have access to this config which
needs to be used to determine whether a
       user can be authenticated based on the policy state information
present in the user's entry.

  The second step will change the API and I think this is the right
time to change before 2.0-RC1

   let me know your thoughts about the above mentioned and as well as
about password policy implementation
   (like if you think a feature xyz is good to have)

thanks for your time

Kiran Ayyagari

[1] http://tools.ietf.org/html/draft-behe...assword-policy-10


Problems changing admin password
I have this strange problem where changing the admin password does not seem
to have any effect.

I've done exactly what Justin explained below and in fact with curl I get
a
login page when using the old admin password (the default "admin") and I
get
the landing page when using the new one.

But... and this is the strange thing... when I try to access
/system/console/bundles it only accepts the old password! Even after
restarting glassfish.

Any ideas?

Thanks,
-Tako


On Wed, Jun 30, 2010 at 14:57, Justin Edelson
<justin### @gmail.com>wrote:

 On 6/30/10 8:13 AM, Tako Schotanus wrote:
 > And do you have any idea what I'm doing wrong while trying to
change the
 > admin password? I just can't get it to work.

 The instructions on the FAQ work for me. Starting with an empty
 repository and the default bundles:

 curl http://admin:adm### @localhost:8888/index.html" rel="nofollow" target="_blank">http://admin:ad### @localhost:8888/index.html - works
 curl http://admin:bad### @localhost:8888/index.html - returns login
form

 curl -F"oldPwd=admin" -F"newPwd=Fritz" -F"newPwdConfirm=Fritz"
 http://admin:ad### @localhost
 :8888/system/userManager/user/admin.changePassword.html


 curl http://admin:adm### @localhost:8888/index.html" rel="nofollow" target="_blank">http://admin:ad### @localhost:8888/index.html - returns login
form
 curl http://admin:Frt### @localhost:8888/index.html - works

 You can safely ignore the bit in the FAQ about updating the admin
 password in the web console. That no longer applies.

 As Bertrand said, if the above steps don't work for you, please post
 some addition details (ideally under a new subject line to help
 findability).

 Justin



Password (getpass()) truncation issue on HP-UX in apr-0.9.18
Hello APR Developers:

I am using subversion client on HP-UX which has a dependency on apr,
apr-util. The packages available for HP-UX porting and archiving center
from 

http://hpux.connect.org.uk/hppd/hpux/...aries/apr-0.9.18/

has password truncation issue on HP-UX (all versions, 11.11, 11.23, 11,31)
on PA-RISC and IA64.

I could track the issue to HP-UX getpass() API which truncates the
password at 8 characters. Unfortunately, apr configure scripts finds and
uses getpass() HP-UX API. To resolve the issue I had to edit
.../apr-0.9.18/passwd/apr_getpass.c to manually undefine HAVE_GETPASS and
let apr internal getpass() function be used.

#if defined(__hpux) || defined(__hpux__)
  #undef HAVE_GETPASS
#endif

I checked the apr source tree up to 1.4.2 and the issue is present in all
apr versions.

The recommended password reading API on HP-UX is getpasswd() defined in
libsec. I would like to request apr developers to resolve the apr issue on
HP-UX by either of following methods,

- On HP-UX, always use apr internal getpass() / apr_getpass().
- On HP-UX, configure should check for getpasswd() available in libsec
library.

If this issue could be resolved in apr on HP-UX, we don't need users to
make source change to apr to be able to use it on HP-UX with password
lengths greater than 8 characters.

This is a critical issue being faced on HP-UX while using subversion
client.

Regards
-Rajesh


      


Re: change management workflow for puppet configs
On Jun 24, 4:02 pm, Eric Sorenson <eric.so### @me.com> wrote:
 - Describe your environment (general application, number of clients,
number of puppetmasters)
Internet facing private SaaS application (at my former employer),
about 150 nodes, one puppetmaster for production, one for testing
running on a different port.

 - Describe revision control setup
Commits are pushed to a "central" git repository into topic branches.
This is distinctly different than subversion, which doesn't handle
branches like Git does.  On each of the two puppet master servers,
environments are setup for individual people to work without affecting
other people.  Environments hack at the modulepath, so this
effectively tells the puppet master where to look for the local git
clone.  During testing, the environment in question is checked out to
the branch in question and the nodes are tested using puppetd --test --
environment=jmccune

To promote from development to testing, commits are cherry-picked or
full on merged into another branch named environment/testing, which is
shared and a sort of "staging area"

To promote from testing to production, the testing branch where topic
branches are merged and staged, we would simply merge the environment/
testing branch into the environment/production branch, then pull down
the branch from the "central" git repository onto the puppet master.

 - What do you like about it?
I love that Git allows you to switch branches quickly and easily
without the filesystem path changing.  This allows for a relatively
static --modulepath configuration setting.  I love that Git
facilitates each topic branch being tied to a specific Sales Force
case number (any ticketing system would work just as well).  I love
the clear and easy promotion from development to testing to
production.  Git is fast.  Very fast.  I like being able to hack on
puppet code on an airplane without network access.  I like being able
to rebase a topic branch and consolidate a number of small commits
into a single patch, then apply it to another branch.

 - What do you NOT like about it?
Git is difficult.  It took me some time to wrap my brain around it,
but once I did everything is great.  Git is difficult for junior level
people to approach as well.  The "central" git repository used a
shared "git" unix account with SSH authorized_keys containing a public
key for each person with commit access.  I was surprised to find many
of my colleagues had difficulty even setting up SSH keys for this
purpose.

 - What are you doing to improve/change the setup?
Pre-commit hook to check syntax before accepting a commit to the
environment/production branch.
Post-commit hook to trigger a git pull on the puppet masters after a
commit to the environment/production branch.
Integration with Salesforce case numbers (Ticketing system).

I also wrote a custom report processor for the puppet master to append
the Git commit ID to every log message generated.  This allowed me to
identify the state of the environment/production repository that
caused a resource to change or whatever log message coming from the
client.  My presentation on this is available at:
http://puppetcamp.org/europe-2010-ghe...ule-and-speakers/
Slides: http://bit.ly/puppetsplunkslides
Video of the talk: http://blip.tv/file/3759813/
Custom Report Processor:
http://github.com/jeffmccune/puppet-d...rts/logversion.rb
Finally, the config_version command line option to actually get the
Git SHA.  This could easily use Subversion as well:
http://github.com/jeffmccune/puppet-d...et-config-version


Let me know if you have any questions about this setup, I'm happy to
help.

Cheers,






Re: change management workflow for puppet configs
Hi Eric,

thanks for starting this interesting thread!

On 6/25/2010 1:02 AM, Eric Sorenson wrote:
 - Describe revision control setup subversion server with a branch
 named 'test' and a branch named 'prod'. all puppetmasters live on the
 prod branch - $moduledir is a working-copy checkout of svn, and one
 puppetmaster in each env has a second server running on :8141 that
 lives on the test branch.  prod branch commits should only be 'svn
 merge's of commits in test but this isn't enforced by technological
 control.  Post-commit hook sends out mail with the diff to everyone
 on the team.

Is there a specific reason you're not using real environments?

 - What are you doing to improve/change the setup? Pre-commit hook to
 do syntax checking on files to refuse commits on blatant errors
 Contemplating a post-commit push to 'svn up' the puppetmasters but
 not sure if this is really a good idea

Guess that depends on the quality of your checkins.

 Need some auditing between the
 branches to see what changes are not yet merged or if prod has
 somehow diverged (non-merge changes on the branch) Maybe one/handful
 of clients per class of host ought to live pointed at the test
 server.

This would also reduce the danger of automatically svn ups.



How are you handling "breaking" changes which shall be done in 
maintenance windows and/or "rolling upgrades"?



Best Regards, David


        FB-Nr.: FN 309285 g          FB-Gericht: LG Korneuburg





Use of JMeter as general test-management framework
Hello,

I have used JMeter in a previous life but I'm coming back to it with 
fresh eyes now. What I am looking for has nothing to do with Web sites, 
HTTP or Java. I'm just looking for a distributed test-management 
framework that can run multiple instances of scripted test clients using 
multiple client test systems. On first look I'm not sure if I'm going to 
be able to get JMeter to bent to my will here. I'm also looking at 
Grinder. I'd appreciate any hints from someone who has already done 
something similar.

Alan.