This article explains how to regain access to a locked or unavailable profile. This occurs if
You receive a message that the selected profile is already "in use" while using the
You start the application and it won't run, but it doesn't display any error messages.
You see an error that your SeaMonkey or Firefox "profile cannot be loaded. It may be missing or inaccessible"
A "Close Firefox",
"Close Thunderbird", or (starting in SeaMonkey 2) "Close SeaMonkey" dialog box appears with one of these messages
(using Firefox as an example) :
(On Mac OS)
A copy of Firefox is already open. Only one copy of Firefox can be open at a time."
(On Mac OS)
A copy of Firefox is already open. The running copy of Firefox will quit in order to open this one.
Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system. (shown below):
Firefox is already running, but is not responding. The old Firefox process must be closed to open a new window.
Starting in Firefox 34 on Windows (Vista and above), the "Firefox is already running" dialog includes a "Close Firefox" button (shown ) that, when clicked,
dismiss the dialog, end the Firefox process(es) and, after a few seconds, will automatically restart Firefox. .
[]Common causes
The most common cause of this error is that your Mozilla application did not shut down properly.
It might still be running in the background (even though it's not visible) or it might have closed abnormally, without deleting the lock file.
To avoid conflicts, Mozilla applications such as ,
are designed to allow only one copy of the application to access a
at the same time.
This is done by checking for the existence of a lock file when it starts. If the lock file already exists, the application exits with an error message.
Otherwise, it creates a lock file in the profile and deletes it at exit.
Normally this is completely tra however, in the case of an abnormal shutdown, the application might not delete the lock file, preventing you from using the profile.
Other causes include the following:
This error can occur
because of a delayed shutdown, if you try to reopen it too soon after it was last closed.
Another possible cause is that your Mozilla application cannot find the
because it is not in the expected location ().
This error will occur if you moved the profile to an external drive and forgot to turn it on. You might also run into it if the profile is on a file share and you didn't mount it/redirect the drive to it.
You can also get this message if you try to open a link from an external program (e.g., double-click a link in an email or HTML file) and there is another instance running that uses the default profile and that was started with the -no-remote argument (or you have the environment variable MOZ_NO_REMOTE=1 set).
You should never use -no-remote to start the "default" profile.
for more information.
Note: Entering an incorrect -profile &path&
used to produce this error and was commonly caused by entering -Profile Manager by mistake (instead of the correct -ProfileManager argument) when trying to start the .
Currently, due to the fix for , instead of producing an error a new profile is created at &path& and launched.
[]Solutions
[]End processes
Go through your
and stop each instance of the Mozilla application, or restart your computer.
(If you need to do this on a recurring basis,
for possible causes and solutions.)
[]Remove the profile lock file
The application may have shut down abnormally, leaving the lock in place.
To fix this, open the
and delete the file,"parent.lock" (Windows),"lock" and ".parentlock" (Linux), or".parentlock" (Mac OS X)
For Mac OS X: You need to use a free utility like Onyx or Maintain to turn on visibility for invisible files to show ".parentlock". This file contains no information, and deleting it will unlock the profile.
For Windows: If you attempt to delete the "parent.lock" file and receive the error, "Cannot delete parent: The file or directory is corrupted and unreadable", restart the computer and run the system
in Windows 2000/XP/Vista/7 or
in Windows 98/ME). .
[]Check the profile folder name and location
your Mozilla application cannot find the
it will typically report that the profile is in use or, in Firefox, Thunderbird, and SeaMonkey 2,
that the application "is already running, but is not responding" or that your ". It may be missing or inaccessible".
This can happen if you delete, rename or move the profile folder, if you run the application from removable media, or if the profile folder is stored on a network drive ().
If possible, you should restore the profile folder to its original name and location, so that your Mozilla application can find it. Alternately, you can edit the "profiles.ini" file to show the changed location () .
Another solution is use the
to create a new profile that points to the new folder location, by using the "Choose Folder" option during the profile creation process. See
for more information.
Important: If you deleted your only profile folder, have no backup to restore and are now seeing the "already running" dialog box, delete or rename the
(or its parent Firefox, Thunderbird, or SeaMonkey folder) in the
path. A new default profile will be created when you next start your Mozilla application.
[]Check the profiles.ini file
Firefox, Thunderbird, and SeaMonkey 2 look for the profile folder based on the information stored inside the
(see the linked article for details).
You can use a text editor such as Notepad to open the "profiles.ini" file to see what information it contains.
Here is an example:
StartWithLastProfile=1
[Profile0]
Name=default
IsRelative=1
Path=Profiles/v6zui74n.default
IsRelative=1 indicates a relative path in the expected profile location, as above.
IsRelative=0 indicates a custom (absolute) profile location, for example, someone might use this to put their profile on a thumb drive or removable disk:
IsRelative=0
Path=D:\firefoxProf
If you can't spot an error in that file try running the Mozilla application . This bypasses the profile manager and profiles.ini. If you succeed then you know that the problem is with profiles.ini, For example,
firefox.exe -profile "C:\Documents and Settings\&user&\Application Data\Mozilla\Firefox\Profiles\xxx.default''
That example is for XP. &user& is the Windows log-in user account name and "xxx" is a random string.
If that fails check that the location of each profile is correct and edit its location in the profiles.ini file if necessary. If that fails you probably need to use the Profile Manager to create a new version of that file (see below) but there are a couple other solutions you should consider first.
[]Check access rights
This problem can also occur if you don't have the rights to edit the files in the profile (or create the lock file in the first place). Please note that this can happen if you try to use a profile from a filesystem mounted with read-only (e.g. a remote Windows share which doesn't have "allow network users to change my files" checked). This can be pretty tricky to diagnose because there is no lock file in the profile, yet the same message appears (profile in use).
Incidentally, Linux users may have ~/.thunderbird and/or ~/.mozilla-thunderbird in their home directories if they have had more than one version of Thunderbird installed.
[]Check for other applications using the profile
SeaMonkey 1.x, Mozilla Suite, and Netscape 7 all use the same
and profile registry.
If two or more of these programs are installed and you see a "profile in use" message, another of these programs may be using the profile.
Try shutting down this program to unlock the profile.
Additionally, you should
SeaMonkey 1.x, Mozilla Suite, and/or Netscape 7, as profile corruption can result if these programs share the same profile.
(This problem does not occur with Firefox and Thunderbird, which do not share profiles with other applications in the same way that SeaMonkey 1.x, Mozilla Suite, and Netscape 7 do.)
[]Initialize the connection to a file share
If you are running Windows and store the profile on a file share try accessing the file share beforehand using Windows Explorer. Some users have reported this prevents the problem.
[]Create a replacement
Mozilla applications are extremely picky about the contents of the profiles.ini file, they will not ignore any errors in it, even if they're for other profiles. If you can't fix the problem by editing the location backup the profiles.ini file, delete the original, and then follow the instructions in
to create a new known good profiles.ini file and have the profile manager update it with the location of your profile. If that works you can "move the profile" again to tell it about other profiles.
[]Restoring data from a locked profile
If you are unable to unlock the profile using the above methods, use the
to create a new profile and
from the locked profile to the new profile.
[]See also
[]External links
[]Related bug reports
(Thunderbird) -Fixed in TB trunk/3.x as ofweblogic unable to get file lock问题 - zhengqiqiqinqin的专栏
- 博客频道 - CSDN.NET
5487人阅读
原文地址：
非正常结束weblogic进程导致weblogic无法启动
由于先前服务器直接down掉了，所有进程都非正常的进行关闭了，也就导致了下次启动weblogic的时候报了以下错误：
& 下午05时08分34秒 CST& &Info& &Management& &BEA-141281& &unable to get file lock, will retry …&&
& 下午05时08分44秒 CST& &Info& &Management& &BEA-141281& &unable to get file lock, will retry …&
一.删掉Domain下的*.lok文件
1. 删除edit.lok
进入到domain_home下：
cd /u01/Oracle/Middleware/user_projects/domains/idm_domain
将edit.lok文件删掉
rm edit.lok
2.删除config.lok
进入到domain_home/config下：
cd /u01/Oracle/Middleware/user_projects/domains/idm_domain/config/
将config.lok文件删掉
rm config.lok
3.删除AdminServer.lok
cd /u01/Oracle/Middleware/user_projects/domains/idm_domain/servers/AdminServer/tmp
rm AdminServer.lok
4.删除EmbeddedLDAP.lok
/u01/Oracle/Middleware/user_projects/domains/idm_domain/servers/AdminServer/data/ldap/ldapfiles
rm EmbeddedLDAP.lok
二.删掉Domain下的*.DAT文件：
进入到domain_home当中
cd /u01/Oracle/Middleware/user_projects/domains/idm_domain
找到文件被删掉
[oracle@idm idm_domain]$ find servers/ -name &*.DAT&&
servers/AdminServer/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT&
servers/AdminServer/data/store/default/_WLS_ADMINSERVER000000.DAT
* 以上用户言论只代表其个人观点，不代表CSDN网站的观点或立场
访问：534790次
积分：7626
积分：7626
排名：第1061名
原创：199篇
转载：197篇
评论：97条
(1)(1)(1)(2)(14)(8)(10)(21)(44)(14)(6)(17)(20)(62)(31)(11)(50)(12)(10)(7)(13)(12)(3)(10)(9)(7)yesu898 的BLOG
用户名：yesu898
文章数：178
访问量：23177
注册日期：
阅读量：48754
阅读量：2873
51CTO推荐博文
一、启动关闭weblogic命令
#bin/nohup ./startWebLogic.sh &&& 启动信息输出打到本路径下nuhup.out文件内。
#./stopWebLogic.sh
如果用root帐户启动了weblogic则有部分文件会自动修改属主为root，所以再用weblogic用户启动则无法启动weblogic服务。
需要chown&-R&weblogic:weblogic&&mydomain_dir&
二、Weblogic修改默认console增强安全性
我们可以修改console为你想要的值如“bestpay”，不使用默认登陆界面，加强安全性。
三、修改weblogic端口
1，Vi Config/config.xml
&name&AdminServer&/name&
&listen-port&7002&/listen-port&
&listen-address&192.168.x.x&/listen-address&
2，这样是停不掉服务的需要修改./stopWebLogic.sh
把其中7001改成7002
3，如果改成80端口，linux下0~1024端口启动要有更高权限。Weblogic用户启动会报Permission denied。 所以要用root用户启动。
四、启动时提示如下报错：
&Jun 25, :08 PM CST&
&Info& &Management& &BEA-141281& &unable to get file lock,
will retry ...&
&Jun 25, :38 PM CST&
&Info& &Management& &BEA-141281& &unable to get file lock,
will retry ...&
查找lok文件然后删除
bash-3.2$ cd Middleware/
-bash-3.2$ find . -name *.lok
./user_projects/domains/adf_domain/edit.lok
./user_projects/domains/adf_domain/servers/ADFServer/tmp/ADFServer.lok
./user_projects/domains/adf_domain/servers/ADFServer/data/ldap/ldapfiles/EmbeddedLDAP.lok
./user_projects/domains/adf_domain/servers/AdminServer/tmp/AdminServer.lok
./user_projects/domains/adf_domain/config/config.lok
另外删除DAT文件，路径如下：
servers/AdminServer/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT
servers/AdminServer/data/store/default/_WLS_ADMINSERVER000000.DAT
删除即可。
了这篇文章
类别：┆阅读(0)┆评论(0)weblogic unable to get file lock问题 - 世上无难事，只要肯攀登
- 博客频道 - CSDN.NET
本文转自：http://blog.csdn.net/zhengqiqiqinqin/article/details/
非正常结束weblogic进程导致weblogic无法启动
由于先前服务器直接down掉了，所有进程都非正常的进行关闭了，也就导致了下次启动weblogic的时候报了以下错误：
& 下午05时08分34秒 CST& &Info& &Management& &BEA-141281& &unable to get file lock, will retry …&&
& 下午05时08分44秒 CST& &Info& &Management& &BEA-141281& &unable to get file lock, will retry …&
一.删掉Domain下的*.lok文件
1. 删除edit.lok
进入到domain_home下：
cd /u01/Oracle/Middleware/user_projects/domains/idm_domain
将edit.lok文件删掉
rm edit.lok
2.删除config.lok
进入到domain_home/config下：
cd /u01/Oracle/Middleware/user_projects/domains/idm_domain/config/
将config.lok文件删掉
rm config.lok
3.删除AdminServer.lok
cd /u01/Oracle/Middleware/user_projects/domains/idm_domain/servers/AdminServer/tmp
rm AdminServer.lok
4.删除EmbeddedLDAP.lok
/u01/Oracle/Middleware/user_projects/domains/idm_domain/servers/AdminServer/data/ldap/ldapfiles
rm EmbeddedLDAP.lok
二.删掉Domain下的*.DAT文件：
进入到domain_home当中
cd /u01/Oracle/Middleware/user_projects/domains/idm_domain
找到文件被删掉
[oracle@idm idm_domain]$ find servers/ -name &*.DAT&&
servers/AdminServer/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT&
servers/AdminServer/data/store/default/_WLS_ADMINSERVER000000.DAT
删除这些文件之后，weblogic 如果停止不了，根据端口号，
netstat -apn | grep xxx(xxx为端口号)
查到进程编号，kill掉就可以了。在重启WebLogic，恩，启动ok。
* 以上用户言论只代表其个人观点，不代表CSDN网站的观点或立场
访问：170734次
积分：2459
积分：2459
排名：第6946名
原创：76篇
转载：35篇
评论：36条
(1)(1)(1)(3)(1)(1)(4)(3)(4)(7)(1)(5)(3)(4)(5)(7)(1)(7)(1)(8)(13)(13)(14)(3)由于weblogic服务直接down掉了，所有进程都非正常的进行关闭了，也就导致了下次启动weblogic的时候报了以下错误：
& 下午05时08分34秒 CST& &Info& &Management& &BEA-141281& &unable to get file lock, will retry &&&B3h8F@E;f;tu9S0& 下午05时08分44秒 CST& &Info& &Management& &BEA-141281& &unable to get file lock, will retry &&
一.删掉Domain下的*.lok文件
1. 删除edit.lok
进入到domain_home下：
cd /u01/Oracle/Middleware/user_projects/domains/idm_domain
将edit.lok文件删掉
rm edit.lok
2.删除config.lok
进入到domain_home/config下：
cd /u01/Oracle/Middleware/user_projects/domains/idm_domain/config/
将config.lok文件删掉
rm config.lok
3.删除AdminServer.lok
cd /u01/Oracle/Middleware/user_projects/domains/idm_domain/servers/AdminServer/tmp
rm AdminServer.lok
4.删除EmbeddedLDAP.lok
/u01/Oracle/Middleware/user_projects/domains/idm_domain/servers/AdminServer/data/ldap/ldapfiles
rm EmbeddedLDAP.lok
二.删掉Domain下的*.DAT文件：
进入到domain_home当中
cd /u01/Oracle/Middleware/user_projects/domains/idm_domain
找到文件被删掉
[oracle@idm idm_domain]$ find servers/ -name "*.DAT"&ITPUB个人空间U0s!W/d*ybM'Vn+xservers/AdminServer/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT&ITPUB个人空间QQu k1gZ?0?servers/AdminServer/data/store/default/_WLS_ADMINSERVER000000.DAT
*********************************************************解决示例*****************************************************************
weblogic域地址:
/root/weblogic11/middleware/user_projects/domains/xoafind -name "*.lok"&&&&&&&&&&&&&&& &//查找域下所有.lok文件find -name "*.DAT"&&&&&&&&&&&&&&&//查找域下所有.DAT文件
下面是查出的结果：（对照地址删除相应的文件）
/config/config.lok/servers/AdminServer/data/ldap/ldapfiles/EmbeddedLDAP.lok/servers/AdminServer/tmp/AdminServer.lok
/servers/AdminServer/data/store/default/_WLS_ADMINSERVER000000.DAT/servers/AdminServer/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT
*********************************************************解决示例*****************************************************************
weblogic启动和关闭进程脚本：
启动脚本：（weblogic_startup.startup）
# Get the aliases and functions# User specific environment and startup programsexport LANG=zh_CN.GB2312dd=`date +%Y%m%d`nohup sh ./startWebLogic.sh 2&&1 & nohup.out.${dd} &tail -f ./nohup.out.${dd}
关闭脚本：（weblogic_stopup.stopup）
# Get the aliases and functions# User specific environment and startup programs#export LANG=zh_CN.GB2312#dk=`8888`#nohup sh ./startWebLogic.sh 2&&1 & nohup.out.${dd} &#tail -f ./nohup.out.${dd}lsof -i:80 | cut -c 8-13 | xargs kill -9lsof -i:80 | cut -c 8-13 | xargs kill -9
阅读(...) 评论()}