I have enable the s3fs module and I have getting following warning message during drush clear cache:
is_dir(): Unable to find the wrapper "public" - did you forget to enable it when you configured PHP? file.inc
here the details(web-server Nginx and OS is Ubuntu):
ubuntu#ip-172-31-xx-xxx$ drush cc
Enter a number to choose which cache to clear.
[0] : Cancel
[1] : all
[2] : drush
[3] : theme-registry
[4] : menu
[5] : css-js
[6] : block
[7] : module-list
[8] : theme-list
[9] : registry
[10] : advagg
[11] : libraries
[12] : token
[13] : views
1
is_dir(): Unable to find the wrapper "public" - did you forget to enable it when you configured PHP? file.inc:2144 [warning]
is_dir(): Unable to find the wrapper "public" - did you forget to enable it when you configured PHP? file.inc:2144 [warning]
is_dir(): Unable to find the wrapper "public" - did you forget to enable it when you configured PHP? file.inc:2144 [warning]
is_dir(): Unable to find the wrapper "public" - did you forget to enable it when you configured PHP? file.inc:2144 [warning]
is_dir(): Unable to find the wrapper "public" - did you forget to enable it when you configured PHP? file.inc:439 [warning]
is_dir(): Unable to find the wrapper "public" - did you forget to enable it when you configured PHP? file.inc:439 [warning]
is_dir(): Unable to find the wrapper "public" - did you forget to enable it when you configured PHP? file.inc:439 [warning]
is_dir(): Unable to find the wrapper "public" - did you forget to enable it when you configured PHP? file.inc:439 [warning]
WD php: Error: Call to a member function getDirectoryPath() on boolean in image_menu() (line 83 of [error]
/xxxx/xxxx/public_html/modules/image/image.module).
This may not be the case for every instance of this error, but I was getting this when I was syncing a site from a production server to my local environment. Turned out it was my temporary file path being invalid causing the issue. Was able to fix it quickly via drush: drush vset file_temporary_path /tmp.
Related
BUILD FAILED in 2s
error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup.
Error: Command failed: gradlew.bat app:installDebug -PreactNativeDevServerPort=8081
FAILURE: Build failed with an exception.
What went wrong:
A problem occurred configuring root project 'Peace Garden'.
Could not determine the dependencies of null.
Could not resolve all task dependencies for configuration ':classpath'.
> Could not resolve com.facebook.react:react-native:+.
Required by:
project :
> No matching variant of com.facebook.react:react-native:0.71.0-rc.0 was found. The consumer was configured
to find a runtime of a library compatible with Java 11, packaged as a jar, and its dependencies declared externally,
as well as attribute 'org.gradle.plugin.api-version' with value '7.3.3'
I have changed some rights within a new core (solr 7.7.1) I am trying to configure. That has now led to failing to start the core on solr start. The rights look allright to me and everything else as well. Not different to other cores.
The error msg:
SolrCore Initialization Failures
test: org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: Could not load conf for core test: Error loading solr config from /var/solr/data/test/conf/solrconfig.xml
Please check your logs for more information
log:
core test is not available due to init failure: Could not load conf for core test: Error loading solr config from /var/solr/data/test/conf/solrconfig.xml
at org.apache.solr.core.CoreContainer.getCore(CoreContainer.java:1644)
The file itself:
ls -ls /var/solr/data/test/conf/solrconfig.xml
4 lrwxrwxrwx 1 solr solr 71 Mar 25 09:52 /var/solr/data/test/conf/solrconfig.xml -> /home/www/test/solrconfig.xml
Looks 1:1 with another core config. What am I missing?
Check, if the file /home/www/test/solrconfig.xml exits
Find out, under which user account solr is running. Use something like ps -efa | grep solr and check, if this user has access to /home/www/test/solrconfig.xml
If /var/solr/data/test/conf/solrconfig.xml and /home/www/test/solrconfig.xml resists at the same filesystem: try to use hardlinks instead of softlinks.
I'm trying to install hazelcast-all-3.6.5 version in Jboss Fuse 6.2.1 server (Fabric Managed). Upon installation it throws the following error.
Unable to update agent org.osgi.service.resolver.ResolutionException: Unable to resolve root: missing requirement [root]
osgi.identity; osgi.identity=appid1-hazelcast; type=karaf.feature; version=0
[caused by: Unable to resolve appid1-hazelcast/3.0.1.release: missing requirement [appid1-hazelcast/3.0.1.release]
osgi.identity; osgi.identity=com.hazelcast; type=osgi.bundle; version="[3.6.5,3.6.5]"; resolution:=mandatory
[caused by: Unable to resolve com.hazelcast/3.6.5: missing requirement [com.hazelcast/3.6.5]
osgi.wiring.package; filter:="(osgi.wiring.package=sun.misc)"]]
Tried installing fragment bundle to expose sun.misc package but got the following error "Error: Resource has no uri".
Fragment bundle : mvn:com.diffplug.osgi/com.diffplug.osgi.extension.sun.misc/0.0.0
2017-03-16 18:02:22,814 | INFO | 2.0.1-1-thread-1 | Agent | 72 - io.fabric8.fabric-agent - 1.2.0.redhat-621166 | null
2017-03-16 18:02:22,814 | ERROR | 2.0.1-1-thread-1 | DeploymentAgent | 72 - io.fabric8.fabric-agent - 1.2.0.redhat-621166 | Unable to update agent
java.lang.IllegalStateException: Resource has no uri
at io.fabric8.agent.service.Deployer.getBundleInputStream(Deployer.java:1466)[72:io.fabric8.fabric-agent:1.2.0.redhat-621166]
at io.fabric8.agent.service.Deployer.deploy(Deployer.java:812)[72:io.fabric8.fabric-agent:1.2.0.redhat-621166]
at io.fabric8.agent.service.Agent.provision(Agent.java:366)[72:io.fabric8.fabric-agent:1.2.0.redhat-621166]
at io.fabric8.agent.service.Agent.provision(Agent.java:199)[72:io.fabric8.fabric-agent:1.2.0.redhat-621166]
at io.fabric8.agent.DeploymentAgent.doUpdate(DeploymentAgent.java:733)[72:io.fabric8.fabric-agent:1.2.0.redhat-621166]
at io.fabric8.agent.DeploymentAgent$4.run(DeploymentAgent.java:289)[72:io.fabric8.fabric-agent:1.2.0.redhat-621166]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.0_55]
at java.util.concurrent.FutureTask.run(FutureTask.java:262)[:1.7.0_55]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_55]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_55]
at java.lang.Thread.run(Thread.java:745)[:1.7.0_55]
Note: The same approach works fine in Fuse 6.1.0 version (both standalone and fabric).
You need to activate access to sun.misc.Unsafe package in jboss. Normally the OSGi framework has some configuration where you can enable packages from the system classloader into bundles (boot class delegation). Not sure though how it exactly works in fabric8 but this older post fixed it in the past, guess the config is still the same: https://developer.jboss.org/message/884503#884503
Initially I have appended sun.misc package to "org.osgi.framework.system.packages.extra" property in etc/config.properties file, but this didn't solve the issue. (This should work 90% of the case) .
Later figured out that there was one another property named "org.osgi.framework.system.packages.extra" present in /etc/custom.properties file, adding sun.misc package to /etc/custom.properties file fixed the issue.
# Branding
org.osgi.framework.system.packages.extra = org.apache.karaf.branding,com.sun.xml.bind.v2.model.core,sun.misc
I'm using Worklight 6.2 server edition and I can't deploy a working runtime (of other environments) on my server.
I'm using webpshere liberty profile v8.5.5 and when I deploy the runtime via GUI it says success and on server.xml I can see the new configuration for the app.
However when I go to the worklightconsole I don't see my runtime to upload the app.
On messages.log there is a error regarding JMX connection.
The quoted error is
Failed to obtain JMX connection to access an MBean. There might be a JMX configuration error: No JMX connector is configured
I'm refering this because I've seen some post on SO saying that these issues might be connected. However I have the restConnector-1.0 on my WLP features.
Reference: No runtime on my Worklight 6.2 Console after installing analytics
On messages.log there is some other things that I found interesting, like the correct start of the runtime I've deployed
[11/12/14 5:50:45:177 CST] 00000012 com.worklight.server.bundle.project.JeeProjectActivator I FWLST0002I: ========= Project /HelloWorld started. The project WAR file version is 6.2.0.00.20140922-2259,running on server version 6.2.0.00.20140613-0730. [project HelloWorld]
and two erros while starting my server
[11/12/14 5:50:49:911 CST] 00000012 SystemErr R 24 WorklightPU WARN [Scheduled Executor-thread-1] openjpa.Runtime - An error occurred while registering a ClassTransformer with PersistenceUnitInfo: name 'WorklightPU', root URL [file:/opt/IBM/WebSphere/Liberty/usr/shared/resources/worklight/lib/worklight-jee-library.jar]. The error has been consumed. To see it, set your openjpa.Runtime log level to TRACE. Load-time class transformation will not be available.
Second error:
java.lang.RuntimeException: Timeout while waiting for the management service to start up
I don't know what these are but I think it might be related to my problem and this errors eventually appear when I start my server.
Does anyone have any tips for troubleshooting this issue?
Thanks in advance.
This is a known issue from Websphere.
There is a APAR to fix that, a workaround is to restart the server with the --clean option to force a refresh onto the shared libraries.
http://www-01.ibm.com/support/docview.wss?uid=swg1PI17830
I am configuring Tibco EMS 7.0 server on Solaris 10 from the default file based store to a Database Store (Oracle RAC). Starting the instance the log shows the following JVM error:
2014-09-18 14:34:36.729 Logging into file '/lcl/dev/logs/tibco/jmspm2.log'
2014-09-18 14:34:36.729 ERROR: Error Loading JVM: ld.so.1: tibemsd64: fatal: /lcl/dev /apps/tibco/components/eclipse/_jvm/lib/sparc/libjvm.so/lib/sparcv9/server/libjvm.so: Not a directory
I have installed hibernate 3.2.5.001 from Tibco that uses the Eclipse JVM and files. Also istalled the recommended instantclient_11_2 that includes ojdbc5.
Below is my modified tibemsd.conf with dbstore_classpath, dbstore_driver_name, dbstore_driver_dialect, jre_library as:
dbstore_classpath = /lcl/dev/apps/tibco/components/eclipse/plugins/com.tibco.tpcl.org.hibernate_3.2.5.001/hibernate3.jar;/lcl/dev/apps/tibco/ems/7.0/bin/dom4j-1.6.1.jar;/lcl/dev/apps/tibco/ems/7.0/bin/commons-collections-2.1.1.jar;/lcl/dev/apps/tibco/ems/7.0/bin/commons-logging-1.0.4.jar;/lcl/dev/apps/tibco/ems/7.0/bin/ehcache-1.2.3.jar;/lcl/dev/apps/tibco/jta.jar;/lcl/dev/apps/tibco/ems/7.0/bin/cglib-2.1.3.jar;/lcl/dev/apps/tibco/antlr-2.7.6.jar;/lcl/dev/apps/tibco/ems/7.0/bin/antlr-2.7.6.jar;/lcl/dev/apps/tibco/components/eclipse/plugins/com.tibco.tpcl.org.com.mchange.c3p0_0.9.1.001/c3p0-0.9.1.jar;/lcl/dev/apps/tibco//ems/7.0/bin/asm.jar;/lcl/dev/apps/tibco/asm-attrs.jar;/lcl/dev/apps/tibco;../db_components/instantclient_11_2/ojdbc5.jar
dbstore_driver_name = oracle.jdbc.driver.OracleDriver
dbstore_driver_dialect = org.hibernate.dialect.Oracle10gDialect
jre_library = /lcl/dev/apps/tibco/components/eclipse/_jvm/lib/sparc/libjvm.so
I get the same error when I installed jdk1.5.0_71 and attempted to call ./jdk1.5.0_71/jre/lib/sparc/libjvm.so
I get the same error when set jre_library to: /lcl/dev/apps/tibco/components/eclipse/_jvm/lib/sparc since it appears to be looking for a directory.
Questions:
Is the ld.so.1 libray required (can't find it)?
Any ideas how to resolve this error and configure Java?
Solved!
I installed Java 1.6 via jdk1.6.0_45 and it worked! Below are the JRE settings that were used.
# jre_library = "/lcl/dev/apps/tibco/jdk1.6.0_45/jre/lib/sparcv9/server/libjvm.so" # This also works
jre_library = "/lcl/dev/apps/tibco/jdk1.6.0_45/jre" # This path works too, more consise
jre_option = -Xmx256m