Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fcCfW-0000nD-CO for pgsql-performance@arkaria.postgresql.org; Sun, 08 Jul 2018 16:36:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fcCfT-0000yh-Bs for pgsql-performance@arkaria.postgresql.org; Sun, 08 Jul 2018 16:36:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fcCfT-0000yX-4b for pgsql-performance@lists.postgresql.org; Sun, 08 Jul 2018 16:36:11 +0000 Received: from mail-qk0-x242.google.com ([2607:f8b0:400d:c09::242]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fcCfK-0004ak-C9 for pgsql-performance@postgresql.org; Sun, 08 Jul 2018 16:36:09 +0000 Received: by mail-qk0-x242.google.com with SMTP id y4-v6so8637945qka.5 for ; Sun, 08 Jul 2018 09:36:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=from:subject:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=IL7cvDcbcf8DtHoLG1SvflWkebMHx5fvt17Lp7tOpsg=; b=R8lTMcarpTVkkHCAlfEwZy3EoXMAIpjTNXTTXbeJT99zj35NtGI4N18NvhaXguZ2NZ D2aZI8lR346kT7CQy7E+V6LwxM04yugZxez55dXZVvD+nwXajlimCIzf5UERxufCOzZr hanNNbFMbdztfD2AWZIBZEf6yF8BJWu6/sza2Ma3BmPuTiTuiK4VsiK1AJUEF0NZi2cE wvZU0tB45c3GANkUYs3hGQftsuYP/hnbHh3R+zt+5OZVphAxs+4tXcPYELFa7be/Mwm2 PPH9IQ/9F6/f0RdEinJ+ikQrLQrIrGiF8yPQJLfpGNh5McjsN4rv4ST5UJcJgSyF5s5O jC+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=IL7cvDcbcf8DtHoLG1SvflWkebMHx5fvt17Lp7tOpsg=; b=tNmbbY73sqbrB/TwM+SjFh1lX2DFgjoHVQ7VFkJREVxUdLMaWR7sl0TJOr4/G5YxPx vTGIBqdJiHOdcAPzgUGexl+oa5K+O+I+O5Z8Pv09khYeRYsztZTp3eZk7Ub0PgfPbrtv 4xBvMOZ+gYPG8yOoSvEnaKmTfLgvoJVRdfuw7Kyj0v1XVPaYdxNRJdBVE9qkQx0ssZ3J kgHmN0+bk+BBsU138X27R48ySjMSokocjah5WNNiVBleJQBJGaDkyRv+l4TmUHdfPJqp AfonsylvOEbJyeL+OxuYZguKp0VvYNImlyAI7nFMBF2MovGNcxuv7BQk+kEamki5ICPV kuMw== X-Gm-Message-State: APt69E1pwHuTfkPvCg1FKINF1lSS6zrqoZ6YE1pHYdxYVub4/ygSiHwM mri7Aq0I/Jg5eGoCRf7cH4gBLfqXDFGgUVo7yzLu1pr04Icnss2SSG+nheOm/yECAR9y5usozMZ tj47+77/RYgD2EEH5lxnkeSUZrywAB6yEplVAGFo3abKI9UEejjqJmYI+oDU2iGaq0FPhYzH/DX wcFTwBf66+PUFU0JSWtQ== X-Google-Smtp-Source: AAOMgpcKe8XrPDDatcoBOFTYstVhe3HnITEkR7TWqdN/xz16NKXC71PoKdFJJB9s2OCVowrEev4Hvw== X-Received: by 2002:a37:1194:: with SMTP id 20-v6mr15796518qkr.379.1531067759199; Sun, 08 Jul 2018 09:35:59 -0700 (PDT) Received: from [192.168.10.146] ([98.122.175.38]) by smtp.gmail.com with ESMTPSA id m12-v6sm6291803qkl.54.2018.07.08.09.35.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 08 Jul 2018 09:35:58 -0700 (PDT) From: Andrew Dunstan X-Google-Original-From: Andrew Dunstan Subject: Re: Problems with installing pgwatch2 without docker To: Mariel Cherkassky , "office@cybertec.at" Cc: "pgsql-performance@postgresql.org" References: Message-ID: Date: Sun, 8 Jul 2018 12:35:57 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-MW List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 07/08/2018 10:22 AM, Mariel Cherkassky wrote: > > Hi, > > I'm trying to install the pgwatch2 tool in our company without using > the docker option. I followed the instructions that are specified in > the github page but I'm facing an error during STEP 4.2 when I try to > add my cluster to be the /dbs page in order to monitor it. After I add > it I'm getting the error : > > ERROR: Could not connect to InfluxDB > > On the same machine I have an influxdb database running : > > ps -ef | grep influx > > influxdb 3680     1  0 17:12 ?        00:00:01 influxd -config > /PostgreSQL/influxdb/config/influxdb.conf > > When I look at the log of the influxdb I see that every time I press > the "New" button under DBS page the next row : > > [httpd] ::1 - root [08/Jul/2018:17:19:04 +0300] "GET > /query?q=SHOW+TAG+VALUES+WITH+KEY+%3D+%22dbname%22&db=pgwatch2 > HTTP/1.1" 401 33 "-" "python-requests/2.19.1" > de27bc5c-82b9-11e8-8003-000000000000 141 > > What else do you recommend to check ? > > Thanks , Mariel. > Please stop asking questions in inappropriate forums. This is not a performance issue, so it definitely doesn't belong on this list.. If it belongs on a postgres forum at all it belongs on pgsql-general. More likely, you should be asking in the pgwatch2 forums, not Postgres forums. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services