I am installing eucalyptus 4.4.4 on centos 7 and i have done all the installation steps but DNS is still not working. When i using ping to check it is showing error that cannot find service.
To check the status of the eucalyptus dns service you can use:
# euserv-describe-services --filter service-type=dns --expert
SERVICE arn:euca:bootstrap:api.10.117.111.14:dns:api.10.117.111.14.dns/ enabled 21 http://192.168.111.14:8773/services/Dns
If the service is not enabled then the most likely reason is that another service is installed and using the dns port.
If the service is enabled then you can check the output using dig:
dig +short ec2.internal #192.168.111.14
192.168.111.14
In this example my dns and ec2 (compute) services are on the same host.
If you see a response such as:
Warning: query response not set
from the dig command then you may not have enabled dns functionality, to check and then enable dns run:
# euctl dns.enabled
# euctl dns.enabled=true
It is also a good idea to review other setting described in the documentation to verify dns settings:
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#shared/setting_up_dns.html
Related
my client machine has syslog-ng and my remote machine has rsyslog configuration.
my server/remote machine manages many clients and I need to differentiate which machine is sending which logs.
normally I would use syslog-ng on the server side but these machines aren't meant to have them.
Also would like to mention it isn't for apache or web servers just physical machines.
On the client's side
Tried altering and adding different options or changing them to yes/no respectively.
options {
keep_hostname(yes);
create_dirs(no);
use_dns(no);
};
for eg:keep_hostname to no, it worked but only when I changed the hostname to the machine's ip address. which is not what I want.
Using a template
template("$(ISODATE) $(FULLHOST_FROM) $(SOURCEIP) $(HOST) $(HOSTNAME) ${PROGRAM}: ${MESSAGE}\n")
output:
day time localhost abc[ID] .source.s_local SourceIP=127.0.0.1 localhost localhost (root) CMD (xyz.conf)#ID
this isn't the output I want, it is printing in the message section when I want it in the place of the "host" and I don't understand how the source ip is the loopback address.
Using structured logging
rewrite r_sourceip{
set('${SOURCEIP}' value(HOST));
};
log { source(s_local); rewrite(r_sourceip);destination(d_syslog_tcp); };
output:
and the ip is displayed in the logs as the loopback address instead of the machine ip.
day date time 127.0.0.1 syslog-ng.service: Succeeded.
Tried installing rsyslog on my client but it doesn't work
sudo add-apt-repository ppa:adiscon/v8-stable
sudo apt-get update
sudo apt-get install rsyslog
I kept running into many errors, fixing them was impossible due to the difference in OS version or type maybe.
add apt repository command not found
wget command not found
On the server's side
Using a template
which creates a folder with the client's hostname and stores the logs in that particular folder.
not the solution I want.
$template DynaFile,"/var/log/%FROMHOST-IP%/%syslogfacility-text%.log"
*.* -?DynaFile
I want the logs to appear as such
day date time `client's ip address` syslog-ng.service: Succeeded.
Can someone suggest me a solution and why I keep getting the loopback address as my client's ip?
I have installed the neo4j in centos azure vm
I am trying to access it using the my local browser outside the vm. I am trying to create a 3 tier architecture where my neo4j will be sitting in one linux centos vm. But I am not able to access the neo4j.
I have added the inbound rules for ports 8080,7474,7687,7473.
Kindly help me in hosting the neo4j in azure vm. Please let me know what is the issue or configuration needed.
> yum remove neo4j-4.2.0-1.noarch
> systemctl enable neo4j
> service neo4j start
> service neo4j status
curl -v http://ip:7474/db/data
Neo4j.conf
# Bolt connector
dbms.connector.bolt.enabled=true
dbms.connector.bolt.tls_level=OPTIONAL
dbms.connector.bolt.listen_address=:7687
#dbms.connector.bolt.advertised_address=:7687
# HTTP Connector. There can be zero or one HTTP connectors.
dbms.connector.http.enabled=true
dbms.connector.http.listen_address=:#{default.http.port}
#dbms.connector.http.advertised_address=:7474
# HTTPS Connector. There can be zero or one HTTPS connectors.
dbms.connector.https.enabled=true
#dbms.connector.https.listen_address=:7473
#dbms.connector.https.advertised_address=:7473
# To enable HTTP logging, uncomment this line
dbms.logs.http.enabled=false
I try to connect to the VPN with openvpn.
If I connect from the cli with sudo openconnect..... its working fine. The vpn change the /etc/resolv.conf to the desired format.
But If I would connect from the GUI. Settings > Network > VPN it doesn-t change the resolv.conf
The SELinux is in permissive mode
/etc/NetworkManager/NetworkManager.conf
Should contains the following setting
[main]
dns=dnsmasq
And everything will goes well. If you want to keep an ability to use internet during you are on vpn. Add the google dns (8.8.8.8) to the vpn settings aswel
I have a Ubuntu VM on Azure (Resource Group, not the Classic VM) and it all worked out of the box. I recently tried to SSH into the VM using Putty and I could not.
I get the error: Network Error: Connection Timed out.
I have made sure that the port 22 is opened for SSH on the VM Inbound rules.
I had this VM setup about 2 months ago for a side project and at that time I was able to SSH easily without any troubles. Now I can't. Am I missing something?
PS: The HTTP works fine. I have the website running on it and it shows up in the browser. Also, I tried using a browser-based SSH client and it was able to SSH into the VM.
Looks to be an issue with the local firewall. Try resetting the SSH configuration in the portal.
Go to Azure Portal
Select VM in question
Select Reset
Password
Select Reset Configuration Only
Select Update
I am adding this because it might help someone, the chosen answer did not work for me
for some reason the firewall on the ubuntu server
Go to Serial Console type in your ssh username and you will be logged into the server
Check the firewall status to see if port 22 is allowed
sudo ufw status verbose
If the rule is not there then add it
sudo ufw allow ssh
I encountered the same issue. The following is how I solve this issue:
Don't add any port While creating your VM, do it only after only the VM is created
Add the port 22 in the networking tab until the VM status is Running.
When a new VM is created on Azure, by-default the Protocol TCP on Port 22 is Disabled. Need to allow this.
Follow:
https://medium.com/techinpieces/practical-azure-how-to-enable-ssh-on-azure-vm-84d8fba8103e
Create below directory : mkdir -p /run/sshd
Then restart service : systemctl restart ssh
This will definitely solve your issue.
I'm following the Micro cloud Foundry Quick-Start guide here:
http://support.cloudfoundry.com/entries/20316811-micro-cloud-foundry-getting-started-guide
I'm on step 10: registering a new user and I'm not able to connect:
$ vmc target api.lsmith.cloudfoundry.me Host is not available or is
not valid: 'http://api.lsmith.cloudfoundry.me' Would you like see the
response? [yN]: y HTTP exception: Errno::ECONNREFUSED:Connection
refused - connect(2)
My VM is in NAT mode. The Current Configuration in my VM is listed as:
Current Configuration: Identity: lsmith.cloudfoundry.me (ok) IP
Address: 172.16.x.x (network up)
When I run the host command in my console I get:
$ host api.lsmith.cloudfoundry.me api.lsmith.cloudfoundry.me is an
alias for lsmith.cloudfoundry.me. lsmith.cloudfoundry.me has address
127.0.0.1
I'm not able to reach the vmc target in my browswer but when I visit http://172.16.x.x/info I get:
VCAP ROUTER: 404 - DESTINATION NOT FOUND
I think this is a DNS issue but have no idea what I need to do to fix it. I tried changing the nameserver IP in my /etc/resolv.conf from 127.0.0.1 to 172.16.x.x but that didn't work.
I was able to resolve this by reconfiguring my domain (option 4 in the VM) using a newly generated domain token at https://micro.cloudfoundry.com/dns