I am trying to add the new accumulo 1.7.2 parcel for el7 into Cloudera manager. My version of Cloudera manager is 5.5.2 which is valid with the Accumulo parcel (minimum is 5.5.0). And My cloudera machine have no internet connection
I downloaded the new parcel from this site: http://archive.cloudera.com/accumulo-c5/parcels/1.7.2/ACCUMULO-1.7.2-5.5.0.ACCUMULO5.5.0.p0.8-el7.parcel
I added the parcel into /opt/cloudera/parcel-repo/accumulo/
I have an older version of Accumulo there that is running fine. I also updated the manifest.json file include the SHA of the new parcel.
I am not able to see the parcel under Parcels in Cloudera manager.
I could not find any documentations about it.
How can I get the new Accumulo Parcel run with Cloudera manager?
Thank you
Keep Accumulo parcel and manifest.json in one directory, in the same location start simple python server python -m SimpleHTTPServer 8000. Now open Cloudera Manager --> parcel icon --> edit settings --> Remote Parcel Repository URLs. In this windows you will see URI's like below
Now click on + and add your ipaddress:8000. Then click on Check for new parcels
Related
Preventing pulling in new dependencies from one build to the next, due to the way 3rd parties could define their dependencies.
Currently I'm utilizing the Remote Repositories in JFrog Artifact which reduces the downloads from public repos.
In my build scripts I can hard code the versions of the 3rd party modules/libraries I want to pull in. But if one of the dependencies hasn't it could pull in a new version on the next build.
So was curious if it there was a feature within JFrog Artifactory to copy an artifact and it's dependency from a remote repo into a local repo ?
There is a concept of virtual repo's in artifacory that is a combination of remote and loca repo.
local repo --> mostly used for custom build/artifacts/packages
remote repo --> points to the repo server of the technology configured.
For eg. with npm virtual repo.
npm local --> custom packages
npm remote --> https://www.npmjs.com/~npmre
Windows Server 2016
Installed Java JDK 1.8.0_192, and set JAVA_HOME path as directed
Download and install of WSO2 API manager 2.6.0 was all good...
when trying to start wso2server.bat,
briefly get the following error message on screen:
Error: Could not find or load main class
Manager\2.6.0\bin..\repository\conf\carbon.xml
From folder structures, carbon.xml file appears to be in proper place:
C:\Program Files\WSO2\API Manager\2.6.0\repository\conf
Thanks for any pointers!
Using the comment from Rans, I simplified the path with latest install to the following:
C:\WSO2\APImgr\v260\bin
I also ran the WSO2server.bat from command line, while in the bin folder, and it completes the startup tasks, and now appears to be running fine.
Thanks!
Respected Sir/Madam,
I am trying to install IBM Process Designer, but getting below errors.
ERROR: The Installation Manager's registry information is inconsistent with its installation information.
ERROR: The registry information at "HKLM\SOFTWARE\IBM\Installation Manager" indicates that the Installation Manager is not installed. However, the information at the "C:\ProgramData\IBM\Installation Manager" data location indicates that Installation Manager 1.7.2 (internal version: 1.7.2000.20140227_0303) is installed at location "C:\Program Files\IBM\InstallationManager\eclipse".
00:00.76 ERROR [main] com.ibm.cic.agent.core.application.HeadlessApplication run The Installation Manager's registry information is inconsistent with its installation information. The registry information at "HKLM\SOFTWARE\IBM\Installation Manager" indicates that the Installation Manager is not installed. However, the information at the "C:\ProgramData\IBM\Installation Manager" data location indicates that Installation Manager 1.7.2 (internal version: 1.7.2000.20140227_0303) is installed at location "C:\Program Files\IBM\InstallationManager\eclipse".
Resolution provided by IBM at below url http://www-01.ibm.com/support/docview.wss?uid=swg21639541 says,
" Run IBM Installation Manager directly; do not use the LaunchPad. From the Windows Start menu, select All Programs ->IBM Installation Manager > IBM Installation Manager. When Installation Manager starts, click Install, ensure all products are selected, and click Next to start the typical installation. "
But when I start the installation manager from Windows Start menu , it does not provide me the option to install IBM Process Designer at all.
Please find error logs "" attached, which come when I try to install IBM Process Designer from its setup "installProcessDesigner_admin".
I have installed Process center v8.5 successfully but not the way suggested. I have first installed db2 separately( used same db2 setup which came inside IBM BPM 8.5 PACKAGE ) and then installed Process center v8.5 using launchpad.exe , as it was giving db related errors when I was trying to install directly from launchpad.exe in BPM package I think IBM installation manager got installed when I was installing IBM BPM V8.5.
Please guide
Error says Installation Manager has been already installed in different location.
I would suggest to open Installation Manager from Start, then
In Installation Manager, File - > Preferences -> Add repository.config
if 32 bit operating system - repository.config location (C:\IBM_Process_Designer\IM)
if 64 bit operating system - repository.config location (C:\IBM_Process_Designer\IM64)
Quickstart for Endpoints on Compute Engine says
you need to run the Extensible Service Proxy before sending requests
to the API
But it also says
This quickstart works only on Debian. Make sure you create a VM that
runs Debian.
I have an existing GCE VM instance running Red Hat EL 7 that I'm adding this Endpoint to. Where are instructions for installing and running Extensible Service Proxy on it?
FWIW I examined the contents of the Debian package. It appears to be just nginx with custom configs and some extra scripts. If there's no RPM or other way of installing ESP on RHEL7, can I just manually install the contents extracted from the .deb package?
Yes, it should work (not tested). nginx in the .deb package is a statically compiled binary with a custom module that runs fine standalone. Please make sure to place the remaining files (config templates, root CA certificates, start-up script) in the same directories as in the .deb package.
The instructions for installing the ESP are implied in the instructions for installing the Cloud SDK on Red Hat and CentOS, since the endpoints-runtime RPM is available from the same repo as is the SDK.
$ sudo tee -a /etc/yum.repos.d/google-cloud-sdk.repo << EOM
[google-cloud-sdk]
name=Google Cloud SDK
baseurl=https://packages.cloud.google.com/yum/repos/cloud-sdk-el7-x86_64
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg
https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg
EOM
$
$ sudo yum install google-cloud-sdk
Note that the ESP installs as nginx, with supporting scripts and config files, that will replace any existing nginx and any files with the same name, which will overwrite any existing nginx functionality (like proxy, cache etc). It might be best to archive any host-specific nginx configs first, then install ESP, then merge old configs into the new ones installed by yum.
when i'm trying to upgrade cloudera manager via CM parcel page (at: http://hostname:7180/cmf/parcel/status) i get the flowing errors:
Local parcel error for parcel CDH-5.6.0-1.cdh5.6.0.p0.45-el6.parcel : The version 5.6.0-1.cdh5.6.0.p0.45 is too new to be supported. Please upgrade Cloudera Manager to at least 5.6.0 before using this parcel..
when trying to activate the parcel i get the following error:
The new version of CDH: '5.6.0-1.cdh5.6.0.p0.45' is newer than the running Cloudera Manager version: '5.4.8'.
how can i fix that?
It seems your cloudera manager is older version. So first update your manager then try to upgrade your cluster. Refer below link for more details
http://www.cloudera.com/documentation/enterprise/latest/topics/install_upgrade_to_cdh56.html