I'm new to Node-red and cloud.ibm.com. I'm using the lite version of the service with an academic account. In the manage palette side bar, I searched for node-red-dashboard, clicked install and waited for a while until I got the error "Installation of module node-red-dashboard failed:". I also got three strings after the error ""------------------------------------------", "", and "------------------------------------------" (those characters appear as dashes). Where should I start looking to fix this? Thank you!
I just attempted to recreate and got an error with the installation when my CF application did not have enough memory. However, when I upped the memory in my application, it worked fine.
I recommend following this tutorial on IBM Developer which explains the recommended steps to install the node-red-dashboard in addition to adding extra nodes to your Node-RED palette. It also explains how to deploy the application with 256MB memory.
https://developer.ibm.com/components/node-red/tutorials/how-to-create-a-node-red-starter-application/
Related
When I try to install google cloud SDK, I was getting the following error:
ERROR:
(gcloud.components.update) Failed to fetch component listing from
server. Check your network settings and try again. This will install
all the core command line tools necessary for working with the Google
Cloud Platform. Failed to install.
After reinstalling python (v3.7.0), I added the path and also added CLOUDSDK_PYTHON environment variable to make sure. Now when I attempt the installation, the installation simply hangs:
If I attempt the installation trough terminal by executing install.bat, it also gets stuck after requesting to send diagnostics to google:
Welcome to the Google Cloud SDK!
Active code page: 65001
To help improve the quality of this product, we collect anonymized usage data
and anonymized stacktraces when crashes are encountered; additional information
is available at <https://cloud.google.com/sdk/usage-statistics>. This data is
handled in accordance with our privacy policy
<https://policies.google.com/privacy>. You may choose to opt in this
collection now (by choosing 'Y' at the below prompt), or at any time in the
future by running the following command:
gcloud config set disable_usage_reporting false
Do you want to help improve the Google Cloud SDK (y/N)? n
Nothing gets printed after that.
it seems that the "(gcloud.components.update) Failed to fetch component listing from server" error might be caused by some proxies or antivirus in your environment, I'd recommend you to try a clean installation in a vm or using another network.
Also, I was able to find soem similar errors for this on issue tracker and the team gave a soltion at comment10, also, as you can see on the issue tracker, sometimes this behavior is because the Python SDK is installed on default "Program Files" location, you could give it a try by changing the location of the python SDK
Sometimes the logs tab is empty and the instance creations fails bringing it to error state. How can i debug what went wrong and where? I am using Bluemix GUI to copy paste the terraform template.
Typically for a failed deployment in Cloud Automation Manager (CAM) you will see an error message in the deployment's Log File tab. However if you do not see anything on the Log File tab and did not receive an error message at time of deployment, first check the template formatting and then open a support ticket with IBM for further diagnosis. You can following the instructions at this link for contacting support.
https://console.bluemix.net/docs/services/CloudAutomationManager/cam_ts.html#ts_cam
The internal logs for Cloud Automation Manager will be reviewed by IBM support to help diagnose the issue. Thanks!
The CAM traouble shooting documentation is available here: https://console.bluemix.net/docs/services/CloudAutomationManager/cam_ts.html#ts_cam
I see that there some known issues with CAM. You can go through the troubleshooting guide and see if your error is one of the known issues. If not - they have provided instruction on how to contact support. I suggest you contact their support and seek help in getting the logs.
I've installed the latest W-Systems DocuSign module for SugarCRM and I followed the installation guide to the T (https://www.w-systems.com/media/DocuSign/SugarConnectortoDocuSign_InstallationUseGuide.pdf). However, my problem start at the end of page 7 where I click "Configure DocuSign" or "DocuSign User Settings > Log In". Nothing happens.. no error message, no dialog window, nada.
I've run "Rebuild JS Grouping Files", "Quick Repair and Rebuild", cleared the cache and tried multiple browsers.
Has somebody else encountered this problem? Any suggestions on how to solve it?
EDIT: I was able to use the module without problems on a co-workers machine, but I still cannot use it on my own.
The SugarCRM <-> DocuSign Connector is written and maintained by SugarCRM, not DocuSign. The only integrations (Connectors) that DocuSign implements and maintains are its integrations with Microsoft, Google, and Salesforce.
With that said, if you're running into bugs/issues with the connector you'll need to contact SugarCRM and go through their support to resolve.
After being in contact with W-Systems support, they found out (by looking at the debug logs) that the database tables hadn't been correctly set up. The problem was fixed by uninstalling the module (without removing the tables), reinstalling the module, Admin > Quick Repair and Rebuild, and finally hard refresh (for me Ctrl+F5).
Everything now runs normally.
Recently upgraded to Service Fabric SDK v2.3.301, but for some reason my project got corrupted. I cannot debug the project, I get the following error: "A project with an Output Type of Class Library cannot be started."
It seems that the solution now fails to recognize the Service Fabric App. Yet I am able to deploy to my local cluster.
Anyone had similar issues while upgrading to the new SDK?
Thanks
PS Just in case, the service fabric app is the already set as startup project :o)
We have been using Service Fabric to develop a product for about a year with various versions of the SDK and I see this frequently. It happens both when hitting F5 with the SF Application as the sole startup project and even when right-clicking the SF Application and choosing "Debug -> Start New Instance".
Sometimes I have to try several times before it finally works. Other developers in our team see this as well, going all the way back to v2.0.
One thing that seems to make it happen less frequently is not touching anything on your computer after launching the project. Don't click anything else. Don't select another window. Let go of the mouse. Don't touch the keyboard.
Something I've started doing on the advice of a colleague is choosing "Debug -> Start Without Debugging", then attaching to the process if I want to debug it. I've had better luck with this approach in general - including not getting the "A project with an Output Type of Class Library cannot be started" issue.
I hope that helps.
I have had the same issue a couple of times. I have not been able to identify the source. But I have solved it with the following actions:
Close all Visual Studio windows.
Restart the Service Fabric service: Type services.msc in the windows run tool. Find Microsoft Service Fabric Host Service. Right Click + Restart.
Reset the local cluster: Look at the Service Fabric Local Cluster Manager Icon in the notification area in the right side of the task bar. Right Click + Reset Local Cluster.
Open the problematic solution in Visual Studio.
Clean and Rebuild solution.
Finally run your solution (press F5).
Hope this helps.
The error indicates that the service fabric application project (*.sfproj) is not set as start up project. Please try to change the start up project as some other project and again change it back to service fabric application project and see if that resolves the issue.
I am trying to get the Apache DayTrader benchmarking app on OpenShift quickstart working see link https://openshift.redhat.com/app/console/application_type/quickstart!17609
I have a free 3 gear openshift online account and the quickstart starts up but then after a while posts the message
"Application creation is taking longer than expected. Please wait a few minutes, then refresh this page."
Waiting and refreshing the page shows the whole application rolled back and removed from the gear.
I suspected it might need a larger gear but I can build an openshift gear manually with JBoss Enterprise Application Platform 6 and PostgreSQL 9.2 as per requirements in a small gear
I tried manually building the application via jboss developer studio and downloaded the git locally, imported it as a general project,converted to Mavern project, started openshift application wizard and choose the jbosseap-6 app type with postgresql-9.2 cartridge and went through using the existing daytrader project.
That all seemed to work and the app was created in my openshift online gear
Cartridges
JBoss Enterprise Application Platform 6
Status: Started
Gears
1 small, Storage 1 GB PostgreSQL 9.2
the account webpage then displays
"Welcome to your JBoss EAP application on OpenShift"
but I cant seem to access the daytrader index.jsp or app from there.
If anyone has successfully built Daytrader on openshift either manually or via quickstart could they please post the steps.
I am just starting with jboss and the solution may be an absurdly simple oversight on my part.
Much appreciated John
I am assuming this is not your cartridge. If that is the case, you should try logging an issue on the github project that feeds into that quickstart here: https://github.com/gvijayar/daytrader
The creator of the cartridge should be able to help you out.
I posted ( some time ago ) the issue in github for gvijayar but there has been no reponse. I have managed to build via command line as per "Deploying from Source" making allowance for the error.
The application name needs to change in the create command to be consistent across all the commands you list.
ex:
rhc app create -a daytradereap -t jbosseap-6 -g large
but the quickstart still fails consistently.