I have in my kibana directory a custom plugin "custom_plugin"
My impression from reading this portion of the elastic docs is that the directory needs to be zipped.
So based on that, I do:
zip -r custom_plugin.zip custom_plugin
Then, adhering to the elastic doc example, I run:
mkdir plugins
bin/kibana-plugin install file:///custom_plugin.zip -d plugins
I get the following output:
Warning: Using the -d, --plugin-dir option is deprecated, and is known to not work for all
plugins, including X-Pack.
Attempting to transfer from file:///custom_plugin.zip Error: ENOTFOUND
Attempting to transfer
from https://artifacts.elastic.co/downloads/kibana-plugins/file:///custom_plugin.zip/file:///custom_plugin.zip-6.7.2.zip
Plugin installation was unsuccessful due to error "No valid url
specified."
The command bin/kibana-plugin install file:///custom_plugin.zip will look for your file at the directory /custom_plugin.zip, so your root directory.
Try instead with an absolute path to your zip file as:
file://<absolute-path>/custom_plugin.zip
Related
I am setting up my first VIP theme on Ubuntu 14.04 LTS computer by following instructions at:
https://vip.wordpress.com/documentation/vip/dev-environment/ and
http://docs.chassis.io/en/latest/quickstart/#prerequisites
At this point I have:
- Virtual Box 5.1 installed
- Vagrant 1:1.9.4 installed
Before writing the steps in detail here is my current folder structure
/var/www/html
|-> thevp (Chassis installation)
|-> wp
|-> wp-content/themes/vip/plugins
| | |-> vip-init.php
| |-> vp-theme (custom theme)
|-> mu-plugins
Vagrant URL: vagrant.local
Admin URL: vagrant.local/wp/wp-admin
After installing above two I installed Chassis inside /var/www/html/thevp folder. This installed a folder called wp, which I believe the default WordPress installation. So now I have /var/www/html/thevp/wp (plus other folders and files).
The wp-content folder sits inside "wp" folder.
Next I installed VIP Plugins and Helpers from svn co https://vip-svn.wordpress.com/plugins/ wp-content/themes/vip/plugins inside /var/www/html/thevp/wp/wp-content/themes/vip/plugins.
Then I installed VIP mu-Plugins inside /var/www/html/thevp/wp/wp-content/mu-plugins
And finally, I cloned my VIP theme from Github inside /var/www/html/thevp/wp/wp-content/themes/vp-theme
After all installations and cloning I ran $vagrant up from within /var/www/html/thevp/, which provisioned my Chassis Box and presented with the URL http://vagrant.local/.
The above URL runs fine and opens default site with TwentySeventeen theme.
Under Admin > Themes I can see my own theme vp-theme present along with other default themes WordPress has installed.
But whenever I am trying to Activate this theme I am getting this error message:
Warning:
require_once(/vagrant/content/themes/vip/plugins/vip-init.php): failed
to open stream: No such file or directory in
/vagrant/wp/wp-content/themes/vip/yrc-wordpress-theme/functions.php on
line 9
Fatal error: require_once(): Failed opening required
'/vagrant/content/themes/vip/plugins/vip-init.php'
(include_path='.:/usr/share/php') in
/vagrant/wp/wp-content/themes/vip/yrc-wordpress-theme/functions.php on
line 9
Assuming that /var/www/htm/thevp is not being recognized as the correct path becausd wp-content folder actually resides under /var/www/html/thevp/wp and this should be root, I destroyed running instance of VirtualBox and ran $ vagrant up again but this time from inside /var/www/html/thevp/wp.
But I still get the same error. Cannot figure out how to resolve this problem.
This is my first time with VIP theme. Please help!
UPDATE:
I checked my theme's functions.php for the following line
require_once WP_CONTENT_DIR . '/themes/vip/plugins/vip-init.php';
which is there, but I have a feeling that WP_CONTENT_DIR is probably outputting wrong path for some reason as the error message says
require_once(/vagrant/content/themes/vip/plugins/vip-init.php)...
I don't find any folder /vagrant/content. Got completely stuck here as I have no idea what to do next!
After long research and googling I finally got this to work.
The main reason for the error to come up was the content folder defined in config.yaml file.
When Chassis installs, it creates a file called config.yaml in its root. This is the default settings in the file under "path" section.
# Base directory for reference. Relative to the Chassis directory.
base: .
# Where WordPress lives. Relative to the base directory.
wp: wp
# Content directory. Relative to the base directory.
content: content
First thing I did was changed content: content to content: wp/wp-content. Thing to notice here is Chassis creates the default WordPress installation under "wp" not under "Wordpress".
Second thing I needed to change was from multisite: No to multisite: Yes in the same file.
However, while booting Virtual machine I encountered the following error:
It appears your machine doesn't support NFS, or there is not an
adapter to enable NFS on this machine for Vagrant
That got fixed by installing NFS Common and NFS Kernel Server
$ sudo apt-get install nfs-common nfs-kernel-server
I encountered another error during VitualBox booting with vagrant. It asked me for my sudo password. But after supplying it the execution failed and I received the following message on console:
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mount -o 'vers=3,udp' 33.33.33.1:'/home/subrata/' /var/www
Stdout from the command: Stderr from the command: stdin: is not a tty
mount.nfs: requested NFS version or transport protocol is not
supported
To fix that I had to add the following lines in /etc/sudoers file.
vagrant ALL=(ALL) NOPASSWD:ALL
Defaults:vagrant !requiretty
Finally I am all set! $vagrant up has successfully booted my VM.
http://vagrant.local runs fine as well as now I am able to activate my own VIP theme for the first time :)
I was trying to setting up my AWS beanstalk by following the implementation guide provided by AWS.
But when I got to the "Launch an Elastic Beanstalk Environment" section, this message appeared which basically said the app is not created.
Here's the message:
[Instance: i-088472611e1ef4405] Command failed on instance. Return
code: 1 Output: ln: failed to create symbolic link
'wp-content/uploads': No such file or directory. container_command
2link in wordpress-beanstalk/.ebextensions/efs-mount.config failed.
For more detail, check /var/log/eb-activity.log using console or EB
CLI.
Does anyone have the same problem or know how to resolve this?
Try changing the efs-mount to read the following, the directory clearly doesn't exist so lets just create it.
container_commands:
1chown:
command: "chown webapp:webapp /wpfiles"
2create:
command: "sudo -u webapp mkdir -p wp-content/uploads"
3link:
command: "sudo -u webapp ln -s /wpfiles wp-content/uploads"
2create will create the directory owned by the webapp user and should let you continue.
I just faced the same issue. I am going to assume deploying via the AWS console. That is how I started.
STEP 1: I checked if there was an actual directory wp-content/uploads in wordpress-beanstalk and there was not. It might get created on the first WP upload So, I created the folder, rezipped the application, and deployed to Beanstalk via the AWS Console.
I still received the same error and moved on to step 2
STEP 2: Run EB DEPLOY from the command line
from my local wordpress-beanstalk directory
eb init
choose region (if you already created your app should be this region)
if you already created application choose that wordpress-beanstalk for example
eb use name of your environment
eb deploy
I am not certain that Step 1 is related to Step 2, but was able to successfully deploy facing the same issue using EB CLI.
This is the mounting error of EFS .
EB is using EFS storage to store the wordpress files .
Please check the no.7 in documentation .
"Modify the configuration files in the .ebextensions folder with the IDs of your default VPC and subnets, and your public IP address."
Please edit the efs-create.config file inside the .ebextension folder.
A bit late here so for anyone else having this issue, it's caused when that directory does not exist. Here are some reasons this might happen:
1). WP has not created it - Check manually that it exists.
2). .gitignore - When a .ebignore file is not present, EB uses your .gitignore instead. This can cause the directory to not be uploaded with the EB deploy command. If this is the case, make a .ebignore, EB will start ignoring the .gitignore
3). Document root - If you have modified the document root, to something like /src you have to modify the efs-mount.config file.
##############################################
#### Do not modify values below this line ####
##############################################
container_commands:
1chown:
command: "chown webapp:webapp /wpfiles"
2link:
command: "sudo -u webapp ln -s /wpfiles src/wp-content/uploads"
Even though the file mentions not to modify it, you have to add your document root path in the 2link entry. Change wp-content/uploads to src/wp-content/uploads (replace src with your document root)
Finally, I would not include a command to automatically make this directory, as that only puts a band-aid on the problem.
Hope this helps
I'm trying to install Grav on Heroku following the learn.getgrav.org docs.
I've got the web app deployed successfully, however it tells me to bin/grav install.
I do that and it gives me the following output:
ERROR Missing .dependencies file in user/ folder
I do not know what to do at this point as it's happened everytime I've installed Grav.
Hope this will be solved.
Sadly this problem is all too common when copying files :(
hidden (dotted) files are not always copied.
.dependencies
.htaccss
using ls -l -a in the folder where you extracted the files originally Dowloads/grav I could see the files that were not copied to fix it
cp .dependencies .htaccss /var/www/grav/
When I install GRAV on my server each time, I always copy the Zip file to the server, unzip it in place, then remove the zip file - using this method I have never had a problem with the installing of GRAV
HTH Rich
I am a Drupal newbie and trying to clone my site which is hosted on an Aegir server (using BOA). I ran 'Drupal generate-makefile' command in the working directory (the directory in which site is located) and the file did get generated - but it is not in the working directory. I also tried forcing a path using 'Drupal make-generate path/to/store/makefile/makefilename' but the command ran and ended with an error 'call to an undefined function drush_make_error()'. Any ideas where the file may be getting generated? Also, any tips on how I can force a path for .make file would be really helpful!
Maybe it depends on your Drush version, but with Drush 5.x the makefile is sent to stout.
This is how I use make-generate if I want my makefile written in /root/:
drush make-generate -r /path/of/my/drupal/installation > /root/drupal-org.make
I have installed elasticsearch with brew install elasticsearch. My plugins seem to reside in /usr/local/Cellar/elasticsearch/0.19.8/plugins. With cat $( which plugin ) I see a ES_HOME variable that contains the correct path.
Is there a way to ask elastic for ES_HOME or the plugins directory?
EDIT
What I am looking for is the directory used by the plugin executable to install the plugins when I do plugin -install something. I want to use that path in a script to fire up elastic search.
To find your elasticsearch home directory & install plugin(s) follow these steps below.
Locate your home directory ( Look for Settings -> Path -> Home for value )
$ curl "localhost:9200/_nodes/settings?pretty=true"
Goto Location (Example settings.path.home value: /usr/local/Cellar/elasticsearch/1.5.0)
$ cd /usr/local/Cellar/elasticsearch/1.5.0
Install Plugin (Example plugin: mobz/elasticsearch-head)
$ bin/plugin -install mobz/elasticsearch-head
I used this command:
$ curl "localhost:9200/_nodes?pretty=true&settings=true"
Check next setting: nodes - settings - path - plugins and use it as your plugins directory.
I had the same problem as you and I was able to locate the ES_HOME directory by following
#imotiv's suggestion.
Simply call PATH_TO_SERVER:9200/_cluster/nodes?settings=true&pretty=true
Therein you'll see the path.home entry. That is your ES working directory.
Once you locate your ElasticSearch home folder, in my case /usr/share/elasticsearch, cd down to that location.
Once there, you could simply run bin/plugin -install elasticsearch/elasticsearch-analysis-phonetic/1.3.0 and it will automatically do the rest for you.
Hope this helps.
Not totally sure what you are trying to achieve, but hopefully this will help. There are a couple of way to find the plugins directory for elasticsearch. You can set plugins: TRACE in the logging.yml file, it will cause elasticsearch to log the full path of plugins that it's loading. You can also execute
$ curl "localhost:9200/_cluster/nodes?settings=true&pretty=true"
to check the current settings. Elasticsearch is using location specified in the path.plugins settings to load plugins. If path.plugins is not set, it will use plugins directory in the directory specified by the path.home setting.