@pitaj but why with this particular version? from v1.4.x to v1.5.x was perfectly fine... now I should be doing it with my nodebb account? That should be added to the docs, I think. My nodebb account is literally just a service account [nologin account with selinux limiting it too, and correct policies are applied to it too]...
1.6.0 uses compiled template files, which if owned by root... Are not so accessible 
@julian is that one of the changes?
the 2 lines I ran was literally this (as root):
systemctl stop nodebb; git fetch; git checkout v1.5.x; git merge origin/v1.5.x; ./nodebb upgrade; systemctl start nodebb
wait a minute and the forum works, without an issue (upgrading from v1.4.6 to v1.5.3)
next (as root):
systemctl stop nodebb; git fetch; git checkout v1.6.x; git merge origin/v1.6.x; ./nodebb upgrade; systemctl start nodebb
File ownership is not correct (might be due to extra files not being there, due to older release) and once ownership is corrected, pages get stuck until it is refreshed.
Should I try a different branch, maybe?
@adam-poniatowski what is your service file? My guess is that it starts nodebb under the nodebb user. Running ./nodebb upgrade as root is going to mess stuff up because it will change the ownership of certain files and directories during the build step.
@pitaj but it doesn't explain why when I do this from v1.4 to 1.5 it works fine, but v1.5 to v1.6 it doesn't work. If that was one of the changes in the upgrade parameter, then I will try it with my nodebb account (which my service file is using nodebb.service)
@adam-poniatowski because templates are done differently in v1.6.0, because it uses Benchpress.
@pitaj aaah ok... so what step should I change to update it properly then? let my nodebb account run ./nodebb upgrade or should I let my account fetch/checkout/merge as well (which I will have to modify some policies for that)?
Ideally you should run everything without root, and under the nodebb account. Everything besides systemctl commands, that is. @julian pointed out above how best to run bash under a different user: su - nodebb
@pitaj that part I already know. I am a sysadmin as well... freebsd habits, when it comes to starting services (I am not really in the mood to explain admin tasks for spinning up services in any OS with an admin/root account, too tired for that now).
short answer could've been:
due to changes to v1.6.0, it is mandatory to use the account that you use for nodebb for upgrading, to avoid extra admin work and/or issues.
off to bed with me ;(
as a last ditch effort... I did it again, but upgrading with the nodebb account...
v1.4 ---> v1.5 = perfect
v1.5 ---> v1.6 = now I don't get internal server error, but pages get stuck ~75% and when I manually refresh, it works (*edit to add: for every page I go to, besides login and admin).
I'm sticking to v1.5 until I can find the time and strength to reinstall it to v1.6
I have same problem
after this
git fetch
git checkout v1.6.0
./nodebb upgrade
first time i found nodebb-plugin-category-sort-by-title will make nodebb crash, i disable it
then i found
Error: EACCES: permission denied, open '/home/nodebb/build/public/templates/recent.jst'
then
chown -R nodebb /home/nodebb
problem solved
It Works!
sudo chown -R $USER:$GROUPS NodeBB/
sudo chmod -R 770 build/
I think I'm having the same issue here, folks. I installed everything and have always done upgrades as root. Now, when trying to upgrade from 1.5.3 to 1.6.1 I get permission denied errors.
I have never used my NodeBB login to do anything with NodeBB as far as installation or upgrading, and so I'm kind of lost on how to fix all this. 
@michael-pfaff You shouldn't be using root to do anything with ./nodebb. You should always do such things as the nodebb user or whatever user you use to run it.
The easiest way to fix this is to delete the build directory, and then su - nodebb and run ./nodebb build as that user.
@pitaj said in v1.6.0 permission problems after upgrade/update:
@michael-pfaff You shouldn't be using root to do anything with
./nodebb. You should always do such things as thenodebbuser or whatever user you use to run it.The easiest way to fix this is to delete the
builddirectory, and thensu - nodebband run./nodebb buildas that user.
Thanks, @PitaJ. I didn't realize that was the case. I'll try this out and see if it works.
To clarify:
What does the su - nodebb command do exactly?
Appreciate all the help.
@michael-pfaff su - nodebb switches to the nodebb user and goes to their home directory.
@baris said in v1.6.0 permission problems after upgrade/update:
@michael-pfaff
su - nodebbswitches to the nodebb user and goes to their home directory.
Sorry y'all. Just getting around to doing this. Apparently, I don't have a nodebb user. And, I'm not entirely sure what user was used to install nodebb. So, it's not letting me do anything. Can't even use the ./nodebb stop command like I used to at root.
I didn't initially install NodeBB on my server. Is there a way to determine which user? Can I do a fresh install with my old data?
You can run ls -l to see who owns the files in the nodebb directory and change ownership with chown -R nodebb <nodebb_folder> command
ls -l with an l not 1
