I was following this guide for installing spark on ec2.But getting following error while launching cluster:
ERROR:boto:403 Forbidden
I ran into this problem and got around it by using a "-w 600", which basically says wait for 600 second. Apparently, there is some housekeeping that the process needs more time on.
Ok I found out here that you have to set the privilege of the user (the user from which you got your AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY) to the value AmazonEC2FullAccess
This should solve your problem for most of you !
Related
I am getting this error when i am trying to restart my clickhouse server.
Failed to start clickhouse-server.service: The name org.freedesktop.PolicyKit1 was not provided by any .service files
See system logs and 'systemctl status clickhouse-server.service' for details.
Upon further inspection of server. We noticed that Log directory was full. After flushing the logs clickhouse server restarted normally. But the error message made no sense cite the actual problem. then what is this error pointing to ? Pls enlight
org.freedesktop.PolicyKit1 , is like sudo but for systemd. It should be enabled for systemd to work. Resolved it by accessing ec2 superuser privelage.
sudo su
I have installed Kyma version 1.13.0 on Windows, it's working fine if I don't restart my machine or minikube. But when I restart minikube by following steps provided in the below link. Kyma is not working.
https://kyma-project.io/docs/latest/root/kyma#installation-install-kyma-locally-stop-and-restart-kyma-without-reinstalling
I need to reinstall kyma again to make it work.
Any help would be appreciated
This sounds similar to what I get on my Windows machine.
This is the error that I get after restarting minikube.
stderr:
error execution phase addon/coredns: unable to patch the CoreDNS deployment: Timeout: request did not complete within requested timeout 30s
To see the stack trace of this error execute with --v=5 or higher
If you get same error, this has been reported as a bug.
https://github.com/kyma-project/cli/issues/455
My solution to this issue is to get the kyma working by issuing provision command twice, so give it a try.
I am getting the following error when I run google-assistant-demo
OpenAlsaHandle PcmOpen: No such file or directory
[4571:4583:ERROR:audio_input_processor.cc(756)] Input error
ON_MUTED_CHANGED:
{'is_muted': False}
ON_START_FINISHED
ON_ASSISTANT_ERROR:
{'is_fatal': True}
[4571:4586:ERROR:audio_input_processor.cc(756)] Input error
ON_ASSISTANT_ERROR:
{'is_fatal': True}
I got this error a couple of times, assuming you have done everything described here and it is working: https://developers.google.com/assistant/sdk/prototype/getting-started-pi-python/configure-audio
Do a sudo reboot to make sure there aren't multiple instances of the google-assistant-demo running.
Then if you are running the google-assistant-demo from a script (either start-up or manually) try running it without a sudo prefix, that fixed my problem!
See my post here for more detail about how I got it running smoothly from start-up
Its an error due to improper alsa.conf configuration. You need to change it according to your audio setup.
I am using supervisor to run a queue work and it is failing with the following error:
Parse error: parse error, expecting `'&'' or `"variable (T_VARIABLE)"' in /Users/chris/Development/project/repo/vendor/laravel/framework/src/Illuminate/Foundation/helpers.php on line 475
This error shows up repeatedly in the worker logs.
Has anyone ever encountered this? Any idea what the issue might be?
So it turns out the Supervisor works were using a different version of PHP than my CLI and web server. I updated the php path to the correct bin in the worker config and all is well.
i'm new to ceph but have to build a mini-cluster as part of a project, i have been following an online tutorial of how to build one and all was fine until i restarted my machines the following day. now when i perform the command ceph health it returns an error saying: 2015-01-08 15:35:04.037375 7fae717fa700 0 -- :/1003525 >> 192.168.1.12:6789/0 pipe(0x7fae6c000c00 sd=3 :0 s=1 pgs=0 cs=0 l=1 c=0x7fae6c000e90).fault.
and whenever i run the same command on the 192.168.1.12 machine it returns an error saying: monclient(hunting): ERROR: missing keyring, cannot use cephx for authentication.
0 librados: client.admin initialization error (2) No such file or directory. Error connecting to cluster: ObjectNotFound.
I have been searching the internet for a while now for any answers and not found much, i noticed this site tends to be good in answering most if not all questions though, so any help would be greatly appreciated thanks. Im using centos 7 on all machines if thats any help.
Check if you have the permission to read the keyring file in
/etc/ceph/ceph.client.admin.keyring
If this file is not readable by your user, or it is missing, you are not able to do
ceph -w
If the keyring is missing you can install the keyring from the admin node using ceph-deploy admin serverhostname
As the error saying: ERROR: missing keyring. That means you don't have the keyring file.
Beside, this error,
error saying: 2015-01-08 15:35:04.037375 7fae717fa700 0 -- :/1003525 >> 192.168.1.12:6789/0 pipe(0x7fae6c000c00 sd=3 :0 s=1 pgs=0 cs=0 l=1 c=0x7fae6c000e90).fault.
It means your monitor didn't start up cause you missing the keyring file.
Step to resolve this problem:
1. Check the monitor host, and let it start up.
2. Execute the command "ceph -s" on monitor to check this cluster.