v1.6.0 permission problems after upgrade/update
-
At this point should I delete the
build
directory and try to run./nodebb build
? I'm nervous that command won't work since I can't run./nodebb log
. -
try
sudo chown -R www-data nodebb
. If that doesn't work then try deleting stuff -
@pitaj said in v1.6.0 permission problems after upgrade/update:
try
sudo chown -R www-data nodebb
. If that doesn't work then try deleting stuffThat changed this, yes?
-rw-r--r-- 1 www-data www-data 15468 Aug 4 00:08 nodebb
Still doesn't seem to get me to where I can run
./nodebb log
. Getting this error:-su: ./nodebb: Permission denied
. -
@pitaj said in v1.6.0 permission problems after upgrade/update:
If that doesn't work then try deleting stuff
Oh lawdy.
-
Any advice on a fresh install?
-
Check and make sure that you're actually lived in as www-data.
Permission issues should be fixable
-
This post is deleted!
-
Yeah that would certainly do it. The
chown -R
should have fixed that though if you ran it with sudo. -
@pitaj said in v1.6.0 permission problems after upgrade/update:
Yeah that would certainly do it. The
chown -R
should have fixed that though if you ran it with sudo.Yeah, for some reason I still can't run
./nodebb log
. Hmmm. Back to the drawing board. -
Oh, wait a second. Your user is
mike
? In that case, the crown command should havemike
not www-data I think. Have you tried editing those files from the account? Also, check the log directory ownership and permissions. -
This post is deleted!
-
@michael-pfaff can you try editing one of the files with nano or vim? If there's an error there then that would confirm the issue
-
@pitaj said in v1.6.0 permission problems after upgrade/update:
@michael-pfaff can you try editing one of the files with nano or vim? If there's an error there then that would confirm the issue
Just open any file in that directory?
-
@michael-pfaff yeah just try editing one of the log files and see if you still get an error. You might also try using chmod to change the actual permissions on the files rather than the ownership.
-
@pitaj said in v1.6.0 permission problems after upgrade/update:
@michael-pfaff yeah just try editing one of the log files and see if you still get an error. You might also try using chmod to change the actual permissions on the files rather than the ownership.
Seemed like I could edit and save it just fine using
nano output.log
.