-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GeoLite2 db access, with license, fails at "error retrieving updates: error creating database writer: could not acquire lock " #70
Comments
Thanks for the report! What OS are you using? I think this is caused by what #69 is fixing - the error check when closing is not quite right, causing us to not unlock the file. It continues despite the problematic check in at least some environments it seems. |
I'm seeing this on a variety of my linux boxen e.g., `this one',
|
Interesting! I wonder what causes the behaviour difference since it works on other Linux hosts I try. I don't have a good workaround - we'll need a fix like #69 I think. Essentially I believe Unlock() here is not getting called because of the first error in your output causes us to return before doing so - |
fwiw, here's my
|
atm, this^ issue is 100% reproducible on the 20-or-so boxes I've tested. of course, COULD be something common across my env, &/or #69 et al. in the interim, any clever workarounds come to mind? |
@pgnd, are you compiling I believe this is caused by pkg/errors#219. We currently are pinned against 0.8.1, which should not have this issue. |
yup, tho with go, rather than a direct pull/build from git. namely, GOPATH=/usr/local/ go get -u github.com/maxmind/geoipupdate/cmd/geoipupdate which I assume grabs latest head.
dunno, haven't tried -- always used the above method -- but can explore. |
Confirming we too see the same bugs will latest code from master. Running on mac OS or fresh debian install |
doing an explicit clean+pull (NOT something I've typically bothered with b4 ...) seems to do the trick, even with
an errant remnant from prior pull/build causing a problem? I'll have to try on a couple of machines that I've not yet cleaned, and pay closer attention. This^^ work for anyone else here? |
4.2.0 * The major version of the module is now included at the end of the module path. Previously, it was not possible to import the module in projects that were using Go modules. Reported by Roman Glushko. GitHub #81. * The minimum Go version is now 1.13. * A valid account ID and license key combination is now required for database downloads, so those configuration options are now required. * The error handling when closing a local database file would previously ignore errors and, upon upgrading to `github.com/pkg/errors` 0.9.0, would fail to ignore expected errors. Reported by Ilya Skrypitsa and pgnd. GitHub #69 and #70. * The RPM release was previously lacking the correct owner and group on files and directories. Among other things, this caused the package to conflict with the `GeoIP` package in CentOS 7 and `GeoIP-GeoLite-data` in CentOS 8. The files are now owned by `root`. Reported by neonknight. GitHub #76.
after reading notice
i'm updating my local installs.
building clean, as usual, from git sources, with no errors,
and
I've created an account, and gotten my acctID + license key; config file is
on exec of
goeipupdate
I get an error,
Note, the first lock is acquired
here's with
--stack-trace
The text was updated successfully, but these errors were encountered: