i have upgraded Ubuntu OS to 18.04, this cause my mongo db version upgrade from 2.4 to 3.6.
i have tried to downgrade but i think there is compatibility issue with OS 18.04
Related
Getting this error on Ubuntu 20.04.
I had origianlly installed the default version 3.0.6 on ubuntu.
I have purged it and installed 5.0.9. But now I get this error in logs and mongod won't start.
"Failed to start up WiredTiger under any compatibility version. This may be due to an unsupported upgrade or downgrade."
It's a massive gap between versions. You need to upgrade all versions in-between one at a time: https://www.mongodb.com/docs/manual/release-notes/5.0-upgrade-standalone/#upgrade-version-path:
To upgrade an existing MongoDB deployment to 5.0, you must be running a 4.4-series release.
To upgrade from a version earlier than the 4.4-series, you must successively upgrade major releases until you have upgraded to 4.4-series. For example, if you are running a 4.2-series, you must upgrade first to 4.4 before you can upgrade to 5.0.
Or you can export data from 3.0.6 , start 5.0.9 with empty data directory (Storage.dbPath option in config), import data to 5.0.9
postgres upgrade from 10.9 to 11.4 on aws rds failure with below reason
Database instance is in a state that cannot be upgraded: PreUpgrade
checks failed: The instance could not be upgraded because there are
one or more databases with an older version of PostGIS installed.
Please upgrade all installations of PostGIS and try again.
i have postgis 2.4.4 installed and command
ALTER EXTENSION postgis UPDATE;
fails with message
NOTICE: version "2.4.4" of extension "postgis" is already installed
and command
ALTER EXTENSION postgis UPDATE TO "2.5.1"
fails with this message
extension "postgis" has no update path from version "2.4.4" to version
"2.5.1"
In order to upgrade to version 2.5.* you need to run the following command
ALTER EXTENSION postgis UPDATE TO "2.5.2";
It gives you that error because there is no upgrade from 2.4.4 to 2.5.1. You can only move to 2.5.2 as next step.
Refer to this page under section "PostgreSQL version 10.x extensions supported on Amazon RDS".
And similarly if you wanted to go to 3.1.4 from 2.4.4, you must first go to 2.5.2 and then to 3.1.4.
I'm trying to upgrade mongodb to version 3.6. I ran brew update to get any new formulae. Then I ran brew upgrade mongodb and it complains that I already have 3.4. Is it possible to upgrade to 3.6 through homebrew, and if so, what am I doing wrong?
~: brew update
Updated 2 taps (homebrew/core, caskroom/cask).
==> New Formulae
ddgr
==> Updated Formulae
qt ✔ dialog octave suite-sparse
ansible-lint fd pyenv sundials
artifactory graphicsmagick python-markdown traefik
ceres-solver html-xml-utils reminiscence wtf
chromedriver libtiff sfk
~: brew upgrade mongodb
Error: mongodb 3.4.10 already installed
I also tried this this-morning and go the same error. I guess it is not yet available via homebrew ☹️
The mongoDB web site has a statement about it being untested on OSX 10.13:
https://docs.mongodb.com/manual/tutorial/install-mongodb-on-os-x/
I was having an issue with Facebook login, and found this.
Updating meteor and all the packages to the latest version fixed the Facebook login issue, but then I've found out that server-side rendering stopped working. I'm using FlowRouter.
I tried a different approach and instead of upgrading meteor and all the packages, I just upgraded accounts-facebook to version 1.0.12.
meteor add accounts-facebook#1.0.12
Meteor just doesn't upgrade account-facebook package, it does it do a bunch of other packages (probably to keep dependencies right), so after running the last command, this is what have changed:
accounts-base upgraded from 1.2.12_1 to 1.2.14
accounts-facebook upgraded from 1.0.10 to 1.0.12
accounts-oauth upgraded from 1.1.13 to 1.1.15
babel-compiler upgraded from 6.9.1_1 to 6.13.0
babel-runtime upgraded from 0.1.11_1 to 0.1.12
base64 upgraded from 1.0.9 to 1.0.10
binary-heap upgraded from 1.0.9 to 1.0.10
boilerplate-generator upgraded from 1.0.10 to 1.0.11
callback-hook upgraded from 1.0.9 to 1.0.10
check upgraded from 1.2.3 to 1.2.4
ddp-rate-limiter upgraded from 1.0.5 to 1.0.6
diff-sequence upgraded from 1.0.6 to 1.0.7
ecmascript upgraded from 0.5.8_1 to 0.5.9
ecmascript-runtime upgraded from 0.3.14_1 to 0.3.15
ejson upgraded from 1.0.12 to 1.0.13
es5-shim upgraded from 4.6.14_1 to 4.6.15
facebook upgraded from 1.2.9 to 1.2.11
geojson-utils upgraded from 1.0.9 to 1.0.10
http upgraded from 1.2.9_1 to 1.2.10
id-map upgraded from 1.0.8 to 1.0.9
localstorage upgraded from 1.0.11 to 1.0.12
logging upgraded from 1.1.15_1 to 1.1.16
meteor upgraded from 1.2.17_1 to 1.6.0
minimongo upgraded from 1.0.17 to 1.0.18
modules upgraded from 0.7.6_1 to 0.7.7
modules-runtime upgraded from 0.7.6_1 to 0.7.7
mongo upgraded from 1.1.13 to 1.1.14
mongo-id upgraded from 1.0.5 to 1.0.6
npm-mongo upgraded from 2.2.11_1 to 2.2.11_2
oauth upgraded from 1.1.11 to 1.1.12
oauth2 upgraded from 1.1.10 to 1.1.11
ordered-dict upgraded from 1.0.8 to 1.0.9
promise upgraded from 0.8.7 to 0.8.8
rate-limit upgraded from 1.0.5 to 1.0.6
reload upgraded from 1.1.10 to 1.1.11
routepolicy upgraded from 1.0.11 to 1.0.12
service-configuration upgraded from 1.0.10 to 1.0.11
tracker upgraded from 1.1.0 to 1.1.1
underscore upgraded from 1.0.9 to 1.0.10
url upgraded from 1.0.10 to 1.0.11
webapp upgraded from 1.3.11_1 to 1.3.12
Like the first approach, Facebook login issue has been fixed but lost SSR along the way.
Now, what could possibly be the best solution to keep both (Facebook login and SSR) working?
Thanks.
So here's how to fix:
clone a copy of the facebook package folder from Meteor 1.4.1.3 (in my case) into packages/facebook folder within the app;
apply commits meteor/meteor#873f13d and meteor/meteor#2c5dda1.
Source: [backport] Facebook API changes for 1.4.2.x accounts-facebook users. #8534
Hi I need to upgrade mongodb standalone server from 1.4.5 to 2.4 and a replica set from 1.8.3 to 2.4. I have got docs to upgrade from 2.2 to 2.4. But I am not able to get docs upgrading mongodb from version 1.4 to 2.4 or from 1.8 t o2.4. In one of the documents I found that to upgrade from 2.0 to 2.4, its first needed to upgrade to 2.2 and then to 2.4. So do I need to do gradual upgrade?