perfsonar-user - Re: [perfsonar-user] HTTP proxy error in central server
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Szymon Trocha <>
- To:
- Subject: Re: [perfsonar-user] HTTP proxy error in central server
- Date: Wed, 7 Sep 2016 10:41:56 +0200
- Ironport-phdr: 9a23:2TDEkhbaNQUrF3esldxKHmb/LSx+4OfEezUN459isYplN5qZpsuybnLW6fgltlLVR4KTs6sC0LWG9f27EjVdqb+681k8M7V0HycfjssXmwFySOWkMmbcaMDQUiohAc5ZX0Vk9XzoeWJcGcL5ekGA6ibqtW1aSV3DMl9tK/77AYnUht7yyvu/4bXSZRlFnjywfek0IRmr/ivLscxDuplzL6E3gifTpXBIcqwC3nF5IFWV2Qrm4cyw9bZm+iIWo/Uz8cdGF73+KfdrBYdEBSgrZjhmrPbgsgPOGFOC
- Organization: PCSS
W dniu 06.09.2016 o 18:49, Andrew Lake
pisze:
In maddash-server.out I'm getting this: ============= begin nested exception, level (3) =========== ERROR XBM0H: Directory /etc/httpd/conf.d/data/dashboard.db/maddash cannot be created. at org.apache.derby.iapi.error.StandardException.newException(Unknown Source) at org.apache.derby.impl.services.monitor.StorageFactoryService$9.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at org.apache.derby.impl.services.monitor.StorageFactoryService.createServiceRoot(Unknown Source) at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(Unknown Source) at org.apache.derby.impl.services.monitor.BaseMonitor.createPersistentService(Unknown Source) at org.apache.derby.iapi.services.monitor.Monitor.createPersistentService(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.createDatabase(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection30.<init>(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection40.<init>(Unknown Source) at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source) at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source) at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source) at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:119) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:143) at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:148) at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014) at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32) at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810) at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547) ============= end nested exception, level (3) =========== Cleanup action completed log4j:WARN No appenders could be found for logger (com.mchange.v2.resourcepool.BasicResourcePool). log4j:WARN Please initialize the log4j system properly. log4j:WARN No appenders could be found for logger (com.mchange.v2.resourcepool.BasicResourcePool). log4j:WARN Please initialize the log4j system properly. log4j:WARN No appenders could be found for logger (com.mchange.v2.resourcepool.BasicResourcePool). log4j:WARN Please initialize the log4j system properly. Initialization error: Connections could not be acquired from the underlying database! java.lang.RuntimeException: Connections could not be acquired from the underlying database! at net.es.maddash.MaDDashGlobals.<init>(MaDDashGlobals.java:213) at net.es.maddash.MaDDashGlobals.getInstance(MaDDashGlobals.java:484) at net.es.maddash.Invoker.main(Invoker.java:55) 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:606) at com.simontuffs.onejar.Boot.run(Boot.java:340) at com.simontuffs.onejar.Boot.main(Boot.java:166) [root@prinsepia11 maddash]# and in netlogger some messages too: level=ERROR ts=2016-09-06T13:34:45.924913Z event=maddash.init.end guid=e62d2b86-826a-45c7-8ded-83ccf8917c53 status=-1 msg="Connections could not be acquired from the underlying database!" level=INFO ts=2016-09-06T14:03:54.412516Z event=maddash.init.start guid=e0047493-dab3-4fbc-95da-692623a0a779 level=ERROR ts=2016-09-06T14:04:24.433540Z event=maddash.init.end guid=e0047493-dab3-4fbc-95da-692623a0a779 status=-1 msg="Connections could not be acquired from the underlying database!" -- Szymon Trocha Poznań Supercomputing & Networking Center Tel. +48 618582022 ::: http://noc.pcss.pl |
- [perfsonar-user] HTTP proxy error in central server, Szymon Trocha, 09/06/2016
- Re: [perfsonar-user] HTTP proxy error in central server, Andrew Lake, 09/06/2016
- Re: [perfsonar-user] HTTP proxy error in central server, Szymon Trocha, 09/07/2016
- Re: [perfsonar-user] HTTP proxy error in central server, Szymon Trocha, 09/07/2016
- Re: [perfsonar-user] HTTP proxy error in central server, Antoine Delvaux, 09/07/2016
- Re: [perfsonar-user] HTTP proxy error in central server, Szymon Trocha, 09/07/2016
- Re: [perfsonar-user] HTTP proxy error in central server, Antoine Delvaux, 09/07/2016
- Re: [perfsonar-user] HTTP proxy error in central server, Szymon Trocha, 09/07/2016
- Re: [perfsonar-user] HTTP proxy error in central server, Szymon Trocha, 09/07/2016
- Re: [perfsonar-user] HTTP proxy error in central server, Andrew Lake, 09/06/2016
Archive powered by MHonArc 2.6.19.