Error while installing camel-jetty feature in Fuse ESB - apache
I am trying to configure Fuse ESB on my Windows 7 machine. Here are the configs.
Configuration
JRE 1.6.0_30
MS VC++ Redistributable - x86 9.0.30729.17
JAVA_HOME set to "C:\Program Files\Java\jre6"
Apache ServiceMix 4.4.1-fuse-02-02
After starting the ServiceMix console, I am trying to install camel-jetty using the following command.
features:install camel-jetty
Which fails with the following message.
Error executing command: URL [mvn:org.apache.camel/camel-http/2.8.0-fuse-02-02]
could not be resolved.
Full log message is as follows.
12:37:45,299 | INFO | l Console Thread | FeaturesServiceImpl | 39 - org.apache.karaf.features.core - 2.2.2.fuse-03-02 | Installing feature camel-jetty 2.8.0-fuse-02-02
12:37:45,299 | INFO | l Console Thread | FeaturesServiceImpl | 39 - org.apache.karaf.features.core - 2.2.2.fuse-03-02 | Installing feature jetty 7.4.5.fuse20111017
12:37:45,299 | INFO | l Console Thread | FeaturesServiceImpl | 39 - org.apache.karaf.features.core - 2.2.2.fuse-03-02 | Installing feature camel-core 2.8.0-fuse-02-02
12:37:45,299 | INFO | l Console Thread | FeaturesServiceImpl | 39 - org.apache.karaf.features.core - 2.2.2.fuse-03-02 | Installing feature camel-http 2.8.0-fuse-02-02
12:37:45,299 | INFO | l Console Thread | FeaturesServiceImpl | 39 - org.apache.karaf.features.core - 2.2.2.fuse-03-02 | Installing feature camel-core 2.8.0-fuse-02-02
12:37:58,718 | INFO | l Console Thread | Console | 32 - org.apache.karaf.shell.console - 2.2.2.fuse-03-02 | Exception caught while executing command
java.lang.RuntimeException: URL [mvn:org.apache.camel/camel-http/2.8.0-fuse-02-02] could not be resolved.
at org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:195)[2:org.ops4j.pax.url.mvn:1.2.6.fuse-01]
at org.apache.felix.bundlerepository.impl.FileUtil.openURL(FileUtil.java:203)[6:org.apache.felix.bundlerepository:1.6.4]
at org.apache.felix.bundlerepository.impl.FileUtil.openURL(FileUtil.java:196)[6:org.apache.felix.bundlerepository:1.6.4]
at org.apache.felix.bundlerepository.impl.DataModelHelperImpl$2.loadEntry(DataModelHelperImpl.java:452)[6:org.apache.felix.bundlerepository:1.6.4]
at org.apache.felix.bundlerepository.impl.DataModelHelperImpl$2.<init>(DataModelHelperImpl.java:411)[6:org.apache.felix.bundlerepository:1.6.4]
at org.apache.felix.bundlerepository.impl.DataModelHelperImpl.createResource(DataModelHelperImpl.java:404)[6:org.apache.felix.bundlerepository:1.6.4]
at org.apache.karaf.features.obr.internal.ObrResolver.resolve(ObrResolver.java:75)[28:org.apache.karaf.features.obr:2.2.2.fuse-03-02]
at org.apache.karaf.features.internal.FeaturesServiceImpl.resolve(FeaturesServiceImpl.java:505)[39:org.apache.karaf.features.core:2.2.2.fuse-03-02]
at org.apache.karaf.features.internal.FeaturesServiceImpl.doInstallFeature(FeaturesServiceImpl.java:474)[39:org.apache.karaf.features.core:2.2.2.fuse-03-02]
at org.apache.karaf.features.internal.FeaturesServiceImpl.doInstallFeature(FeaturesServiceImpl.java:453)[39:org.apache.karaf.features.core:2.2.2.fuse-03-02]
at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:292)[39:org.apache.karaf.features.core:2.2.2.fuse-03-02]
at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:280)[39:org.apache.karaf.features.core:2.2.2.fuse-03-02]
at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:276)[39:org.apache.karaf.features.core:2.2.2.fuse-03-02]
at org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:62)[17:org.apache.karaf.features.command:2.2.2.fuse-03-02]
at org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:39)[17:org.apache.karaf.features.command:2.2.2.fuse-03-02]
at org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:38)[32:org.apache.karaf.shell.console:2.2.2.fuse-03-02]
at org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)[32:org.apache.karaf.shell.console:2.2.2.fuse-03-02]
at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[32:org.apache.karaf.shell.console:2.2.2.fuse-03-02]
at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474)[32:org.apache.karaf.shell.console:2.2.2.fuse-03-02]
at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)[32:org.apache.karaf.shell.console:2.2.2.fuse-03-02]
at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[32:org.apache.karaf.shell.console:2.2.2.fuse-03-02]
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[32:org.apache.karaf.shell.console:2.2.2.fuse-03-02]
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[32:org.apache.karaf.shell.console:2.2.2.fuse-03-02]
at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)[32:org.apache.karaf.shell.console:2.2.2.fuse-03-02]
at org.apache.karaf.shell.console.jline.Console.run(Console.java:240)[32:org.apache.karaf.shell.console:2.2.2.fuse-03-02]
at java.lang.Thread.run(Unknown Source)[:1.6.0_30]
Can anybody please help me out here?
The org.ops4j.opx.url.mvn.cfg file contents are as follows
################################################################################
#
# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements. See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
################################################################################
#
# If set to true, the following property will not allow any certificate to be used
# when accessing maven repositories through SSL
#
#org.ops4j.pax.url.mvn.certificateCheck=
#
# Path to the local maven settings file.
# The repositories defined in this file will be automatically added to the list
# of default repositories if the 'org.ops4j.pax.url.mvn.repositories' property
# below is not set.
# The following locations are checked for the existence of the settings.xml file
# * 1. looks for the specified url
# * 2. if not found looks for ${user.home}/.m2/settings.xml
# * 3. if not found looks for ${maven.home}/conf/settings.xml
# * 4. if not found looks for ${M2_HOME}/conf/settings.xml
#
#org.ops4j.pax.url.mvn.settings=
#
# Path to the local maven repository which is used to avoid downloading
# artifacts when they already exist locally.
# The value of this property will be extracted from the settings.xml file
# above, or defaulted to:
# System.getProperty( "user.home" ) + "/.m2/repository"
#
#org.ops4j.pax.url.mvn.localRepository=
#
# Default this to false. It's just weird to use undocumented repos
#
org.ops4j.pax.url.mvn.useFallbackRepositories=false
#
# Uncomment if you are behind a web proxy. PAX URL will use the proxy settings
# from the Maven conf/settings.xml file
#
# org.ops4j.pax.url.mvn.proxySupport=true
#
# Disable aether support by default. This ensure that the defaultRepositories
# below will be used
#
org.ops4j.pax.url.mvn.disableAether=true
#
# Comma separated list of repositories scanned when resolving an artifact.
# Those repositories will be checked before iterating through the
# below list of repositories and even before the local repository
# A repository url can be appended with zero or more of the following flags:
# #snapshots : the repository contains snaphots
# #noreleases : the repository does not contain any released artifacts
#
# The following property value will add the system folder as a repo.
#
org.ops4j.pax.url.mvn.defaultRepositories=file:${karaf.home}/${karaf.default.repository}#snapshots,\
file:${karaf.home}/local-repo#snapshots
#
# Comma separated list of repositories scanned when resolving an artifact.
# The default list includes the following repositories:
# http://repo1.maven.org/maven2
# http://repository.apache.org/content/groups/snapshots-group
# http://svn.apache.org/repos/asf/servicemix/m2-repo
# http://repository.springsource.com/maven/bundles/release
# http://repository.springsource.com/maven/bundles/external
# To add repositories to the default ones, prepend '+' to the list of repositories
# to add.
# A repository url can be appended with zero or more of the following flags:
# #snapshots : the repository contains snaphots
# #noreleases : the repository does not contain any released artifacts
#
org.ops4j.pax.url.mvn.repositories= \
http://repo1.maven.org/maven2, \
http://repo.fusesource.com/nexus/content/repositories/releases, \
http://repo.fusesource.com/nexus/content/repositories/snapshots#snapshots#noreleases, \
http://repository.apache.org/content/groups/snapshots-group#snapshots#noreleases, \
http://svn.apache.org/repos/asf/servicemix/m2-repo, \
http://repository.springsource.com/maven/bundles/release, \
http://repository.springsource.com/maven/bundles/external
This error means Fuse ESB could not found the camel-http artifact from any repository available.
Fuse search in its local repository first and then on configured remote maven repositories.
All the configuration is done in <%Fuse Install dir%>\etc\org.ops4j.pax.url.mvn.cfg
See http://fusesource.com/docs/esb/4.4/esb_deploy_osgi/Locate-RunTime.html for more details about how to configure it properly.
Related
Accessing agent computer in azure devops
I am new in azure devops services, and i am trying to run a pipeline that process an asp.net core application. I have a task for restoring the project dependencies. Its code is dotnet Restore . The piepeline fail on that command with this message : 1:5>C:\Program Files\dotnet\sdk\5.0.410\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.TargetFrameworkInference.targets(141,5): error NETSDK1045: The current .NET SDK does not support targeting .NET 6.0. Either target .NET 5.0 or lower, or use a version of the .NET SDK that supports .NET 6.0. [D:\a\1\s\AspNetProjectOnDocker.csproj] Done executing task "NETSdkError" -- FAILED. 1:5>Done building target "_CheckForUnsupportedNETCoreVersion" in project "AspNetProjectOnDocker.csproj" -- FAILED. 1:5>Done Building Project "D:\a\1\s\AspNetProjectOnDocker.csproj" (_GenerateRestoreGraphProjectEntry target(s)) -- FAILED. 1>Done executing task "MSBuild" -- FAILED. 1>Done building target "_GenerateRestoreGraph" in project "AspNetProjectOnDocker.csproj" -- FAILED. 1>Done Building Project "D:\a\1\s\AspNetProjectOnDocker.csproj" (Restore target(s)) -- FAILED. AspNetProjectOnDocker is the name of my .net project My Questions : How to access to the folder : C:\Program Files\dotnet\sdk\5.0.410\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.TargetFrameworkInference.targets specified in the error message above. Thanks.
My Questions : How to access to the folder : C:\Program Files\dotnet\sdk\5.0.410\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.TargetFrameworkInference.targets specified in the error message above. Answer to your question: This is not a folder, it is a file. You can access it via the following YAML pipeline definition. trigger: - none pool: vmImage: windows-2019 steps: - script: | echo Check target file C: cd C:\Program Files\dotnet\sdk\5.0.410\Sdks\Microsoft.NET.Sdk\targets more Microsoft.NET.TargetFrameworkInference.targets displayName: 'Check target file' # if you encounter some issue such as can't find directory, you can use the following method to check what happens. # - script: | # echo Check target file step by step # dir # C: # dir # cd Program Files # dir # cd dotnet # dir # cd sdk # dir # cd 5.0.410 # dir # cd Sdks # dir # cd Microsoft.NET.Sdk # dir # cd targets # dir # more Microsoft.NET.TargetFrameworkInference.targets # displayName: 'Check target file step by step' Successfully get the file content:
How to link libraries in cmakelists.txt
I am mainly using ROS which is cmake based, where I want to link a library that I compiled previously and copied the .so and .a file to /usr/lib and .h to /usr/include. When I compile it with gcc, there is no problem with: gcc -o test test.c -lpynq -lcma -lpthread. How can I link those libraries in the cmakelist.txt? Thank you for the help. EDIT: Following JohnFilleau and the answer from ChrisZZ, this is my CMakeLists.txt: cmake_minimum_required(VERSION 3.0.2) project(proof_of_concept_string_ips) ## Compile as C++11, supported in ROS Kinetic and newer # add_compile_options(-std=c++11) ## Find catkin macros and libraries ## if COMPONENTS list like find_package(catkin REQUIRED COMPONENTS xyz) ## is used, also find other catkin packages find_package(catkin REQUIRED COMPONENTS roscpp std_msgs ) ## System dependencies are found with CMake's conventions # find_package(Boost REQUIRED COMPONENTS system) ## Uncomment this if the package has a setup.py. This macro ensures ## modules and global scripts declared therein get installed ## See http://ros.org/doc/api/catkin/html/user_guide/setup_dot_py.html # catkin_python_setup() ################################################ ## Declare ROS messages, services and actions ## ################################################ ## To declare and build messages, services or actions from within this ## package, follow these steps: ## * Let MSG_DEP_SET be the set of packages whose message types you use in ## your messages/services/actions (e.g. std_msgs, actionlib_msgs, ...). ## * In the file package.xml: ## * add a build_depend tag for "message_generation" ## * add a build_depend and a exec_depend tag for each package in MSG_DEP_SET ## * If MSG_DEP_SET isn't empty the following dependency has been pulled in ## but can be declared for certainty nonetheless: ## * add a exec_depend tag for "message_runtime" ## * In this file (CMakeLists.txt): ## * add "message_generation" and every package in MSG_DEP_SET to ## find_package(catkin REQUIRED COMPONENTS ...) ## * add "message_runtime" and every package in MSG_DEP_SET to ## catkin_package(CATKIN_DEPENDS ...) ## * uncomment the add_*_files sections below as needed ## and list every .msg/.srv/.action file to be processed ## * uncomment the generate_messages entry below ## * add every package in MSG_DEP_SET to generate_messages(DEPENDENCIES ...) ## Generate messages in the 'msg' folder # add_message_files( # FILES # Message1.msg # Message2.msg # ) ## Generate services in the 'srv' folder # add_service_files( # FILES # Service1.srv # Service2.srv # ) ## Generate actions in the 'action' folder # add_action_files( # FILES # Action1.action # Action2.action # ) ## Generate added messages and services with any dependencies listed here # generate_messages( # DEPENDENCIES # std_msgs # ) ################################################ ## Declare ROS dynamic reconfigure parameters ## ################################################ ## To declare and build dynamic reconfigure parameters within this ## package, follow these steps: ## * In the file package.xml: ## * add a build_depend and a exec_depend tag for "dynamic_reconfigure" ## * In this file (CMakeLists.txt): ## * add "dynamic_reconfigure" to ## find_package(catkin REQUIRED COMPONENTS ...) ## * uncomment the "generate_dynamic_reconfigure_options" section below ## and list every .cfg file to be processed ## Generate dynamic reconfigure parameters in the 'cfg' folder # generate_dynamic_reconfigure_options( # cfg/DynReconf1.cfg # cfg/DynReconf2.cfg # ) ################################### ## catkin specific configuration ## ################################### ## The catkin_package macro generates cmake config files for your package ## Declare things to be passed to dependent projects ## INCLUDE_DIRS: uncomment this if your package contains header files ## LIBRARIES: libraries you create in this project that dependent projects also need ## CATKIN_DEPENDS: catkin_packages dependent projects also need ## DEPENDS: system dependencies of this project that dependent projects also need catkin_package( # INCLUDE_DIRS include # LIBRARIES proof_of_concept_string_ips # CATKIN_DEPENDS roscpp std_msgs # DEPENDS system_lib ) ########### ## Build ## ########### ## Specify additional locations of header files ## Your package locations should be listed before other locations include_directories( # include ${catkin_INCLUDE_DIRS} ) ## Declare a C++ library # add_library(${PROJECT_NAME} # src/${PROJECT_NAME}/proof_of_concept_string_ips.cpp # ) ## Add cmake target dependencies of the library ## as an example, code may need to be generated before libraries ## either from message generation or dynamic reconfigure # add_dependencies(${PROJECT_NAME} ${${PROJECT_NAME}_EXPORTED_TARGETS} ${catkin_EXPORTED_TARGETS}) ## Declare a C++ executable ## With catkin_make all packages are built within a single CMake context ## The recommended prefix ensures that target names across packages don't collide # add_executable(${PROJECT_NAME}_node src/proof_of_concept_string_ips_node.cpp) ## Rename C++ executable without prefix ## The above recommended prefix causes long target names, the following renames the ## target back to the shorter version for ease of user use ## e.g. "rosrun someones_pkg node" instead of "rosrun someones_pkg someones_pkg_node" # set_target_properties(${PROJECT_NAME}_node PROPERTIES OUTPUT_NAME node PREFIX "") ## Add cmake target dependencies of the executable ## same as for the library above # add_dependencies(${PROJECT_NAME}_node ${${PROJECT_NAME}_EXPORTED_TARGETS} ${catkin_EXPORTED_TARGETS}) ## Specify libraries to link a library or executable target against # target_link_libraries(${PROJECT_NAME}_node # ${catkin_LIBRARIES} # ) ############# ## Install ## ############# # all install targets should use catkin DESTINATION variables # See http://ros.org/doc/api/catkin/html/adv_user_guide/variables.html ## Mark executable scripts (Python etc.) for installation ## in contrast to setup.py, you can choose the destination # catkin_install_python(PROGRAMS # scripts/my_python_script # DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION} # ) ## Mark executables for installation ## See http://docs.ros.org/melodic/api/catkin/html/howto/format1/building_executables.html # install(TARGETS ${PROJECT_NAME}_node # RUNTIME DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION} # ) ## Mark libraries for installation ## See http://docs.ros.org/melodic/api/catkin/html/howto/format1/building_libraries.html # install(TARGETS ${PROJECT_NAME} # ARCHIVE DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION} # LIBRARY DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION} # RUNTIME DESTINATION ${CATKIN_GLOBAL_BIN_DESTINATION} # ) ## Mark cpp header files for installation # install(DIRECTORY include/${PROJECT_NAME}/ # DESTINATION ${CATKIN_PACKAGE_INCLUDE_DESTINATION} # FILES_MATCHING PATTERN "*.h" # PATTERN ".svn" EXCLUDE # ) ## Mark other files for installation (e.g. launch and bag files, etc.) # install(FILES # # myfile1 # # myfile2 # DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION} # ) ############# ## Testing ## ############# ## Add gtest based cpp test target and link libraries # catkin_add_gtest(${PROJECT_NAME}-test test/test_proof_of_concept_string_ips.cpp) # if(TARGET ${PROJECT_NAME}-test) # target_link_libraries(${PROJECT_NAME}-test ${PROJECT_NAME}) # endif() ## Add folders to be run by python nosetests # catkin_add_nosetests(test) add_executable(pc_pub_string src/pc_pub_string.cpp) target_link_libraries(pc_pub_string ${catkin_LIBRARIES}) #add_dependencies(pc_pub_string0 proof_of_concept_string_ips_generate_messages_cpp) add_executable(arm_to_fpga src/arm_to_fpga.cpp) target_link_libraries(arm_to_fpga ${catkin_LIBRARIES}) # target_link_libraries(arm_to_fpga ${catkin_LIBRARIES}) /usr/lib/libpynq.so) #add_dependencies(arm_to_fpga proof_of_concept_generate_messages_cpp) # add_executable(pynq_test_api src/pynq_test_api.cpp) # target_link_libraries(pynq_test_api ${catkin_LIBRARIES}) set(pynq_lib "/usr/lib/libpynq.so") set(cma_lib "/usr/lib/libcma.so") add_executable(pynq_test_api src/pynq_test_api.cpp) target_link_libraries(pynq_test_api PUBLIC ${catkin_LIBRARIES} ${pynq_lib} ${cma_lib} pthread ) target_include_directories(pynq_test_api PUBLIC "/usr/include" ) And the error: CMakeFiles/pynq_test_api.dir/src/pynq_test_api.cpp.o: In function `main': pynq_test_api.cpp:(.text+0xba): undefined reference to `PYNQ_allocatedSharedMemory(shared_memory_state_struct*, unsigned int, int)' pynq_test_api.cpp:(.text+0xc8): undefined reference to `PYNQ_allocatedSharedMemory(shared_memory_state_struct*, unsigned int, int)' collect2: error: ld returned 1 exit status proof_of_concept_string_ips/CMakeFiles/pynq_test_api.dir/build.make:114: recipe for target '/home/xilinx/fpga_ros_scheduler/catkin_ws/devel/lib/proof_of_concept_string_ips/pynq_test_api' failed make[2]: *** [/home/xilinx/fpga_ros_scheduler/catkin_ws/devel/lib/proof_of_concept_string_ips/pynq_test_api] Error 1 CMakeFiles/Makefile2:449: recipe for target 'proof_of_concept_string_ips/CMakeFiles/pynq_test_api.dir/all' failed make[1]: *** [proof_of_concept_string_ips/CMakeFiles/pynq_test_api.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs....
The quick-but-not-elegant solution: cmake_minimum_required(VERSION 3.20) # I like newer version project(my_project) set(pynq_lib "/usr/lib/libpynq.a") # the full path. if postfix is `.so`, change it set(cma_lib "/usr/lib/libcma.a") # the full path. change if needed. add_executable(test_app test.c) target_link_libraries(test_app PUBLIC ${pynq_lib} ${cma_lib} pthread ) target_include_directories(test_app PUBLIC "/usr/include" ) The elegant way: as JohnFilleau suggested, suppose we generate pynq and cma libraries via CMake, then we treat them as "packages", and we "find package and link package", with commands like find_package() for external installed packages, or just use target_link_libraries() if build from same CMake based project.
cmake not moving targets to install directory
My project is structured as follows ProjDir | - CMakeLists.txt | - SubDir1 | | - CMakeLists.txt | | - src | | - inc | - SubDir2 | | - CMakeLists.txt | | - src | | - inc I have targets in each subdirectory and the subdirectories are included in the main CMakeLists.txt as follows. add_subdirectory(${CMAKE_SOURCE_DIR}/SubDir1) add_subdirectory(${CMAKE_SOURCE_DIR}/SubDir2) My targets in each subdirectory are installed with the cmake function install. These commands are in the CMakeLists.txt of respective subdirectories and are specified per-target (see this post). install(TARGETS exe1 DESTINATION ${CMAKE_INSTALL_PREFIX}/bin CONFIGURATIONS Release) While I'm able to successfully compile, the install command doesn't move the binaries to ${CMAKE_INSTALL_PREFIX}/bin but rather finishes after generated the output: Install the project... -- Install configuration: "" How could I resolve this?
On Linux, default build configuration is empty: neither debug, nor release, etc. It can be easily found from the CMake output: -- Install configuration: "" Because your install command is "tagged" with Release configuration, it is not triggered by default (with empty configuration).
Rabbitmq crash when boot failed
I meet a problem when booting rabbitmq which is driving me crazy... Env:redhat4 erlang version:R16B03 installed from source code rabbitmq version:rabbitmq-server-3.6.1 from source code when I ran 'rabbitmq-server start' command, it gave me some error information, then I ran that again it showed: RabbitMQ 3.6.1. Copyright (C) 2007-2016 Pivotal Software, Inc. ## ## Licensed under the MPL. See http://www.rabbitmq.com/ ## ## ########## Logs: /var/log/rabbitmq/rabbit#bogon.log ###### ## /var/log/rabbitmq/rabbit#bogon-sasl.log ########## Starting broker... And it stucked there, I thought may be it had started, so I ran './rabbitmq-plugins enable rabbitmq_management' to enable web plugins, but I got: The following plugins have been enabled: mochiweb webmachine rabbitmq_web_dispatch amqp_client rabbitmq_management_agent rabbitmq_management Applying plugin configuration to rabbit#bogon... failed. Error: {undef,[{crypto,module_info,[attributes],[]}, {rabbit_misc,module_attributes,1, [{file,"src/rabbit_misc.erl"},{line,805}]}, {rabbit_misc,'-all_module_attributes/1-fun-0-',3, [{file,"src/rabbit_misc.erl"},{line,825}]}, {lists,foldl,3,[{file,"lists.erl"},{line,1248}]}, {rabbit_boot_steps,find_steps,1, [{file,"src/rabbit_boot_steps.erl"}, {line,40}]}, {rabbit_boot_steps,run_boot_steps,1, [{file,"src/rabbit_boot_steps.erl"}, {line,26}]}, {rabbit,start_apps,1,[{file,"src/rabbit.erl"},{line,343}]}, {rabbit_plugins,ensure,1, [{file,"src/rabbit_plugins.erl"},{line,52}]}]} I don't know why... so I stopped the rabbitmq server and started it again, and it gave me this: RabbitMQ 3.6.1. Copyright (C) 2007-2016 Pivotal Software, Inc. ## ## Licensed under the MPL. See http://www.rabbitmq.com/ ## ## ########## Logs: /var/log/rabbitmq/rabbit#bogon.log ###### ## /var/log/rabbitmq/rabbit#bogon-sasl.log ########## Starting broker... BOOT FAILED =========== Error description: {could_not_start,rabbit, {undef, [{crypto,module_info,[attributes],[]}, {rabbit_misc,module_attributes,1, [{file,"src/rabbit_misc.erl"},{line,805}]}, {rabbit_misc,'-all_module_attributes/1-fun-0-',3, [{file,"src/rabbit_misc.erl"},{line,825}]}, {lists,foldl,3,[{file,"lists.erl"},{line,1248}]}, {rabbit_boot_steps,find_steps,1, [{file,"src/rabbit_boot_steps.erl"},{line,40}]}, {rabbit_boot_steps,run_boot_steps,1, [{file,"src/rabbit_boot_steps.erl"},{line,26}]}, {rabbit,start,2,[{file,"src/rabbit.erl"},{line,477}]}, {application_master,start_it_old,4, [{file,"application_master.erl"},{line,269}]}]}} Log files (may contain more information): /var/log/rabbitmq/rabbit#bogon.log /var/log/rabbitmq/rabbit#bogon-sasl.log {"init terminating in do_boot",{could_not_start,rabbit,{undef,[{crypto,module_info,[attributes],[]},{rabbit_misc,module_attributes,1,[{file,"src/rabbit_misc.erl"},{line,805}]},{rabbit_misc,'-all_module_attributes/1-fun-0-',3,[{file,"src/rabbit_misc.erl"},{line,825}]},{lists,foldl,3,[{file,"lists.erl"},{line,1248}]},{rabbit_boot_steps,find_steps,1,[{file,"src/rabbit_boot_steps.erl"},{line,40}]},{rabbit_boot_steps,run_boot_steps,1,[{file,"src/rabbit_boot_steps.erl"},{line,26}]},{rabbit,start,2,[{file,"src/rabbit.erl"},{line,477}]},{application_master,start_it_old,4,[{file,"application_master.erl"},{line,269}]}]}}} Crash dump was written to: erl_crash.dump init terminating in do_boot () I don't understand... Why there are a lot of issues? Is there any procedure that was not correct?
{could_not_start,rabbit,{undef,[{crypto,module_info,[attributes] means that you need the crypto Erlang. Check this https://www.rabbitmq.com/which-erlang.html. use SSL/TLS reliably 17.0 you need the version >= 17.0
I got same issue because of mismatch of RabbitMQ version installed on 3rd node other than two nodes. Install same versions on all nodes of cluster.
zsh "command not found: plugin:" for build.gradle
I've used Maven a few times before, but I'm new to Gradle. I'm using Intellij IDEA 14.0.2 on Mac OS X 10.10.1. I also have ruby with rails installed. "gem update" shows that I have the latest. I also have brew & oh_my_zsh installed and the latest. Ok back to my problem. My purpose is to change a small project from Maven to Gradle. I created a new module for Gradle with IDEA: apply plugin: 'java' sourceCompatibility = 1.5 version = '1.0' repositories { mavenCentral() } dependencies { testCompile group: 'junit', name: 'junit', version: '4.11' } The output when running is: /bin/bash /Users/lucianirimie/BCD/bcd-remote-tests/Gradle/build.gradle zsh:1: command not found: plugin: /Users/lucianirimie/BCD/bcd-remote-tests/Gradle/build.gradle: line 3: sourceCompatibility: command not found /Users/lucianirimie/BCD/bcd-remote-tests/Gradle/build.gradle: line 4: version: command not found /Users/lucianirimie/BCD/bcd-remote-tests/Gradle/build.gradle: line 6: repositories: command not found /Users/lucianirimie/BCD/bcd-remote-tests/Gradle/build.gradle: line 8: syntax error near unexpected token }' /Users/lucianirimie/BCD/bcd-remote-tests/Gradle/build.gradle: line 8:}'` Here is the content of my .zshrc file # DISABLE_CORRECTION="true" # Uncomment following line if you want red dots to be displayed while waiting for completion # COMPLETION_WAITING_DOTS="true" # Uncomment following line if you want to disable marking untracked files under # VCS as dirty. This makes repository status check for large repositories much, # much faster. # DISABLE_UNTRACKED_FILES_DIRTY="true" # Which plugins would you like to load? (plugins can be found in ~/.oh-my-zsh/plugins/*) # Custom plugins may be added to ~/.oh-my-zsh/custom/plugins/ # Example format: plugins=(rails git textmate ruby lighthouse) plugins=(git) source $ZSH/oh-my-zsh.sh # Customize to your needs... export PATH=$PATH:/Users/lucianirimie/.rvm/gems/ruby-2.0.0-p247/bin:/Users/lucianirimie/.rvm/gems/ruby-2.0.0-p247#global/bin:/Users/lucianirimie/.rvm/rubies/ruby-2.0.0-p247/bin:/Users/lucianirimie/.rvm/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/git/bin export PATH="$PATH:$HOME/.rvm/bin" # Add RVM to PATH for scripting export PATH="/usr/local/bin:$PATH" [[ -sbrew --prefix/etc/autojump.sh ]] && .brew --prefix/etc/autojump.sh # Set name of the theme to load. # Look in ~/.oh-my-zsh/themes/ # Optionally, if you set this to "random", it'll load a random theme each # time that oh-my-zsh is loaded. ZSH_THEME="robbyrussell" # Example aliases # alias zshconfig="mate ~/.zshrc" # alias ohmyzsh="mate ~/.oh-my-zsh" # Set to this to use case-sensitive completion # CASE_SENSITIVE="true" # Uncomment this to disable bi-weekly auto-update checks # DISABLE_AUTO_UPDATE="true" # Uncomment to change how often before auto-updates occur? (in days) # export UPDATE_ZSH_DAYS=13 # Uncomment following line if you want to disable colors in ls # DISABLE_LS_COLORS="true" # Uncomment following line if you want to disable autosetting terminal title. # DISABLE_AUTO_TITLE="true" # Uncomment following line if you want to disable command autocorrection # DISABLE_CORRECTION="true" # Uncomment following line if you want red dots to be displayed while waiting for completion # COMPLETION_WAITING_DOTS="true" # Uncomment following line if you want to disable marking untracked files under # VCS as dirty. This makes repository status check for large repositories much, # much faster. # DISABLE_UNTRACKED_FILES_DIRTY="true" # Which plugins would you like to load? (plugins can be found in ~/.oh-my-zsh/plugins/*) # Custom plugins may be added to ~/.oh-my-zsh/custom/plugins/ # Example format: plugins=(rails git textmate ruby lighthouse) plugins=(git) source $ZSH/oh-my-zsh.sh # Customize to your needs... export PATH=$PATH:/Users/lucianirimie/.rvm/gems/ruby-2.0.0-p247/bin:/Users/lucianirimie/.rvm/gems/ruby-2.0.0-p247#global/bin:/Users/lucianirimie/.rvm/rubies/ruby-2.0.0-p247/bin:/Users/lucianirimie/.rvm/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/git/bin export PATH="$PATH:$HOME/.rvm/bin" # Add RVM to PATH for scripting export PATH="/usr/local/bin:$PATH" [[ -sbrew --prefix/etc/autojump.sh ]] && .brew --prefix/etc/autojump.sh
Executing a Gradle build requires the installation of Gradle, or the use of a the Gradle wrapper. Take a look at the Gradle docs for installation instructions. I do believe Gradle is available via Brew as well. With the gradle command properly registered on your path, you would build your project something like this (from the folder with the build.gradle file. $ gradle build