Error with velocity.log

Not sure why this is popping up now a a fresh install. WHere is this
log attempting to be written? Using 2.9

* ERROR 2012-09-25 09:30:27,805 Context initialization failed
(ContextLoader.java [pool-2-thread-1])
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name
'org.hisp.dhis.system.velocity.VelocityManager' defined in URL
[jar:file:/var/lib/tomcat7/webapps/dhis/WEB-INF/lib/dhis-support-system-2.9.jar!/META-INF/dhis/beans.xml]:
Instantiation of bean failed; nested exception is
org.springframework.beans.BeanInstantiationException: Could not
instantiate bean class
[org.hisp.dhis.system.velocity.VelocityManager]: Constructor threw
exception; nested exception is
org.apache.velocity.exception.VelocityException: Error initializing
log: Failed to initialize an instance of
org.apache.velocity.runtime.log.Log4JLogChute with the current runtime
configuration.
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:997)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:943)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
        at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294)
        at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225)
        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585)
        at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:913)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:464)
        at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:385)
        at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:284)
        at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4779)
        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5273)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:895)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:871)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:615)
        at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:958)
        at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1599)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:679)
Caused by: org.springframework.beans.BeanInstantiationException: Could
not instantiate bean class
[org.hisp.dhis.system.velocity.VelocityManager]: Constructor threw
exception; nested exception is
org.apache.velocity.exception.VelocityException: Error initializing
log: Failed to initialize an instance of
org.apache.velocity.runtime.log.Log4JLogChute with the current runtime
configuration.
        at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:162)
        at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:76)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:990)
        ... 27 more
Caused by: org.apache.velocity.exception.VelocityException: Error
initializing log: Failed to initialize an instance of
org.apache.velocity.runtime.log.Log4JLogChute with the current runtime
configuration.
        at org.apache.velocity.runtime.RuntimeInstance.initializeLog(RuntimeInstance.java:875)
        at org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:262)
        at org.apache.velocity.app.VelocityEngine.init(VelocityEngine.java:93)
        at org.hisp.dhis.system.velocity.VelocityManager.<init>(VelocityManager.java:60)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
        at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:147)
        ... 29 more
Caused by: org.apache.velocity.exception.VelocityException: Failed to
initialize an instance of
org.apache.velocity.runtime.log.Log4JLogChute with the current runtime
configuration.
        at org.apache.velocity.runtime.log.LogManager.createLogChute(LogManager.java:220)
        at org.apache.velocity.runtime.log.LogManager.updateLog(LogManager.java:269)
        at org.apache.velocity.runtime.RuntimeInstance.initializeLog(RuntimeInstance.java:871)
        ... 37 more
Caused by: java.lang.RuntimeException: Error configuring Log4JLogChute :
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
        at org.apache.velocity.util.ExceptionUtils.createWithCause(ExceptionUtils.java:67)
        at org.apache.velocity.util.ExceptionUtils.createRuntimeException(ExceptionUtils.java:45)
        at org.apache.velocity.runtime.log.Log4JLogChute.initAppender(Log4JLogChute.java:133)
        at org.apache.velocity.runtime.log.Log4JLogChute.init(Log4JLogChute.java:85)
        at org.apache.velocity.runtime.log.LogManager.createLogChute(LogManager.java:157)
        ... 39 more
Caused by: java.io.FileNotFoundException: velocity.log (Permission denied)
        at java.io.FileOutputStream.openAppend(Native Method)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:207)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
        at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
        at org.apache.log4j.RollingFileAppender.setFile(RollingFileAppender.java:207)
        at org.apache.log4j.FileAppender.<init>(FileAppender.java:110)
        at org.apache.log4j.RollingFileAppender.<init>(RollingFileAppender.java:79)
        at org.apache.velocity.runtime.log.Log4JLogChute.initAppender(Log4JLogChute.java:118)
        ... 41 more
Sep 25, 2012 9:30:27 AM org.apache.catalina.core.StandardContext startInternal
SEVERE: Error listenerStart
Sep 25, 2012 9:30:27 AM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [/dhis] startup failed due to previous errors
* INFO 2012-09-25 09:30:27,821 De-registering jdbc driver:
org.postgresql.Driver@22893e69 (StartupListener.java
[pool-2-thread-1])
Sep 25, 2012 9:30:27 AM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: The web application [/dhis] appears to have started a thread
named [Camel Thread 0 - ShutdownTask] but has failed to stop it. This
is very likely to create a memory leak.
Sep 25, 2012 9:30:27 AM org.apache.catalina.loader.WebappClassLoader
checkThreadLocalMapForLeaks
SEVERE: The web application [/dhis] created a ThreadLocal with key of
type [com.sun.xml.bind.v2.ClassFactory$1] (value
[com.sun.xml.bind.v2.ClassFactory$1@55ac8c3d]) and a value of type
[java.util.WeakHashMap] (value [{class
org.apache.camel.model.PackageScanDefinition=java.lang.ref.WeakReference@454e3bb0,
class org.apache.camel.spring.CamelProducerTemplateFactoryBean=java.lang.ref.WeakReference@1330c35c,
class java.util.ArrayList=java.lang.ref.WeakReference@6669d6db, class
org.apache.camel.spring.CamelContextFactoryBean=java.lang.ref.WeakReference@2e98f864,
class javax.xml.bind.annotation.adapters.CollapsedStringAdapter=java.lang.ref.WeakReference@3cdb8522}])
but failed to remove it when the web application was stopped. Threads
are going to be renewed over time to try and avoid a probable memory
leak.
Sep 25, 2012 9:30:27 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /var/lib/tomcat7/webapps/ROOT
Sep 25, 2012 9:30:28 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Sep 25, 2012 9:30:28 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 79479 ms

Might be an unintended consequence of a change I did lately. Just
reverted it, try again with latest 2.9.

Lars

Hi

Can you explain me how to disable data entry when data entry is complete. We want to block any data entry or editing in the system after a period is closed up.

Lungo

Hi Lungo,

go to "edit data set", there you can set number of "expiry days". This
means that the data set/form will be locked this number of days after
the end date of the reporting period.

If you later need to cater for exceptions then you can go to "lock
exceptions" in data admin module.

Lars

···

On Tue, Sep 25, 2012 at 4:08 PM, Juma Lungo <jlungo@yahoo.com> wrote:

Hi

Can you explain me how to disable data entry when data entry is complete. We
want to block any data entry or editing in the system after a period is
closed up.

Lungo

Thanks Lars

How can i block uploading of data (Data Import), just in case the user decide to upload instead

Lungo

···

From: Lars Helge Øverland larshelge@gmail.com
To: Juma Lungo jlungo@yahoo.com
Cc: DHIS 2 developers dhis2-devs@lists.launchpad.net
Sent: Tuesday, September 25, 2012 5:16 PM
Subject: Re: Disable Data Entry

Hi Lungo,

go to “edit data set”, there you can set number of “expiry days”. This
means that the data set/form will be locked this number of days after
the end date of the reporting period.

If you later need to cater for exceptions then you can go to “lock
exceptions” in data admin module.

Lars

On Tue, Sep 25, 2012 at 4:08 PM, Juma Lungo jlungo@yahoo.com wrote:

Hi

Can you explain me how to disable data entry when data entry is complete. We
want to block any data entry or editing in the system after a period is
closed up.

Lungo

Do not grant them the permission to do so.

Regards,
Jason

···

On Tue, Sep 25, 2012 at 4:25 PM, Juma Lungo <jlungo@yahoo.com> wrote:

Thanks Lars

How can i block uploading of data (Data Import), just in case the user
decide to upload instead

Lungo

________________________________
From: Lars Helge Øverland <larshelge@gmail.com>
To: Juma Lungo <jlungo@yahoo.com>
Cc: DHIS 2 developers <dhis2-devs@lists.launchpad.net>
Sent: Tuesday, September 25, 2012 5:16 PM
Subject: Re: Disable Data Entry

Hi Lungo,

go to "edit data set", there you can set number of "expiry days". This
means that the data set/form will be locked this number of days after
the end date of the reporting period.

If you later need to cater for exceptions then you can go to "lock
exceptions" in data admin module.

Lars

On Tue, Sep 25, 2012 at 4:08 PM, Juma Lungo <jlungo@yahoo.com> wrote:

Hi

Can you explain me how to disable data entry when data entry is complete.
We
want to block any data entry or editing in the system after a period is
closed up.

Lungo

_______________________________________________
Mailing list: DHIS 2 developers in Launchpad
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : DHIS 2 developers in Launchpad
More help : ListHelp - Launchpad Help

Jason
they users cannot live without importing data! an alternative means please

···

From: Jason Pickering jason.p.pickering@gmail.com
To: Juma Lungo jlungo@yahoo.com
Cc: Lars Helge Øverland larshelge@gmail.com; DHIS 2 developers dhis2-devs@lists.launchpad.net
Sent: Tuesday, September 25, 2012 5:29 PM
Subject: Re: [Dhis2-devs] Disable Data Entry

Do not grant them the permission to do so.

Regards,
Jason

On Tue, Sep 25, 2012 at 4:25 PM, Juma Lungo jlungo@yahoo.com wrote:

Thanks Lars

How can i block uploading of data (Data Import), just in case the user
decide to upload instead

Lungo


From: Lars Helge Øverland larshelge@gmail.com
To: Juma Lungo jlungo@yahoo.com
Cc: DHIS 2 developers dhis2-devs@lists.launchpad.net
Sent: Tuesday, September 25, 2012 5:16 PM
Subject: Re: Disable Data Entry

Hi Lungo,

go to “edit data set”, there you can set number of “expiry days”. This
means that the data set/form will be locked this number of days after
the end date of the reporting period.

If you later need to cater for exceptions then you can go to “lock
exceptions” in data admin module.

Lars

On Tue, Sep 25, 2012 at 4:08 PM, Juma Lungo jlungo@yahoo.com wrote:

Hi

Can you explain me how to disable data entry when data entry is complete.
We
want to block any data entry or editing in the system after a period is
closed up.

Lungo


Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp

We do not have that fine-grained control per-dataset through the Web
API as of now but we need to implement that soon.

Lars

···

On Tue, Sep 25, 2012 at 4:25 PM, Juma Lungo <jlungo@yahoo.com> wrote:

Thanks Lars

How can i block uploading of data (Data Import), just in case the user
decide to upload instead

Lungo

________________________________
From: Lars Helge Øverland <larshelge@gmail.com>
To: Juma Lungo <jlungo@yahoo.com>
Cc: DHIS 2 developers <dhis2-devs@lists.launchpad.net>
Sent: Tuesday, September 25, 2012 5:16 PM
Subject: Re: Disable Data Entry

Hi Lungo,

go to "edit data set", there you can set number of "expiry days". This
means that the data set/form will be locked this number of days after
the end date of the reporting period.

If you later need to cater for exceptions then you can go to "lock
exceptions" in data admin module.

Lars

On Tue, Sep 25, 2012 at 4:08 PM, Juma Lungo <jlungo@yahoo.com> wrote:

Hi

Can you explain me how to disable data entry when data entry is complete.
We
want to block any data entry or editing in the system after a period is
closed up.

Lungo

It is okay Lars

This feature is highly needed especially for those who are using DHIS2 as an accounting package, but i think is useful to many users.

···

From: Lars Helge Øverland larshelge@gmail.com
To: Juma Lungo jlungo@yahoo.com
Cc: DHIS 2 developers dhis2-devs@lists.launchpad.net
Sent: Tuesday, September 25, 2012 5:32 PM
Subject: Re: Disable Data Entry

We do not have that fine-grained control per-dataset through the Web
API as of now but we need to implement that soon.

Lars

On Tue, Sep 25, 2012 at 4:25 PM, Juma Lungo jlungo@yahoo.com wrote:

Thanks Lars

How can i block uploading of data (Data Import), just in case the user
decide to upload instead

Lungo


From: Lars Helge Øverland larshelge@gmail.com
To: Juma Lungo jlungo@yahoo.com
Cc: DHIS 2 developers dhis2-devs@lists.launchpad.net
Sent: Tuesday, September 25, 2012 5:16 PM
Subject: Re: Disable Data Entry

Hi Lungo,

go to “edit data set”, there you can set number of “expiry days”. This
means that the data set/form will be locked this number of days after
the end date of the reporting period.

If you later need to cater for exceptions then you can go to “lock
exceptions” in data admin module.

Lars

On Tue, Sep 25, 2012 at 4:08 PM, Juma Lungo jlungo@yahoo.com wrote:

Hi

Can you explain me how to disable data entry when data entry is complete.
We
want to block any data entry or editing in the system after a period is
closed up.

Lungo