3.6.0 Upgrade Support
-
@dave1904 said in 3.6.0 Upgrade Support:
EDIT: npm install fixed it for me. thanks @phenomlab
You're welcome!
-
For whatever it is worth
I had to run a "rebuild & restart" in the ACP after upgrade from 3.5.0 > 3.6.1, for the ACP to register the 3.6.1 version, it was still alerting me to update to 3.61 from 3.5.0
I also got this error at the end of upgrading (before running the ACP rebuild-restart) post
./nodebb start
command:Error: kill EPERM at process.kill (node:internal/process/per_thread:233:13) at /home/nodebb/loader.js:198:14 at /home/nodebb/node_modules/graceful-fs/graceful-fs.js:362:16 at FSReqCallback.oncomplete (node:fs:200:23) /home/nodex/nodebb/loader.js:211 throw err; ^ Error: kill EPERM at process.kill (node:internal/process/per_thread:233:13) at /home/nodebb/loader.js:198:14 at /home/nodebb/node_modules/graceful-fs/graceful-fs.js:362:16 at FSReqCallback.oncomplete (node:fs:200:23) { errno: -1, code: 'EPERM', syscall: 'kill' } Node.js v18.17.1
However the NodeBB install appears to work
-
Hi @baris
Thanks for opening this topic.
I am currently running v.2.8.1 and need to upgrade to the latest (v3.6.3).
I plan to shut down my current VM and choose a different provider. I will be taking a dump from the current MongoDB and backing up public uploads so I can connect the same DB with v3.6.3.
I did some reading but could not find anything that says that there is any discrepancy between a v2.x db and a v3.x db. Neither have I had a chance to perform this on a test server yet so was wondering to perform the upgrade as above in a totally new VM whether I need to:
- Install my current version on a new VM, restore the dump and connect the DB and public uploads, and then upgrade that to v3.6.3
- Install v3.6.3 in one go on a new VM, restore the dump and connect the DB and public uploads
Any insight would be appreciated!
Thanks -
Hi @baris
Thanks for the response.- Install my current version on a new VM, restore the dump and connect the DB and public uploads, and then upgrade that to v3.6.3
* Install v3.6.3 in one go on a new VM, restore the dump and connect the DB and public uploads
Do you mean that instead of installing v3.6.3 straightaway and restoring the DB dump (dumped from v2.8.1 earlier), it would be wiser to install v2.8.1 on a new VM, restore the db dump, and then upgrade to V3.6.3?
- Install my current version on a new VM, restore the dump and connect the DB and public uploads, and then upgrade that to v3.6.3
-
@yasas you should be able to install v3.6.3 right away and then just run
./nodebb upgrade
first thing. -