【已解决】Ubuntu下weblogic启动报错

本文记录了一次WebLogic服务器启动失败的问题及解决过程。启动失败的原因是EmbeddedLDAP服务初始化错误,通过调整文件权限解决了该问题。

Q

问题描述:一段时间没启动weblogic,启动突然报错如下

$ sh /home/weblogic/user_projects/domains/base_domain/startWebLogic.sh
.
.
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m  -XX:MaxPermSize=256m
.
WLS Start Mode=Development
.
CLASSPATH=/home/weblogic/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/weblogic/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/local/jdk1.7.0_80/lib/tools.jar:/home/weblogic/wlserver_10.3/server/lib/weblogic_sp.jar:/home/weblogic/wlserver_10.3/server/lib/weblogic.jar:/home/weblogic/modules/features/weblogic.server.modules_10.3.6.0.jar:/home/weblogic/wlserver_10.3/server/lib/webservices.jar:/home/weblogic/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/weblogic/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/home/weblogic/wlserver_10.3/common/derby/lib/derbyclient.jar:/home/weblogic/wlserver_10.3/server/lib/xqrl.jar:.:/usr/local/jdk1.7.0_80/lib/dt.jar:/usr/local/jdk1.7.0_80/lib/tools.jar
.
PATH=/home/weblogic/wlserver_10.3/server/bin:/home/weblogic/modules/org.apache.ant_1.7.1/bin:/usr/local/jdk1.7.0_80/jre/bin:/usr/local/jdk1.7.0_80/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
.
***************************************************
*  To start WebLogic Server, use a username and   *
*  password assigned to an admin-level user.  For *
*  server administration, use the WebLogic Server *
*  console at http://hostname:port/console        *
***************************************************
starting weblogic with Java version:
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
Starting WLS with line:
/usr/local/jdk1.7.0_80/bin/java -client   -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m  -XX:MaxPermSize=256m -Dweblogic.Name=AdminServer -Djava.security.policy=/home/weblogic/wlserver_10.3/server/lib/weblogic.policy  -Xverify:none  -da -Dplatform.home=/home/weblogic/wlserver_10.3 -Dwls.home=/home/weblogic/wlserver_10.3/server -Dweblogic.home=/home/weblogic/wlserver_10.3/server   -Dweblogic.management.discover=true  -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home/weblogic/patch_wls1036/profiles/default/sysext_manifest_classpath:/home/weblogic/patch_ocp371/profiles/default/sysext_manifest_classpath  weblogic.Server
<Jun 10, 2021 5:32:04 PM CST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true> 
<Jun 10, 2021 5:32:04 PM CST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true> 
<Jun 10, 2021 5:32:04 PM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 24.80-b11 from Oracle Corporation> 
<Jun 10, 2021 5:32:05 PM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050 > 
<Jun 10, 2021 5:32:06 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING> 
<Jun 10, 2021 5:32:06 PM CST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool> 
<Jun 10, 2021 5:32:06 PM CST> <Notice> <LoggingService> <BEA-320400> <The log file /home/weblogic/user_projects/domains/base_domain/servers/AdminServer/logs/AdminServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.> 
<Jun 10, 2021 5:32:06 PM CST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /home/weblogic/user_projects/domains/base_domain/servers/AdminServer/logs/AdminServer.log00005. Log messages will continue to be logged in /home/weblogic/user_projects/domains/base_domain/servers/AdminServer/logs/AdminServer.log.> 
<Jun 10, 2021 5:32:06 PM CST> <Notice> <Log Management> <BEA-170019> <The server log file /home/weblogic/user_projects/domains/base_domain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.> 
<Jun 10, 2021 5:32:07 PM CST> <Error> <EmbeddedLDAP> <BEA-000000> <Error opening the Transaction Log: /home/weblogic/user_projects/domains/base_domain/servers/AdminServer/data/ldap/ldapfiles/EmbeddedLDAP.tran (Permission denied)> 
<Jun 10, 2021 5:32:07 PM CST> <Error> <EmbeddedLDAP> <BEA-000000> <Error Instantiating 'dc=base_domain': null> 
<Jun 10, 2021 5:32:07 PM CST> <Critical> <EmbeddedLDAP> <BEA-171522> <An error occurred while initializing the Embedded LDAP Server. The exception thrown is java.lang.ClassCastException: com.octetstring.vde.backend.BackendRoot cannot be cast to com.octetstring.vde.backend.standard.BackendStandard. This may indicate a problem with the data files for the Embedded LDAP Server. If the problem is with the data files and it can not be corrected, backups of previous versions of the data files exist in /home/weblogic/user_projects/domains/base_domain/servers/AdminServer/data/ldap/backup.> 
<Jun 10, 2021 5:32:07 PM CST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: 

There are 1 nested errors:

java.lang.ClassCastException: com.octetstring.vde.backend.BackendRoot cannot be cast to com.octetstring.vde.backend.standard.BackendStandard
	at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:303)
	at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
	at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
	at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

> 
<Jun 10, 2021 5:32:07 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED> 
<Jun 10, 2021 5:32:07 PM CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down> 
<Jun 10, 2021 5:32:07 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN> 

A

给weblogic安装目录整体重新给个权限即可

chown -R weblogic:weblogic weblogic

再次启动正常

$ sh /home/weblogic/user_projects/domains/base_domain/startWebLogic.sh
.
.
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m  -XX:MaxPermSize=256m
.
WLS Start Mode=Development
.
CLASSPATH=/home/weblogic/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/weblogic/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/local/jdk1.7.0_80/lib/tools.jar:/home/weblogic/wlserver_10.3/server/lib/weblogic_sp.jar:/home/weblogic/wlserver_10.3/server/lib/weblogic.jar:/home/weblogic/modules/features/weblogic.server.modules_10.3.6.0.jar:/home/weblogic/wlserver_10.3/server/lib/webservices.jar:/home/weblogic/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/weblogic/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/home/weblogic/wlserver_10.3/common/derby/lib/derbyclient.jar:/home/weblogic/wlserver_10.3/server/lib/xqrl.jar:.:/usr/local/jdk1.7.0_80/lib/dt.jar:/usr/local/jdk1.7.0_80/lib/tools.jar
.
PATH=/home/weblogic/wlserver_10.3/server/bin:/home/weblogic/modules/org.apache.ant_1.7.1/bin:/usr/local/jdk1.7.0_80/jre/bin:/usr/local/jdk1.7.0_80/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
.
***************************************************
*  To start WebLogic Server, use a username and   *
*  password assigned to an admin-level user.  For *
*  server administration, use the WebLogic Server *
*  console at http://hostname:port/console        *
***************************************************
starting weblogic with Java version:
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
Starting WLS with line:
/usr/local/jdk1.7.0_80/bin/java -client   -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m  -XX:MaxPermSize=256m -Dweblogic.Name=AdminServer -Djava.security.policy=/home/weblogic/wlserver_10.3/server/lib/weblogic.policy  -Xverify:none  -da -Dplatform.home=/home/weblogic/wlserver_10.3 -Dwls.home=/home/weblogic/wlserver_10.3/server -Dweblogic.home=/home/weblogic/wlserver_10.3/server   -Dweblogic.management.discover=true  -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home/weblogic/patch_wls1036/profiles/default/sysext_manifest_classpath:/home/weblogic/patch_ocp371/profiles/default/sysext_manifest_classpath  weblogic.Server
<Jun 10, 2021 5:47:16 PM CST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true> 
<Jun 10, 2021 5:47:16 PM CST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true> 
<Jun 10, 2021 5:47:17 PM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 24.80-b11 from Oracle Corporation> 
<Jun 10, 2021 5:47:17 PM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050 > 
<Jun 10, 2021 5:47:18 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING> 
<Jun 10, 2021 5:47:18 PM CST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool> 
<Jun 10, 2021 5:47:18 PM CST> <Notice> <LoggingService> <BEA-320400> <The log file /home/weblogic/user_projects/domains/base_domain/servers/AdminServer/logs/AdminServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.> 
<Jun 10, 2021 5:47:18 PM CST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /home/weblogic/user_projects/domains/base_domain/servers/AdminServer/logs/AdminServer.log00006. Log messages will continue to be logged in /home/weblogic/user_projects/domains/base_domain/servers/AdminServer/logs/AdminServer.log.> 
<Jun 10, 2021 5:47:18 PM CST> <Notice> <Log Management> <BEA-170019> <The server log file /home/weblogic/user_projects/domains/base_domain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.> 
<Jun 10, 2021 5:47:20 PM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.> 
<Jun 10, 2021 5:47:22 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY> 
<Jun 10, 2021 5:47:22 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING> 
<Jun 10, 2021 5:47:22 PM CST> <Notice> <LoggingService> <BEA-320400> <The log file /home/weblogic/user_projects/domains/base_domain/servers/AdminServer/logs/base_domain.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.> 
<Jun 10, 2021 5:47:22 PM CST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /home/weblogic/user_projects/domains/base_domain/servers/AdminServer/logs/base_domain.log00005. Log messages will continue to be logged in /home/weblogic/user_projects/domains/base_domain/servers/AdminServer/logs/base_domain.log.> 
<Jun 10, 2021 5:47:22 PM CST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.> 
<Jun 10, 2021 5:47:22 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN> 
<Jun 10, 2021 5:47:22 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING> 
<Jun 10, 2021 5:47:22 PM CST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.159.152:7001 for protocols iiop, t3, ldap, snmp, http.> 
<Jun 10, 2021 5:47:22 PM CST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:2727:4d0b:bcda:15fd:7001 for protocols iiop, t3, ldap, snmp, http.> 
<Jun 10, 2021 5:47:22 PM CST> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.> 
<Jun 10, 2021 5:47:22 PM CST> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 0:0:0:0:0:0:0:1:7001 for protocols iiop, t3, ldap, snmp, http.> 
<Jun 10, 2021 5:47:22 PM CST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "AdminServer" for domain "base_domain" running in Development Mode> 
<Jun 10, 2021 5:47:22 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING> 
<Jun 10, 2021 5:47:22 PM CST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode> 

Referer

https://www.sanjitoimacadmy.com/2019/10/oim-weblogic-server-state-changed-to.html

### 关于WebLogic启动时错误BEA-149231的解决方案 当遇到WebLogic服务器启动过程中报错`BEA-149231`时,通常是因为管理服务器(Managed Server)无法正确连接到管理员服务器(Admin Server)。以下是可能的原因以及对应的解决方法: #### 原因分析 该错误的主要原因可以归纳为以下几点: 1. **网络配置问题**:管理服务器尝试通过不正确的主机名或IP地址访问管理员服务器[^4]。 2. **DNS解析问题**:如果管理员服务器绑定到了一个不可解析的DNS名称,则可能导致连接失败[^4]。 3. **未使用的服务器实例存在干扰**:某些不再使用的服务器实例仍然存在于控制台中,可能会引发冲突[^5]。 #### 解决方案 针对以上提到的各种可能性,提供如下几种具体的解决措施: 1. 修改管理服务器指向的管理员服务器地址 可以调整`managedServerName`使其指向不同于当前`adminHost`的一个新的管理员节点;或者采用指定IP地址的方式定义`adminHost`(即设置参数 `-Dweblogic.admin.host=a.b.c.d`)来规避潜在的名字解析难题[^4]。 2. 更新DNS记录 如果决定继续沿用现有的`adminHost`,那么就需要确认此域名能够映射至实际运行着管理员服务的那个机器的真实IP,这往往涉及到对内部DNS系统的修改操作。 3. 清理无用的服务条目 登录到WebLogic Server Console界面下查看是否有冗余或者是已经废弃掉却尚未被移除出去的老版本server entries。如果有发现的话就应当及时把这些不必要的项目给删掉再重试整个流程看是否恢复正常工作状态[^5]。 另外,在处理这类跨机部署场景下的复杂环境设定之时还可以参照官方文档关于如何把WebLogic 12c分布安装到多台物理计算机上的指导说明来进行更细致全面地排查与修正作业[^2]。 ```bash # Example command line options when starting Managed Server with specific Admin Host via IP Address. java ... -Dweblogic.admin.host=192.168.x.y ... ``` ### 注意事项 在整个修复过程里要特别留意任何有关安全凭证方面的变动情况因为之前有过案例显示有时看似简单的密码输入失误也会造成类似的登录拒绝现象发生就像前面提及过的ORA-01017那样所以务必保证所有的认证资料都是最新有效的才行[^1]。
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值