I tried searching for the forum for a similar problem, but haven’t found one. Of course this happened while I was out of the office, so I’m not sure what could’ve triggered it or exactly what happened, but here goes. Basically, our network Repository directory’s content was completely gone except the folders structure was intact. Users, jobs (current and archived), slaves, etc. all gone. Then I went ahead and copied over the Repository directory from my local computer so we could at least get up and running again (of course having to reconfigure everything). After I did that and connected the slave on my machine to the Repository I kept getting an error saying it couldn’t update the slave info file as it was being accessed by another program. I restarted the machine, same thing.
So far, I have our IT seeing if they can replace the directory with a backup from a couple days ago, but wanted to see if anyone else ever had this happen.
-Chip
That’s really strange. Was there maybe some sort of disk failure on the repository machine? Hopefully the backup works. If it doesn’t, maybe try reinstalling the repository to a different folder on the server, but then configure the share so that it’s the same as it was before. That way, you don’t have to update any of the slaves to point to a new repository path.
Cheers,
Technically, it’s just a big NAS, so lots of network shares on it. That being said, all I can really do is move it to a different directory within our own share. The thing that is weird is that after I updated the Repository to default, it was giving me errors about updating slave.info file saying it was being used by another program. Then the same thing happened to a user when he submitted a job and tried to chance settings while in Super User Mode. Said he couldn’t change them because it was locked by another program. I’ll follow up once our IT has tried to sort out the backup.
Ryan, thanks so much for following up! 
-Chip
Ryan,
Below is what is generated by the slave upon starting.
I replaced our server name and share name with \server\share
I don’t know what process could be accessing it. The slave client has admin rights and my user has read/write/execute rights on the network share. Slave info file is showing me as the Owner, so not sure what the deal is. This is all very strange. Still waiting on IT to follow up on the backup.
-Chip
Are you guys running Pulse? If so, try restarting it to see if that helps. Maybe restart any Monitors you have running too.
Finally, is it possible to reboot the NAS drive? In theory, that should release any locks it has open.
Nope, no Pulse. Also told all users to shut down any launchers (not just monitors, but the whole thing. lol!) they had running.
Unfortunately, that would require about 50 different depts. to be down. lol! I can see what I can do about it. I was able to submit a job and change settings myself, so I’m not sure what the deal is. It’s not critical right now as we’re not rendering, so it may just wait until Monday to look into it further. Maybe see if IT can put in a notice of restart over the weekend.
Also, just an edit here. I’m able to manually delete the slave.info file. And whenever the slave is restarted, it gives me the same error.
Thanks again for following up.
-Chip