similar to: Problems with control (TCP) connections

Because of security vulnerabilities in tinc that have recently been discovered, we hereby release tinc versions 1.0.35 and 1.1pre17. Here is a summary of the changes in tinc 1.0.35: * Prevent oracle attacks (CVE-2018-16737, CVE-2018-16738). * Prevent a MITM from forcing a NULL cipher for UDP (CVE-2018-16758). Here is a summery of the changes in tinc 1.1pre17: * Prevent oracle attacks in the

Because of security vulnerabilities in tinc that have recently been discovered, we hereby release tinc versions 1.0.35 and 1.1pre17. Here is a summary of the changes in tinc 1.0.35: * Prevent oracle attacks (CVE-2018-16737, CVE-2018-16738). * Prevent a MITM from forcing a NULL cipher for UDP (CVE-2018-16758). Here is a summery of the changes in tinc 1.1pre17: * Prevent oracle attacks in the

Hi folks, When I enabled stored configs on my puppet master, it began keeping lots of open connections to the MySQL server (as far as I understand it opened one connection for each client run and never closed them). I set up the server to close idle connections after 5 minutes. Now the database server does close the connections but the puppet master keeps them in CLOSE_WAIT state and eventually

We've seen Samba crash and burn twice in the last 48 hours - it just started happening, and we have no idea what might be causing it. I'm hoping that someone will recognize this problem. Platform: we are running RedHat Enterprise Server, with Samba 3.0.7. We're using security=domain in an old-style NT4 domain environment. The symptom that we're seeing is that the number of

Hello list Our central fileserver is a Samba 3.0.25b on Solaris 9 and has 10'000 users (several hundreds at the same time). This week it died on us and when I inspected the machine, it was out of 8GB Memory and 16GB Swap because thousands of smbd processes were running. netstat -na showed that many hundreds of connections to port 445 were in CLOSE_WAIT state. We first thought it could be

Lately it never fails when I attach a Mac running OSX 10.5 that I get runaway pid's. I tracked them down so far to multiple close_wait's: # /usr/sbin/lsof | grep pbg5mac smbd 24876 root 6u IPv4 80015755 TCP yoda.wrenkasky.com:netbios-ssn->pbg5mac.wrenkasky.com:49381 (CLOSE_WAIT) They can grow to over 100 if I don't catch it or nobody can log on anymore ;-)

hi everyone, congratulations on the release of icecast 2.1.0 I presume this is the right place to post about iceS. please correct if wrong. I have a two instance setup, and have been finding that after a network error occurs, the instance does not reconnect. The source server is behind a linux NAT box. I have simulated the problem by using iptables REJECT with tcp-reset and here is the

I have the need to know how many connection the server has, i run this command but i don't know how to sum all the results and get a final number. any ideas? netstat -an | grep -E 'tcp|udp' | awk '{print $6}' | sort | uniq -c | sort -n ?? 1 CLOSE_WAIT ?? 1 FIN_WAIT_2 ?? 1 LAST_ACK ?? 1 TIME_WAIT ?? 4 SYN_SENT ? 15 ? 37 LISTEN ? 44 ESTABLISHED

Hi, I''m running into a strange issue where one mongrel will sometimes develop hundreds of CLOSE_WAIT TCP connections, mostly to apache (I think -- see sample lsof output below). I haven''t had a chance to get the mongrel with this behavior into USR1 debug mode yet. I didn''t catch it in time. This happens a couple times a day on average at seemingly random times.

Hi folks I know that has, to some degree, been run over the past year in different ways, but, I may have yet another instance of an issue on this. The puppetmaster system and the puppet system are both running 0.24.7-r1, on a gentoo system. Other puppet systems are running 0.24.4. The puppet system (not the puppetmaster system) that is running 0.24.7-r1 is showing multiple close_wait

Hello, I''m experiencing a strange, but very bad behavior with Mongrel 0.3.13.4 and Pound 1.8. Every 6 hours or so one of our nine (not consistent on which one) application servers ( each one running several mongrel processes ) will start leaving lots of socket connections with pound open. This leads to "Too many open files" errors. I''ve set pound to close connections

* cross posted to the mongrel mailing list* Hi, I''m running into a strange issue where one mongrel will sometimes develop hundreds of CLOSE_WAIT TCP connections, mostly to apache (I think -- see sample lsof output below). I haven''t had a chance to get the mongrel with this behavior into USR1 debug mode yet. I wrote a little loop below that will catch it next time. This

I'm still battling with the bleedin' C4D Net client, which fails to do some of the network stuff that it's designed to do. Now I do get an error: If I leave the client open overnight, it eventually loses to connection to the server and the terminal window from where I started the client says: fixme:winsock:NtStatusToWSAError Status code c000011f converted to DOS error code 4 wine

Hi, We are using a samba server as a NTLM authenticator for our web filter. However, Samba closes the SMB connections after 60 seconds of inactivity, causing connections from the web filter to the Samba DC to get stuck in CLOSE_WAIT state, and failing to authenticate the users. Is the some way, other than changing IDLE_CLOSED_TIMEOUT, or (in Samba 3.0.23) commenting the check that closes the TCP

I''m checking out backgroundrb for a calculation process I estimate will take 2-3 minutes and be ran on-demand only via Rails. Very easy and slick. But I have a question. The connections never close, if I do a netstat they just keep piling up. Do I need to do some housekeeping somewhere? I noticed the @ connection.close statements are commented out in favor of a # FIXME type deal.

Hello samba people. I am having a odd problem related to winbindd. When I leave it running overnight on a quiet (not silent however) server I find that it generates a large number of CLOSE_WAIT state connections. 84 on a fairly quiet system in the last 18 hours. I can't seem to find any command that directly affects the number of CLOSE_WAITS. Below is my netstat listing. Any ideas would

We have a windows 2003 dc here at the university and I have successfully setup samba-3.0.2-6.3E on a RHEL WS3 machine. The problem is that after several hours, or several days winbind stops running and connections fail. I have seen instances of this on other sites, but no firm answers. I can provide files and logs if helpful

the rail application I have developed (really simple one 2 -> db tables with no more than 100 records) works perfectly in development / production mode on my windows desktop (win200 pro + mysql + ruby 1.8.2 + rails 1.1.6). when deploying the application on linux (ruby 1.8.4 , rails 1.1.6 the same mysql as on windows) everything *seems* to work fine. well atleast for the first few hours. the

Hi We tried to update our Dovecot Director-Ring to 2.3 (latest version) and had one problem/bug. When we try to deliver an email from Exim to a receiving Dovecot (2.3 latest) via the LMTP-Proxy the LMTP process stays open forever and never closes. So after a few hours, we hit the LMPT-Process limit.? The problem only exists if the receiving Dovecot reports "Quota exceeded (mailbox for user

> Problem with this is client needs to listen to the call recordings and my interface will only display .wav or .mp3 so they will moan if they have to wait until the next day for today's recordings If you're up to writing a bit of shell script, and are running on Linux, you could automate the conversion process so that it happens as soon as the recording is completed. Look at the