I'm having issues on MacOSX with a Packer Plugin that doesn't seem to be recognized. I've installed it using multiple methods. Including creating a ~/.packer.d/plugins directory and moving the plugin there and granting execute permissions.
This is the plugin:
packer-builder-vsphere
I'm running a very simple packer build just to test it and I get the error:
Failed to initialize build 'vsphere-iso': builder type not found: vsphere-iso
I've also tried adding it to the same directory as packer /usr/local/bin/ AND I've tried running it from the Current Running Directory as well. None of these methods are working and I'm not sure what I'm missing.
Any help would be appreciated.
Thanks!
The name of the plugin executable is wrong, it should be packer-builder-vsphere-iso and not include the version.
Related
I am trying to do a simple simulation in Cooja (literally the example on the Contiki website here).
However I have an error message linked to my #include "net/rime.h", Cooja outputs the following message while compiling:
fatal error: net/rime.h: No such file or directory
I thought that it came with Contiki when I've installed contiki-ng following the procedure on the official website. My quick fix was to download the file from the github repository and store it in my active directory. However I find it quite ugly, is there a way to install this library ? Because I haven't found a way yet.
Thanks a lot.
It's a question close to this one.
Which kind of method are you using to start Cooja? Directly on the SO? Over Docker?
I recommend you de Docker way, and remember to apply the command
git submodule update --init --recursive
after cloning the git repository.
Also, if you are using Docker, check if the binding of the Contiki folders between de Host and the Container are correctly made.
I am using custom Nagios plugins for the first time and am running into this error when I create a service for the plugin.
(No output on stdout) stderr: execvp(/usr/local/nagios/libexec/check_load.py, ...) failed. errno is 2: No such file or directory
The plugin works when I run it on the command line, however does not work when it runs within Nagios.
I followed these steps to get the plugin into Nagios
https://assets.nagios.com/downloads/nagiosxi/docs/Managing-Plugins-in-Nagios-XI.pdf
Here is what it looks like in the Nagios UI
The plugin is in the correct path: /usr/local/nagios/libexec and the resource.cfg file has the same path within it.
I tried two separate plugins, both which work on the command line, and the result is the same error.
The error indicates the file location is incorrect, however the plugin is in the specified directory and runs with no errors within that directory.
I am totally stumped and appreciate any help.
For anyone reading this, I solved the problem.
The first time I added the plugin, I forgot to add the python extension. When I updated the already created plugin, Nagios still threw the error.
Once I completely deleted the plugin and re-created it the 'file not found', error went away.
I faced a similar issue when I was trying to add a custom plugin ( I had custom plugins in ruby and python ).
The issue was the missing shebang line at the start of the script (which determines the script's ability to be executed like a standalone executable).
For example, if you have a python plugin custom-plugin.py then make sure this script has shebang at the start of script #!/usr/bin/env python3. Also if you have other scripts (ruby, bash etc.) make sure to add the appropriate path at the start of your scripts.
Also, check the path for plugins Nagios version. For my setup path was /usr/local/nagios/libexec/ and make sure your custom plugin is executable and has correct ownership permissions.
Sample custom template I used :
define command {
command_name check_switch_health
command_line /usr/local/nagios/libexec/check_snmp.rb --host $HOSTADDRESS$ --model "$ARG1$" --community "$ARG2$"
}
The above workaround worked for me.
I am trying to create a local development environment on a Windows machine using Xampp. Xampp has been setup correctly and I am able to access localhost, locahost/phpmyadmin and a virtual host I created domain.local. This Virtual Host is a CakePHP application that I had been running on a Linux Box (nginx). I use that code to setup the site, but when I try to run
php composer.phar update
to have composer download all dependencies, I get the following error:
Fatal error: Class 'Cake\Composer\Installer\PluginInstaller' not found in
phar://C:/Users/admin/Documents/Sites/domain.local/website/composer.phar/src/Composer/Plugin/PluginManager.php
on line 244
I have tried a bunch of things without success.
Also to note php composer.phar self-update, runs without issue.
Not sure what to do at this point. Any help is appreciated.
After more tryouts, I finally decided to delete the vendor folder and surprisingly it fixed my issue. Composer downloaded all dependencies and everything works as expected.
Greetings,
I am trying to start a scala/liftweb project for deployment on Google App Engine. To do this, i need to package it up as a .war using maven.
However, whenever I run the 'mvn' command, I am met with:
Error opening zip file or JAR manifest missing : /Applications/JRebel/jrebel.jar
Error occurred during initialization of VM
agent library failed to init: instrument
Is there something wrong with my maven or do I need Jrebel? I see jrebel is not free which is why I am so surprised.
thanks!
No, JRebel is definitely not required to run Maven.
As Matt mentioned, JRebel is not required to run Maven. However, ZeroTurnaround does offer a free version that works with Scala. You can get it here:
http://sales.zeroturnaround.com/
As for your error - it indicates you are trying to start the JVM as though you are using JRebel. What is the full Maven command you are running? What is in your MAVEN_OPTS environment variable? If either of them contain something like -noverify -javaagent:/Applications/JRebel/jrebel.jar, then that's your problem.
One of the reason of the problem is a blank in the path of jrebel.jar
Make sure that there is no blank in the path like in "Program Files"
I am unable to build my Web Application (not Web Site) in our build environement. We use DMAKE in our build environment (this unfortunately is non negotiable, therefore using MSBUILD is not permitted ) and when invoking the asp.net precompiler through
C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_compiler -d -nologo -p Site -f -fixednames -errorstack -v / Debug
We get the following error
error ASPPARSE: Could not load type 'X.Y.Admin.Site.Global
If I compile from the ide it is successful. If i then compile with aspnet_compilier it is successful. So i only get a successful compile with aspnet_compiler when the target dll i am trying to compile is in the bin of the web application i am compiling.
I keep running into postings that talk about solutions using MSBUILD which unfortunately I cant try.
Any help would be appreciated
We had the same problem on our web application:
error ASPPARSE: Could not load type '...'
The problem was that we had the file on disk (on the project folder) but it wasn't included in our application project (in the .csproj file). We solved the problem by including the file in the project :)
I ran into a similar problem using NANT. The trick was to compile the web applications code files into a dll then include that when using aspnet_compiler.
use the command line compiler,either csc.exe (c#) or vbc.exe (visual basic), to compile your web application with an output of type library. This will create a dll that you can use in your aspnet_compiler task
Have you tried specifying the path using -p? Sounds to me like it can't find that type / assembly.
http://msdn.microsoft.com/en-us/library/ms229863(VS.80).aspx
For web applications, you have to build the .vb files into a dll and put that in the bin folder before you run the aspnet compiler. Check the output window in visual studio and you'll see the command line for the VB compiler. Run that first before you run the aspnet compiler, and the asp pages should be able to find the missing types.
This problem was resolved for me by simply deleting all bin and obj folders. Seems like they were in a bad state somehow. I also deleted the the .sou file, but I don't think that was the issue.
I received the same problem.
I fixed it by copying my webapp's DLL from the OBJ/DEBUG folder to the BIN folder.
I just had this error and found 2 ways to fix it, either:
Change the Codebehind attribute in the global.asax file to CodeFile and add "partial" to the class declaration
In the deployment project's property pages, set "Version output assemblies" and provide a version number
I don't really know why either worked, but it did.
solution :
-p Site path must have the directory path of .csproj file location.
ex :-
aspnet_compiler -p D:\Projects\MGM\mgm\mgm -v / D:\Projects\MGM-deploy\mgm_compiled