nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is deployment to a NFS mount is legitimate?

psr

Hi,

TS 552
OD 5.6

I am trying to deploy to a NFS mout point on a server on which "regular deployment works without any issue".

Its giving me following error,

The target deployment path used on NFS Mount is:
/files/stage/java

The target log file alos shows following error:
ENG: 2006-04-26 15:44:49 BST GMT+01:00 Thread-4 COMPARE
id=0 server: FailedCommit 0.
id=0 server: Destination directory [/files/stage]
ERROR: [/files/stage] is not an allowed deployment path.
ERROR: Failed deploying local_directory[0] (/export/home/deven/temp/test) to (/files/stage)
ERROR: Failed 1 of 1 local_directories
ENG: 2006-04-26 15:44:49 BST GMT+01:00 Thread-4 After COMPARE res=-1

The facts:
- The deployment works successfully on the same server on non NFS folders
- The error above, generally means that the path that OD is trying to deploy to is not an allowed deployment path. But the deployment path very well exists in the allowed deployment paths (as /files/stage) on the target servers odrcvr.xml
- The permissions are all 777 for the folders & sub-folders & user/group do exist on the taeget server, with other config details verified many times.

The important thing is case already opened with IWOV since more than a month now & been moved to higher level support since 2-3 weeks. The techteam is saying we should be able to deploy to NFS. but till date they dont have any positive suggestion in the case & were also experiencing simillar error.

I was just wondering, if anybody have tried deploying to NFS mount with success? & if configutration/setting is anyway different than the regular deployment. With no access to the target servers (I have to request the admins to cross check the things) I am kind of blocked now for the tests from my end.

!Thanks
ANC

Find more posts tagged with

Comments

nipper

One possibility

OD normally runs as root. However NFS does not recognize root access by default, the mount must be made allowing root access. Usually when root tries to access a shared drive, it is done as Nobody, which is severely limited. Even with 777 perms.

Can you get the sys admin to mount with root access turned on ?

HTH

Andy

psr

Nipper,

I guess root is default allowed for all NFS access, after mount. Let me request sysadmins for the details, how its currently setup & to turn ON the root access in case does not exist. That will be interesting.

!Thanks
ANC

nipper

Nipper,

I guess root is default allowed for all NFS access, after mount. Let me request sysadmins for the details, how its currently setup & to turn ON the root access in case does not exist. That will be interesting.

!Thanks
ANC

No, by default root is not allowed. You must explicitly allow it. Big security hole if it was allowed by default.

Depends on how NFS mounts are done. This is from man mount...

For example, if host A were to export a filesystem /F,
which would be mounted with CacheFS on host B, then the /etc/exports on
host A would need to have an entry similar to:

/F -rw,root=B

psr

Nipper,

The details look OK to me,

Here is the response from Unix Admin:-
--------------
Exports and imports are owned by root with the subdirectories owned by the applications account.

Here is folder specific info:
for "files"
drwxr-xr-x 4 root root 96 Feb 1 11:26 files

for "stage"
drwxrwxr-x 5 kestg kestg 1024 Feb 25 14:03 stage
--------------
!Thanks
ANC

timetableSectionwise.rptdesign

r21 - Timetable Section Wise.pdf

nipper

not quite.

Try this.

as root on the system that is mounting the disk,
cd files
touch foo

If it creates a file named foo on that NFS mount, then there are no issues. If it fails, then you have a problem

psr

Nipper,

The root access is well set on the NFS & was able to create the foo file.

!Thanks
ANC

dispatchReport.rptdesign

r2 - weekly attendance report.pdf

13adam13

ERROR: [/files/stage] is not an allowed deployment path.

Perhaps the issue is that in the odrcvr.xml on the reciever, the path has not been configured as an allowed path.