Вообщем переодически сервер дохнет по: The WebLogic Server encountered a critical failure java.lang.OutOfMemoryError: Metaspace Reason: There is a panic condition in the server. The server is configured to exit on panic И хотя это гавно пишет типа Reason: There is a panic condition in the server. The server is configured to exit on panic чёт ни хуя он ни куда не exit.... Вообщем т.к разбираться с тем чем он жрётся нет ни времени ни желания (оно обязательно появится)... как вариант можно приделать костыль... костыль будет заключаться в ребуте сервера при возникновении этой ошибки. Что значит для этого надо... Желания и понимание что так жить нельзя, и вообще... Делаем новый модуль называем скажем: Reboot-OOMMetaSpace Идём в в новый модуль делаем Policy: Называем его OOM-Metaspace и говорит что это Server log: Жмём next в Configuration Policy пишем: log.logMessage.contains('java.lang.OutOfMemoryError: Metaspace'...
Постоянно блять забываю!!!
Короче случается такое гавно при установке OVD в
/opt/oracle/ovdmiddleware/asinst_1/EMAGENT/EMAGENT/sysman/log/emagent.nohup
--- Shared agent
----- Wed Oct 5 15:18:30 2016::tzOffset for W-SU is 240(min), but agent is runnning with tzOffset 180(min)
-----
----- Wed Oct 5 15:18:30 2016::trying again after waiting for 1 sec to account for daylight transition
-----
----- Wed Oct 5 15:18:30 2016::tzOffset for W-SU is 240(min), but agent is runnning with tzOffset 180(min)
-----
----- Wed Oct 5 15:18:30 2016::Mismatch detected between timezone in env (W-SU) and in /opt/oracle/ovdmiddleware/asinst_1/EMAGENT/EMAGENT/sysman/config/emd.properties (W-SU). Forcing value
to latter.. -----
----- Wed Oct 5 15:18:32 2016::tzOffset for W-SU is 240(min), but agent is runnning with tzOffset 180(min)
-----
----- Wed Oct 5 15:18:32 2016::trying again after waiting for 1 sec to account for daylight transition
-----
----- Wed Oct 5 15:18:32 2016::tzOffset for W-SU is 240(min), but agent is runnning with tzOffset 180(min)
-----
----- Wed Oct 5 15:18:32 2016::The agentTZRegion value in /opt/oracle/ovdmiddleware/asinst_1/EMAGENT/EMAGENT/sysman/config/emd.properties is not in agreement with what agent thinks it shou
ld be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.
If you modified the timezone setting in the environment, please stop the agent and exectute 'emctl resetTZ agent' and also execute the script mgmt_target.set_agent_tzrgn(<agent_name>, <new_
tz_rgn>) to get the value propagated to repository -----
Короче случается такое гавно при установке OVD в
/opt/oracle/ovdmiddleware/asinst_1/EMAGENT/EMAGENT/sysman/log/emagent.nohup
--- Shared agent
----- Wed Oct 5 15:18:30 2016::tzOffset for W-SU is 240(min), but agent is runnning with tzOffset 180(min)
-----
----- Wed Oct 5 15:18:30 2016::trying again after waiting for 1 sec to account for daylight transition
-----
----- Wed Oct 5 15:18:30 2016::tzOffset for W-SU is 240(min), but agent is runnning with tzOffset 180(min)
-----
----- Wed Oct 5 15:18:30 2016::Mismatch detected between timezone in env (W-SU) and in /opt/oracle/ovdmiddleware/asinst_1/EMAGENT/EMAGENT/sysman/config/emd.properties (W-SU). Forcing value
to latter.. -----
----- Wed Oct 5 15:18:32 2016::tzOffset for W-SU is 240(min), but agent is runnning with tzOffset 180(min)
-----
----- Wed Oct 5 15:18:32 2016::trying again after waiting for 1 sec to account for daylight transition
-----
----- Wed Oct 5 15:18:32 2016::tzOffset for W-SU is 240(min), but agent is runnning with tzOffset 180(min)
-----
----- Wed Oct 5 15:18:32 2016::The agentTZRegion value in /opt/oracle/ovdmiddleware/asinst_1/EMAGENT/EMAGENT/sysman/config/emd.properties is not in agreement with what agent thinks it shou
ld be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.
If you modified the timezone setting in the environment, please stop the agent and exectute 'emctl resetTZ agent' and also execute the script mgmt_target.set_agent_tzrgn(<agent_name>, <new_
tz_rgn>) to get the value propagated to repository -----
Для решения проблемы открываем:
/opt/oracle/ovdmiddleware/asinst_1/EMAGENT/EMAGENT/sysman/config/emd.properties
в конце правим строчку на:
agentTZRegion=Etc/GMT-3 (это для Москвы).
Комментарии
Отправить комментарий