I have installed Oracle XE on linux mint, but it won't start.
when I do:
sudo /etc/init.d/oracle-xe-18c start
I get this back:
Starting Oracle Net Listener.
Starting Oracle Database instance XE.
Oracle Database instance XE started.
Failed to start Oracle Net Listener using
/opt/oracle/product/18c/dbhomeXE/bin/tnslsnr and Oracle Database
/opt/oracle/product/18c/dbhomeXE/bin/sqlplus.
Oracel configured without errors after I added localhost th /etc/hosts.
Now hosts look like this:
127.0.0.1 localhost
127.0.1.1 ksb-Latitude-E6420
# The following lines are desirable for IPv6 capable hosts ::1
ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0
ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters
127.0.0.1 localhost.localdomain localhost
How can I trouble shoot this?
I can't find any logfile.
BR Kresten
Related
After a system update on Fedora 36 Linux, Localhost alias now uses the ipv6 address by default which has broken a lot of my code.
For instance:
// Connecting to MongoDB using mongoose on express (nodejs)
mongoose.connect('mongodb://localhost:27017/farmStand')
.then(()=>{
console.log('Connected to Mongo');
})
Does not work and throws this error:
MongooseServerSelectionError: connect ECONNREFUSED ::1:27017
I've done some research and found multiple workarounds such as replacing localhost with 127.0.0.1, localhost4 or even removing the following line,
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
from from /etc/hosts,
# Loopback entries; do not change.
# For historical reasons, localhost precedes localhost.localdomain:
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
# See hosts(5) for proper format and other examples:
# 192.168.1.10 foo.mydomain.org foo
# 192.168.1.13 bar.mydomain.org bar
However since this the former forces me to change a lot of code and the later is not recommended by the hosts file itself,
How do i return localhost to its former state or bind mongodb to ipv6?
Start your MongoDB with this settings:
net:
bindIpAll: true
ipv6: true
Then it should work
I am getting error in puppet agent test:
parallels#puppet-server:~$ puppet agent -t
Error: Could not request certificate: Failed to open TCP connection to puppet:8140 (getaddrinfo: Name or service not known)
Exiting; failed to retrieve certificate and waitforcert is disabled
parallels#puppet-server:~$ sudo puppet agent -t
Warning: Unable to fetch my node definition, but the agent run will continue:
Warning: Failed to open TCP connection to puppet:8140 (getaddrinfo: Name or service not known)
Info: Retrieving pluginfacts
Error: /File[/var/cache/puppet/facts.d]: Failed to generate additional resources using 'eval_generate': Failed to open TCP connection to puppet:8140 (getaddrinfo: Name or service not known)
Error: /File[/var/cache/puppet/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet:///pluginfacts: Failed to open TCP connection to puppet:8140 (getaddrinfo: Name or service not known)
Info: Retrieving plugin
Error: /File[/var/cache/puppet/lib]: Failed to generate additional resources using 'eval_generate': Failed to open TCP connection to puppet:8140 (getaddrinfo: Name or service not known)
Error: /File[/var/cache/puppet/lib]: Could not evaluate: Could not retrieve file metadata for puppet:///plugins: Failed to open TCP connection to puppet:8140 (getaddrinfo: Name or service not known)
Error: Could not retrieve catalog from remote server: Failed to open TCP connection to puppet:8140 (getaddrinfo: Name or service not known)
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
Error: Could not send report: Failed to open TCP connection to puppet:8140 (getaddrinfo: Name or service not known)
MASTER CONF FILE: /etc/puppet/puppet.conf:
[main]
ssldir = /var/lib/puppet/ssl
logdir = /var/log/puppet
localconfig = $vardir/localconfig
classfile = $vardir/classes.txt
[master]
environment = production
server = puppet-server
ca_server = puppet-server
vardir = /var/lib/puppet
cadir = /var/lib/puppet/ssl/ca
dns_alt_names = puppet
MASTER /etc/hosts:
127.0.0.1 localhost
127.0.1.1 parallels-Parallels-Virtual-Platform
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
192.168.64.14 puppet-server
192.168.64.16 node-01
AGENT CONF FILE: /etc/puppet/puppet.conf:
[main]
ssldir = /var/lib/puppet/ssl
vardir = /var/lib/puppet
cadir = /var/lib/puppet/ssl/ca
dns_alt_names = puppet
[agent]
server=192.168.64.14
ca_server=192.168.64.14
AGENT /etc/hosts:
127.0.0.1 localhost
127.0.1.1 parallels-Parallels-Virtual-Platform
192.168.64.14 puppet-server
192.168.64.16 node-01
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
As the error message says:
Failed to open TCP connection to puppet:8140 (getaddrinfo: Name or service not known)
It cannot find the host puppet.
If you add that to /etc/hosts on your client and server, it should work:
192.168.64.14 puppet
If you run puppet agent -t as a non-root user, Puppet creates a configuration folder structure under ~/.puppetlabs and ignores /etc/puppetlabs/puppet/* (source: https://puppet.com/docs/puppet/latest/dirs_confdir.html, you can pick your version from the drop-down if you're not using the latest)
If you can, try running as root (sudo -i first, then run puppet agent -t) or try with sudo (which does not work for me, but may for you).
check if you open port 8140.
telnet puppet-server 8140
I have two vm in same network, I type listen_address and rpc_address in cassandra.yaml file for each node.I have edited only these three property rest of all default settings.
Here how my cassandra.yaml files looking:
vm1(ip:192.168.0.35): vm2(ip:192.168.0.36):
listen_address: 192.168.0.35 listen_address: 192.168.0.36
rpm_address: 192.168.0.35 rpc_address: 192.168.0.36
seeds: "192.168.0.36" seeds: "192.168.0.36"
And I start both of them and check bin/nodetool status
but each node running seperately not talking in each other.
I watch a sample in cassandra 2.1 and these are the only things he did and it works but not mine..
Anyone got idea ? or tried this in cassandra 3.x version ?
EDITED: here is a command message from cassandra that he is handshaking with the other node:
but he is not in the list(nodetool status) somehow..
/etc/hosts:
127.0.0.1 localhost
127.0.1.1 ubuntu
192.168.0.35 Node2
192.168.0.36 Node3
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
System & Tools:
OS: Ubuntu 14.04 64bit
vagrant_1.8.1_x86_64
virtualbox-5.0_5.0.12-104815~Ubuntu~trusty_amd64
(VM) https://atlas.hashicorp.com/laravel/boxes/homestead-7/versions/0.2.1/providers/virtualbox.box
Im having problem with laravel & vagrant setup. The same setups used to work with laravel 5.1 but now with 5.2 its stopped working.
When I open the URL http://laravel.app it redirect to my localhost page not laravel app.
But if i do http://laravel.app:8000/ it gives Unable to connect firefox can't establish a connection to the server at laravel.app:8000.
Please guide me what i'm doing wrong. i'm new to laravel and vagrant and did managed to run 5.1 few weeks ago but now 5.2 is stcuk with virtualbox php 7
Instructions followed from laravel site:
https://laravel.com/docs/5.2
https://laravel.com/docs/5.2/homestead
~.homestead/Homestead.yaml
---
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox
authorize: ~/.ssh/id_rsa.pub
keys:
- ~/.ssh/id_rsa
folders:
- map: ~/www/sites
to: /home/vagrant/Code
sites:
- map: laravel.app
to: /home/vagrant/Code/Laravel/public
databases:
- homestead
# blackfire:
# - id: foo
# token: bar
# client-id: foo
# client-token: bar
# ports:
# - send: 50000
# to: 5000
# - send: 7777
# to: 777
# protocol: udp
hosts
127.0.0.1 localhost
127.0.1.1 raven
192.168.10.10 laravel.app
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
Forwarding ports...
default: 80 (guest) => 8000 (host) (adapter 1)
default: 443 (guest) => 44300 (host) (adapter 1)
default: 3306 (guest) => 33060 (host) (adapter 1)
default: 5432 (guest) => 54320 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
Your /etc/hosts file should point your domain to 127.0.0.1, this is because homestead forwards 127.0.0.1:8000 to port 80 on your vagrant box. In this case 192.168.10.10:80.
So your /etc/hosts should look like this
127.0.0.1 laravel.app
In your browser you should then access http://laravel.app:8000/
Thanks to #Wader for helping me out. With his help I found the problem.
Coming from Windows user experience the case sensitive names got me this time.
The homestead.yaml file had Laravel as site directory while my directory name was in lower case laravel. I capitalised the directory and it worked. Along with the IP change and appending the port as suggested by #Warden
Try placing
box: laravel/homestead-7
at the top of your homestead.yaml file
Then in terminal enter homestead ssh
then type in serve laravel.app /home/vagrant/Code/laravel/public
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 months ago.
Improve this question
I'm having an issue where my remote command-line cannot resolve the local hostname. It doesn't show as user#localhost, user#ip or any variant, but instead as user#(none):
Using username "rogue".
rogue#<my-ip>'s password:
Linux (none) 3.13.7-x86_64-linode38 #1 SMP Tue Mar 25 12:59:48 EDT 2014 x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Apr 27 15:34:56 2014 from ---
rogue#(none):~$
Any proceeding commands cause this warning message:
rogue#(none):~$ sudo service nginx start
sudo: unable to resolve host (none)
[sudo] password for rogue:
Looking at my hosts and hostname files, I'm not seeing anything out of the ordinary:
/etc/hostname
127.0.0.1 localhost
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
/etc/hosts
127.0.0.1 localhost
127.0.1.1 debian
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
What could potentially be wrong with my network configuration? If possible, I would like that it says user#my.domain, but I need localhost to still route correctly to 127.0.0.1
Your /etc/hostname is very wrong.
It should be plain text of FQDN, like example.com or localhost, instead of a similar copy of /etc/hosts
You may want to use command hostname to view and set hostname, man it
What about these commands?
hostname here.yourhost.name
sudo sed -i "s|localhost|localhost $(hostname)|g" /etc/hosts
adding hostname next to other, localhost names in /etc/hosts