have created a volume and when I tried to attach the volume, I run this command:
euca-attach-volume -i i-3C66428A -d /dev/sdf vol-639C3E6C
After theat when I tried euca-describe-volumes it says failed. I have checked my cc.log but it seems like it has no error in it. So I have checked in nc.log and got this error in nc.log.
ERROR 000003074 ncAttachVolumeMarshal | [i-F7893F67][vol-8C9741E9] failed error=1
What do I have to do to fix it? Any idea?
It seems like a bug as I have get one similar posted in https://eucalyptus.atlassian.net/browse/EUCA-6201:
2013-05-15 19:35:58 ERROR 000011295 ncAttachVolumeMarshal | [i-116D3ECC][vol-A51C3B6E] failed error=1
Related
I'm trying to use microk8s for my KubernetesPodOperator in my dag. Unfortunately I can't seem get it to install consistently.
I'm using homebrew to install (or reinstall) microk8s and multipass. When I execute
microk8s install --cpu=4 --mem=10000
I get the errors:
launch failed: The following errors occurred:
qemu-system-aarch64: Error: HV_BAD_ARGUMENT
launch failed: instance "microk8s-vm" already exists
An error occurred with the instance when trying to launch with 'multipass': returned exit code 2.
Ensure that 'multipass' is setup correctly and try again.
(where launch failed: instance "microk8s-vm" already exists appears several times.)
I've tried reinstalling both several times and that doesn't appear to help. Any advice?
Turns out I need to be using microk8s install --cpu=4 --mem=10 not 10000. It wants GB, not MB. My bad. I wish the error message was a little clearer though.
I spent a lot of time trying to debug and fix a database that was working without a problem few days earlier, and is refusing to start with:
FATAL ERROR: Upgrade failed
after adding the env var:
- name: BITNAMI_DEBUG
value: "true"
I can see that the real error is:
2021-07-14 23:12:32 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.db' doesn't exist
2021-07-14 23:12:32 0 [ERROR] Aborting
crazy that bitnami hides these errors by default....
Until now I couldn't figure out what broke it and how to really fix it, but I managed to start the database by exec into the container and running:
adduser mysql --uid=1001
chown mysql:root /opt/bitnami/mariadb/tmp/
mysql_install_db --user=mysql --basedir=/opt/bitnami/mariadb --datadir=/bitnami/mariadb/data
mysqld --skip-grant-tables --user=mysql --skip-external-locking --port=3306 --sock=/opt/bitnami/mariadb/tmp/mysql.sock --datadir=/bitnami/mariadb/data
After running the db I managed to run a mysqldump, copy all what is relevant for me, and reinstall a new db from scratch then restoring the content.
Why the user was not present and why I needed to change the permissions is beside me.
I am glad you were able to recover the database. I was going to suggest the mysql_install_db command as you mentioned, I am not sure if there is any other approach to solve that kind of issue. In any case, I think the ideal solution would pass through finding what causes the problem initially.
After installing Inhanced-Table plugin, my Kibana is stuck on the following message
"Kibana server is not ready yet"
However after some minutes it completely became out of reach and I am facing with "Unable to connect" error on my browser.
I removed the plugin with the following command, but the error still exists.
./bin/kibana-plugin remove enhanced-table
Would you mind helping me in order to solve this problem. Also Kibana logfile is available via following link.
https://drive.google.com/file/d/1LILdo07Q9r0-VNG7hgkbTOaE2eJzhQPs/view?usp=sharing
Thanks
Best Regards
Looking through the log of your kibana, I've seen:
{ "type":"log",
"#timestamp":"2020-11-11T05:44:01Z",
"tags":["fatal","root"],"pid":2884,
"message":"{ Error: Optimizations failure.\n 9263 modules\n \n
ERROR in ./src/legacy/core_plugins/console/public/np_ready/application/components/editor_example.js\n
Module not found: Error: Can't resolve '../constants/help_example.txt' in 'D:\\Elastic\\Kibana\\kibana-7.6.1\\src\\legacy\\core_plugins\\console\\public\\np_ready\\application\\components'\n\n
So might be Kibana is still looking for the plugin, that's why the error occurred.
You should try stop kibana and start it again.
I installed a new clear kibana and problem fixed
I have a problem with my zsh. It works some time after running in VS code and then fails and blocks bash. The error is: "zsh: error on TTY read: unknown error 512". I reinstalled zsh and ran it once again and then it failed again. Does anyone have any idea how to solve the problem? Thank you!
I am using Ubuntu 18.04-3 and when executing the command >
personal.unlockAccount(web3.eth.accounts[0],null)
I am getting the following error,
enter image description here
I tried some of the suggestions here (enter link description here)
and the suggestions (here) for the internal/ethapi/api.go
I included in the file
--allow-insecure-unlock (//I have add as in the suggestions but does not indicate where and how to place it//)
Appreciate your time in advance
You have places --allow-insecure-unlock at the wrong place. It should be when starting geth instant.
Example:
$ geth {--rpc etc your other flags} --allow-insecure-unlock