This ensures that there is no data loss events from this type of misconfiguration. The two lock files exist so that two Bitbucket Server instances can not use the same Bitbucket Server home directory or shared folder at the same time. This can happen because the portmap and dbus services (at least, in Ubuntu Linux) are not always enabled by default.īitbucket Server and Bitbucket Server Data Center will create the following lock files:īitbucket Server acquires an exclusive lock on both directories, preventing any other instances of Bitbucket Server (Server or Data Center) from using them.īitbucket Data Center acquires an exclusive lock on $/shared (allowing it to be shared with other Bitbucket Data Center cluster nodes but not Bitbucket Server instances). Cause Cau se 1:Ī common reason for this error is that your NFS lock service is disabled or misconfigured. DiagnosisĪttempt to perform a locked file operation (such as a mv) against a file in the shared Bitbucket home using flock or another similar command. File locks are released as soon as the process holding the locks closes some file descriptor for the file. If this section overlaps an earlier locked section, both are merged. If (part of) this section is already locked, the call blocks until the previous lock is released. This article is meant for a clustered Bitbucket Data Center implementation that has a shared home mounted via NFS, but could also possibly impact a Bitbucket Server instance using a mounted network location for other reasons. Set an exclusive lock on the specified section of the file. shared/.lock cannot be created in home directory.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |