Closed seisman closed 1 month ago
I guess it's because Paul is the owner of these directories.
Where are those directories located?
There are also some files/directories own by Paul in the candidate server (e.g. /export/gmtserver/gmt/candidate/server/earth/earth_synbath).
What can we do? Make another directory?
I guess it's because Paul is the owner of these directories.
Where are those directories located?
There are also some files/directories own by Paul in the candidate server (e.g. /export/gmtserver/gmt/candidate/server/earth/earth_synbath).
What can we do? Make another directory?
I'm talking about the /export/gmtserver/gmt/gmtserver-admin
. It's a local clone of this repository. The server should update the local clone and then copy the files in cache
to the /export/gmtserver/gmt/data
directory. But as I said, the cron job failed to run.
What can we do? Make another directory?
Since it's just a local copy of this repository, I think we can delete this directory, make a new clone, and then add the cron job. All these steps should be done by a single account. I can do it if you're OK with it.
Since it's just a local copy of this repository, I think we can delete this directory, make a new clone, and then add the cron job. All these steps should be done by a single account. I can do it if you're OK with it.
Do you mean the gmtserver-admin
directory? or the candidate
? or both?
Just the gmtserver-admin
directory.
For other directories, the owner is still Paul and the group is gmt
. We're all in the gmt
group, so we should be able to read and write the directories without permission issues.
The gmtserver-admin
directory is special that it contains .git
directories which have files that are read-only to Paul.
For other directories, the owner is still Paul and the group is
gmt
. We're all in thegmt
group, so we should be able to read and write the directories without permission issues.
So you suggest to leave it like this?
Since it's just a local copy of this repository, I think we can delete this directory, make a new clone, and then add the cron job. All these steps should be done by a single account. I can do it if you're OK with it.
Ok, go ahead with this.
Since it's just a local copy of this repository, I think we can delete this directory, make a new clone, and then add the cron job. All these steps should be done by a single account. I can do it if you're OK with it.
Ok, go ahead with this.
OK, I've renamed the old gmtserver-admin
to gmtserver-admin-pwessel
and also add a cron job using my account. The next cron job is expected to run in a few minutes. Will see if it works.
@Esteban82
drwxrwxr-x 14 pwessel gmt 4096 Aug 8 16:50 .
drwxr-xr-x. 13 root root 242 Mar 4 19:06 ..
drwxrwxr-x 2 pwessel gmt 153 Nov 8 2023 ancient
drwxr-xr-x 2 seisman gmt 4096 May 11 2020 BlackMarble2016
drwxrwxr-x 4 pwessel gmt 163 Aug 8 10:10 candidate
drwxrwxr-x 5 pwessel gmt 4096 Aug 8 14:56 data
drwxrwxr-x 10 seisman gmt 4096 Aug 8 16:49 gmtserver-admin
drwxrwxr-x 10 pwessel gmt 4096 Dec 12 2023 gmtserver-admin-pwessel
drwxrwxr-x 2 pwessel gmt 33 Aug 5 02:24 LOGS
drwxrwxr-x 17 esteban82 gmt 4096 May 16 16:17 old-earth-relief_2.5.5
drwxrwxr-x 2 pwessel gmt 4096 Oct 17 2019 old-earth-reliefs-v1
drwxrwxr-x 2 pwessel gmt 4096 Mar 15 2020 old-earth-reliefs-v2
drwxrwxr-x 4 pwessel gmt 105 Sep 13 2023 static
drwxrwxr-x 4 pwessel gmt 4096 Dec 13 2023 test
Perhaps we should create a backup
directory and move the old/unused directories like old-earth-reliefs-v1 to it.
I think it works.
In #266, I added a new file to cache, but the server is not updated.
Then I login in the server and see the log file
git_update.cron.log
.The cron job hasn't run at all since February.
I also can't run the update script
gmtserver-admin/scripts/srv_git_update.sh
orgit pull origin master
, with errors like:I guess it's because Paul is the owner of these directories.