From owner-freebsd-python@freebsd.org Mon Jul 8 11:32:23 2019 Return-Path: Delivered-To: freebsd-python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CFA3815DBC08 for ; Mon, 8 Jul 2019 11:32:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 646E469E5A for ; Mon, 8 Jul 2019 11:32:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 224F815DBC05; Mon, 8 Jul 2019 11:32:23 +0000 (UTC) Delivered-To: python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB4EC15DBC04 for ; Mon, 8 Jul 2019 11:32:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5A0D669E52 for ; Mon, 8 Jul 2019 11:32:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id A0517A03B for ; Mon, 8 Jul 2019 11:32:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x68BWL9I058734 for ; Mon, 8 Jul 2019 11:32:21 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x68BWLO5058733 for python@FreeBSD.org; Mon, 8 Jul 2019 11:32:21 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 238785] sysutils/py-google-compute-engine: Some GCE packages fill the logs with an error message Date: Mon, 08 Jul 2019 11:32:21 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: needs-qa, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: mage@mage.gold X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jul 2019 11:32:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238785 --- Comment #6 from Mage --- It got interesting.=20 First, I could not reproduce the issue in a VM on my home computer. I thoug= ht the reason was something like the daemon couldn=E2=80=99t connect and refus= ed to run. Then I created a test machine on Google cloud, using an image I created on 28.1.2019. The issue also didn=E2=80=99t appear on this machine. That was normal as I = started having it only this year, likely after January. However, when I upgraded the test machine=E2=80=99s packages to the current= version with pkg, the issue also did not appear. Yet every machine that has been running in the last few months and that I k= ept upgrading on a regular basis has the issue. In addition that I know I didn= =E2=80=99t edit any related config file (I don=E2=80=99t even know if py27-google-comp= ute-engine has one in the first place), the machines are on two separated accounts. On= one of the accounts, I hardly ever edit any config. I thought that somewhere between 28 January and today, a specific version of py27-google-compute-engine must have created some file that causes the issu= e. This would explain why I don=E2=80=99t see it on either a fresh install (ho= me VM) or on the server I upgraded from 28 January to today=E2=80=99s state in a single = step. By the way, the upgrade was: py27-google-compute-engine: 2.8.6 -> 2.8.13_5 I uninstalled every package that had "google" in their name. I executed pkg autoremove as well. There aren=E2=80=99t many files left in the system that have "google" in th= eir path. There is a folder called "/var/lib/google". That reminds me of the bad days= of Linux. Shouldn=E2=80=99t it be /var/db/google? /var/lib/google # ls -l total 14 drwxr-xr-x 7 root wheel 7 Nov 15 2016 per-instance -rw-r--r-- 1 root wheel 20 Nov 15 2016 vm-instance-id -rw-rw-rw- 1 root wheel 0 Sep 9 2018 vm-instance-id.lock The 'per-instance' directory contains empty subdirectories that are named a= s a 19 digits decimal number. There are five of them from November 2016.=20 That=E2=80=99s probably when I created my first instance. All my servers in= Google Compute Engine are a descendant or let=E2=80=99s say, a clone of my first i= nstance that I created from the FreeBSD image on GCE. I have been upgrading them for yea= rs.=20 The vm-instance-id is neither the same nor different on each of my servers.= On some of the servers, it=E2=80=99s the same. On a few other servers, it=E2= =80=99s unique.=20 The file is from 2016 Movember from each of my servers. The lock is from 20= 18 September 9 everywhere. I=E2=80=99m not sure, but the latter might be when = I migrated from the deprecated google-cloud-something-cant-remember to the py27-google-compute-engine. I feel like deleting the /var/lib/google everywhere, or more like rm -rf /var/lib. Can I do that? In addition to making things right, I=E2=80=99m trying to figure out the ca= use of the issue that=E2=80=99s the original subject of this ticket. --=20 You are receiving this mail because: You are on the CC list for the bug.=