FreeBSD STABLE_10 (10.3) - lots of IPv6 connections in CLOSED state

2016-05-05 Thread Robert Blayzor via freebsd-stable
Started seeing a ton of these in dmesg:

sonewconn: pcb 0xf8001570f188: Listen queue overflow: 301 already in queue 
awaiting acceptance (41 occurrences)
sonewconn: pcb 0xf8001570f188: Listen queue overflow: 301 already in queue 
awaiting acceptance (45 occurrences)
sonewconn: pcb 0xf8001570f188: Listen queue overflow: 301 already in queue 
awaiting acceptance (41 occurrences)
sonewconn: pcb 0xf8001570f188: Listen queue overflow: 301 already in queue 
awaiting acceptance (39 occurrences)
sonewconn: pcb 0xf8001570f188: Listen queue overflow: 301 already in queue 
awaiting acceptance (42 occurrences)
sonewconn: pcb 0xf8001570f188: Listen queue overflow: 301 already in queue 
awaiting acceptance (40 occurrences)
sonewconn: pcb 0xf8001570f188: Listen queue overflow: 301 already in queue 
awaiting acceptance (44 occurrences)
sonewconn: pcb 0xf8001570f188: Listen queue overflow: 301 already in queue 
awaiting acceptance (43 occurrences)
sonewconn: pcb 0xf8001570f188: Listen queue overflow: 301 already in queue 
awaiting acceptance (38 occurrences)


The process normally listening, the service stopped working. (manage-sieve, TCP 
port 4190)…

After looking at netstat I see 300+ connections on this service in a “CLOSED” 
state…  All of the connections are via IPv6.


Sockstat shows all of these connections not related to a user, command, pid, 
etc….  If I restart the process, all of the connections are freed and things 
work as expected for a while.


sockstat
USER COMMANDPID   FD PROTO  LOCAL ADDRESS FOREIGN ADDRESS
??  ? ?  tcp6   dead:beef:110:2::1:0:25 
dead:beef:110:2::f:0:24162
??  ? ?  tcp6   dead:beef:110:2::1:0:110 
dead:beef:110:2::f:0:1566
??  ? ?  tcp6   dead:beef:110:2::1:0:25 
dead:beef:110:2::f:1:30064
??  ? ?  tcp6   dead:beef:110:2::1:0:143 
dead:beef:110:2::f:0:7199
??  ? ?  tcp6   dead:beef:110:2::1:0:110 
dead:beef:110:2::f:1:48062
??  ? ?  tcp6   dead:beef:110:2::1:0:143 
dead:beef:110:2::f:1:54271
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:1:36446
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:1:57291
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:0:48429
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:1:56473
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:1:61870
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:1:5971
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:1:64942
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:1:46824
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:1:14230
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:1:34070
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:1:24494
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:0:43982
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:0:38576
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:0:13346
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:0:46491
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:0:57936
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:0:3863
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:0:52049
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:0:45212
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:0:43416
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:1:56373
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:0:51448
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:1:51996
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:1:52523
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:0:19061
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:1:41591
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:0:5
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:1:47299
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:1:18115
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:1:64664
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:0:31583
??  ? ?  tcp6   dead:beef:110:2::1:0:4190 
dead:beef:110:2::f:1:24094
?   

Jenkins build is back to normal : FreeBSD_stable_10 #249

2016-05-05 Thread jenkins-admin
See 

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: binary updates for 10.3 failing

2016-05-05 Thread Andreas Ott
On Thu, May 05, 2016 at 09:07:52AM -0700, Andreas Ott wrote:
> I'm not sure if the stable list is the correct place to report this,

Magically, overnight a PR appeared...

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209147

and it seems more widespread than 10.3-RELEASE.
-andreas
-- 
Andreas Ott   K6OTT   +1.408.431.8727   andr...@naund.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: binary updates for 10.3 failing

2016-05-05 Thread Kevin Oberman
On Thu, May 5, 2016 at 9:07 AM, Andreas Ott  wrote:

> Hi,
>
> I'm not sure if the stable list is the correct place to report this,
> but currently binary updates are not working. I see posts on the forum
> but no solutions are being offered (other than updates from source,
> which are difficult on production systems missing the src component).
> Something broke recently, it worked to update from RELEASE to -p1.
>
> Symptoms are like this (note that the system is -p1 already but the binay
> updater identifies it as -p0):
>
> [root@www ~]# freebsd-version
> 10.3-RELEASE-p1
> [root@www ~]# freebsd-update fetch
> src component not installed, skipped
> Looking up update.FreeBSD.org mirrors... none found.
> Fetching metadata signature for 10.3-RELEASE from update.FreeBSD.org...
> done.
> Fetching metadata index... done.
> Inspecting system... done.
> Preparing to download files... done.
>
> No updates needed to update system to 10.3-RELEASE-p0.
> [root@www ~]#
>
> I deleted /var/db/freebsd-update/* and tried again, same result.
>
> -andreas
> -
> Andreas Ott   K6OTT   +1.408.431.8727   andr...@naund.org
>

I am seeing the exact same issue. I really, really would like to get the
SSL fixes onto my web server, but I get the "No updates needed to update
system to 10.3-RELEASE-p0." message.

# freebsd-version -u -k
10.3-RELEASE
10.3-RELEASE-p1
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


10.1-RELEASE-p33 update does not exist?

2016-05-05 Thread Nick Rogers
Hello,

I am not sure if this is the appropriate place to inquire about this, but I
am unable to update my 10.1-RELEASE machines to the latest releng branch
(10.1-RELEASE-p33) with the latest FreeBSD-SA-16:17.openssl advisory.

Here's what happens when I try freebsd-update.

# freebsd-version -ku
10.1-RELEASE-p31
10.1-RELEASE-p32
# uname -v
FreeBSD 10.1-RELEASE-p31 #0: Wed Mar 16 18:39:20 UTC 2016
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
# freebsdupdatec
# freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 4 mirrors found.
Fetching metadata signature for 10.1-RELEASE from update6.freebsd.org...
done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

The following files are affected by updates, but no changes have
been downloaded because the files have been modified locally:
/etc/mtree/BSD.usr.dist
/var/db/etcupdate/current/etc/mtree/BSD.usr.dist
/var/db/etcupdate/current/etc/ntp.conf
/var/db/mergemaster.mtree

No updates needed to update system to 10.1-RELEASE-p32.

There seems to be some discussion that is perhaps related to this issue in
this bug:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209147

Thanks.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


binary updates for 10.3 failing

2016-05-05 Thread Andreas Ott
Hi,

I'm not sure if the stable list is the correct place to report this,
but currently binary updates are not working. I see posts on the forum
but no solutions are being offered (other than updates from source,
which are difficult on production systems missing the src component).
Something broke recently, it worked to update from RELEASE to -p1.

Symptoms are like this (note that the system is -p1 already but the binay
updater identifies it as -p0):

[root@www ~]# freebsd-version 
10.3-RELEASE-p1
[root@www ~]# freebsd-update fetch
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... none found.
Fetching metadata signature for 10.3-RELEASE from update.FreeBSD.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

No updates needed to update system to 10.3-RELEASE-p0.
[root@www ~]#

I deleted /var/db/freebsd-update/* and tried again, same result.

-andreas
- 
Andreas Ott   K6OTT   +1.408.431.8727   andr...@naund.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Build failed in Jenkins: FreeBSD_stable_10 #248

2016-05-05 Thread jenkins-admin
See 

--
[...truncated 319700 lines...]
[192.168.10.2] out: bin/date/format_string_test:j_test  ->  passed  [0.144s]
[192.168.10.2] out: bin/date/format_string_test:k_test  ->  passed  [0.170s]
[192.168.10.2] out: bin/date/format_string_test:l_test  ->  passed  [0.203s]
[192.168.10.2] out: bin/date/format_string_test:m_test  ->  passed  [0.120s]
[192.168.10.2] out: bin/date/format_string_test:p_test  ->  passed  [0.141s]
[192.168.10.2] out: bin/date/format_string_test:percent_test  ->  passed  
[0.167s]
[192.168.10.2] out: bin/date/format_string_test:plus_test  ->  passed  [0.271s]
[192.168.10.2] out: bin/date/format_string_test:r_test  ->  passed  [0.168s]
[192.168.10.2] out: bin/date/format_string_test:s_test  ->  passed  [0.166s]
[192.168.10.2] out: bin/date/format_string_test:u_test  ->  passed  [0.314s]
[192.168.10.2] out: bin/date/format_string_test:v_test  ->  passed  [0.207s]
[192.168.10.2] out: bin/date/format_string_test:w_test  ->  passed  [0.151s]
[192.168.10.2] out: bin/date/format_string_test:x_test  ->  passed  [0.687s]
[192.168.10.2] out: bin/date/format_string_test:y_test  ->  passed  [0.357s]
[192.168.10.2] out: bin/date/format_string_test:z_test  ->  passed  [0.185s]
[192.168.10.2] out: bin/sleep/sleep_test:fraction  ->  passed  [0.839s]
[192.168.10.2] out: bin/sleep/sleep_test:hex  ->  passed  [1.187s]
[192.168.10.2] out: bin/sleep/sleep_test:nonnumeric  ->  passed  [0.243s]
[192.168.10.2] out: bin/dd/dd_test:io  ->  passed  [0.133s]
[192.168.10.2] out: bin/dd/dd_test:length  ->  passed  [0.039s]
[192.168.10.2] out: bin/dd/dd_test:seek  ->  passed  [0.303s]
[192.168.10.2] out: bin/cat/cat_test:align  ->  passed  [0.030s]
[192.168.10.2] out: bin/cat/cat_test:nonexistent  ->  passed  [0.029s]
[192.168.10.2] out: bin/pax/legacy_test:main  ->  passed  [3.379s]
[192.168.10.2] out: bin/ls/ls_tests:1_flag  ->  passed  [1.306s]
[192.168.10.2] out: bin/ls/ls_tests:A_flag  ->  passed  [2.424s]
[192.168.10.2] out: bin/ls/ls_tests:A_flag_implied_when_root  ->  passed  
[1.323s]
[192.168.10.2] out: bin/ls/ls_tests:B_flag  ->  passed  [0.042s]
[192.168.10.2] out: bin/ls/ls_tests:C_flag  ->  passed  [1.433s]
[192.168.10.2] out: bin/ls/ls_tests:D_flag  ->  passed  [0.050s]
[192.168.10.2] out: bin/ls/ls_tests:F_flag  ->  passed  [3.518s]
[192.168.10.2] out: bin/ls/ls_tests:H_flag  ->  passed  [1.297s]
[192.168.10.2] out: bin/ls/ls_tests:I_flag  ->  passed  [0.829s]
[192.168.10.2] out: bin/ls/ls_tests:I_flag_voids_implied_A_flag_when_root  ->  
passed  [1.634s]
[192.168.10.2] out: bin/ls/ls_tests:L_flag  ->  passed  [0.056s]
[192.168.10.2] out: bin/ls/ls_tests:R_flag  ->  passed  [0.982s]
[192.168.10.2] out: bin/ls/ls_tests:S_flag  ->  passed  [3.468s]
[192.168.10.2] out: bin/ls/ls_tests:T_flag  ->  passed  [0.057s]
[192.168.10.2] out: bin/ls/ls_tests:a_flag  ->  passed  [1.497s]
[192.168.10.2] out: bin/ls/ls_tests:b_flag  ->  passed  [0.040s]
[192.168.10.2] out: bin/ls/ls_tests:d_flag  ->  passed  [0.402s]
[192.168.10.2] out: bin/ls/ls_tests:f_flag  ->  passed  [3.321s]
[192.168.10.2] out: bin/ls/ls_tests:g_flag  ->  passed  [2.011s]
[192.168.10.2] out: bin/ls/ls_tests:h_flag  ->  passed  [1.756s]
[192.168.10.2] out: bin/ls/ls_tests:i_flag  ->  passed  [2.802s]
[192.168.10.2] out: bin/ls/ls_tests:k_flag  ->  passed  [1.512s]
[192.168.10.2] out: bin/ls/ls_tests:l_flag  ->  passed  [0.050s]
[192.168.10.2] out: bin/ls/ls_tests:lcomma_flag  ->  passed  [3.812s]
[192.168.10.2] out: bin/ls/ls_tests:m_flag  ->  passed  [0.062s]
[192.168.10.2] out: bin/ls/ls_tests:n_flag  ->  passed  [0.099s]
[192.168.10.2] out: bin/ls/ls_tests:o_flag  ->  passed  [0.176s]
[192.168.10.2] out: bin/ls/ls_tests:p_flag  ->  passed  [3.535s]
[192.168.10.2] out: bin/ls/ls_tests:q_flag_and_w_flag  ->  passed  [0.070s]
[192.168.10.2] out: bin/ls/ls_tests:r_flag  ->  passed  [1.516s]
[192.168.10.2] out: bin/ls/ls_tests:s_flag  ->  passed  [1.075s]
[192.168.10.2] out: bin/ls/ls_tests:t_flag  ->  passed  [0.132s]
[192.168.10.2] out: bin/ls/ls_tests:u_flag  ->  passed  [0.137s]
[192.168.10.2] out: bin/ls/ls_tests:x_flag  ->  passed  [2.180s]
[192.168.10.2] out: bin/ls/ls_tests:y_flag  ->  passed  [1.318s]
[192.168.10.2] out: bin/pkill/pgrep-F_test:main  ->  passed  [0.322s]
[192.168.10.2] out: bin/pkill/pgrep-LF_test:main  ->  passed  [0.668s]
[192.168.10.2] out: bin/pkill/pgrep-P_test:main  ->  passed  [0.337s]
[192.168.10.2] out: bin/pkill/pgrep-U_test:main  ->  passed  [0.667s]
[192.168.10.2] out: bin/pkill/pgrep-_g_test:main  ->  passed  [0.657s]
[192.168.10.2] out: bin/pkill/pgrep-_s_test:main  ->  passed  [0.017s]
[192.168.10.2] out: bin/pkill/pgrep-g_test:main  ->  passed  [1.027s]
[192.168.10.2] out: bin/pkill/pgrep-i_test:main  ->  passed  [0.339s]
[192.168.10.2] out: bin/pkill/pgrep-j_test:main  ->  passed  [6.582s]
[192.168.10.2] out: bin/pkill/pgrep-l_test:main  ->  passed  [0.319s]
[192.168.10.2] out: bin/pkill/pgrep-n_test:main