[Translated from mos] When Weblogic AdminServer starts fail, the error is & quot; unable to get file lock, will retry & quot;, mosadminserver

[Translated from mos] When Weblogic AdminServer starts fail, the error is "unable to get file lock, will retry", mosadminserver

When Weblogic AdminServer starts fail, the error "unable to get file lock, will retry" is returned"

Reference Original:
Weblogic AdminServer fails with "unable to get file lock, will retry" error message (Doc ID 1613945.1)

Applicable:
Oracle WebLogic Server-Version 8.1 and later
Information in this document applies to any platform.

Objectives:
WebLogic Server startup error:
<Jan 7, 2014 9:09:20 am pst> <Info> <Management> <BEA-141281> <unable to get file lock, will retry...>
<Jan 7, 2014 9:09:30 am pst> <Info> <Management> <BEA-141281> <unable to get file lock, will retry...>
<Jan 7, 2014 9:09:40 am pst> <Info> <Management> <BEA-141281> <unable to get file lock, will retry...>
<Jan 7, 2014 9:09:50 am pst> <Info> <Management> <BEA-141281> <unable to get file lock, will retry...>
<Jan 7, 2014 9:10:00 am pst> <Info> <Management> <BEA-141281> <unable to get file lock, will retry...>

Solution:
When a server is started, A. lok file is created. The file is in $ FMW_HOME/servers/SERVERNAME/tmp/SERVERNAME. lok. If the file exists, it cannot be created again and cannot be started by the server.
To solve this problem, delete an existing lok file or kill the running process that is holding the file.

Error/tmp/AdminServerlok (No such file or directory) When weblogic is started

The file may be deadlocked.
In this case, you should use the "fuser-u file name" command to find the process in which the file is deadlocked.

When weblogic is started, the following error occurs:

Unable to obtain lock on E: \ base_domain \ servers \ AdminServer \ tmp \ AdminServer. lok. Server may already be running

Check the error. You have restarted weblogic again. Is there a service running!

Restart the machine!