cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1548
Views
10
Helpful
2
Replies

ncs bad configuration issue

elouancouvey
Level 1
Level 1

Hello, 

I just update my NSO version to ncs-5.5. 

I've add 2 neds which are : cisco-ios-cli-6.71 juniper-junos-nc-4.6.

When I try to reload my packages, I have this message : 

"./state/packages-in-use.old/1/cisco-ios-cli-6.71/private-jar/.nfs000000000513169800000011: Failed to delete: file busy"

 

I have this message for the first time and I don't know the origin of this.

 

Thanks for your help

1 Accepted Solution

Accepted Solutions

snovello
Cisco Employee
Cisco Employee
Your problem relates to NFS
See http://nfs.sourceforge.net/#faq_d2 for an explanation what that this .nfsNNNN file is doing.

One possibility is you are trying to run NSO in an NFS mounted directory. I’m not sure there is a specific statement to say this is not supported, but I would advise against,. If you have to make this directory structure available elsewhere and rsync is too slow, it has to be real time, then I would reverse the nfs mount, use a local file system for NSO and have the other server mount the directory from the NSO server.

The other possibility that a process on a remote server that mounts the NSO directory via NFS has opened a scratch file in the state directory. You should find out which server and use lsof to find the process, and kill it so the file is removed.

You may be tempted to solve your problem by using another network file system instread of NFS, but using file renaming to emulate unix remove on close semantics is common, I checked glusterFS and it does the same for example.

View solution in original post

2 Replies 2

snovello
Cisco Employee
Cisco Employee
Your problem relates to NFS
See http://nfs.sourceforge.net/#faq_d2 for an explanation what that this .nfsNNNN file is doing.

One possibility is you are trying to run NSO in an NFS mounted directory. I’m not sure there is a specific statement to say this is not supported, but I would advise against,. If you have to make this directory structure available elsewhere and rsync is too slow, it has to be real time, then I would reverse the nfs mount, use a local file system for NSO and have the other server mount the directory from the NSO server.

The other possibility that a process on a remote server that mounts the NSO directory via NFS has opened a scratch file in the state directory. You should find out which server and use lsof to find the process, and kill it so the file is removed.

You may be tempted to solve your problem by using another network file system instread of NFS, but using file renaming to emulate unix remove on close semantics is common, I checked glusterFS and it does the same for example.

Hello,

 

Thanks for your answer.

Issue come from the directory I was trying to install ncs in.

 

Issue is now solved !