From owner-freebsd-dtrace@FreeBSD.ORG Wed Jun 4 01:45:58 2014 Return-Path: Delivered-To: freebsd-dtrace@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5738F35E for ; Wed, 4 Jun 2014 01:45:58 +0000 (UTC) Received: from mail-ve0-x22a.google.com (mail-ve0-x22a.google.com [IPv6:2607:f8b0:400c:c01::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1721721AE for ; Wed, 4 Jun 2014 01:45:58 +0000 (UTC) Received: by mail-ve0-f170.google.com with SMTP id db11so7926645veb.15 for ; Tue, 03 Jun 2014 18:45:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=GnyjYxCYkG7/hl/ZnKSs8UsuHELCioRnDYVGb/KsuhE=; b=CCg7nTcFgfQW+ujUbe6NSCInmBLsR3Z7rY70qsHzaGt5t9xJGRAif4pwGzS0qa8Ddj fZZIwkQPOoCMr64Kt5xIPfs9KyexHvdnN1iZKpjteNjhF8DrQoqe0SBEoApkd87yDC8a YkuRECadXNmB69kZHKJU383X5/iEBUb4U9D8q3bXKIkgB27VT8BABnUC5rhLX1YaVodE OB6RNOBpDAa4bkVjJYXWK4K9U3HZOhjK7pQBGstZdjiWCmuwmstSEGS9UXcmKtUXhCo6 J9j0wNhXDruAH0oiizirnf4349aDIzqd7yCcy3XlaMlGJx6jE4tzgBlDet8IUaPmOxzE Zk5Q== MIME-Version: 1.0 X-Received: by 10.58.135.136 with SMTP id ps8mr40471848veb.18.1401846356971; Tue, 03 Jun 2014 18:45:56 -0700 (PDT) Sender: markjdb@gmail.com Received: by 10.220.162.68 with HTTP; Tue, 3 Jun 2014 18:45:56 -0700 (PDT) In-Reply-To: References: Date: Tue, 3 Jun 2014 21:45:56 -0400 X-Google-Sender-Auth: fJuMEDaTUdJ6iAjjM0bb6l74bWI Message-ID: Subject: Re: Postgresql provider no longer working From: Mark Johnston To: "Sevan / Venture37" Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-dtrace@freebsd.org" X-BeenThere: freebsd-dtrace@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "A discussion list for developers working on DTrace in FreeBSD." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 01:45:58 -0000 On Sun, Jun 1, 2014 at 1:00 PM, Sevan / Venture37 wrote: > Hi, > It appears that the Postgresql provider stopped working at some point, > I'm running r266890 of 11.0-CURRENT with Postgresql 9.3.4 installed > and the probes are not showing up. > > I've rebuild postgresql with debug defined for both client & server, > but not a sausage. > Starting postgreql spits out: > LOG: ending log output to stderr > HINT: Future log output will go to log destination "syslog". > > & that's it. Hi, I can't reproduce this using postgres 9.3.4 on r267033 (current). As usual, it was necessary to first kldload dtraceall and make sure postgres could access /dev/dtrace/helper (in my case I've added the pgsql user to the wheel group). It's also necessary to build with dtraceall loaded (otherwise dtrace -G will fail I think). With that, the probes show up as expected. Do other ports create probes successfully? lang/php5 has a DTrace option and manages to create probes when I run it. If it doesn't in your environment, could you try running it with the DTRACE_DOF_INIT_DEBUG environment variable set to "1" and pass along the output? Thanks, -Mark