I was trying to change my admin password using
memsql-ops memsql-update-root-password -p <password>
but i get this error
J543a0b [ERROR] Could not deobfuscate password
Any thing i am doing wrong ?
Use change-root-password command:
For Example
$ sudo memsqlctl change-root-password --password "NewSecurePass"
Related
I'm trying to update the fields while importing the OSM data into the PostgreSQL DB using psql command on Linux.
I wanted to add the bash variables in the command., but I'm getting the error.
Command : sudo docker exec dc2b20d450 su -l postgres -c /usr/lib/postgresql/14/bin/psql --dbname=postgres --username=postgres --command=UPDATE planet_osm_point SET name_display=name WHERE "\""name:en"\"" IS NULL OR char_length(trim(both from "\""name:en"\""))<1 OR "\""name:en"\""=name;
When I try to run the above command I'm receiving this error -bash: syntax error near unexpected token `('
I'm not getting how to fix this issue., Can anyone help me on this.
I use the mcr.microsoft.com/mssql/server:2017 docker container to run a mssql server. I tried to change the collation like this:
echo "SQL_Latin1_General_CP1_CI_AS" | /opt/mssql/bin/mssql-conf set-collation
Unfortunately I get this error:
No passwd entry for user 'mssql'
How is it possible to fix this error?
I created a new user with useradd mssql, but now I get this error if I run the command:
sqlservr: Unable to open /var/opt/mssql/.system/instance_id: File: pal.cpp:566 [Status: 0xC0000022 Access Denied errno = 0xD(13) Permission denied]
/opt/mssql/bin/sqlservr: PAL initialization failed. Error: 101
It looks the latest mcr.microsoft.com/mssql/server fix such issue, if you insist on the old, next could be the procedure to fix all user/permission issue:
cake#cake:~/20211012$ docker run --rm -it mcr.microsoft.com/mssql/server:2017-latest /bin/bash
SQL Server 2019 will run as non-root by default.
This container is running as user root.
To learn more visit https://go.microsoft.com/fwlink/?linkid=2099216.
root#4fd0bdf1d21c:/# useradd mssql
root#4fd0bdf1d21c:/# mkdir -p /var/opt/mssql
root#4fd0bdf1d21c:/# chmod -R 777 /var/opt/mssql
root#4fd0bdf1d21c:/# echo "SQL_Latin1_General_CP1_CI_AS" | /opt/mssql/bin/mssql-conf set-collation
Enter the collation: Configuring SQL Server...
The SQL Server End-User License Agreement (EULA) must be accepted before SQL
Server can start. The license terms for this product can be downloaded from
http://go.microsoft.com/fwlink/?LinkId=746388.
You can accept the EULA by specifying the --accept-eula command line option,
setting the ACCEPT_EULA environment variable, or using the mssql-conf tool.
In a simple jenkinsfile as seen bellow:
pipeline {
agent {
label 'my-agent'
}
stages {
stage ('Docker version') {
steps {
sh 'docker --version'
}
}
stage ('Docker Login Test') {
steps {
script {
withCredentials([usernamePassword(credentialsId: 'mycredentials', usernameVariable: 'DOCKER_USER', passwordVariable: 'DOCKER_PASSWORD')]) {
echo "docker login naked"
sh "docker login myAzureRepo.azurecr.io -u admin -p 1234"
echo "docker login protected"
sh "docker login myAzureRepo.azurecr.io -u $DOCKER_USER -p $DOCKER_PASSWORD"
}
}
}
}
}
When naked credentials are used, I get successfull login, and have even tried to push images, and works fine.
But when i get the password from credentials store, I get the following error from jenkins.
docker login myAzureRepo.azurecr.io -u ****Error: Cannot perform an interactive login from a non TTY device
After trying out many different ways, one worked. The username must be provided, only the password can be passed as variable.
So instead of
sh "docker login myAzureRepo.azurecr.io -u $DOCKER_USER -p $DOCKER_PASSWORD"
I used
sh "docker login myAzureRepo.azurecr.io -u admin -p $DOCKER_PASSWORD"
And worked fine. At least the password is hidden.
The registry in the examples is a made one one, the registry I am working on has different name and credentials.
But if you know better ways, please spread the love. I am just starting working with Jenkins, docker and microservices and am loving it.
I am using Azure Hdinsight. When I do restart It gives following error
"On host abc.internal.cloudapp.net role HBASE_CLIENT in invalid state.
Invalid transition. Invalid event: HOST_SVCCOMP_OP_IN_PROGRESS at INSTALL_FAILED"
I am not able to start HMaster.
you can remove and install again,see here same kind question
Remove:
curl -H "X-Requested-By:ambari" -u admin:admin -X DELETE "http://<AMBARI-SERVER>:8080/api/v1/clusters/<cluster-name>/hosts/<host-name>/host_components/HBASE_CLIENT"
Install:
Open Host UI -> Add -> HBASE_CLIENT
ubuntu#ubuntu-14-lts:~$ export OS_USERNAME=admin
ubuntu#ubuntu-14-lts:~$ export OS_TENANT_NAME=admin
ubuntu#ubuntu-14-lts:~$ export OS_PASSWORD=admin
ubuntu#ubuntu-14-lts:~$ export OS_AUTH_URL=http://localhost:35357/v2.0/
Executed the command to create the Admin tenant
ubuntu#ubuntu-14-lts:~$ sudo keystone tenant-create --name admin --description "Admin Tenant"
got the below error
Expecting an auth URL via either --os-auth-url or env[OS_AUTH_URL]
modified the url
ubuntu#ubuntu-14-lts:~$ export OS_AUTH_URL="http://localhost:35357/v2.0/"
re-run the same command and same error thrown
ubuntu#ubuntu-14-lts:~$ sudo keystone tenant-create --name admin --description "Admin Tenant"
Expecting an auth URL via either --os-auth-url or env[OS_AUTH_URL]
Is there any Issues in running the command ?
The issue is probably with sudo - sudo may not maintain environment variables. Depends on configuration.
Why do you need sudo anyway? The keystone command does not require it. Either drop sudo, or add
--os-auth-url http://localhost:35357/v2.0/
to your command. You can also do
sudo -e keystone ...
You have failed to create a new user or tenant because you have no access to keystone... just like you need to login to mysql to create new tables and all, the same is here. The following steps will help you through:
# unset OS_SERVICE_TOKEN OS_SERVICE_ENDPOINT
# keystone --os-username=ADMIN_USERNAME --os-password=ADMIN_PASSWORD --os-auth-url=http://controller:35357/v2.0 token-get
# source admin_creds //this is the file where you have saved the admin credentials
# keystone token-get
# source creds // this is the other file where you have backed up your admin credentials
now you can run your keystone commands normally. Please put a tick mark if it helped you! lol