I'm trying to use Ambari.
First, because I cannot use the root permission of lab's server, I tried to start Ambari agent manually.
This is my conf of agent:
The server port is 8082, but I got this error in agent log:
server at http://172.19.104.24:8082 is not reachable.
Before that, I closed the SELinux of server, and added rules in server's iptables. So I can't figure it out.
Have you turned the iptables off? Did you edit the network configuration file (etc/sysconfig/network)? Also try running setenforce 0.
Related
I've setup a weblogic cluster with 2 managed servers.In order to configure node manager on both nodes i've followed the related article :
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/wls/12c/12_2_1/01-12-001-ConfiguringandUsingNodeManager/Configuring_and_Using_NM.html
with the following configuration :
Machine-0 :
DomainsFile=/u01/app/oracle/config/domains/base_domain/Machine-
0/nodemanager.domains
LogLimit=0
PropertiesVersion=12.1.3
AuthenticationEnabled=true
NodeManagerHome=/u01/app/oracle/config/domains/base_domain/Machine-0
JavaHome=/opt/jdk1.8.0_131
LogLevel=INFO
DomainsFileEnabled=true
StartScriptName=startWebLogic.sh
ListenAddress=localhost
NativeVersionEnabled=true
ListenPort=5558
LogToStderr=true
SecureListener=false
LogCount=1
StopScriptEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=500
CrashRecoveryEnabled=false
StartScriptEnabled=true
LogFile=/u01/app/oracle/config/domains/base_domain/Machine-
0/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
Machine-1 (the second managed server) has the same configuration with the exceptions of ports (5557) and name.
Although node manager is successfully started on both machines (startNodeManager.sh on machine-0 and machine-1) from admin console on Machine-0 the following error occurs and node manager doesnt start :
weblogic.nodemanager.NMConnectException
nodemanager.log of Machine-0 has no indications of errors or any helpful stuff.
Any help would be appreciated.
thanks in advance
These are the things that I usually check when I am setting up a new WebLogic domain:
It is possible that the Listen Address of Machine-1 is not correct. Check the Listen Address of the machine from the WebLogic Domain Configuration. It should match the host's machine name. Using localhost might not work because the Admin Server is trying to connect to the Machine-1, which can be on the other server.
Make sure to check if the port is reachable from the Admin Server's machine.
Check that the Node Manager configuration uses Plain instead of SSL connection, as stated in your nodemanager.properties file. Under Environments > Machines, click the machine and go to Configuration Tab, Node Manager. Check if the Type is Plain and not SSL. Changing this will require a restart of the Admin Server.
Please verify the items below before you start nodemanager.
Check if the nodemanager.domains has your domain name listed.
Try to see if the ports are listening using the commands below.
netstat -an|grep 5557
netstat -an|grep 5558
Also, check if the nodemanager is reachable in weblogic console.
I have a server with Apache Directory Server installed. I can connect using the Apache directory studio over 10389. Now I would like to connect on 389 instead of 10389. I go into (as sudo) /var/lib/apacheds-2.0.0_M23/default/conf/ou\=config/ads-directoryserviceid\=default/ou\=servers/ads-serverid\=ldapserver/ou\=transports/ads-transportid\=ldap.ldif and I set ads-systemPort to
ads-systemPort: 389
However, now when I run I see...
java.io.IOException: Error while binding on /0.0.0.0:389
original message : Permission denied
Changing it back to 10389 works great. I am confused because I am using sudo, which should avoid permission issues. What am I doing wrong?
If you start the apache directory server as a service (or like sudo service apacheds... start), it will run as system user apacheds:apacheds and will have permission to listen on any well known port like 389. As a normal user, you usually don't have that permission.
Change ads-transportAddress to your IP address instead of default value in file ads-transportid\=ldap.ldif.
I am facing some problem while starting sql in xampp. here is the screenshotenter image description here
Your SQL is attempting to use port 3306, which is already in use as stated in the error. Go into
Config > Service and Port Settings > Change 3306 to any other unused ports
Restart the service and see if it works.
I am using Jenkins and currently Jenkins is running fine in the background; however, when i am trying to access Jenkins using browser the homepage of Jenkins is not accessible. When I access it I get "Error reading from remote server ( 502 )". Has anyone encountered such an issue? What could be the workaround?
Try to remove proxy: export http_proxy="" && curl http://servername:portnumber/destinationpath/
or use https instead of http or vice-versa ( check which port is your jenkins running on )
Is it running on apache/nginx/whatever? Restart that. Restart Jenkins once more. Check the server configuration regarding those.
Did restart of iptables post which I have seen the issue to be resolved.
service iptables restart
Have a VPS and access to WHM as cpanel.But how can i access the php.ini and also connect using SSH.With SSH getting error
Failed to connect to server:
Network error: Connection refused.
If there is a proxy that is blocking it?
This question is probably better asked at serverfault. Having said that, by default in common Linux distributions (Ubuntu, for example), SSHD is not running by default.
Verify that you are running an SSH server, and if you are still having issues, this is better taken somewhere more relevant.