Date: Tue, 02 Feb 2021 17:42:07 +0100 From: "Kristof Provost" <kp@FreeBSD.org> To: "Johan Hendriks" <joh.hendriks@gmail.com> Cc: freebsd-stable@freebsd.org, mjg@FreeBSD.org Subject: Re: latest stable13.0-ALPHA3 can not start varnish anymore. Message-ID: <44315237-2B01-4C1B-A992-E235A5A911B0@FreeBSD.org> In-Reply-To: <9821a854-9c86-060b-607b-01a2fbbc076e@gmail.com> References: <890f2a63-62a9-f4a7-b57f-5b122a4a9709@gmail.com> <9821a854-9c86-060b-607b-01a2fbbc076e@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2 Feb 2021, at 14:05, Johan Hendriks wrote: > On 01/02/2021 22:48, Johan Hendriks wrote: >> I just updated my FreeBSD 13.0-APLPHA3 to the latest revision and now >> i can not start varnish anymore. >> This is on two machines. >> >> if i start varnish it errors out as the startup script does a config >> file check. >> If i try to do a test of the config file i get the following error. >> >> root@jhost002:~ # varnishd -C -f /usr/local/etc/varnish/default.vcl >> Error: Cannot create working directory '/tmp/varnishd_C_dwbl7mn/': Is >> a directory >> Error: Cannot create working directory (/tmp/varnishd_C_dwbl7mn/): No >> error: 0 >> (-? gives usage) >> root@jhost002:~ # >> >> This is on: >> FreeBSD jhost002.mydomain.nl 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #35 >> stable/13-c256281-gc415d0df47fc: Mon Feb 1 17:04:49 CET 2021 >> root@srv-01.home.local:/usr/obj/usr/src/amd64.amd64/sys/KRNL amd64 >> >> I did not update the package or installed any other software besides >> the buildworld. >> >> regards, >> Johan >> >> > I have tried some bisecting as far as my understanding of git goes. I > do not know which one is the latest, but on these revisions varnish > works. > > FreeBSD jhost002 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #8 > c256261-g9375a93b6c22: Tue Feb 2 13:33:05 CET 2021 > root@jhost002:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > > uname -a > FreeBSD jhost002 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #7 > c256260-g247f652e622d: Tue Feb 2 13:07:37 CET 2021 > root@jhost002:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > Can you try setting `sysctl vfs.cache_fast_lookup=0` ? (As suggested by Mateusz elsewhere.) Best regards, Kristof From owner-freebsd-stable@freebsd.org Tue Feb 2 16:44:39 2021 Return-Path: <owner-freebsd-stable@freebsd.org> Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2E600536AE6 for <freebsd-stable@mailman.nyi.freebsd.org>; Tue, 2 Feb 2021 16:44:39 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DVVyv0stgz3lTw; Tue, 2 Feb 2021 16:44:39 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qk1-f172.google.com (mail-qk1-f172.google.com [209.85.222.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 0C1DD2B19B; Tue, 2 Feb 2021 16:44:39 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qk1-f172.google.com with SMTP id u20so20405855qku.7; Tue, 02 Feb 2021 08:44:39 -0800 (PST) X-Gm-Message-State: AOAM530m79nRXyHRJ1rEBSioKq1Mp15XzhiUJtktmZCQdNPSuKe/hAtY bw/glHNxkQcsP6d3YGlWKi8sd2WgXPGMtX+73NU= X-Google-Smtp-Source: ABdhPJz+nVRYRA636hNckrLinB48fjJhr9J2tMpE8WkWcQWSCs7cp2nbY9cZECTtbu5sLQpqkwUZ/dCW0/FuejH3hKo= X-Received: by 2002:a37:745:: with SMTP id 66mr23310931qkh.120.1612284278526; Tue, 02 Feb 2021 08:44:38 -0800 (PST) MIME-Version: 1.0 References: <890f2a63-62a9-f4a7-b57f-5b122a4a9709@gmail.com> <9821a854-9c86-060b-607b-01a2fbbc076e@gmail.com> <44315237-2B01-4C1B-A992-E235A5A911B0@FreeBSD.org> In-Reply-To: <44315237-2B01-4C1B-A992-E235A5A911B0@FreeBSD.org> From: Kyle Evans <kevans@freebsd.org> Date: Tue, 2 Feb 2021 10:44:25 -0600 X-Gmail-Original-Message-ID: <CACNAnaEtwDkxQJKmfX_shgWFJZCqB6XrTR9EgXb0cwfE__sAvw@mail.gmail.com> Message-ID: <CACNAnaEtwDkxQJKmfX_shgWFJZCqB6XrTR9EgXb0cwfE__sAvw@mail.gmail.com> Subject: Re: latest stable13.0-ALPHA3 can not start varnish anymore. To: Kristof Provost <kp@freebsd.org> Cc: Johan Hendriks <joh.hendriks@gmail.com>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>, Mateusz Guzik <mjg@freebsd.org> Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>; List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 02 Feb 2021 16:44:39 -0000 On Tue, Feb 2, 2021 at 10:42 AM Kristof Provost <kp@freebsd.org> wrote: > > On 2 Feb 2021, at 14:05, Johan Hendriks wrote: > > On 01/02/2021 22:48, Johan Hendriks wrote: > >> I just updated my FreeBSD 13.0-APLPHA3 to the latest revision and now > >> i can not start varnish anymore. > >> This is on two machines. > >> > >> if i start varnish it errors out as the startup script does a config > >> file check. > >> If i try to do a test of the config file i get the following error. > >> > >> root@jhost002:~ # varnishd -C -f /usr/local/etc/varnish/default.vcl > >> Error: Cannot create working directory '/tmp/varnishd_C_dwbl7mn/': Is > >> a directory > >> Error: Cannot create working directory (/tmp/varnishd_C_dwbl7mn/): No > >> error: 0 > >> (-? gives usage) > >> root@jhost002:~ # > >> > >> This is on: > >> FreeBSD jhost002.mydomain.nl 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #35 > >> stable/13-c256281-gc415d0df47fc: Mon Feb 1 17:04:49 CET 2021 > >> root@srv-01.home.local:/usr/obj/usr/src/amd64.amd64/sys/KRNL amd64 > >> > >> I did not update the package or installed any other software besides > >> the buildworld. > >> > >> regards, > >> Johan > >> > >> > > I have tried some bisecting as far as my understanding of git goes. I > > do not know which one is the latest, but on these revisions varnish > > works. > > > > FreeBSD jhost002 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #8 > > c256261-g9375a93b6c22: Tue Feb 2 13:33:05 CET 2021 > > root@jhost002:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > > > > uname -a > > FreeBSD jhost002 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #7 > > c256260-g247f652e622d: Tue Feb 2 13:07:37 CET 2021 > > root@jhost002:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > > > Can you try setting `sysctl vfs.cache_fast_lookup=0` ? > > (As suggested by Mateusz elsewhere.) > We confirmed that reverting 006ec2ed fixes it, I'm still trying to get an idea of what's happening. My initial analysis suggests that fplookup hits the trailing slash and aborts, leaving us at the degenerate state back up in the slow-path. I have a small reproducer that I'm working with: https://people.freebsd.org/~kevans/namereg.c
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44315237-2B01-4C1B-A992-E235A5A911B0>