similar to: bind: Address already in use

Displaying 20 results from an estimated 50000 matches similar to: "bind: Address already in use"

2005 Feb 01
5
Cannot save/migrate domains
Hi, I had a problem trying to migrate domains, in trying to locate it I noticed that saving domains doesn''t work either, which I believe explains why the receiving xfrd doesn''t actually receive anything. So here it goes... xenone:/tmp# xm list Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 123 0 r---- 900.6 sky 9
2005 Oct 25
3
live migration with DRBD devices
Hi all, I want to do live migration of domains using DRBD block devices for synchronisation between the two Xen hosts with Xen 2.0.7. I''ve written a script ( block-drbd ) which binds / unbinds DRBD devices for specific domains (with DRBD, only one host can write on a drbd device at the same time). This script sets the current host as master (bind) or secondary (unbind) in a DRBD
1999 Oct 13
2
bind failed on port 139 socket_addr=0.0.0.0 (Address already in use)
I can't figure out what is causing the error message of [1999/10/13 11:39:42, 0] lib/util_sock.c:open_socket_in(671) bind failed on port 139 socket_addr=0.0.0.0 (Address already in use) in my logs and thus preventing smbd from serving up connections. How can I track down what is causing this? Samba has been working great and now I must have done something but I don't know what. The
2005 Feb 02
1
Migration Errors
Hi, I am trying to migrate a domain (testDomain) from node1 to node2. Here is some information about the problem: node1#: xm migrate testDomain node2 After the command is executed, there is some communication between the node1 and node2 Xen hosts. xfrd daemon (which is forked by xend) is primarily responsible for vm migration and there is error in its log (/var/log/xfrd.log) The exact
2001 Nov 27
1
patch for problem with "Bind to port 22 on 0.0.0.0 failed: Address already in use."
Hi, there is a cosmetic problem in openssh (all versions AFAIK): When you start sshd with no "ListenAddress" lines in sshd_config, it tries to bind address "::" (successfuly) and then "0.0.0.0" and it fails with "Address already in use". Moreover it can happen that "0.0.0.0" is in addr list sooner than "::" so sshd than will listen
2006 Jul 28
0
vncviewer: ListenAtTcpPort: bind: Address already in use
Hello, if I start a unmodified Guest Already working on A SLES Installation now I get under gentoo: VNC= 1 vncviewer: ListenAtTcpPort: bind: Address already in use vncviewer: ListenAtTcpPort: bind: Address already in use The config: disk = [ ''file:/var/lib/xen/images/win/hda,ioemu:hda,w'' ] memory = 512 vcpus = 1 builder = ''hvm'' device_model =
2013 Jul 10
0
Fwd: Re: nsd can't bind udp socket: Address already in use
Rick, My apologies :) zongo -------- Original Message -------- Subject: Re: [nsd-users] nsd can't bind udp socket: Address already in use Date: Wed, 10 Jul 2013 19:33:20 +0200 From: Rick van Rein (OpenFortress) <rick at openfortress.nl> To: zongo saiba <zongosaiba at gmail.com> zongo, you only sent this to me? -rick On Jul 10, 2013, at 7:04 PM, zongo saiba
2004 May 21
2
Failed to bind to 0.0.0.0:5060: Address already in use
Hi, I have a strange error, that I haven't yet found in another posting on the archive. Here's my sip.conf: [general] port = 5060 ; Port to bind to bindaddr = 0.0.0.0 ; Address to bind SIP channel to context = default ; Default context for incoming calls callerid=No CallID [stefan] type=friend secret=blah username=stefan
2006 Jan 05
1
Xenoppix(Xen 3.0 CD size) is released
Dear, We released New Xenoppix (based on Xen3.0, CD size). Detail HP http://unit.aist.go.jp/itri/knoppix/xen/index-en.html 670MB knoppix_v4.0.2CD_20050923_xen3.0-20060104+IPAFont_cdsize.iso --------------------------------- # New Features * Xen is updated to version 3.0. * Host-Xenoppix(Knoppix on Domain0) boots Guest-Xenoppix(Knoppix on DomainU) with same kernel and same Root
2006 Dec 08
2
Bug#402081: xen-utils-3.0.3-1: xen-utils missing xfrd
Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 Severity: important the xen-utils packages lack xfrd, which is required for live domain migrations using xm migrate. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-686 Locale:
2008 Sep 17
1
pbx_dundi.c:4582 load_module: Unable to bind to 0.0.0.0 port 4520: Address already in use
On Tue, Sep 16, 2008 at 2:21 AM, Michiel van Baak <michiel at vanbaak.info> wrote: > On 22:46, Mon 15 Sep 08, hugolivude wrote: >> I have two Asterisk servers running on the same LAN. One starts fine, >> but when I start the other I get: >> >> pbx_dundi.c:4582 load_module: Unable to bind to 0.0.0.0 port 4520: >> Address already in use >> >>
2023 Apr 24
1
nsd issue
Hi Jean Claude, The message is printed when the bind operation failed. Why that happens is hard to say, I'd need more information for that. As the message does not say: address already in use (or similar), I'm guessing the address is not configured? Best regards, Jeroen On Fri, 2023-04-21 at 18:03 +0200, HAKIZIMANA Jean Claude via nsd-users wrote: > Dear nsd Users, > kindly can
2023 Jun 26
1
NSD reload and restart : in-memory data
Hi, I'm new to NSD and would really appreciate if someone can point me to the right direction. I have like 8 NSD servers (secondary) serving around 30,000 zones. Zone updates are transferred from the primary DNS servers by AXFR/IXFR. The 8 NSD servers do not save the zones file on disk but are only held in memory. Therefore after NSD service is restarted zone transfer requests are being
2004 Feb 02
2
Solaris 8 & Samba 3: "address already in use"
I am getting errors when I try to start smbd which say that port 445 is already in use, but nothing else is using it. In the log, the full error is: -----start log.smbd---- [2004/02/02 11:03:53, 0] lib/util_sock.c:open_socket_in(662) bind failed on port 445 socket_addr = 0.0.0.0. Error = Address already in use ------end log.smbd----- In my /etc/services file, I have these entries:
2024 Jul 30
1
NSD 4.10.1rc2 pre-release
Hi Andreas, The suggestions I captured in GitHub issues. Thanks for sharing. Regarding whether notifies are still plain UDP. Yes, the config parser doesn't accept additional arguments to "notify" and judging by the xfrd code anything to do with notify is using UDP, so no TLS yet. I've added a GitHub issue for this too. Thanks for the suggestions. They make for nice
2005 Jun 02
5
[Bug 1051] error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
http://bugzilla.mindrot.org/show_bug.cgi?id=1051 Summary: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Product: Portable OpenSSH Version: 4.1p1 Platform: ix86 URL: http://www.tietoenator.de OS/Version: Linux Status: NEW Severity: critical Priority: P4
2023 Jul 27
1
High memory consumption for small AXFR
Hello! I use NSD 4.7.0 self compiled: Configure line: --build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking
2024 Jul 24
2
NSD 4.10.1rc2 pre-release
Am 23.07.24 um 17:28 schrieb Jeroen Koekkoek via nsd-users: > NSD 4.10.1rc2 pre-release is available: no compile time warnings while building on debian bookworm/x86_64 > @bilias implemented mutual TLS authentication for zone transfers. > Please consult the nsd.conf manual for details on the newly introduced > configuration options tls-auth-port and tls-auth-xfr-only. this is an nice
2013 Jul 10
4
nsd can't bind udp socket: Address already in use
Greetings, Unbound 1.4.20 OS X 10.8.4 - Server NSD 3.2.15 I have installed 'unbound' and it works nicely on my client (test purpose) - Client is MacBook Air. I have installed NSD (will be in replacement of BIND) on said client. All is good but when i try to start NSD Error --> nsd can't bind udp socket: address already in use. Everything is configured to bind to 127.0.0.1. #
2011 May 18
9
Address already in use - bind(2) (Errno::EADDRINUSE)
I made a new rails app and when i started the server ,it gave following error message. => Booting Mongrel => Rails 2.3.8 application starting on http://0.0.0.0:3000 => Call with -d to detach => Ctrl-C to shutdown server Exiting /usr/lib/ruby/1.8/mongrel/tcphack.rb:12:in `initialize_without_backlog'': Address already in use - bind(2) (Errno::EADDRINUSE) from