Pulseaudio problem , snd_pcm_open failed: Connection refused.

Hello everyone, i have this problem that appeared last week.
I cant play music in any player cause i get this error : snd_pcm_open failed: Connection refused.
i tried things like adding the user to audio group, creating a "pulse" user cause pulseaudio gave me an error like "pulse user" not existent .
but if i test the sound card in the kde4 audio setup it works
anyone have any ideea on how to fix this ?

just restart alsa.
sudo /etc/rc.d/alsa restart
it solved my problem.

Similar Messages

Problems with SSH: Connection Refused

Greetings fellow Arch users,
I have hit a bit of a snag that I could really use some extra help getting around. I've tried everything I can think of (and everything that Google thought might work) and I have my back rather against a wall, so I thought I'd come here to see if anyone can offer some advice.
To make a long story short, I am a college student and am attempting to set up an ssh server on a desktop at my house so I can access it remotely from the college. I have the computer set up and the server running, however I am having difficulty making connections to it from my laptop. I know that the server is running, because I can log into it both from the server itself (sshing into local host) and from my laptop when I use the internal IP address.
The server is on a static IP address within the network(192.168.0.75), and my router is configured to forward TCP port 1500 to it (I'm using 1500 as the port for my ssh server). However, when I attempt to log into the ssh server using my network's external IP address, the connection is refused. I used nmap to scan my network and found that, even though the proper ports are forwarded to the proper place as far as my Router's configuration interface is concerned, port 1500 is not listed as one of the open TCP ports. I also, to test it, temporarily disabled the firewalls on both the server and the client. That didn't help. The command that I am running is:
ssh -p 1500 douglas@[external ip address
As I am really not sure what is causing this problem, I don't know what information to provide. So here is everything that my inexperienced mind sees as likely being important. If you need anything more, let me know and I will do my best to provide it.
Here is the sshd_config file from my server.
# This is the sshd server system-wide configuration file. See
# sshd_config(5) for more information.
# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin
# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented. Uncommented options override the
# default value.
Port 1500
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::
# The default requires explicit activation of protocol 1
#Protocol 2
# HostKey for protocol version 1
#HostKey /etc/ssh/ssh_host_key
# HostKeys for protocol version 2
#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_dsa_key
#HostKey /etc/ssh/ssh_host_ecdsa_key
# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 1024
# Ciphers and keying
#RekeyLimit default none
# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
#LogLevel INFO
# Authentication:
#LoginGraceTime 2m
PermitRootLogin no
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10
#RSAAuthentication yes
#PubkeyAuthentication yes
# The default is to check both .ssh/authorized_keys and .ssh/authorized_keys2
# but this is overridden so installations will only check .ssh/authorized_keys
AuthorizedKeysFile .ssh/authorized_keys
#AuthorizedPrincipalsFile none
#AuthorizedKeysCommand none
#AuthorizedKeysCommandUser nobody
# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#RhostsRSAAuthentication no
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes
# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no
# Change to no to disable s/key passwords
ChallengeResponseAuthentication no
# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no
# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes
# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication. Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM yes
#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
#X11Forwarding no
#X11DisplayOffset 10
#X11UseLocalhost yes
PrintMotd no # pam does that
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
UsePrivilegeSeparation sandbox # Default for new installations.
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS yes
#PidFile /run/sshd.pid
#MaxStartups 10:30:100
#PermitTunnel no
#ChrootDirectory none
#VersionAddendum none
# no default banner path
#Banner none
# override default of no subsystems
Subsystem sftp /usr/lib/ssh/sftp-server
# Example of overriding settings on a per-user basis
#Match User anoncvs
# X11Forwarding no
# AllowTcpForwarding no
# ForceCommand cvs server
The ouptut of ip addr when run on the server:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp8s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:21:9b:3a:be:94 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.75/24 brd 192.168.255.0 scope global enp8s0
valid_lft forever preferred_lft forever
inet6 fe80::221:9bff:fe3a:be94/64 scope link
valid_lft forever preferred_lft forever
Here is the output from running nmap on the network:
Starting Nmap 6.40 ( http://nmap.org ) at 2013-09-28 21:05 EDT
Initiating Ping Scan at 21:05
Scanning address [2 ports]
Completed Ping Scan at 21:05, 0.01s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 21:05
Completed Parallel DNS resolution of 1 host. at 21:05, 0.05s elapsed
Initiating Connect Scan at 21:05
Scanning pa-addresss.dhcp.embarqhsd.net (address) [1000 ports]
Discovered open port 80/tcp on address
Discovered open port 443/tcp on address
Discovered open port 23/tcp on address
Discovered open port 21/tcp on address
Completed Connect Scan at 21:05, 4.08s elapsed (1000 total ports)
Nmap scan report for pa-address.dhcp.embarqhsd.net (address)
Host is up (0.036s latency).
Not shown: 995 closed ports
PORT STATE SERVICE
21/tcp open ftp
23/tcp open telnet
80/tcp open http
443/tcp open https
8080/tcp filtered http-proxy
Read data files from: /usr/bin/../share/nmap
Nmap done: 1 IP address (1 host up) scanned in 4.19 seconds
Here is the ssh_config client-side:
# $OpenBSD: ssh_config,v 1.27 2013/05/16 02:00:34 dtucker Exp $
# This is the ssh client system-wide configuration file. See
# ssh_config(5) for more information. This file provides defaults for
# users, and the values can be changed in per-user configuration files
# or on the command line.
# Configuration data is parsed as follows:
# 1. command line options
# 2. user-specific file
# 3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.
# Site-wide defaults for some commonly used options. For a comprehensive
# list of available options, their meanings and defaults, please see the
# ssh_config(5) man page.
# Host *
# ForwardAgent no
# ForwardX11 no
# RhostsRSAAuthentication no
# RSAAuthentication yes
# PasswordAuthentication yes
# HostbasedAuthentication no
# GSSAPIAuthentication no
# GSSAPIDelegateCredentials no
# BatchMode no
# CheckHostIP yes
# AddressFamily any
# ConnectTimeout 0
# StrictHostKeyChecking ask
# IdentityFile ~/.ssh/identity
# IdentityFile ~/.ssh/id_rsa
# IdentityFile ~/.ssh/id_dsa
# Port 22
Protocol 2
# Cipher 3des
# Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc
# MACs hmac-md5,hmac-sha1,[email protected],hmac-ripemd160
# EscapeChar ~
# Tunnel no
# TunnelDevice any:any
# PermitLocalCommand no
# VisualHostKey no
# ProxyCommand ssh -q -W %h:%p gateway.example.com
# RekeyLimit 1G 1h
Output of ssh -v during connection attempt:
OpenSSH_6.3, OpenSSL 1.0.1e 11 Feb 2013
debug1: Reading configuration data /home/douglas/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Connecting to address [address] port 1500.
debug1: connect to address address port 1500: Connection refused
ssh: connect to host address port 1500: Connection refused
Thank you guys ahead of time. Getting this server operational is hardly critical, it is just a side project of mine, but I would really like to see it working.
Douglas Bahr Rumbaugh
Last edited by douglasr (2013-09-29 02:58:56)

Okay, so I finally have the opportunity to try and log in from a remote network. And. . . it doesn't work. Which is just my luck because I now need to wait an entire week, at least, before I can touch the server again. Anyway, running ssh with the maximum verbosity I get this output:
douglas ~ $ ssh -vvv -p 2000 address
OpenSSH_6.3, OpenSSL 1.0.1e 11 Feb 2013
debug1: Reading configuration data /home/douglas/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Connecting to address [address] port 2000.
debug1: connect to address address port 2000: Connection timed out
ssh: connect to host address port 2000: Connection timed out
It takes a minute or two for the command to finish with the connection timeout, as one would expect. And yes, I am reasonably sure that the address that I am using is my home network's external IP. It is dynamic, but I checked it before I left which was just over an hour ago. I guess that it may have changed. I'll know that for sure in the morning, when my server sends me an automatic email with the network's current address. In the meantime I am operating under the assumption that the address I am using is correct. What else could be the problem?

Tcp/ip bconnection to host has failed,connection refused

Exception in thread "main" com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed. java.net.ConnectException: Connection refused: connect at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.loginWithoutFailover(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(Unknown Source) at java.sql.DriverManager.getConnection(UnknownSource)
Can anyone pls help me out .
I ve tried netstat -an port 1433 is not listed
firewall is diasbled .

You need to enable TCP services on SQL Server.

Certificate authority export fails connection refused

I am trying to export zenwork certificate and I receive the following error:
Command
zman --debug certificate-authority-export /root/cert
Error:Could not connect to the ZENworks Server. Ensure that the server is running, and the host and port information specified is correct.
Debug:
com.novell.zenworks.datamodel.exceptions.Connectio nException: Connection refused
What can I look at?

zman certificate-authority-export /root/cert --debug
Error:Could not connect to the ZENworks Server. Ensure that the server is runnin g, and the host and port information specified is correct.
Debug:
com.novell.zenworks.datamodel.exceptions.Connectio nException: Connection refused
at com.novell.zenworks.zman.exceptions.ZManExceptionH andler.createExcept ion(ZManExceptionHandler.java:286)
at com.novell.zenworks.zman.exceptions.ZManExceptionH andler.makeDataMode lException(ZManExceptionHandler.java:260)
at com.novell.zenworks.zman.exceptions.ZManExceptionH andler.processRemot eException(ZManExceptionHandler.java:390)
at com.novell.zenworks.zman.commands.CAHandler.<init> (CAHandler.java:72)
at sun.reflect.NativeConstructorAccessorImpl.newInsta nce0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInsta nce(NativeConstruct orAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newI nstance(DelegatingC onstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Construc tor.java:501)
at com.novell.zenworks.zman.CommandRunner.execute(Com mandRunner.java:86)
at com.novell.zenworks.zman.ZMan.executeRunner(ZMan.j ava:321)
at com.novell.zenworks.zman.ZMan.main(ZMan.java:505)
Caused by: java.rmi.ConnectException: Connection refused
at com.novell.soa.ws.portable.ApplicationException.ma pToRemote(Applicati onException.java:207)
at com.novell.zenworks.datamodel.services.zoneconfig. soap.ZoneConfigAdmi nServiceBinding_Stub.hasZENServerRole(ZoneConfigAd minServiceBinding_Stub.java:50 71)
at com.novell.zenworks.zman.commands.CAHandler.<init> (CAHandler.java:68

RemoteGui.bat Login attempt failed:connection refuse to SDM

Heloo Guru's,
I am trying to deploy service via running path: D:\usr\sap\XIG\DVEBMGS00\SDM\program <b>RemoteGui.bat</b> file .
I am giving password for SDM user but error coming on clicking login button
Error:could not establish connection to server <host> at port <50018>:connection refused:connect.
Please advise.

Hi Gaurav,
You can find the SDM configuration file in \usr\sap\<system_id>\<instance no>\SDM\program\config with file name sdmrepository.sdc. In this file you will find your sdm host name and gui port number (default 50018). You change it from here and restart the server if its not set properly.
Go to the mmc, select your serve node, expand instance 0 and look at the process table, you should have dispatcher / server0 and SDM nodes with their states set as started.
It is possible that SDM was kept in standalone mode and not started with your server. If that is the case
Run sdm jstartup "mode=integrated"
restart your cluster.
Regards,
Prateek

Mpd and pulse problem - Connection refused [SOLVED]

I'm having problems getting mpd to play nice with pulse-audio. Pulse is installed and works with vlc, mplayer, flash, etc. just fine. When I try to play through mpd the song in the gui simply shows a status of "paused" and the following gets written to the mpd.log.
Advice is appreciated.
# tail -f /var/log/mpd/mpd.log
Oct 08 11:12 : output: Failed to enable "pulse audio" [pulse]: pa_context_connect() has failed: Connection refused
Oct 08 11:12 : output: Failed to enable "pulse audio" [pulse]: pa_context_connect() has failed: Connection refused
Oct 08 11:12 : output: Failed to enable "pulse audio" [pulse]: pa_context_connect() has failed: Connection refused
Oct 08 11:12 : player_thread: problems opening audio device while playing "Not_So_Hard_Stuff/Disturbed-The Sickness-2000/01_Voices.flac"
Here is my mpd.conf
$ sed '/#/d' /etc/mpd.conf
music_directory "/media/data/all_genres"
playlist_directory "/var/lib/mpd/playlists"
db_file "/var/lib/mpd/mpd.db"
log_file "/var/log/mpd/mpd.log"
pid_file "/var/run/mpd/mpd.pid"
state_file "/var/lib/mpd/mpdstate"
user "mpd"
gapless_mp3_playback "yes"
zeroconf_enabled "yes"
zeroconf_name "Music Player"
input {
plugin "curl"
audio_output {
type "pulse"
name "pulse audio"
mixer_type "software"
audio_buffer_size "35000"
buffer_before_play "5%"
The pulseaudio wiki suggests that a 'pulse' group and 'pulse-access' and even 'pulse-rt' groups may be required? I have used mpd for a year now with no such groups on my system.
EDIT: solved in post #13
Last edited by graysky (2011-10-16 13:42:46)

graysky wrote:
I too modified my /etc/mpd.conf to use alsa even though I don't have alsa-utils installed at all.
$ sed '/#/d' /etc/mpd.conf
music_directory "/media/data/all_genres"
playlist_directory "/var/lib/mpd/playlists"
db_file "/var/lib/mpd/mpd.db"
log_file "/var/log/mpd/mpd.log"
pid_file "/var/run/mpd/mpd.pid"
state_file "/var/lib/mpd/mpdstate"
user "mpd"
gapless_mp3_playback "yes"
zeroconf_enabled "yes"
zeroconf_name "Music Player"
input {
plugin "curl"
audio_output {
type "alsa"
name "My ALSA Device"
mixer_type "software"
audio_buffer_size "35000"
buffer_before_play "5%"
Doesn't work for me I get this error when I try to play something with your configuration:
ALSA lib pulse.c:229:(pulse_connect) PulseAudio: Unable to connect: Connection refused
Oct 16 18:23 : output: Failed to open "My ALSA Device" [alsa]: Failed to open ALSA device "default": Connection refused

Decision Service calls failing with connection refused

Hi All,
Breifing of the bpel process - Async bpel process XX_BPEL_ASYNC_002 calls decision services and a sync bpel process XX_BPEL_SYNC_001.
We have moved to cluster 10.1.3.5.0 from 10.1.3.3.0 and the deployement of the bpel process and the decision service done on two nodes i.e., node51 and node55.
But the bpel process is able to call the decision service only when the node 51 is UP and running, but if node 51 is down and node 55 is up and running it is failing with connection refused error. It is also working when 55 is DOWN and 051 is UP.
the exact error is:
exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection refused.
We are using file based repository.
It is failing when it tries to call particular url:
http://loadbalancerurl:7777/orabpel/domain001/XX_BPEL_ASYNC_002/1.0/decisionservices.decs
Can anyone please help me or advice me for finding some solution.
Thanks
Sreejit

Hi Fatsah,
It has been a while since we resolved this problem. But these were the basic steps that we had taken.
The receiver was configured a File adatpter with FTP:
Port: 10021
Connection security : FTPS (FTP using SSL/TLS) for Control and Data Connection
Command Order: AUTH TLS,USER,PASS,PBSZ,PROT
Problem: The message was blocked in our firewall.
FTPS in this case used 10021 as the control port and the firewall allowed to pass the control request.
Once the connection was accepted at the control level, it generated a random port number to pass data on the channel.
This random port number was blocked in the firewall.
We monitored the data port numbers generated at firewall. Then we configured the firewall to open any port number between the specific IP addresses of the sender and the receiver. That resolved the problem.
Hope this helps!
Please give points if this is helpful.
Thank you.
Dharmasiri Amith

Pulse Audio Not Working (Connection Refused)

Thank you in advanced for your help. I am having issues getting pulse audio to work. I have followed the wiki to a tee. However, i am getting
pactl load-module module-equalizer-sink
pactl load-module module-equalizer-sink
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
qpaeq
There was an error connecting to pulseaudio, please make sure you have the pulseaudio dbus and equalizer modules loaded, exiting.
Any help ,
Thanks

Thank you in advanced for your help. I am having issues getting pulse audio to work. I have followed the wiki to a tee. However, i am getting
pactl load-module module-equalizer-sink
pactl load-module module-equalizer-sink
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
qpaeq
There was an error connecting to pulseaudio, please make sure you have the pulseaudio dbus and equalizer modules loaded, exiting.
Any help ,
Thanks

SOAP Exception, Connection refused error in jdeveloper 11g

Hello,
I am using jdeveloper 11g 11.1.2.3.0.
I have been experiencing the following error everytime I try to run the applicaiton. I use webservices in my applicaiton and recently the webservices url were changed pointing now to dev instead of the lab environment. The code has been migrated to dev environment, I tested the webservices in my browser, they seem to be working fine and are pulling up the required data.
ERROR:
javax.xml.soap.SOAPException: Message send failed: Connection refused: connect
Error
Message send failed: Connection refused: connect
Error
Connection refused: connect
I am not sure what is causing this. Any help would be appreciated.
Thanks in advance,
Sal

Hello Frank,
Thanks for your response. I checked the browser proxy settings in Jdeveloper, nothing is set there right now. Use HTTP Proxy Server is unchecked. What do I need to set this to?
Thanks,
Sal

Fms edge connected refused with unknown reason.

i found some error logs in edge.*.log, like this.
2012-11-14 18:39:04 3903 (e)2661034 Connect failed ( , 1161928336 ) : Connect failed: Connection refused (111) -
2012-11-14 18:39:46 3903 (e)2661034 Connect failed ( , 16 ) : Connect failed: Connection refused (111) -
2012-11-14 18:40:31 3903 (e)2661034 Connect failed ( , 3 ) : Connect failed: Connection refused (111) -
2012-11-14 19:47:46 3903 (e)2661034 Connect failed ( , 16 ) : Connect failed: Connection refused (111) -
2012-11-14 19:48:28 3903 (e)2661034 Connect failed ( , 16 ) : Connect failed: Connection refused (111) -
2012-11-14 19:49:10 3903 (e)2661034 Connect failed ( , 1170349712 ) : Connect failed: Connection refused (111)
it seems because of invalid ports resulst in TCP connection faild.But abvously, these ports are not used in the applications, even some port is out of valid port range. Does anyone konws what the reason.
btw, there are two adaptors on our machine, one is for intranet, the other is for internet. And the lattter is configured with to IPs
like this:
eth0      Link encap:Ethernet HWaddr 00:21:5E:26:62:28
          inet addr:******* Bcast:******* Mask:255.255.255.0
          inet6 addr: fe80::221:5eff:fe26:6228/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:116994653 errors:0 dropped:0 overruns:0 frame:0
          TX packets:151851798 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:52655302829 (49.0 GiB) TX bytes:124235260628 (115.7 GiB)
          Interrupt:106 Memory:ce000000-ce012800
eth0:1    Link encap:Ethernet HWaddr 00:21:5E:26:62:28
          inet addr:**** Bcast:**** Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

Is there any info in the node manager log files?
You can try changing the health check timeout.
# Health Check Interval: Specify the interval (in seconds) between Node Manager health state queries to the Managed Server. Enter a value between 1 and 2147483647 seconds (default is 180 seconds).
# Health Check Timeout: Enter the number of seconds that Node Manager will await a response to a health state query. If the timeout is reached, Node Manager assumes the Managed Server is "failed", and kills the process. Enter a value between 1 and 2147483647 seconds (default is 60 seconds).

TCP DNS Connection Refused

I am testing an application which uses tcp for dns.
My ActionTec router is set to "Medium" so it should allow all outbound connections.
When I use a dns server on my network all is well. When I try to use the ActionTec for dns I get connection refused with tcp requests but udp requests go through. I suspect the dns server on the ActionTec does not support tcp but I would like confirmation in case there is a setting I can change to make it work.
$ host yahoo.com
yahoo.com has address 98.138.253.109
yahoo.com has address 98.139.183.24
yahoo.com has address 72.30.38.140
yahoo.com mail is handled by 1 mta5.am0.yahoodns.net.
yahoo.com mail is handled by 1 mta7.am0.yahoodns.net.
yahoo.com mail is handled by 1 mta6.am0.yahoodns.net.
$ host -T yahoo.com
;; Connection to 192.168.1.1#53(192.168.1.1) for yahoo.com failed: connection refused.
Thanks,
AustinPowered

Keep in mind the ActionTecs are based around the dnsmasq lightweight DNS resolver if I remember correctly. If Verizon/ActionTec is using a version of dnsmasq older than v2.10, then it is a known limitation of dnsmasq to not support TCP queries. If someone can confirm what version the FiOS routers have, that would be great. This tool may be able to identify it:
http://netalyzr.icsi.berkeley.edu/
If you'd like me to analyze it, please send me a private message with the URL to your result, unless you don't mind your IP address being given out to the forums.
========
The first to bring me 1Gbps Fiber for $30/m wins!

Connection refused: proxy: HTTP: attempt to connect to failed [error] ap_proxy_connect_backend disabling worker

Hi all,
I'm investigating cause of a wedged wiki this morning. The MacMini (10.7.5) was working well for the last year but we're not sure when it gave up the ghost.
I've already applied the fixes detailed at Mac OS X v10.5, Mac OS X Server v10.5: Web, Mail, Wiki, Personal Web Sharing, Parental Controls services may not start after restoring a Time Machine backup but it has't helped.
The error we see when we visit the top level of the server is:
Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Apache/2.2.22 (Unix) PHP/5.3.15 with Suhosin-Patch mod_ssl/2.2.22 OpenSSL/0.9.8r DAV/2 Server at sacmini.local Port 80
The message in the httpd error logs is:
Connection refused: proxy: HTTP: attempt to connect to failed [error] ap_proxy_connect_backend disabling worker
Let me know if you have any ideas. Thank you.
--Athonia

Thanks for the reply.
So, there were some Ruby related log file entries. Do these have any meaning to you? I'm checking to see what collabcored2 does exactly.
May 7 14:22:33 sacmini com.apple.collabcored2[22106]:
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygem s/custom_require.rb:31:in `require'
May 7 14:22:33 sacmini com.apple.collabcored2[22106]:
from /usr/share/collabd/coreclient/config/environment.rb:11
May 7 14:22:33 sacmini com.apple.collabcored2[22106]:
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygem s/custom_require.rb:31:in `gem_original_require'
May 7 14:22:33 sacmini com.apple.collabcored2[22106]:
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygem s/custom_require.rb:31:in `require'
May 7 14:22:33 sacmini com.apple.collabcored2[22106]:
from /usr/share/collabd/coreclient/config.ru:13
May 7 14:22:33 sacmini com.apple.collabcored2[22106]:
from /Library/Ruby/Gems/1.8/gems/rack-1.2.1/lib/rack/builder.rb:46:in `instance_eval'
May 7 14:22:33 sacmini com.apple.collabcored2[22106]:
from /Library/Ruby/Gems/1.8/gems/rack-1.2.1/lib/rack/builder.rb:46:in `initialize'
May 7 14:22:33 sacmini com.apple.collabcored2[22106]:
from /usr/share/collabd/coreclient/config.ru:1:in `new'
May 7 14:22:33 sacmini com.apple.collabcored2[22106]:
from /usr/share/collabd/coreclient/config.ru:1
May 7 14:22:33 sacmini com.apple.launchd[1] (com.apple.collabcored2[22106]): Exited with code: 1
May 7 14:22:33 sacmini com.apple.launchd[1] (com.apple.collabcored2): Throttling respawn: Will start in 9 seconds

Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)

Hello All,
There are some changes in out portal sever, but not related to SAP EP.
So it is needed to restart the server. After restarting the server,
we are not avail to start the server. There is nothing in the SAPMMC.
"There is no item to display" is showing in the SAPMMC.
So we tried couple of time to get the SAPMMC icons by restarting the server.
But it is not getting any display in SAPMMC.
I am sending some part of the latest log file of that server below:
Our server name is INMAA02AS03.
1.5#00145E3D3B630046000000000000175000041A3F6EB5EB39#1154759649523#com.sap.engine.core.cluster.impl6.ms.MSEventListener##com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(protocol, port, serverCount)#######OrderedChannel for http service##0#0#Error##Plain###java.net.SocketException: Socket closed#
#1.5#00145E3D3B630046000000010000175000041A3F6EB5EC0B#1154759649523#com.sap.engine.core.cluster.impl6.ms.MSEventListener##com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(protocol, port, serverCount)#######OrderedChannel for http service##0#0#Error##Plain###java.net.SocketException: Socket closed
     at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:99)
     at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
     at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:66)
     at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:124)
     at com.sap.engine.core.cluster.impl6.ms.MSMessageHeader.write(MSMessageHeader.java:401)
     at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawMessage(MSRawConnection.java:1017)
     at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawMessage(MSRawConnection.java:971)
     at com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(MSEventListener.java:1374)
     at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.putLogonInfo(MSConnectionImpl.java:605)
     at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.putLogonInfo(ClusterManagerImpl.java:3144)
     at com.sap.engine.core.service630.context.cluster.session.CommunicationSessionContextImpl.putLogonInfo(CommunicationSessionContextImpl.java:143)
     at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.putLogonInfo(HttpDispatcherFrame.java:854)
     at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.closeSocket(HttpDispatcherFrame.java:800)
     at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.stop(HttpDispatcherFrame.java:404)
     at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:31)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)
     at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)
#1.5#00145E3D3B630046000000020000175000041A3F6EB5F178#1154759649523#com.sap.engine.services.httpserver.dispatcher##com.sap.engine.services.httpserver.dispatcher#######OrderedChannel for http service##0#0#Error##Plain###Cannot update HTTP load balancing information in the Message service
com.sap.engine.frame.cluster.ClusterException: Socket closed
     at com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(MSEventListener.java:1377)
     at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.putLogonInfo(MSConnectionImpl.java:605)
     at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.putLogonInfo(ClusterManagerImpl.java:3144)
     at com.sap.engine.core.service630.context.cluster.session.CommunicationSessionContextImpl.putLogonInfo(CommunicationSessionContextImpl.java:143)
     at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.putLogonInfo(HttpDispatcherFrame.java:854)
     at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.closeSocket(HttpDispatcherFrame.java:800)
     at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.stop(HttpDispatcherFrame.java:404)
     at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:31)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)
     at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)
Caused by: java.net.SocketException: Socket closed
     at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:99)
     at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
     at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:66)
     at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:124)
     at com.sap.engine.core.cluster.impl6.ms.MSMessageHeader.write(MSMessageHeader.java:401)
     at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawMessage(MSRawConnection.java:1017)
     at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawMessage(MSRawConnection.java:971)
     at com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(MSEventListener.java:1374)
     ... 10 more
#1.5#00145E3D3B6300400000000B0000175000041A3F6EC43762#1154759650461#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000000D0000175000041A3F6EF146BF#1154759653414#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000000F0000175000041A3F6F1E56B0#1154759656367#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000110000175000041A3F6F4B6526#1154759659320#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000130000175000041A3F6F787519#1154759662273#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000150000175000041A3F6FA584C7#1154759665226#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000170000175000041A3F6FD29438#1154759668179#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000190000175000041A3F70014F86#1154759671242#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000001B0000175000041A3F70300A99#1154759674304#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000001D0000175000041A3F705D1A24#1154759677257#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000001F0000175000041A3F705D1B81#1154759677257#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###ReadThread: failed to connect to server 11 times#
#1.5#00145E3D3B630040000000210000175000041A3F708A296B#1154759680210#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000230000175000041A3F70B738CB#1154759683163#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000250000175000041A3F70E4487A#1154759686116#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000270000175000041A3F7111581F#1154759689069#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000290000175000041A3F713E67B3#1154759692022#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000002B0000175000041A3F716B77A1#1154759694976#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000002D0000175000041A3F719886C2#1154759697929#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000002F0000175000041A3F71C596D5#1154759700882#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000310000175000041A3F71F45176#1154759703944#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000330000175000041A3F72230C96#1154759707007#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000350000175000041A3F72230DF3#1154759707007#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###ReadThread: failed to connect to server 21 times#
#1.5#00145E3D3B630040000000370000175000041A3F72501BF9#1154759709960#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000390000175000041A3F727D2BC1#1154759712913#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000003B0000175000041A3F72AA3BCA#1154759715866#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000003D0000175000041A3F72D74B1A#1154759718819#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000003F0000175000041A3F73045A4C#1154759721772#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000410000175000041A3F73316A0D#1154759724725#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000430000175000041A3F735E799A#1154759727678#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000450000175000041A3F738D34D0#1154759730740#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000470000175000041A3F73BBEF81#1154759733803#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000490000175000041A3F73E8FF05#1154759736756#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000004B0000175000041A3F73E90064#1154759736756#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###ReadThread: failed to connect to server 31 times#
#1.5#00145E3D3B6300400000004D0000175000041A3F74160E68#1154759739709#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000004F0000175000041A3F74431E16#1154759742662#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000510000175000041A3F74702DEA#1154759745615#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000530000175000041A3F749D421D#1154759748568#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000550000175000041A3F74CA4CD6#1154759751521#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000570000175000041A3F74F75CC8#1154759754474#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000590000175000041A3F75246C5C#1154759757427#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000005B0000175000041A3F75517C0B#1154759760381#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000005D0000175000041A3F7580368E#1154759763443#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000005F0000175000041A3F75AEF19A#1154759766505#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000610000175000041A3F75AEF2F2#1154759766505#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###ReadThread: failed to connect to server 41 times#
Any idea what to do?
Please help me out.
**Points will be rewarded for a suitable answer.
Regards,
Uttam.

Hi Uttam,
Were you able to solve the problem? I am also getting a similar error message. If you had solved your problem, please share, how?
Thanks & Regards,
Santhosh.C

Opmn fails with connection refused

Hi all,
I've successfully installed Oracle Application Server 10g AS R2.
After installation I could successfull login and access both Infra and Middle Tier using OEM, which were configured under a single Farm.
But unfortunately, after and when the server is restarted... opmnctl startall hangs with ons.log contents as below
08/06/23 16:25:14 [4] ONS server initiated
08/06/23 16:53:15 [4] Logging disabled
08/06/23 16:57:43 [4] ONS server initiated
08/06/23 16:57:43 [4] Connection 1,192.168.6.183,6201 connect (Connection refused)
08/06/23 16:59:42 [4] Connection 1,192.168.6.183,6201 connect (Connection refused)
08/06/23 17:01:41 [4] Connection 1,192.168.6.183,6201 connect (Connection refused)
08/06/23 17:03:40 [4] Connection 1,192.168.6.183,6201 connect (Connection refused)08/06/23 17:04:00 [4] Logging disabled
As a workaround I verified /etc/hosts file... it is as below
127.0.0.1 localhost.localdomain localhost
192.168.6.183 oravis.dsrc2.com oravis
I'm performing the start-up & shutdown in the following order
START DB Tier
Start Database as
Make sure your are in DB Home
$ sqlplus "/as sysdba"
SQL> startup
Start DB Listener as
Make sure your are in DB Home
$ lsnrctl start RETEK
Startup 10gAS Server
Start Middle Tier iAS Console
Make sure your are in Middle Tier Home
cd $ORACLE_HOME/bin
emctl start iasconsole
Start Infra iAS Console
Make sure your are in Infra Home
cd $ORACLE_HOME/bin
emctl start iasconsole
Start Infra listener as
$ lsnrctl start
Start Infra Database as -
$sqlplus "/as sysdba"
SQL> startup
Start Infra OC4J Services as
Make sure your are in Infra Home
$./opmnctl startall
Start Middle Tier OC4J Services as
Make sure your are in Middle Tier Home
$./opmnctl startall
Shutdown 10gAS Server
Stop Middle Tier Services as
Make sure your are in Middle Tier Home
cd $ORACLE_HOME/opmn/bin
$./opmnctl stopall
Stop Infrastructure Services as
Make sure your are in Infra Home
$ ./opmnctl stopall
Stop Infra Listener as
Make sure your are in Infra Home
$ lsnrctl stop [listener_name]
Stop Infra Database as
Make sure your are in Infra Home
$ sqlplus "/as sysdba"
SQL> shutdown immediate
Stop Infra iAS Console
Make sure your are in Infra Home
cd $ORACLE_HOME/bin
emctl stop iasconsole
Stop Middle Tier iAS Console
Make sure your are in Middle Tier Home
cd $ORACLE_HOME/bin
emctl stop iasconsole
Stop DB Tier
Stop Listener as
Make sure your are in DB Home
$ lsnrctl stop [listener_name]
Stop Database as
Make sure your are in DB Home
$ sqlplus "/as sysdba"
SQL> shutdown immediate
Now... I'm able to access the Infra & Middle tier throgh OEM but the status is Unavailable. Moreover now they not under the Farm (Which they were earlier in).
Also it is giving error connecting to repository database.
Please anybody, who have come across this kind of problem, kindly guide me, where actually I'm missing.
-Mahesh

Hi Adith,
Thanx a lot for the updates and correcting me. I've gone through the documents and corrected the way by which I was starting the services.
But... when I try to do opmnctl startall, now I again got struck up with this strange error in ons.log
08/06/24 10:26:02 [4] ONS server initiated
08/06/24 10:47:51 [2] Connection 1,192.168.6.183,1521 SSL handshake failed
08/06/24 10:47:51 [2] Handshake for 1,192.168.6.183,1521: nz error = 28864 interval = 0 (180 max)
08/06/24 10:49:50 [2] Connection 1,192.168.6.183,1521 SSL handshake failed
08/06/24 10:49:50 [2] Handshake for 1,192.168.6.183,1521: nz error = 28864 interval = 0 (180 max)
08/06/24 10:51:49 [2] Connection 1,192.168.6.183,1521 SSL handshake failed
08/06/24 10:51:49 [2] Handshake for 1,192.168.6.183,1521: nz error = 28864 interval = 0 (180 max)
I've gone through metalink and found out that this is a problem with SSL Authentication which been stated as a bug.
Can anybody answer my following queries...
1. Is it mandatory to enable SSL in 10g AS? Can we run server without SSL?
2. If not mandatory, then how to disable SSL?
3. If the handshake error is a bug, how to fix? Do I need to apply any patch for this?
Looking forward for immediate response,
Regards
-Mahesh

FAIL: NIECONN_REFUSED (EDC8128I Connection refused.),

Hi All,
We are receiving the message "FAIL: NIECONN_REFUSED (EDC8128I Connection refused.)," on our CI server which is on OS/390 Operating system. The message comes every time when we restart our SAP system.
Our application server's are on AIX 5.3 Operating system, but the error is coming on CI (Central Instance) which is on MAinframe.
Regards
BAsis Team

Hi,
I have similar problem, it arised after the change of the kernel.
Sapstartsrv is not started, the abend S0C4 is in the z/OS system log and in the work directory is CEEDUMP.
Regards
Vladislav

Pulseaudio problem , snd_pcm_open failed: Connection refused.

Similar Messages

Maybe you are looking for