[Bug 242621] iscsi initiator does not provide devices after reconnection

2019-12-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242621 Bug ID: 242621 Summary: iscsi initiator does not provide devices after reconnection Product: Base System Version: 11.3-RELEASE Hardware: amd64 OS: Any

[Bug 242621] iscsi initiator does not provide devices after reconnection

2019-12-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242621 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|s...@freebsd.org -- You are receiv

[Bug 242606] Low capacity of Variable "IPSEC_MANUAL_REQID_MAX" crashes StrongSwan IPSec/IKEV2 VPN Server

2019-12-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242606 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|n...@freebsd.org -- You are receiv

[Bug 234031] loader can't traverse filesystem, LUA ERROR: cannot open /boot/lua/loader.lua

2019-12-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234031 --- Comment #27 from Toomas Soome --- I did an test today with failing vbox image - with loader from latest current, it does load and start the kernel. However, not 100% sure what was the cause, therefore can not be 100% sure we have fix.

[Bug 242592] bectl - cannot destroy a boot environment

2019-12-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242592 --- Comment #1 from Emrion --- Created attachment 209916 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209916&action=edit Creation of two BEs This is an up-to-date FreeBSD 12.1. With bectl I create two BEs, activate the first o

[Bug 242592] bectl - cannot destroy a boot environment

2019-12-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242592 --- Comment #2 from Emrion --- Created attachment 209917 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209917&action=edit This is what I get after reboot I would like to destroy default BE, then rename be1 as default. It's not

[Bug 242626] Nginx High CPU usage, Nginx crashes, unable to restart daemon, only hard reset helps

2019-12-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242626 Bug ID: 242626 Summary: Nginx High CPU usage, Nginx crashes, unable to restart daemon, only hard reset helps Product: Base System Version: 12.1-RELEASE Hardware: amd6

[Bug 242626] Nginx High CPU usage, Nginx crashes, unable to restart daemon, only hard reset helps

2019-12-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242626 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org --- Comment #1 f

[Bug 242626] Nginx High CPU usage, Nginx crashes, unable to restart daemon, only hard reset helps

2019-12-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242626 --- Comment #2 from Andris Vasers --- PIDTID COMMTDNAME KSTACK 1106 100280 nginx - vfs_bio_getpages ncl_getpages VOP_GETPAGES_APV vop_stdgetpages_async VOP_GETPAGES_ASYNC_A

[Bug 242626] Nginx High CPU usage, Nginx crashes, unable to restart daemon, only hard reset helps

2019-12-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242626 --- Comment #3 from Andris Vasers --- PIDTID COMMTDNAME KSTACK 1106 100280 nginx - vfs_bio_getpages+0x1d9 ncl_getpages+0x2be VOP_GETPAGES_APV+0x7c vop_stdgetpages_async+0x49

[Bug 242626] Nginx High CPU usage, Nginx crashes, unable to restart daemon, only hard reset helps

2019-12-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242626 --- Comment #4 from Andris Vasers --- Now got 2 cores on stuck: root@web1:~ # procstat -kk 1106 PIDTID COMMTDNAME KSTACK 1106 100280 nginx - vfs_bio_ge

[Bug 242626] Nginx High CPU usage, Nginx crashes, unable to restart daemon, only hard reset helps

2019-12-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242626 --- Comment #5 from Andris Vasers --- Created attachment 209920 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209920&action=edit top process list -- You are receiving this mail because: You are the assignee for the bug. __

[Bug 242626] Nginx High CPU usage, Nginx crashes, unable to restart daemon, only hard reset helps

2019-12-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242626 --- Comment #6 from Andris Vasers --- Created attachment 209923 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209923&action=edit 2 minute stuck after init 6 -- You are receiving this mail because: You are the assignee for the

[Bug 242626] Nginx High CPU usage, Nginx crashes, unable to restart daemon, only hard reset helps

2019-12-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242626 --- Comment #7 from Andris Vasers --- Created attachment 209924 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209924&action=edit stuck on sync process still in stuck after 5 minutes need to reboot server manually -- You are r

[Bug 242626] Nginx High CPU usage, Nginx crashes, unable to restart daemon, only hard reset helps

2019-12-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242626 --- Comment #8 from Andris Vasers --- Sorry, forgot to post vmstat list -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https:

[Bug 242626] Nginx High CPU usage, Nginx crashes, unable to restart daemon, only hard reset helps

2019-12-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242626 --- Comment #9 from Mark Johnston --- As a temporary workaround you can try setting vfs.nfs.use_buf_pager=0, but vfs_bio_getpages() has been the default for some time now. Are the files that are being served also being modified or truncate

[Bug 242626] Nginx High CPU usage, Nginx crashes, unable to restart daemon, only hard reset helps

2019-12-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242626 --- Comment #10 from Andris Vasers --- seems that files are ok this server is frontend part, probably files are not saved just log writes in file way. -- You are receiving this mail because: You are the assignee for the bug. _

[Bug 242217] 'make buildworld' type upgrading to 12.1-RELEASE impossible

2019-12-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242217 Krzysztof changed: What|Removed |Added CC||po...@bsdserwis.com --- Comment #4 fro

[Bug 242626] www/nginx High CPU usage, Nginx crashes, unable to restart daemon, only hard reset helps

2019-12-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242626 Mark Linimon changed: What|Removed |Added Flags||maintainer-feedback?(joneum