iceScrum | iceScrum

iceScrum Forums Discuss on iceScrum

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)

  • Author
    Posts
  • in reply to: Installation issue with R#5.1, download the R5#1.1 #10803

    Sabbasth
    Participant

    Hi,

    Maybe I wasn’t clear in my last post.

    With the things I did explained in previous posts, I finally made IS running.

    But it revealed problems probably due to FreeBSD’s tomcat portage. If I found an IS issue I’ll report it to the IS team of course.

    So, what I said in my last post is that I now need to configure a safe and secure environment before putting it in production.

    BR,
    Bastien Semene

    in reply to: Installation issue with R#5.1, download the R5#1.1 #10812

    Sabbasth
    Participant

    @blz wrote:

    Je pense que c’est la troisième (mysql-connector-java-5.1.18.jar) qui est utilisée pour icescrum.
    Avez-vous ce jar là dans un sous répertoire l’application icescrum ?

    @blz wrote:

    D’autre part, votre fichier config.properties […] est-il bien paramétré pour l’utilisation de mysql ?

    Le jar est bien présent et dans la même vesion (5.1.18). J’ai tenté de le changer par la dernière version stable sans succès (5.1.21 de mémoire).
    Autre information, si dans le config.properties je ne configure par MySQL, Icescrum utilise alors HSQLDB et j’ai la même type d’erreur de chargement du jar (le jar de HSQLDB cette fois évidemment).

    Pour répondre à la question, oui config.properties est bien paramétré car Icescrum a crée les tables dans la db fournie lorsqu’il s’est finalement lancé.

    @blz wrote:

    Pour le dossier .lbdsl, je ne comprends pas bien son utilité, je constate que j’ai ce dossier ici:
    /usr/share/tomcat6/.lbdsl
    qu’il est vide, et que sa date de création semble correspondre à la date de déploiement de l’archive icescrum.war.

    Après des recherches j’ai trouvé que ce dossier est utilisé par une autre lib : liquibase-dsl.
    Le problème étant qu’une variable “dsl.home” définie ce répertoire, mais qu’elle ne semble pas modifiable (du moins pas par la config Icescrum).

    Ceci dit, le coeur du problème est qu’une variable “home” ait pour racine “/root”, et je ne pense pas que ceci soit dû à Icescrum ou une quelconque lib.
    En effet sur FreeBSD les scripts rc sont lancés par root. Ensuite le script rc lance l’application correspondante avec le bon utilisateur.
    Je suis persuadé qu’ici le problème est que quelque part le home de root est transmit. D’ailleurs le dossier “icescrum” est bien utilisé et crée par icescrum dans /root.
    Enfin, normalement c’est l’utilisateur “www” qui lance tomcat. Il n’y a effectivement pas d’utilisateur tomcat. On considère que tomcat a les mêmes besoins que www donc pas besoin d’avoir un autre utilisateur, mais il est possible d’en créer un autre.

    Je vais me renseigner pour déterminer le pourquoi et comment pour pouvoir mettre en production tomcat dans un environnement sain et sécurisé, mais je sens que ça va être long et pénible.

    in reply to: Installation issue with R#5.1, download the R5#1.1 #10805

    Sabbasth
    Participant

    J’ai finalement réussi à faire tourner Icescrum.
    Mais cette install est loin d’être exploitable en prod.

    Donc ce que j’ai du faire :

    Je suis preneur sur toute explication du fait que la lib ne soit pas chargée depuis le dossier de la webapp, mais qu’il faille qu’elle soit chargée par tomcat.

    in reply to: Installation issue with R#5.1, download the R5#1.1 #10806

    Sabbasth
    Participant

    Bonjour,

    Le problème de “File Not Found” est résolu.
    J’ai fait plusieurs modifs quand le problème a disparu. La seule pour laquelle je ne peux pas revenir en arrière (et donc tester l’origine du blocage) est que j’ai lancé une fois tomcat à la main avec le script “catalina.sh”.
    Je suppose donc, avec quelques réserves, que ce lancement a réglé le problème.

    Maintenant j’ai une erreur de drivers MySQL.

    Voici le log icescrum.log :

    2012-09-03 11:44:52,205 [localhost-startStop-1] INFO  grails.spring.BeanBuilder  - [RuntimeConfiguration] Configuring data source for environment: PRODUCTION
    2012-09-03 11:44:59,865 [localhost-startStop-1] ERROR org.springframework.web.context.ContextLoader - Context initialization failed
    org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'messageSource': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionManager': Cannot resolve reference to bean 'sessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory': Cannot resolve reference to bean 'lobHandlerDetector' while setting bean property 'lobHandler'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'lobHandlerDetector': Invocation of init method failed; nested exception is org.springframework.jdbc.support.MetaDataAccessException: Error while extracting DatabaseMetaData; nested exception is java.sql.SQLException: org.gjt.mm.mysql.Driver
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionManager': Cannot resolve reference to bean 'sessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory': Cannot resolve reference to bean 'lobHandlerDetector' while setting bean property 'lobHandler'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'lobHandlerDetector': Invocation of init method failed; nested exception is org.springframework.jdbc.support.MetaDataAccessException: Error while extracting DatabaseMetaData; nested exception is java.sql.SQLException: org.gjt.mm.mysql.Driver
    ... 6 more
    Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory': Cannot resolve reference to bean 'lobHandlerDetector' while setting bean property 'lobHandler'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'lobHandlerDetector': Invocation of init method failed; nested exception is org.springframework.jdbc.support.MetaDataAccessException: Error while extracting DatabaseMetaData; nested exception is java.sql.SQLException: org.gjt.mm.mysql.Driver
    ... 6 more
    Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'lobHandlerDetector': Invocation of init method failed; nested exception is org.springframework.jdbc.support.MetaDataAccessException: Error while extracting DatabaseMetaData; nested exception is java.sql.SQLException: org.gjt.mm.mysql.Driver
    ... 6 more
    Caused by: org.springframework.jdbc.support.MetaDataAccessException: Error while extracting DatabaseMetaData; nested exception is java.sql.SQLException: org.gjt.mm.mysql.Driver
    ... 6 more
    Caused by: java.sql.SQLException: org.gjt.mm.mysql.Driver
    at $Proxy20.getMetaData(Unknown Source)
    ... 6 more
    Caused by: java.lang.ClassNotFoundException: org.gjt.mm.mysql.Driver
    at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:247)
    ... 7 more

    icescrum.2019-09-03.log :

    Sep 3, 2012 11:44:27 AM org.apache.catalina.core.StandardContext listenerStart
    FINE: Configuring event listener class 'org.codehaus.groovy.grails.web.util.Log4jConfigListener'
    Sep 3, 2012 11:44:27 AM org.apache.catalina.core.StandardContext listenerStart
    FINE: Configuring event listener class 'com.energizedwork.grails.plugins.sessiontempfiles.SessionListenerImpl'
    Sep 3, 2012 11:44:29 AM org.apache.catalina.core.StandardContext listenerStart
    FINE: Configuring event listener class 'org.codehaus.groovy.grails.web.context.GrailsContextLoaderListener'
    Sep 3, 2012 11:44:29 AM org.apache.catalina.core.StandardContext listenerStart
    FINE: Sending application start events
    Sep 3, 2012 11:44:32 AM org.apache.catalina.core.ApplicationContext log
    INFO: Initializing Spring root WebApplicationContext

    catalina.out :

    Sep 3, 2012 11:44:19 AM org.apache.coyote.AbstractProtocol pause
    INFO: Pausing ProtocolHandler ["http-nio-80"]
    Sep 3, 2012 11:44:19 AM org.apache.coyote.AbstractProtocol pause
    INFO: Pausing ProtocolHandler ["ajp-bio-8009"]
    Sep 3, 2012 11:44:19 AM org.apache.catalina.core.StandardService stopInternal
    INFO: Stopping service Catalina
    Sep 3, 2012 11:44:19 AM org.apache.coyote.AbstractProtocol stop
    INFO: Stopping ProtocolHandler ["http-nio-80"]
    Sep 3, 2012 11:44:19 AM org.apache.coyote.AbstractProtocol stop
    INFO: Stopping ProtocolHandler ["ajp-bio-8009"]
    Sep 3, 2012 11:44:19 AM org.apache.coyote.AbstractProtocol destroy
    INFO: Destroying ProtocolHandler ["http-nio-80"]
    Sep 3, 2012 11:44:19 AM org.apache.coyote.AbstractProtocol destroy
    INFO: Destroying ProtocolHandler ["ajp-bio-8009"]
    Sep 3, 2012 11:44:23 AM org.apache.catalina.core.AprLifecycleListener init
    INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/packages/lib/i386:/lib:/usr/lib:/usr/local/lib
    Sep 3, 2012 11:44:24 AM org.apache.coyote.AbstractProtocol init
    INFO: Initializing ProtocolHandler ["http-nio-80"]
    Sep 3, 2012 11:44:24 AM org.apache.tomcat.util.net.NioSelectorPool getSharedSelector
    INFO: Using a shared selector for servlet write/read
    Sep 3, 2012 11:44:24 AM org.apache.coyote.AbstractProtocol init
    INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
    Sep 3, 2012 11:44:24 AM org.apache.catalina.startup.Catalina load
    INFO: Initialization processed in 2119 ms
    Sep 3, 2012 11:44:24 AM org.apache.catalina.core.StandardService startInternal
    INFO: Starting service Catalina
    Sep 3, 2012 11:44:24 AM org.apache.catalina.core.StandardEngine startInternal
    INFO: Starting Servlet Engine: Apache Tomcat/7.0.28
    Sep 3, 2012 11:44:24 AM org.apache.catalina.startup.HostConfig deployWAR
    INFO: Deploying web application archive /usr/local/apache-tomcat-7.0/webapps/icescrum.war
    Sep 3, 2012 11:44:27 AM org.apache.catalina.core.StandardContext listenerStart
    FINE: Configuring event listener class 'org.codehaus.groovy.grails.web.util.Log4jConfigListener'
    Sep 3, 2012 11:44:27 AM org.apache.catalina.core.StandardContext listenerStart
    FINE: Configuring event listener class 'com.energizedwork.grails.plugins.sessiontempfiles.SessionListenerImpl'
    Sep 3, 2012 11:44:29 AM org.apache.catalina.core.StandardContext listenerStart
    FINE: Configuring event listener class 'org.codehaus.groovy.grails.web.context.GrailsContextLoaderListener'
    Sep 3, 2012 11:44:29 AM org.apache.catalina.core.StandardContext listenerStart
    FINE: Sending application start events
    Server Timezone : Europe/Paris
    log dir : logs
    *** No external configuration file defined (icescrum_config_location). ***
    (*) grails.config.locations = [classpath:config.properties]
    Sep 3, 2012 11:44:32 AM org.apache.catalina.core.ApplicationContext log
    INFO: Initializing Spring root WebApplicationContext

    Configuring Spring Security Core ...
    ... finished configuring Spring Security Core

    Configuring Spring Security ACL ...
    Sep 3, 2012 11:44:59 AM org.apache.catalina.core.StandardContext startInternal
    SEVERE: Error listenerStart
    Sep 3, 2012 11:44:59 AM org.apache.catalina.core.StandardContext startInternal
    SEVERE: Context [/icescrum] startup failed due to previous errors
    Sep 3, 2012 11:44:59 AM org.apache.catalina.startup.HostConfig deployDirectory
    INFO: Deploying web application directory /usr/local/apache-tomcat-7.0/webapps/ROOT
    Sep 3, 2012 11:45:00 AM org.apache.catalina.startup.HostConfig deployDirectory
    INFO: Deploying web application directory /usr/local/apache-tomcat-7.0/webapps/docs
    Sep 3, 2012 11:45:00 AM org.apache.catalina.startup.HostConfig deployDirectory
    INFO: Deploying web application directory /usr/local/apache-tomcat-7.0/webapps/examples
    Sep 3, 2012 11:45:00 AM org.apache.catalina.startup.HostConfig deployDirectory
    INFO: Deploying web application directory /usr/local/apache-tomcat-7.0/webapps/host-manager
    Sep 3, 2012 11:45:00 AM org.apache.catalina.startup.HostConfig deployDirectory
    INFO: Deploying web application directory /usr/local/apache-tomcat-7.0/webapps/manager
    Sep 3, 2012 11:45:00 AM org.apache.coyote.AbstractProtocol start
    INFO: Starting ProtocolHandler ["http-nio-80"]
    Sep 3, 2012 11:45:00 AM org.apache.coyote.AbstractProtocol start
    INFO: Starting ProtocolHandler ["ajp-bio-8009"]
    Sep 3, 2012 11:45:00 AM org.apache.catalina.startup.Catalina start
    INFO: Server startup in 36342 ms

    catalina.2012-09-03.log :

    Sep 3, 2012 11:44:19 AM org.apache.coyote.AbstractProtocol pause
    INFO: Pausing ProtocolHandler ["http-nio-80"]
    Sep 3, 2012 11:44:19 AM org.apache.coyote.AbstractProtocol pause
    INFO: Pausing ProtocolHandler ["ajp-bio-8009"]
    Sep 3, 2012 11:44:19 AM org.apache.catalina.core.StandardService stopInternal
    INFO: Stopping service Catalina
    Sep 3, 2012 11:44:19 AM org.apache.coyote.AbstractProtocol stop
    INFO: Stopping ProtocolHandler ["http-nio-80"]
    Sep 3, 2012 11:44:19 AM org.apache.coyote.AbstractProtocol stop
    INFO: Stopping ProtocolHandler ["ajp-bio-8009"]
    Sep 3, 2012 11:44:19 AM org.apache.coyote.AbstractProtocol destroy
    INFO: Destroying ProtocolHandler ["http-nio-80"]
    Sep 3, 2012 11:44:19 AM org.apache.coyote.AbstractProtocol destroy
    INFO: Destroying ProtocolHandler ["ajp-bio-8009"]
    Sep 3, 2012 11:44:23 AM org.apache.catalina.core.AprLifecycleListener init
    INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/packages/lib/i386:/lib:/usr/lib:/usr/local/lib
    Sep 3, 2012 11:44:24 AM org.apache.coyote.AbstractProtocol init
    INFO: Initializing ProtocolHandler ["http-nio-80"]
    Sep 3, 2012 11:44:24 AM org.apache.tomcat.util.net.NioSelectorPool getSharedSelector
    INFO: Using a shared selector for servlet write/read
    Sep 3, 2012 11:44:24 AM org.apache.coyote.AbstractProtocol init
    INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
    Sep 3, 2012 11:44:24 AM org.apache.catalina.startup.Catalina load
    INFO: Initialization processed in 2119 ms
    Sep 3, 2012 11:44:24 AM org.apache.catalina.core.StandardService startInternal
    INFO: Starting service Catalina
    Sep 3, 2012 11:44:24 AM org.apache.catalina.core.StandardEngine startInternal
    INFO: Starting Servlet Engine: Apache Tomcat/7.0.28
    Sep 3, 2012 11:44:24 AM org.apache.catalina.startup.HostConfig deployWAR
    INFO: Deploying web application archive /usr/local/apache-tomcat-7.0/webapps/icescrum.war
    Sep 3, 2012 11:44:59 AM org.apache.catalina.core.StandardContext startInternal
    SEVERE: Error listenerStart
    Sep 3, 2012 11:44:59 AM org.apache.catalina.core.StandardContext startInternal
    SEVERE: Context [/icescrum] startup failed due to previous errors
    Sep 3, 2012 11:44:59 AM org.apache.catalina.startup.HostConfig deployDirectory
    INFO: Deploying web application directory /usr/local/apache-tomcat-7.0/webapps/ROOT
    Sep 3, 2012 11:45:00 AM org.apache.catalina.startup.HostConfig deployDirectory
    INFO: Deploying web application directory /usr/local/apache-tomcat-7.0/webapps/docs
    Sep 3, 2012 11:45:00 AM org.apache.catalina.startup.HostConfig deployDirectory
    INFO: Deploying web application directory /usr/local/apache-tomcat-7.0/webapps/examples
    Sep 3, 2012 11:45:00 AM org.apache.catalina.startup.HostConfig deployDirectory
    INFO: Deploying web application directory /usr/local/apache-tomcat-7.0/webapps/host-manager
    Sep 3, 2012 11:45:00 AM org.apache.catalina.startup.HostConfig deployDirectory
    INFO: Deploying web application directory /usr/local/apache-tomcat-7.0/webapps/manager
    Sep 3, 2012 11:45:00 AM org.apache.coyote.AbstractProtocol start
    INFO: Starting ProtocolHandler ["http-nio-80"]
    Sep 3, 2012 11:45:00 AM org.apache.coyote.AbstractProtocol start
    INFO: Starting ProtocolHandler ["ajp-bio-8009"]
    Sep 3, 2012 11:45:00 AM org.apache.catalina.startup.Catalina start
    INFO: Server startup in 36342 ms
    in reply to: Installation issue with R#5.1, download the R5#1.1 #10809

    Sabbasth
    Participant

    Effectivement je suis sur FreeBSD.

    Les variables ne sont pas déclarés par un shell, donc je ne peux pas y accéder.
    Elle est déclarée lors du lancement de tomcat par le script rc.

    Voici comment les définir par l’intermédiaire du script rc :

    tomcat7_java_opts="-Xmx512M -XX:MaxPermSize=512M"
    tomcat7_java_home="/usr/local/diablo-jdk1.6.0"

    Voici comment ces variables sont traités dans le script rc :

    eval "_tomcat_java_home=${${name}_java_home:-'/usr/local/diablo-jdk1.6.0'}"

    Sans rentrer dans les détails, si la variable n’est pas définie elle est set à ‘/usr/local/diablo-jdk1.6.0’ (ce qui est correct, mais je la set explicitement quand même.)

    command="/usr/local/bin/jsvc"
    command_args="-java-home '${_tomcat_java_home}'
    -server
    -user ${_tomcat_catalina_user}
    -pidfile '${pidfile}'
    -wait ${_tomcat_wait}
    -outfile '${_tomcat_stdout}'
    -errfile '${_tomcat_stderr}'
    -classpath '/usr/local/apache-tomcat-7.0/bin/bootstrap.jar:/usr/local/share/java/classes/commons-daemon.jar:/usr/local/apache-tomcat-7.0/bin/tomcat-juli.jar${_tomcat_classpath}'
    -Djava.util.logging.manager=${_tomcat_logging_manager}
    -Djava.util.logging.config.file='${_tomcat_logging_config}'
    ${_tomcat_java_opts}
    -Djava.endorsed.dirs='/usr/local/apache-tomcat-7.0/endorsed'
    -Dcatalina.home='${_tomcat_catalina_home}'
    -Dcatalina.base='${_tomcat_catalina_base}'
    -Djava.io.tmpdir='${_tomcat_catalina_tmpdir}'
    org.apache.catalina.startup.Bootstrap
    ${_tomcat_pipe_cmd}"

    l’arg -java-home est envoyé à jsvc avec $_tomcat_java_home
    Voilà comment on le retrouve dans la liste d’args que je vous ai fournis.

    En regardant un peu la manière de lancer jsvc je me dis qu’il faut peut-être que je rajoute un path pour les classes ?

    Ca me fait penser que je n’ai pas précisé que tomcat se lance correctement, j’ai accès aux webapps de base comme par exemple ‘manager’ ou ‘host-manager’.

    in reply to: Installation issue with R#5.1, download the R5#1.1 #10810

    Sabbasth
    Participant

    Bonjour,

    J’ai le même problème avec icescrum R5#1.2.

    • Le serveur (une jail) est “neuve” et apache tomcat y est installé par défaut.
    • J’ai suivi les instruction d’installation décrites dans le post dédié
    • J’ai rajouté un handler de logging sur l’app pour faciliter le debug

    icescrum.log :



    2012-08-30 11:38:32,793 [localhost-startStop-1] INFO grails.spring.BeanBuilder - [RuntimeConfiguration] Configuring data source for environment: PRODUCTION
    2012-08-30 11:38:33,378 [localhost-startStop-1] ERROR org.springframework.web.context.ContextLoader - Context initialization failed
    org.springframework.beans.factory.access.BootstrapException: Error executing bootstraps; nested exception is org.codehaus.groovy.runtime.InvokerInvocationException: java.io.IOException: No such file or directory
    at org.codehaus.groovy.grails.web.context.GrailsContextLoader.createWebApplicationContext(GrailsContextLoader.java:87)
    at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:197)
    at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4790)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5284)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:899)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:875)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:618)
    at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:963)
    at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1600)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: org.codehaus.groovy.runtime.InvokerInvocationException: java.io.IOException: No such file or directory
    at grails.spring.BeanBuilder.invokeBeanDefiningClosure(BeanBuilder.java:723)
    at grails.spring.BeanBuilder.beans(BeanBuilder.java:573)
    at grails.spring.BeanBuilder.invokeMethod(BeanBuilder.java:519)
    ... 6 more
    Caused by: java.io.IOException: No such file or directory
    at java.io.UnixFileSystem.createFileExclusively(Native Method)
    at java.io.File.createNewFile(File.java:883)
    at java_io_File$createNewFile.call(Unknown Source)
    at org.icescrum.core.support.ApplicationSupport$__clinit__closure10.doCall(ApplicationSupport.groovy:119)
    at org.icescrum.core.support.ApplicationSupport$__clinit__closure10.doCall(ApplicationSupport.groovy)
    at IcescrumCoreGrailsPlugin$_closure2.doCall(IcescrumCoreGrailsPlugin.groovy:257)
    at IcescrumCoreGrailsPlugin$_closure2.doCall(IcescrumCoreGrailsPlugin.groovy)
    ... 9 more

    système:

    # uname -imr
    8.2-RELEASE-p3 i386 GENERIC

    java:

    # java -version
    java version "1.6.0_07"
    Diablo Java(TM) SE Runtime Environment (build 1.6.0_07-b02)
    Diablo Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)

    apache-tomcat:

    1.6.0_07-b02

    java service args:

    -java-home '/usr/local/diablo-jdk1.6.0' -server -user www -pidfile '/var/run/tomcat7.pid' -wait 30 -outfile '/usr/local/apache-tomcat-7.0/logs/catalina.out' -errfile '&1' -classpath '/usr/local/apache-tomcat-7.0/bin/bootstrap.jar:/usr/local/share/java/classes/commons-daemon.jar:/usr/local/apache-tomcat-7.0/bin/tomcat-juli.jar' -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file='/usr/local/apache-tomcat-7.0/conf/logging.properties' -Xmx512M -XX:MaxPermSize=512M -Djava.endorsed.dirs='/usr/local/apache-tomcat-7.0/endorsed' -Dcatalina.home='/usr/local/apache-tomcat-7.0' -Dcatalina.base='/usr/local/apache-tomcat-7.0' -Djava.io.tmpdir='/usr/local/apache-tomcat-7.0/temp' org.apache.catalina.startup.Bootstrap

    tomcat process:

    root  70826  0.0  0.1  3380  1084  ??  IsJ  11:38AM   0:00.00 /usr/local/bin/jsvc -java-home /usr/local/diablo-jdk1.6.0 -server -user www -pidfile /var/run/tomcat7.pid -wait 30
    www 70827 0.0 10.0 1191148 207560 ?? IJ 11:38AM 0:53.74 /usr/local/bin/jsvc -java-home /usr/local/diablo-jdk1.6.0 -server -user www -pidfile /var/run/tomcat7.pid -wait 30
    root 71010 0.0 0.0 3500 980 0 RL+J 11:53AM 0:00.00 grep jsvc

    L’utilisateur est donc bien www.

    tomcat user:

    # pw usershow www
    www:*:80:80::0:0:World Wide Web Owner:/home/www:/usr/local/bin/zsh

    le home dir est donc /home/www, et j’ai aussi rajouté un shell au cas où.

    tomcat user’s home folder:

    # ls -al /home/www
    total 6
    drwxr-xr-x 3 www www 512 Aug 30 11:09 .
    drwxr-xr-x 3 root wheel 512 Aug 30 11:05 ..
    drwxr-xr-x 2 www www 512 Aug 30 11:09 icescrum

    Le process peut accéder au dossier et y écrire.

    Comment peux-t-on résoudre le problème ?

Viewing 6 posts - 1 through 6 (of 6 total)