JD Edwards EntrepriseOne : Unable to locate security servera - jdeveloper
I have follow all the steps to install JDE , but i got this error :
Failed to communicate with security server: Unable to locate security server
JD Edwards EntrepriseOne could not sign you on.Make sur your User ID is correct and retype your password.
This the Log file of JDE :
2424/960 MAIN_THREAD Thu Jun 02 09:41:52.327000 jdb_ctl.c4196
Starting OneWorld
2424/960 MAIN_THREAD Thu Jun 02 09:42:01.822000 JDETOOLS.c3065
LIB0000569 - WARNING!!! [SECURITY][Password] Password not encrypted in the INI
1992/2944 UNKNOWN Thu Jun 02 09:42:01.862000 jdeksec.c786
INITIALIZING SECURITY SERVER KERNEL
1992/2944 UNKNOWN Thu Jun 02 09:42:01.862001 jdeksec.c803
WARNING - failed to find site keys in JDE.INI
1992/2944 UNKNOWN Thu Jun 02 09:42:01.862002 JDETOOLS.c3065
LIB0000569 - WARNING!!! [SECURITY][Password] Password not encrypted in the INI
1992/2944 UNKNOWN Thu Jun 02 09:42:01.902000 netpub.c999
JDENet already initialized
1992/2944 UNKNOWN Thu Jun 02 09:42:01.902001 jdb_ctl.c3121
Net init failed or not initialized
1992/2944 UNKNOWN Thu Jun 02 09:42:01.972000 JDETOOLS.c3065
LIB0000569 - WARNING!!! [SECURITY][Password] Password not encrypted in the INI
1992/2944 UNKNOWN Thu Jun 02 09:42:02.704000 jdb_drvm.c478
JDB9900160 - Failed to load driver library jdboci121.DLL
1992/2944 UNKNOWN Thu Jun 02 09:42:02.704001 jdb_omp1.c1928
JDB9900254 - Failed to initialize driver.
1992/2944 UNKNOWN Thu Jun 02 09:42:02.704002 JTP_CM.c209
JDB9909002 - Could not init connect.
1992/2944 UNKNOWN Thu Jun 02 09:42:02.704003 JTP_TM.c1140
JDB9909100 - Get connect info failed: Transaction ID =
1992/2944 UNKNOWN Thu Jun 02 09:42:02.704004 jdb_rq1.c2458
JDB3100013 - Failed to get connectinfo
1992/2944 UNKNOWN Thu Jun 02 09:42:02.704005 jdb_omp1.c3369
JDB9900257 - Failed to open F986101
1992/2944 UNKNOWN Thu Jun 02 09:42:02.834000 jdb_drvm.c478
JDB9900160 - Failed to load driver library jdboci121.DLL
1992/2944 UNKNOWN Thu Jun 02 09:42:02.834001 jdb_omp1.c1928
JDB9900254 - Failed to initialize driver.
1992/2944 UNKNOWN Thu Jun 02 09:42:02.834002 JTP_CM.c209
JDB9909002 - Could not init connect.
1992/2944 UNKNOWN Thu Jun 02 09:42:02.834003 JTP_TM.c1140
JDB9909100 - Get connect info failed: Transaction ID =
1992/2944 UNKNOWN Thu Jun 02 09:42:02.834004 jdb_rq1.c2458
JDB3100013 - Failed to get connectinfo
1992/2944 UNKNOWN Thu Jun 02 09:42:02.834005 jdb_omp1.c1220
JDB9900240 - Failed to open F986101
1992/2944 UNKNOWN Thu Jun 02 09:42:02.834006 jdb_cach.c1369
JDB9900009 - Failed to load ObjectMap Cache
1992/2944 UNKNOWN Thu Jun 02 09:42:02.834007 jdb_cach.c1386
Unable to load primary Object Configuration Manager - switching to secondary
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844000 jdb_omp1.c651
JDB9900247 - Failed to find F98611 System Local in cache
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844001 jdb_rq1.c2023
JDB3100011 - Failed to get location of table F986101 for environment DEMO920
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844002 jdb_omp1.c3369
JDB9900257 - Failed to open F986101
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844003 jdb_omp1.c651
JDB9900247 - Failed to find F98611 System Local in cache
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844004 jdb_rq1.c2023
JDB3100011 - Failed to get location of table F986101 for environment DEMO920
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844005 jdb_omp1.c1220
JDB9900240 - Failed to open F986101
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844006 jdb_cach.c1369
JDB9900009 - Failed to load ObjectMap Cache
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844007 jdb_omp1.c629
JDB9900246 - Failed to find existence of default OMAP for environment DEMO920
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844008 jdb_rq1.c2023
JDB3100011 - Failed to get location of table F00921 for environment DEMO920
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844009 jdecgsc.c201
MSC0000028 - Could not load F00921 cache
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844010 jdb_rq1.c3061
JDB2700019 - Failed to get data source for the table
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844011 jdb_omp1.c629
JDB9900246 - Failed to find existence of default OMAP for environment DEMO920
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844012 jdb_rq1.c2023
JDB3100011 - Failed to get location of table F00941 for environment DEMO920
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844013 jdb_ctl.c819
JDB9900408 - Failed to get package release level
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844014 jdb_ctl.c4439
JDB1100016 - Failed to load Environment - DEMO920
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844015 jdb_omp1.c629
JDB9900246 - Failed to find existence of default OMAP for environment DEMO920
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844016 jdb_rq1.c2023
JDB3100011 - Failed to get location of table F00941 for environment DEMO920
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844017 jdb_omp1.c629
JDB9900246 - Failed to find existence of default OMAP for environment DEMO920
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844018 jdb_rq1.c2023
JDB3100011 - Failed to get location of table F00942 for environment DEMO920
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844019 SpecUtil.c5156
JDESPEC0000051 - Unable to open F00942 to load metadata cache. Fatal Error.
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844020 SpecUtil.c5195
JDESPEC0000052 - Unable to select all records from F00942 to load metadata cache. Fatal Error.
1992/2944 UNKNOWN Thu Jun 02 09:42:02.844021 SpecUtil.c5068
Metadata release cache handle destroyed before it could be used. System probably being shut down. Returning failure.
1992/2944 UNKNOWN Thu Jun 02 09:42:02.854000 SpecOpen.c1845
JDESPEC0000059 - Unable to determine spec release level of the data source DEMO. Cannot determine metadata format version of this path code. Cannot acccess metadata (specs)! Fatal Error.
1992/2944 UNKNOWN Thu Jun 02 09:42:02.854001 SpecOpen.c2633
jdeSpecOpenLocal completed in error - JDESPECRESULT_FAILED.
1992/2944 UNKNOWN Thu Jun 02 09:42:02.854002 evtcache.c890
isNewRTESystemEnabled - DDTABL spec handle cannot be accessed.
1992/2944 WRK:Starting jdeCallObject Thu Jun 02 09:42:02.854003 jdb_omp1.c629
JDB9900246 - Failed to find existence of default OMAP for environment DEMO920
1992/2944 WRK:Starting jdeCallObject Thu Jun 02 09:42:02.854004 jdb_rq1.c2023
JDB3100011 - Failed to get location of table F00942 for environment DEMO920
1992/2944 WRK:Starting jdeCallObject Thu Jun 02 09:42:02.854005 SpecUtil.c5156
JDESPEC0000051 - Unable to open F00942 to load metadata cache. Fatal Error.
1992/2944 WRK:Starting jdeCallObject Thu Jun 02 09:42:02.854006 SpecUtil.c5195
JDESPEC0000052 - Unable to select all records from F00942 to load metadata cache. Fatal Error.
1992/2944 WRK:Starting jdeCallObject Thu Jun 02 09:42:02.854007 SpecUtil.c5068
Metadata release cache handle destroyed before it could be used. System probably being shut down. Returning failure.
1992/2944 WRK:Starting jdeCallObject Thu Jun 02 09:42:02.854008 SpecOpen.c1845
JDESPEC0000059 - Unable to determine spec release level of the data source DEMO. Cannot determine metadata format version of this path code. Cannot acccess metadata (specs)! Fatal Error.
1992/2944 WRK:Starting jdeCallObject Thu Jun 02 09:42:02.854009 SpecOpen.c2633
jdeSpecOpenLocal completed in error - JDESPECRESULT_FAILED.
1992/2944 WRK:Starting jdeCallObject Thu Jun 02 09:42:02.864000 secutil.c422
Failed to init security bootstrap environment using user=DEMO, env=DEMO920, role=*ALL
1992/2944 WRK:Starting jdeCallObject Thu Jun 02 09:42:02.864001 jdeksec.c3864
Failed to init Env
1992/2944 WRK:Starting jdeCallObject Thu Jun 02 09:42:02.864002 netflow.c1219
Dispatch Function '_JDEK_DispatchSecurity#28' returned failure on eNetDispatchInit
2424/960 MAIN_THREAD Thu Jun 02 09:43:21.839000 jdecsec.c2219
JDENET Error = eTimeOut
2424/960 MAIN_THREAD Thu Jun 02 09:43:46.502000 jdecsec.c2706
Failed to communicate with security server: Unable to locate Security Server
2424/960 MAIN_THREAD Thu Jun 02 09:43:47.990000 jdecsec.c264
Failed to validate user DEMO by password
2424/960 MAIN_THREAD Thu Jun 02 09:43:47.990001 jdb_ctl.c4902
JDB1100018 - Failed to get past Security check
2424/960 MAIN_THREAD Thu Jun 02 09:43:49.048000 msc_signon.cpp227
ValidateUser failed from SignOn
2424/960 MAIN_THREAD Thu Jun 02 09:43:51.545000 jdb_ctl.c4306
JDB1100012 - Failed to validate Sign on
2424/960 MAIN_THREAD Thu Jun 02 09:43:51.547000 SpecUtil.c5156
JDESPEC0000051 - Unable to open F00942 to load metadata cache. Fatal Error.
2424/960 MAIN_THREAD Thu Jun 02 09:43:51.547001 SpecUtil.c5195
JDESPEC0000052 - Unable to select all records from F00942 to load metadata cache. Fatal Error.
2424/960 MAIN_THREAD Thu Jun 02 09:43:51.548000 SpecUtil.c5068
Metadata release cache handle destroyed before it could be used. System probably being shut down. Returning failure.
2424/960 MAIN_THREAD Thu Jun 02 09:43:51.548001 SpecOpen.c1845
JDESPEC0000059 - Unable to determine spec release level of the data source DEMO. Cannot determine metadata format version of this path code. Cannot acccess metadata (specs)! Fatal Error.
2424/960 MAIN_THREAD Thu Jun 02 09:43:51.548002 SpecOpen.c2633
jdeSpecOpenLocal completed in error - JDESPECRESULT_FAILED.
2424/960 MAIN_THREAD Thu Jun 02 09:43:51.549000 evtcache.c890
isNewRTESystemEnabled - DDTABL spec handle cannot be accessed.
2424/960 WRK:Starting jdeCallObject Thu Jun 02 09:43:51.550000 SpecUtil.c5156
JDESPEC0000051 - Unable to open F00942 to load metadata cache. Fatal Error.
2424/960 WRK:Starting jdeCallObject Thu Jun 02 09:43:51.550001 SpecUtil.c5195
JDESPEC0000052 - Unable to select all records from F00942 to load metadata cache. Fatal Error.
2424/960 WRK:Starting jdeCallObject Thu Jun 02 09:43:51.550002 SpecUtil.c5068
Metadata release cache handle destroyed before it could be used. System probably being shut down. Returning failure.
2424/960 WRK:Starting jdeCallObject Thu Jun 02 09:43:51.551000 SpecOpen.c1845
JDESPEC0000059 - Unable to determine spec release level of the data source DEMO. Cannot determine metadata format version of this path code. Cannot acccess metadata (specs)! Fatal Error.
2424/960 WRK:Starting jdeCallObject Thu Jun 02 09:43:51.551001 SpecOpen.c2633
jdeSpecOpenLocal completed in error - JDESPECRESULT_FAILED.
2424/960 WRK:Starting jdeCallObject Thu Jun 02 09:43:51.578000 jdb_ctl.c1364
JDB4100001 - Failed to validate Env handle
2424/960 WRK:Starting jdeCallObject Thu Jun 02 09:43:51.728000 jdb_ctl.c10594
JDB1200017 - Exiting JDB_GetLocalClientEnv with NULL hEnv.
1992/636 MAIN_THREAD Thu Jun 02 09:43:51.900000 netpub.c3488
Info:Net program ended(JDENET_RunNet), pid = 1992, JDENETError = 0
1992/636 MAIN_THREAD Thu Jun 02 09:43:51.902000 IPCMISC.C299
API ipcSawUnregisterProcV1 : process 1992 unregistered in entry 0
Since your Enterprise Server is your Security Server, verify that the JDE services are running. If they are not, start them. If they are then stop and restart them.
If this fails after the restart, find the Security Kernel and check the logs.
Since this sounds like a new install, you can edit your JDE.ini file and set the Security Server to *NONE for your Full Client. Try logging in again. If you are successful then, most likely there is an issue with your System ID and password. Verify that the System ID is not disabled or that the password is correct.
Make sure your Enterprise server defined as security server in JDE.INI located under /system/bin32 folder on enterprise server (Windows) have correct server name defined under security server section, and ODBC connection must be created (careful as JDE Enterprise server follows 32bit (now it is coming with 64bit too), however I am assuming this server as 32 bit JDE only, so odbc connection must be created using correct odbcad32 (normally in /system/syswow64) location.
Along with that , you can also minimize warning message of site key with enabling this feature (https://docs.oracle.com/en/applications/jd-edwards/unix-linux/9.2/eouuo/generate-site-key.html).
regards,
Brajesh
Related
Failed to start Elasticsearch. Error opening log file '/gc.log': Permission denied
Dear StackOverflow community,
I was running Kibana/Elasticsearch without a problem until installing a Kibana plugin. Then the service failed and I noticed that the problem is that Elasticsearch stopped. I tried several ways to fix it, and then even reinstalled all. But the problem still avoiding to launch Elasticsearch, even with a fresh installation.
Installation on Debian 9 using apt install.
systemctl start elasticsearch.service
results on:
Exception in thread "main" java.lang.RuntimeException: starting java failed with [1]
[0.000s][error][logging] Error opening log file '/gc.log': Permission denied
Full log with journalctl -xe
-- Unit elasticsearch.service has begun starting up.
Feb 07 14:09:06 Debian-911-stretch-64-minimal kibana[576]: {"type":"log","#timestamp":"2020-02-07T13:09:06Z","tags":["warning","elasticsearch","admin"],"pid":576,"message":"Unable to revive connection: http://localhost:9200/"}
Feb 07 14:09:06 Debian-911-stretch-64-minimal kibana[576]: {"type":"log","#timestamp":"2020-02-07T13:09:06Z","tags":["warning","elasticsearch","admin"],"pid":576,"message":"No living connections"}
Feb 07 14:09:06 Debian-911-stretch-64-minimal kibana[576]: {"type":"log","#timestamp":"2020-02-07T13:09:06Z","tags":["warning","elasticsearch","admin"],"pid":576,"message":"Unable to revive connection: http://localhost:9200/"}
Feb 07 14:09:06 Debian-911-stretch-64-minimal kibana[576]: {"type":"log","#timestamp":"2020-02-07T13:09:06Z","tags":["warning","elasticsearch","admin"],"pid":576,"message":"No living connections"}
Feb 07 14:09:06 Debian-911-stretch-64-minimal elasticsearch[2312]: Exception in thread "main" java.lang.RuntimeException: starting java failed with [1]
Feb 07 14:09:06 Debian-911-stretch-64-minimal elasticsearch[2312]: output:
Feb 07 14:09:06 Debian-911-stretch-64-minimal elasticsearch[2312]: [0.000s][error][logging] Error opening log file '/gc.log': Permission denied
Feb 07 14:09:06 Debian-911-stretch-64-minimal elasticsearch[2312]: [0.000s][error][logging] Initialization of output 'file=/var/log/elasticsearch/gc.log' using options 'filecount=32,filesize=64m' failed.
Feb 07 14:09:06 Debian-911-stretch-64-minimal elasticsearch[2312]: error:
Feb 07 14:09:06 Debian-911-stretch-64-minimal elasticsearch[2312]: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
Feb 07 14:09:06 Debian-911-stretch-64-minimal elasticsearch[2312]: Invalid -Xlog option '-Xlog:gc*,gc+age=trace,safepoint:file=/var/log/elasticsearch/gc.log:utctime,pid,tags:filecount=32,filesize=64m', see error log for details.
Feb 07 14:09:06 Debian-911-stretch-64-minimal elasticsearch[2312]: Error: Could not create the Java Virtual Machine.
Feb 07 14:09:06 Debian-911-stretch-64-minimal elasticsearch[2312]: Error: A fatal exception has occurred. Program will exit.
Feb 07 14:09:06 Debian-911-stretch-64-minimal elasticsearch[2312]: at org.elasticsearch.tools.launchers.JvmErgonomics.flagsFinal(JvmErgonomics.java:118)
Feb 07 14:09:06 Debian-911-stretch-64-minimal elasticsearch[2312]: at org.elasticsearch.tools.launchers.JvmErgonomics.finalJvmOptions(JvmErgonomics.java:86)
Feb 07 14:09:06 Debian-911-stretch-64-minimal elasticsearch[2312]: at org.elasticsearch.tools.launchers.JvmErgonomics.choose(JvmErgonomics.java:59)
Feb 07 14:09:06 Debian-911-stretch-64-minimal elasticsearch[2312]: at org.elasticsearch.tools.launchers.JvmOptionsParser.main(JvmOptionsParser.java:92)
Feb 07 14:09:06 Debian-911-stretch-64-minimal systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
Feb 07 14:09:06 Debian-911-stretch-64-minimal systemd[1]: Failed to start Elasticsearch.
-- Subject: Unit elasticsearch.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit elasticsearch.service has failed.
The mentioned gc.log file was not in that folder. And the permissions were:
drwxr-s--- 2 elasticsearch elasticsearch 4096 Jan 15 13:20 elasticsearch
I created the file and also played with permissions until having these:
-rwxrwxrwx 1 root elasticsearch 0 Feb 7 15:19 gc.log
...and even changed the ownership:
-rwxrwxrwx 1 root root 0 Feb 7 15:19 gc.log
But no success, I still having the same issue.
Thanks
Make sure you are running CMD as Administrator.
This error also happens if you are using docker & running the container as a different user. You have to add --group_add flag to docker command or set TAKE_FILE_OWNERSHIP environment variable as mentioned here Using docker-compose: user: 1007:1007 group_add: - 0 Using docker: --group-add 0
Firstly, I didn't know why gc.log file was not present. Have you changed the logs folder path or something? The gc.log path can be set in jvm.options file. By default ES logs and java garbage collection logs are fed into the logs folder inside $ES_HOME directory. About user perspective, elastic search can't be run as root user. So from the ES directory details its showing you have an elasticsearch user created, and trying to run the cluster by that user. The problem here can be solved by changing the permissions of files insdie the ES directory where all it belongs. Now the gc.log file is owned by root user and it cannot be accessed by the elasticsearch user. Try this: sudo chown <user> <path/to/es/directory> -R Here it becomes : sudo chown elasticsearch elasticsearch/ -R If the issue still persists, check the jvm.options file whether its all configured correctly. Unless you change the -Xloggc:logs/gc.log option, the gc.log won't be pushing to /var/log. Feb 09 17:09:02 server elasticsearch[2199]: Invalid -Xlog option '-Xlog:gc*,gc+age=trace,safepoint:file=/var/log/elasticsearch/gc.log:utctime,pid,tags:filecount=32,filesize=64m', see error log for details. Your log says, the option is given as file=/var/log/elasticsearch/gc.log. Correct any wrong configurations as per documentation : https://www.elastic.co/guide/en/elasticsearch/reference/master/jvm-options.html
sudo systemctl -l status elasticsearch.service
Returns this log:
● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/elasticsearch.service.d
└─override.conf
Active: failed (Result: exit-code) since Sun 2020-02-09 17:09:02 CET; 2min 48s ago
Docs: http://www.elastic.co
Process: 2199 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=1/FAILURE)
Main PID: 2199 (code=exited, status=1/FAILURE)
Feb 09 17:09:02 server elasticsearch[2199]: Invalid -Xlog option '-Xlog:gc*,gc+age=trace,safepoint:file=/var/log/elasticsearch/gc.log:utctime,pid,tags:filecount=32,filesize=64m', see error log for details.
Feb 09 17:09:02 server elasticsearch[2199]: Error: Could not create the Java Virtual Machine.
Feb 09 17:09:02 server elasticsearch[2199]: Error: A fatal exception has occurred. Program will exit.
Feb 09 17:09:02 server elasticsearch[2199]: at org.elasticsearch.tools.launchers.JvmErgonomics.flagsFinal(JvmErgonomics.java:118)
Feb 09 17:09:02 server elasticsearch[2199]: at org.elasticsearch.tools.launchers.JvmErgonomics.finalJvmOptions(JvmErgonomics.java:86)
Feb 09 17:09:02 server elasticsearch[2199]: at org.elasticsearch.tools.launchers.JvmErgonomics.choose(JvmErgonomics.java:59)
Feb 09 17:09:02 server elasticsearch[2199]: at org.elasticsearch.tools.launchers.JvmOptionsParser.main(JvmOptionsParser.java:92)
Feb 09 17:09:02 server systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
Feb 09 17:09:02 server systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
Feb 09 17:09:02 server systemd[1]: Failed to start Elasticsearch.
At this point I'm doing a fresh install. Not able to find the solution I need to continue working...
Jmeter test, takes always the same time between start and finish
Jmeter is taking always the same time to finish remote test. The jmx script is simple and there is no time configured on it, and there are just one request (only 84ms in local test). It happens only on remote test, in local test is ok. Starting the test on host x.x.x.x # Thu Aug 14 09:31:43 BRT 2014 (1408019503091) Finished the test on host x.x.x.x # Thu Aug 14 09:34:43 BRT 2014 (1408019683082) Starting the test on host x.x.x.x # Thu Aug 14 09:35:53 BRT 2014 (1408019753107) Finished the test on host x.x.x.x # Thu Aug 14 09:38:53 BRT 2014 (1408019933091) Starting the test on host x.x.x.x # Thu Aug 14 09:40:33 BRT 2014 (1408020033110) Finished the test on host x.x.x.x # Thu Aug 14 09:43:33 BRT 2014 (1408020213100) Starting the test on host x.x.x.x # Thu Aug 14 10:03:23 BRT 2014 (1408021403158) Finished the test on host x.x.x.x # Thu Aug 14 10:06:23 BRT 2014 (1408021583154) Starting the test on host x.x.x.x # Thu Aug 14 10:07:53 BRT 2014 (1408021673181) Finished the test on host x.x.x.x # Thu Aug 14 10:10:53 BRT 2014 (1408021853164) Starting the test on host x.x.x.x # Thu Aug 14 10:25:23 BRT 2014 (1408022723204) Finished the test on host x.x.x.x # Thu Aug 14 10:28:23 BRT 2014 (1408022903204) Starting the test on host x.x.x.x # Thu Aug 14 10:33:13 BRT 2014 (1408023193224) Finished the test on host x.x.x.x # Thu Aug 14 10:36:53 BRT 2014 (1408023413225)
What's the safest way to shut down MongoDB when running as a Windows Service?
I have a single instance of MongoDB 2.4.8 running on Windows Server 2012 R2. MongoDB is installed as a Windows Service. I have journalling enabled. The MongoDB documentation suggests that the MongoDB service should just be shut down via the Windows Service Control Manager: net stop MongoDB When I did this recently, the following was logged and I ended up with a non-zero byte mongod.lock file on disk. (I used the --repair option to fix this but it turns out this probably wasn't necessary as I had journalling enabled.) Thu Nov 21 11:08:12.011 [serviceShutdown] got SERVICE_CONTROL_STOP request from Windows Service Control Manager, will terminate after current cmd ends Thu Nov 21 11:08:12.043 [serviceShutdown] now exiting Thu Nov 21 11:08:12.043 dbexit: Thu Nov 21 11:08:12.043 [serviceShutdown] shutdown: going to close listening sockets... Thu Nov 21 11:08:12.043 [serviceShutdown] closing listening socket: 1492 Thu Nov 21 11:08:12.043 [serviceShutdown] closing listening socket: 1500 Thu Nov 21 11:08:12.043 [serviceShutdown] shutdown: going to flush diaglog... Thu Nov 21 11:08:12.043 [serviceShutdown] shutdown: going to close sockets... Thu Nov 21 11:08:12.043 [serviceShutdown] shutdown: waiting for fs preallocator... Thu Nov 21 11:08:12.043 [serviceShutdown] shutdown: lock for final commit... Thu Nov 21 11:08:12.043 [serviceShutdown] shutdown: final commit... Thu Nov 21 11:08:12.043 [conn1333] end connection 127.0.0.1:51612 (18 connections now open) Thu Nov 21 11:08:12.043 [conn1331] end connection 127.0.0.1:51610 (18 connections now open) ...snip... Thu Nov 21 11:08:12.043 [conn1322] end connection 10.1.2.212:53303 (17 connections now open) Thu Nov 21 11:08:12.043 [conn1337] end connection 127.0.0.1:51620 (18 connections now open) Thu Nov 21 11:08:12.839 [serviceShutdown] shutdown: closing all files... Thu Nov 21 11:08:14.683 [serviceShutdown] Progress: 5/163 3% (File Closing Progress) Thu Nov 21 11:08:16.012 [serviceShutdown] Progress: 6/163 3% (File Closing Progress) ...snip... Thu Nov 21 11:08:52.030 [serviceShutdown] Progress: 143/163 87% (File Closing Progress) Thu Nov 21 11:08:54.092 [serviceShutdown] Progress: 153/163 93% (File Closing Progress) Thu Nov 21 11:08:55.405 [serviceShutdown] closeAllFiles() finished Thu Nov 21 11:08:55.405 [serviceShutdown] journalCleanup... Thu Nov 21 11:08:55.405 [serviceShutdown] removeJournalFiles Thu Nov 21 11:09:05.578 [DataFileSync] ERROR: Client::shutdown not called: DataFileSync The last line is my main concern. I'm also interested in how MongoDB is able to take longer to shut down than Windows normally allows for service shutdown? At what point is it safe to shut down the machine without checking the log file?
error 500 with xampp for linux and joomla
Im using ubuntu and XAMPP for linux and I have a problem when I try to upload an extension greater than 500kb in Joomla, I get an "HTTP Error 500" http://s4.postimage.org/7wgxcfveq/error500.jpg My php.ini file is configured following the joomla recomendations: "display_errors=Off"...... here is my error log [Mon Jun 06 14:12:45 2011] [notice] suEXEC mechanism enabled (wrapper: /opt/lampp/bin/suexec) [Mon Jun 06 14:12:45 2011] [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?) [Mon Jun 06 14:12:45 2011] [warn] RSA server certificate CommonName (CN) localhost' does NOT match server name!? [Mon Jun 06 14:12:46 2011] [notice] Digest: generating secret for digest authentication ... [Mon Jun 06 14:12:46 2011] [notice] Digest: done [Mon Jun 06 14:12:47 2011] [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?) [Mon Jun 06 14:12:47 2011] [warn] RSA server certificate CommonName (CN) localhost' does NOT match server name!? [Mon Jun 06 14:12:48 2011] [notice] Apache/2.2.17 (Unix) DAV/2 mod_ssl/2.2.17 OpenSSL/1.0.0c PHP/5.3.5 mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.1 configured -- resuming normal operations [Mon Jun 06 14:15:34 2011] [error] [client 192.168.56.1] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /opt/lampp/htdocs/csu/libraries/joomla/filesystem/archive/tar.php on line 154, referer: http://192.168.56.101/csu/administrator/index.php?option=com_installer&view=install
The PHP Fatal error is "Maximum execution time of 30 seconds exceeded". You could try increasing this by altering the max_execution_time in the php.ini file or create a .htaccess file containing.. php_value max_execution_time 60 Should the installation of an extension take longer than 30 seconds? There might be a script issue, such as an endless loop, that's causing problems.
Can't connect to a local apache installation under XAMPP on Win XP 64-bit. Help!
I'm using XAMPP v1.7 on an Win XP-64 bit machine, my Symantec AV is turned off as is my Windows Firewall, and I can't connect to localhost from a browser. I originally had these errors: [Wed Jan 07 16:24:55 2009] [error] (OS 10038)An operation was attempted on something that is not a socket. : Child 2716: Encountered too many errors accepting client connections. Possible causes: dynamic address renewal, or incompatible VPN or firewall software. Try using the Win32DisableAcceptEx directive These errors went away after I added the Win32DisableAcceptEx directive to httpd.conf, but the net result remains the same: no joy. Now, I get these errors: [Wed Jan 07 16:40:15 2009] [notice] Apache/2.2.11 (Win32) DAV/2 mod_ssl/2.2.11 OpenSSL/0.9.8i mod_autoindex_color PHP/5.2.8 configured -- resuming normal operations [Wed Jan 07 16:40:15 2009] [notice] Server built: Dec 10 2008 00:10:06 [Wed Jan 07 16:40:15 2009] [notice] Parent: Created child process 5916 [Wed Jan 07 16:40:15 2009] [notice] Disabled use of AcceptEx() WinSock2 API [Wed Jan 07 16:40:15 2009] [notice] Digest: generating secret for digest authentication ... [Wed Jan 07 16:40:15 2009] [notice] Digest: done [Wed Jan 07 16:40:15 2009] [notice] Child 5916: Child process is running [Wed Jan 07 16:40:15 2009] [notice] Child 5916: Acquired the start mutex. [Wed Jan 07 16:40:15 2009] [notice] Child 5916: Starting 250 worker threads. [Wed Jan 07 16:40:15 2009] [notice] Child 5916: Listening on port 443. [Wed Jan 07 16:40:15 2009] [notice] Child 5916: Listening on port 80. [Wed Jan 07 16:40:15 2009] [error] (OS 10038)An operation was attempted on something that is not a socket. : Too many errors in select loop. Child process exiting. [Wed Jan 07 16:40:15 2009] [notice] Child 5916: Exit event signaled. Child process is ending. [Wed Jan 07 16:40:16 2009] [notice] Child 5916: Released the start mutex [Wed Jan 07 16:40:17 2009] [notice] Child 5916: All worker threads have exited. [Wed Jan 07 16:40:17 2009] [notice] Child 5916: Child process is exiting [Wed Jan 07 16:40:17 2009] [notice] Parent: child process exited with status 0 -- Restarting. [Wed Jan 07 16:40:17 2009] [notice] Digest: generating secret for digest authentication ... [Wed Jan 07 16:40:17 2009] [notice] Digest: done And, apache seems to be crashing (Windows tells me so, and I can see the crash in the system events.) I'm a n00b to apache, but need to get this running. Ideas? Marcus
If anyone comes across this, try running netsh winsock RESET from the command line. It worked for me.