Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#56926 - [mongodb] add note, that manual invastigation is required for some users
Attached to Project:
Community Packages
Opened by Mathias Rohnstock (mrohnstock) - Tuesday, 02 January 2018, 09:31 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 18 January 2018, 23:18 GMT
Opened by Mathias Rohnstock (mrohnstock) - Tuesday, 02 January 2018, 09:31 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 18 January 2018, 23:18 GMT
|
DetailsDescription:
After the upgrade from 3.4.9 to 3.6.1 and restarting the database, mongodb will immediately shutdown. In the log, the following message appear: ** IMPORTANT: UPGRADE PROBLEM: The data files need to be fully upgraded to version 3.4 before attempting an upgrade to 3.6; see http://dochub.mongodb.org/core/3.6-upgrade-fcv for more details. It makes sense, to inform the user about this, before the database get's restarted. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Thursday, 18 January 2018, 23:18 GMT
Reason for closing: Not a bug
Additional comments about closing: Documentation belongs in the wiki.
Thursday, 18 January 2018, 23:18 GMT
Reason for closing: Not a bug
Additional comments about closing: Documentation belongs in the wiki.
Comment by Platon Pronko (Rogach) -
Friday, 05 January 2018, 14:27 GMT
Any workaround to this issue? (besides downgrading entire mongodb)