Jun 16, 2019
Intellij update branch info
Hi All
I am not sure if it's a bug or this is the way it should work. But, i had an issue while my
git left side tool menu with the list of all my remotes and locals wasn't sync with the actual remote repository (bitbucket in my case).
To solve it, just need to do "git fetch" using the menu.
Solved the problem.
Hoped it helped.
Dor
Jun 6, 2019
socket.error: [Errno 110] DNS issue while installing cloudera agent connection timed out; no servers could be reached [AWS]
Recently i was installing cloudera cluster on aws ec2 instances .
AWS setup which we had was having VPC without IGW R53 and we were using site to site vpn connection
cloudera agent installation was failing because cloudera uses "host -t PTR IP" command , while installing cloudera agent and agent node should be able to reach cloudera manager server host via "host" command on port 7182
"host" command should work in order for cloudera installation to work
Cloudera requires "host" and "nslookup" to work on all nodes.
cloudera requires name resolution and a configuring /etc/hosts file.
See the following requirements document:
https://www.cloudera.com/documentation/enterprise/release-notes/topics/rn_consolidated_pcm.html#cdh_cm_network_security
Procedure to install cloudera agent I see is that " from cloudera agent it should be able to reach scm server at serverIP:7182 " via below commands
Solution :
I had issue with my file /etc/resolv.conf , it dint have proper nameserver entry and this file was getting corrupt on every ec2 restart so i had to fix this file and disable NetworkManager as below
make sure you are able to run below commands in your cloudera nodes and below command should not get stuck and must return output
"host -t PTR IP"
check /etc/resolv.conf should have correct nameserver entries
also try to run below command
getent hosts ip-10.XXX.-XXX-XXX.eu-west-1.compute.internal
Port 7182 should be allowed in security group
if you feel your server /etc/resolv.conf is getting corrupt on every restart of ec2 instance then do below
systemctl
status NetworkManager
systemctl
stop NetworkManager
systemctl
disable NetworkManager
also your file on ec2 server /etc/sysconfig/network-scripts/ifcfg-eth0 must have below parameters
PEERDNS=no
DNS1=same nameserver IP as present in /etc/resolv.conf
Error description :
Detecting Cloudera Manager Server...
BEGIN host -t PTR 1x.xx.xx.xx
;; connection timed out; no servers could be reached
END (1)
BEGIN which python
/usr/bin/python
END (0)
BEGIN python -c 'import socket; import sys; s = socket.socket(socket.AF_INET); s.settimeout(5.0); s.connect((sys.argv[1], int(sys.argv[2]))); s.close();' 1x.xx.xx.xx 7182
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/lib64/python2.7/socket.py", line 224, in meth
return getattr(self._sock,name)(*args)
socket.error: [Errno 110] Connection timed out
END (1)
Jun 5, 2019
I can't see testng logs in my intellij console
Hi All,
Simple problem. Simple fix.
Validate that your project pom/gradle consist of log4j / slf4j and you aren't using the current logger.
If you have a log4j properties, or like i do the log4j2.xml file,
you need to change the root logger from info to debug for example.
Regards,
Dor
Simple problem. Simple fix.
Validate that your project pom/gradle consist of log4j / slf4j and you aren't using the current logger.
If you have a log4j properties, or like i do the log4j2.xml file,
you need to change the root logger from info to debug for example.
Regards,
Dor
Labels:
gradle,
log4j,
log4j.properties,
maven,
properties,
slf4j,
testng
Dec 4, 2018
CassandraRoleManager skipped default role setup: some nodes were not ready
Hi
I had this issue with my Cassandra 3.11.3 cluster.
'CassandraRoleManager skipped default role setup: some nodes were not ready'
Actually i didn't raised one of my nodes. The status was:
Datacenter:
datacenter1
=======================
Status=Up/Down
|/
State=Normal/Leaving/Joining/Moving
-- Address
Load Tokens Owns (effective) Host ID Rack
UN X.X.15.141
279.12 KiB 256 49.1% 65b80558-219d-478b-ad24-083a79d78348 rack1
UN X.X.15.140
235.39 KiB 256 49.2% 0efb432f-0789-455f-op24-29c6e2cce9ac rack1
UN X.X.15.142
287.49 KiB 256 49.6% 3558e3f0-717d-783UI-a22c-6891a3bd427f rack1
DN X.X.15.144
? 256 52.2% 8e8cdbac-9088-3421-963d-4857a78087d3 rack1
To solve it, i used the nodetool with 'removenode' method. Reference
Removing this node solved the problem for me.
Regards,
Dor
Aug 7, 2018
Refusing to serve hidden directory, via 404 Error on AWS EC2
Refusing to serve hidden directory, via 404 Error
I got this error while running jupyter notebook inside my EC2
My Solution --> when i first run it, i was inside .jupyter directory.
I created my own 'workspace' directory, switching into it and then run it again the 'jupyter notbook'
Now all ok.
Hoped it helped,
Dor
I got this error while running jupyter notebook inside my EC2
My Solution --> when i first run it, i was inside .jupyter directory.
I created my own 'workspace' directory, switching into it and then run it again the 'jupyter notbook'
Now all ok.
Hoped it helped,
Dor
Jun 6, 2017
Openstack using DevStack - Failed to fetch cdrom
Hi,
While going over all the configuration needed with devstack for open stack and during the installation - after running ./stack.sh i received an error
"failed to fetch cdrom ...."
To solve this, go into /etc/apt
do 'sudo nano sources.list' and remove by using '#" the cd rom line.
Then start again the ./stack.sh and it will work
you just removed / disabled the cd rom
Hoped i helped,
Dor
While going over all the configuration needed with devstack for open stack and during the installation - after running ./stack.sh i received an error
"failed to fetch cdrom ...."
To solve this, go into /etc/apt
do 'sudo nano sources.list' and remove by using '#" the cd rom line.
Then start again the ./stack.sh and it will work
you just removed / disabled the cd rom
Hoped i helped,
Dor
Apr 27, 2017
Parameter CONFIG_CONTROLLER_HOST failed validation: Given host does not listen on port 22:
Hi ,
Happen to me during openstack installation on fedora 25.
Solution - start the sshd service
'sudo service sshd start'
Solved for me
Hoped it helps
Dor
Happen to me during openstack installation on fedora 25.
Solution - start the sshd service
'sudo service sshd start'
Solved for me
Hoped it helps
Dor
Labels:
controller,
failed,
failure,
fedora,
fedora25,
host,
listen,
port,
service,
sshd,
validation
Subscribe to:
Posts (Atom)