Date: Mon, 08 Jul 2019 11:32:21 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 238785] sysutils/py-google-compute-engine: Some GCE packages fill the logs with an error message Message-ID: <bug-238785-7788-cWxTEj0nDZ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-238785-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-238785-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238785 --- Comment #6 from Mage <mage@mage.gold> --- 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 the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-238785-7788-cWxTEj0nDZ>