I have a VM (CoreOS stable) that I am attempting to delete via the developer console. It returns:
Deleting instance failed. Error: request failed with unknown
error.
Any idea what this means?
--p
Related
In my Azure Pipeline I created a container using docker run using the below command:
docker run -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=Pa$$w0rd12' -p 1433:1433 -d mcr.microsoft.com/mssql/server:2017-latest-ubuntu
In another task I tried listing this container with a docker ps and it shows me the container as below:
/usr/bin/docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
afca60eb6fde mcr.microsoft.com/mssql/server:2017-latest-ubuntu "/opt/mssql/bin/nonr…" 1 second ago Up Less than a second 0.0.0.0:1433->1433/tcp, :::1433->1433/tcp nostalgic_jemison
Finishing: list docker containers
Post that I'm trying to run my dotnet integration tests which uses the above container for the SQL server. These tests are supposed to create their own DB inside the servers, run the tests and delete them. But It fails while running the tests with the below error:
Error Message:
System.AggregateException : One or more errors occurred. (A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 40 - Could not open a connection to SQL Server)) (The following constructor parameters did not have matching fixture data: DatabaseSetup databaseSetup)
---- Microsoft.Data.SqlClient.SqlException : A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 40 - Could not open a connection to SQL Server)
---- The following constructor parameters did not have matching fixture data: DatabaseSetup databaseSetup
The connection string I'm using in the integration tests are as below:
"Data Source=localhost,1433;Initial Catalog=dbname;User Id=SA;Password=Pa$$w0rd12"
I'm using Ubuntu 20.04 as the build agent. Same setup works fine on my local system on WSL with Ubuntu20.04
Update 1: I have replaced localhost with the IP address of the container in connection string. Works fine in WSL locally but it still throws the same error on Azure Pipelines.
Update 2: I have just noticed that the container stops when I run dotnet test in the pipeline. I can see container running before dotnet test but can't see the container active after dotnet test
A network-related or instance-specific error occurred while
establishing a connection to SQL Server. The server was not found or
was not accessible. Verify that the instance name is correct and that
SQL Server is configured to allow remote connections. (provider: TCP
Provider, error: 40 - Could not open a connection to SQL Server)
You can follow the below steps to troubleshoot the error:
Verify that the instance is running
Verify that the SQL Server Browser service is running
Verify the server name in the connection string
Verify the aliases on the client machines
Verify the firewall configuration
Verify the enabled protocols on SQL Server
Test TCP/IP connectivity
Test local connection
Test remote connection
The following constructor parameters did not have matching fixture
data: DatabaseSetup databaseSetup
You can refer to The following constructor parameters did not have matching fixture data for more help.
I installed Azure CosmosDb Emulator but it does not start and gives error:
"Failed loading emulator secrets certificate. Error: 0x80092022"
When I check my certificates, it also does not create any certificates related to cosmos db emulator. Then, I tried to create the certificates manually by "Microsoft.Azure.Cosmos.Emulator.exe /GenCert" command on cmd but this time show the error "Error generating Emulator SSL certificates"
How can I solve this problem?
This is an issue I am actively troubleshooting as well. The way to generate the missing certificates is to do the following:
Open cmd.exe with Administrator
Navigate to CosmosDB Install folder with this command
C:\Program Files\Azure Cosmos DB Emulator
Run this command to ensure the CosmosDB Emulator is shutdown
Microsoft.Azure.Cosmos.Emulator.exe /Shutdown
Run this command to generate the missing certificates:
Microsoft.Azure.Cosmos.Emulator.exe /GenCert
Ensure the following certificate correctly generated in Computer Certificates under Local Computer\Personal\Certificates
DocumentDbEmulatorCertificate | LocalHost
Start CosmosDB from either the start menu or command line and wait for it to fully initialize
I am trying to add a startup script in my GCP VM Instance to fetch data from a website (web crawler). I wanted to automate the crawling task following this answer. So, I added a startup script in my VM instance. The script looks like below:
#! /bin/bash
python3 /home/sadmanks/site-spider/src/main.py
Then, I wanted to schedule this instance. But when executing this startup script, it doesn't start the program that I want to execute. The log message that I get is following:
"Error restarting service: Failed to try-restart nscd.service: Unit nscd.service not found
I tried to do this in the browser ssh connection: sudo service nscd start outputs:
Failed to start nscd.service: Unit nscd.service not found.
Does anyone have any idea, how to resolve this issue?
Note: The program runs perfectly when I try to connect the instance with an SSH to my local machine.
The error "Error restarting service: Failed to try-restart nscd.service: Unit crond.service not found." is just harmless log spam. These error messages show up on every VM on start-up and are expected since systemd services like crond.service and nscd.service do not exist on COS. So, try updating the version of google-guest-agent service. But as suggested by #John Hanley that service is not related to python, web scraping/crawling, etc. So, make sure you know what the program is doing before running it on public servers.
When I try to deploy my node app on GAE I get this error (app ID stripped):
WARNING: If this is your first deployment, please try again.
ERROR: (gcloud.preview.app.deploy) Server responded with code [404]:
Not Found Unexpected HTTP status 404.
This application does not exist (app_id=u'<app-id>').
This is this project's first deployment. I am using the app.yaml from the getting started repo, nodejs runtime.
I downloaded the MS Azure Recovery Agent from the portal and registered and set up the server fineI set up a quick backup job to test and when I came to run it I get the following error:
I have rebooted the server and still the same error
The service is missing so i guess that's why it won't run but I cant see or find how to get that service installed.
I would not have expected this issue from a clean install?Anyone help please?