Since yesterday I am trying to start the Azure Cloud shell but every time I am getting the following error:
Sorry, something went wrong: Unknown Error
See attached image.
To troubleshoot I tried to delete the Cloud Shell Resource Group (cloud-shell-storage-westeurope) and its storage account.
After restarting the Cloud Shell I was asked to create the RG and storage account for the Cloud Shell again. But the problem was still there.
Apologies for that experience - we've recently been resolving this issue as it is a bug on our end. We've released a few hotfixes that will hopefully fix this issue, if you still hit it please try simply exiting the shell and launching it again. If at this point you still repeatedly receive this error, please open a support ticket with us here.
Thanks for your patience and for being a Cloud Shell user!
Related
I installed Jenkins previously but it had some issue (there was no start icon) in the folder, so I uninstalled it. Now I'm trying to install it again, but it tends to pop this error:
I tried all the solutions mentioned in this post , but no success - Jenkins failed to start - Verify that you have sufficient privileges to start system services
As mentioned in the option 2 of the post, I tried to start jenkins in services but got a 1067 error
I read a lot of similar posts, but none of them really helped. I believe my user has enough privileges to work without causing any trouble, so the underlying problem is something else. Please help me figure out the issue.
I found the solution!
Turns out Jenkins doesn't work on other JDKs except for 8,11. And I have the 14th version. I'm putting the link to the answer that helped me change the JDK version.
Jenkins requires Java versions [8, 11] but you are running with Java 16 from C:\Program Files\Java\jdk-16.0.1
I trying to create a substrate smart contract by following the tutorial as described in https://substrate.dev/substrate-contracts-workshop/#/0/setup. I have installed all the dependencies on Windows 10 OS. However, the process fails after completing 3 steps ( [3/5] Optimizing wasm file) with the following error message.
"ERROR: Access is denied. (os error 5)"
Please help me in resolving this error.
Thanks
Maybe try an admin console? But ideally developing in WSL2 is best if you can. You'll have a lot less trouble that way.
I'm running CentOS 7 in a Google Compute Engine VM, and trying to connect to it via Chrome Remote Desktop. When I run the start-host command, it fails with "OAuth error" and no more information.
I accessed the https://remotedesktop.google.com/headless site with Chrome, filled out the choices, and went through the authorization phase. There was not an option for CentOS, so I chose "Debian" and when it gave me the connect command, I replaced the path to start-host with the CentOS one of /usr/lib64/chrome-remote-desktop/start-host, and running the resulting command fails.
I did the likely web searches and found some fairly old and unhelpful information, but nothing useful.
If I can't get Chrome Remote Desktop working, I'd be willing to try another method to run GUI-based applications (in this case, IBM's oneWEX). I can get X11 to sort-of work remotely, but not well enough to run oneWEX.
This is the command I got from the Chrome site, modified to work with CentOS:
DISPLAY= /usr/lib64/chrome-remote-desktop/start-host --code="<code>" --redirect-url="https://remotedesktop.google.com/_/oauthredirect" --name=
The start-host command asked the expected questions of the computer name and PIN, then gave the error:
Couldn't start host: OAuth error.
When you get the code from https://remotedesktop.google.com/headless it is only good for a few minutes, and only one time use.
Just go back to https://remotedesktop.google.com/headless follow the prompts and get a new code for every attempt.
In my case, I got another error when I first ran the command. I tried to resolve it, and reran the same command (with the original code). I kept getting the "Couldn't start host: OAuth error." until I figured out I needed to get a new code from https://remotedesktop.google.com/headless for each attempt.
FYI: The error message is not given right away, but after entering the computer name and double entering the pin.
According to https://bugs.chromium.org/p/chromium/issues/detail?id=1039016, this could apparently also happen if the /usr/lib64/chrome-remote-desktop/start-host binary is not one from the "official" DEBian package built and distributed by Google, but one built from source e.g. by yourself or your Linux distribution (such as the chrome-remote-desktop package built by Fedora; https://bugzilla.redhat.com/show_bug.cgi?id=1788448 aims to clarify how to use that one).
What I can see here is that you previously added some libraries to your CentOS instance, I tried replicating the error myself and inside my CentOS 7 instance (from Compute Engine) I don't seem to have any /usr/lib64/chrome-remote-desktop/ folder.
Or is it from your local machine?
I had the same error and found that refreshing the headless page to get a new code string in the command worked.
I'm running the Jenkins as a Docker container on a Virtual Machine on Google Cloud Platform. On the very first screen of setup, I can see that a lot of plugins did not install in my Jenkins server?
Please let me know how to resolve this issue? Is it something due to with the security on the cloud by default which restricts downloading of plugins?
Refer following link for screenshot:-
https://storage.googleapis.com/mydockerissues/Jenkins%20Plugins%20Issue.PNG
Cheers
Something similar happened to me when running Jenkins on Docker on my local machine. To get everything to install I had to keep retrying. It took several retries but eventually I got everything installed.
I'm not sure why this is the case. Maybe it fails downloads whose dependencies aren't installed yet?
I recently set up concourse CI using the following docker-compose: https://concourse-ci.org/docker-repository.html and then tried the flight school training here: https://concourse-ci.org/flight-school.html and then, when that failed showing "no workers", I attempted the hello-world here: https://concourse-ci.org/hello-world.html.
I keep seeing an error saying "no workers". If I had to guess, this is because of a simple configuration issue on my end, but I am having trouble tracking it down.
Can someone please help me figure out how to debug this, I do not see errors in the docker startup logs. Searching for the problem is showing seemingly unrelated errors.
I talked with the team and it appears it was a race condition in v3.1 that I was running. Updating to v3.2 fixed the issues and everything is running smoothly.