iceScrum Forums Discuss on iceScrum
- This topic has 24 replies, 9 voices, and was last updated 8 years, 3 months ago by Nicolas Noullet.
-
AuthorPosts
-
27/06/2012 at 3:17 pm #10630
Nicolas NoulletKeymasterHello,
Some users are facing a problem with the R5#1 version, giving the following error message “No such file or directory”.
The R5#1.1 is now available (http://www.icescrum.org/download/) and should solve this problem.
Don’t hesitate to give your feedback on this new version.
27/06/2012 at 5:07 pm #10796
J3AParticipantUnfortunately, the problem have not been solved cause i still face the same issue with the R5#1.1. Plus may be you could improve your installation information on the forum because it does not help.
27/06/2012 at 11:32 pm #10797
samitharansaraParticipantThats correct J3A.. The problem is still there. 😳
27/06/2012 at 11:35 pm #10798
samitharansaraParticipant@Nicolas Noullet wrote:
Hello,
Some users are facing a problem with the R5#1 version, giving the following error message “No such file or directory”.
The R5#1.1 is now available (http://www.icescrum.org/download/) and should solve this problem.
Don’t hesitate to give your feedback on this new version.
This seems a great product. If you update the documentation, test properly, and deploy tested versions under various system configurations, this could be way more popular, as there are no very good scrumming tools yet.
28/06/2012 at 1:01 am #10799
Vincent BarrierParticipantHello,
Could you try this :
– Check if the user who launch Tomcat Server has an home directory -> if not -> create it -> try launch iceScrum
– If not working -> create a dir ‘icescrum’ inside that home directory -> try launch iceScrumThanks !
29/06/2012 at 9:45 am #10801
Nicolas NoulletKeymasterHello,
Does anybody still face a problem?
If so, did you try the workaround given by Vincent?
29/06/2012 at 1:51 pm #10800
J3AParticipant@Vincent Barrier wrote:
Hello,
Could you try this :
– Check if the user who launch Tomcat Server has an home directory -> if not -> create it -> try launch iceScrum
– If not working -> create a dir ‘icescrum’ inside that home directory -> try launch iceScrumThanks !
Since the beginning i have this configuration and since that time nothing works for me. We all have tomcat installed on our computer so that means normally we have the tomcat home dir, plus when you deploy the war an “icescrum” dir is created in the webapps so why do we have to create tons of “icescrum” dir under tomcat dir? May be i did not understand so i’ll need another kind of help because Vincent’s one did not help at this moment.
29/06/2012 at 3:01 pm #10802
Nicolas NoulletKeymasterWell, if you read again, Vincent was talking about the tomcat home directory (the home of the user that starts tomcat), not the webapp one.
30/08/2012 at 12:56 pm #10810
SabbasthParticipantBonjour,
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 GENERICjava:
# 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 jsvcL’utilisateur est donc bien www.
tomcat user:
# pw usershow www
www:*:80:80::0:0:World Wide Web Owner:/home/www:/usr/local/bin/zshle 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 icescrumLe process peut accéder au dossier et y écrire.
Comment peux-t-on résoudre le problème ?
30/08/2012 at 1:53 pm #10808
blzParticipantBonjour Sabbasth,
Il semblerait que vous soyez sous FreeBSD, comment avez vous rêglé les variables d’environnement JAVA_HOME et JAVA_OPTS ?
Ces variables sont elles définies correctement si vous les lisez avec “echo” par exemple ?30/08/2012 at 2:45 pm #10809
SabbasthParticipantEffectivement 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’.
30/08/2012 at 3:49 pm #10813
blzParticipantje connais mal tomcat avec freeBSD, mais la variable $JAVA_HOME (ou $_tomcat_java_home avec freeBSD apparement) semble être correctement définie;
l’info pertinente d’icescrum.log est:
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
“No such file or directory”… il doit y avoir un chemin mal configuré quelque part; mais où ?
pour contrôler le bon déroulement du lancement de icescrum, il est également utile de regarder les logs suivants:
– catalina.out
– catalina-la_date_du_jour.log (par exemple catalina.2012-08-30.log)
– localhost.2012-08-30.log
(noms des fichiers avec linux, mais ce sont sans doute les mêmes avec freeBSD)d’une manière plus générale, en faisant:
# ls -lrt /var/log/tomcat6/
(adapter le chemin (pour linux ici) vers le répertoire des logs de tomcat avec freeBSD)
après avoir tenté de démarrer icescrum, on voit les fichiers de logs qui ont été modifié dernièrementil faudrait les lire, ou mieux les tracer chacun séparément en direct avec
# tail -f /var/log/tomcat6/fichier.log
pour voir s’il n’y a pas d’infos intéressantes supplémentaires, y voyez-vous quelque chose, ou pouvez-vous les mettre ici ?
04/09/2012 at 1:13 pm #10806
SabbasthParticipantBonjour,
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 moreicescrum.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 WebApplicationContextcatalina.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 mscatalina.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 ms04/09/2012 at 3:42 pm #10805
SabbasthParticipantJ’ai finalement réussi à faire tourner Icescrum.
Mais cette install est loin d’être exploitable en prod.Donc ce que j’ai du faire :
- Ajouter le connecteur MySQL dans le dossier des classes commun à toutes les webapps
- Ensuite j’ai de nouveau eu une erreur “FileNotFound”, il me fallait créér le dossier /root/.lbdsl (explicite dans le log)
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.
05/09/2012 at 12:14 pm #10811
blzParticipantBonjour Sabbasth, et tout d’abord bravo !
D’expérience, c’est souvent nécessaire de refaire l’installation plusieurs fois pour mieux la maîtriser et faire quelque chose de propre…
Ce fil:
viewtopic.php?f=20&t=1156
semble correspondre à votre erreur, mais je ne comprends pas bien la résolution.Pouvez-vous faire une recherche (avec la commande locate par exemple, ou find) du fichier “mysql-connector”.
Pour ma part (Linux-Debian), j’en trouve trois occurences:root@vmicescrum:~# locate mysql-connector
/usr/share/java/mysql-connector-java-5.1.10.jar
/usr/share/java/mysql-connector-java.jar
/var/lib/tomcat6/webapps/icescrum/WEB-INF/lib/mysql-connector-java-5.1.18.jar
root@vmicescrum:~#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 ?D’autre part, votre fichier config.properties (/var/lib/tomcat6/webapps/icescrum/WEB-INF/classes/config.properties pour Linux-Debian) est-il bien paramétré pour l’utilisation de mysql ?
Voilà la section concernée sur ma configuration (adapter le nom d’hôte, le port, le nom de la base mysql, le nom d’utilisateur mysql et son mot de passe):dataSource.driverClassName=org.gjt.mm.mysql.Driver
dataSource.dialect=org.hibernate.dialect.MySQLInnoDBDialect
dataSource.url=jdbc:mysql://localhost:3306/icescrum?useUnicode=true&characterEncoding=utf8&autoReconnect=true
dataSource.username=icescrum_dba
dataSource.password=icescrum_dba_password
dataSource.dbCreate=update
#Use pool connection
dataSource.pooled=true
dataSource.properties.maxActive = 50
dataSource.properties.maxIdle = 25
dataSource.properties.minIdle = 1
dataSource.properties.initialSize = 1
dataSource.properties.minEvictableIdleTimeMillis = 1800000
dataSource.properties.timeBetweenEvictionRunsMillis = 1800000
dataSource.properties.numTestsPerEvictionRun = 3
dataSource.properties.maxWait = 10000
dataSource.properties.testOnBorrow = true
dataSource.properties.testWhileIdle = true
dataSource.properties.testOnReturn = false
dataSource.properties.validationQuery = "SELECT 1"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.Toujours avec Linux Debian, l’utilisateur et le groupe des répertoires importants de tomcat ont été fixés ainsi:
root@vmicescrum:~# ll -d /usr/share/tomcat6*
drwxr-xr-x 7 tomcat6 root 4096 22 août 14:30 /usr/share/tomcat6
drwxr-xr-x 4 tomcat6 root 4096 22 août 10:21 /usr/share/tomcat6-admin
drwxr-xr-x 3 tomcat6 root 4096 22 août 10:17 /usr/share/tomcat6-root
root@vmicescrum:~#
root@vmicescrum:~# ll -d /var/lib/tomcat6/*
drwxr-xr-x 2 root root 4096 22 août 14:10 /var/lib/tomcat6/bin
drwxr-xr-x 3 tomcat6 root 4096 22 août 10:17 /var/lib/tomcat6/common
lrwxrwxrwx 1 tomcat6 root 12 22 août 10:17 /var/lib/tomcat6/conf -> /etc/tomcat6
lrwxrwxrwx 1 tomcat6 root 17 22 août 10:17 /var/lib/tomcat6/logs -> ../../log/tomcat6
drwxr-xr-x 3 tomcat6 root 4096 22 août 10:17 /var/lib/tomcat6/server
drwxr-xr-x 3 tomcat6 root 4096 22 août 10:17 /var/lib/tomcat6/shared
drwxrwxr-x 4 tomcat6 root 4096 22 août 13:54 /var/lib/tomcat6/webapps
lrwxrwxrwx 1 tomcat6 root 19 22 août 10:17 /var/lib/tomcat6/work -> ../../cache/tomcat6
root@vmicescrum:~#
ainsi que leurs sous répertoires.
Selon votre première intervention, il semblerait que votre répertoire de l’application icescrum appartienne à l’utilisateur www et au groupe www.
Serait-ce pour cette raison qu’en déployant le war, tomcat n’ait pas pu créer le répertoire .ldbsl ?
Je n’ai pas de FreeBSD sous la main pour tester; existe-t-il un utilisateur tomcat (ou tomcat6, ou 7) avec FreeBSD, ou est-ce l’utilisateur www qui fait office d’utilisateur tomcat ? -
AuthorPosts
The forum ‘Installation’ is closed to new topics and replies.