I installed ripple server on ubuntu machine after when I goes to start through command line with command
opt/ripple/bin/rippled --conf=/etc/opt/ripple/rippled.cfg
then found error as
Terminating thread rippled: main: unhandled St13runtime_error 'Unable to open/create RocksDB: IO error: lock /var/lib/rippled/db/rocksdb/rippledb.86c2/LOCK: Resource temporarily unavailable'
and How I ensure that my ripple server is fully synced?
Related
These are the errors I got, as a test is done on cucumber, appium for mobile testing. I used windows and eclipse (cucumber) and I got these errors, before it was running
Failed to Create Session. The session identified by fca400..... is not known
and when I ran
adb uninstall io.appium.uiautomator2.server; adb uninstall io.appium.uiautomator2.server.test; adb uninstall io.appium.unlock (was throwing error); adb uninstall io.appium.settings
I got the following error
Failed to create session. An unknown server-side error occurred while processing the command. Original error: Error getting device API level. Original error: Error executing adbExec. Original error: 'Command 'C:\Users\Diego\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 1115fbab02003004 shell getprop ro.build.version.sdk' timed out after 20000ms'. Try to increase the 20000ms adb execution timeout represented by 'adbExecTimeout' capability
I have deployed a Bitnami Parse stack to a Google Cloud VM. This stack is basically Apache running as a proxy, Then a MEAN stack handling parse server and dashboard etc.
Everything appears to be working fine when accessing the dashboard and sending individual CURL requests to test it's all available.
However, there appears to be a fatal flaw in that. When Parse returns one of it's errors e.g.
{"code":101,"error":"Object not found."}
Express sees it as an uncaught exception and dies. Now I realise that it's intentional behaviour (There's enough information out there as to why you don't want to persist after an uncaught exception)
The Bitnami stack uses Forever to run the Parse Server, but as you can see from the logs I will include below, you still run into issues with refused connections.
2016-11-25T11:41:16+00:00 DEBUG (7): {"code":101,"error":"Object not found."}
2016-11-25T11:41:16+00:00 DEBUG (7): Failed to connect to X.X.X.X: Connection refused
2016-11-25T11:41:17+00:00 DEBUG (7): Failed to connect to X.X.X.X: Connection refused
2016-11-25T11:41:17+00:00 DEBUG (7): Failed to connect to X.X.X.X: Connection refused
2016-11-25T11:41:17+00:00 DEBUG (7): Failed to connect to X.X.X.X: Connection refused
Meanwhile in the Forever logs:
Error generating response. ParseError { code: 101, message: 'Object not found.' } code=101, message=Object not found.
[object Object]
/opt/bitnami/apps/parse/htdocs/node_modules/parse-server/lib/ParseServer.js:425
throw err;
^
Error: EACCES: permission denied, open '/opt/bitnami/apps/parse/htdocs/logs/parse-server.info.2016-11-25'
at Error (native)
error: Forever detected script exited with code: 7
error: Script restart attempt #1
parse-server running on port 1337
parse-dashboard running on port 4040
So you can see that immediately following a Parse error being returned, The service is unavailable until Forever can restart the Parse Server.
This issue appears that it would affect all users as well, so if one user receives an exception, all users lose connection for a brief period.
So the question is, how should this be properly handled? Is Parse + Express not the way to go about it? Or is there some method of configuring Node or Express to return the API error to the requester, without Express dying (And without having to fall into the trap of using uncaughtException to keep Node alive)
Any help would be much appreciated, thank you
The logs from Forever said it's EACCES error, that means ParseServer couldn't access the log file and not able to write the info log in it.
Error: EACCES: permission denied, open '/opt/bitnami/apps/parse/htdocs/logs/parse-server.info.2016-11-25'
at Error (native)
error: Forever detected script exited with code: 7
error: Script restart attempt #1
parse-server running on port 1337
parse-dashboard running on port 4040
I think you have to change the /opt/bitnami/apps/parse/htdocs/logs with proper permission so that ParseServer can write log files in it.
I'm running Ionic2 to build windows app. but it is giving me following error:
shell.js: internal error
Error: EBUSY: resource busy or locked, open 'C:\Users\edge\AppData\Local\Temp\shelljs_60d55c70cdc922162f4b'
at Error (native)
at Object.fs.openSync (fs.js:640:18)
at Object.fs.writeFileSync (fs.js:1333:33)
at execSync (C:\Users\edge\AppData\Roaming\npm\node_modules\ionic\node_modules\shelljs\src\exec.js:67:57)
at Object._exec (C:\Users\edge\AppData\Roaming\npm\node_modules\ionic\node_modules\shelljs\src\exec.js:179:12)
at Object.exec (C:\Users\edge\AppData\Roaming\npm\node_modules\ionic\node_modules\shelljs\src\common.js:168:23)
at Object.gatherGulpInfo (C:\Users\edge\AppData\Roaming\npm\node_modules\ionic\node_modules\ionic-app-lib\lib\info.js:201:24)
at Object.t (C:\Users\edge\AppData\Roaming\npm\node_modules\ionic\lib\utils\stats.js:148:15)
at Object.run (C:\Users\edge\AppData\Roaming\npm\node_modules\ionic\lib\cli.js:135:16)
at Object.<anonymous> (C:\Users\edge\AppData\Roaming\npm\node_modules\ionic\bin\ionic:13:10)
I sow a same error:
Ionic run android - Internal Error
But I don't want to remove my antivirus and reinstall nodeJS.
But when I restart my system and immediately after I run the command It works(Possibly some process takes time to execute which one access this resource)
Snapshot of process running on my system are as follows:
I faced the same issue , and resolved it by uninstalling bytefence anti malware . it actually use the same resource mentioned above .(I checked in dell laptop)
While trying to start my hybrisserver in debug mode I got the following error messages and hybrisserver stopped. I tried but not able to solve. Any help please.
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)<br/>
ERROR: transport error 202: bind failed: Permission denied<br/>
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)<br/>
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]<br/>
JVM exited while loading the application.<br/>
Reloading Wrapper configuration...<br/>
Launching a JVM...<br/>
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)<br/>
ERROR: transport error 202: bind failed: Permission denied<br/>
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)<br/>
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]<br/>
JVM exited while loading the application.<br/>
There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
There may be a configuration problem: please check the logs.
<-- Wrapper Stopped<br/>
An error occurred in the process.
#thijsraets is correct. Either you have to check where is the port (8000) has been occupied or you can override the default value to something else in local.properties file.
tomcat.debugjavaoptions=-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,address=8001,suspend=n
Run "ant all". This will configure debug for port 8001.
OR
You can change the JVM parameters in wrapper-debug.conf file...
wrapper.java.additional.23=-Xrunjdwp:transport=dt_socket,server=y,address=8001,suspend=n
People who encounter this problem seem to already have something else bound to the debug port, try changing the port in: tomcat.debugjavaoptions
The same thing happened to me and tried to kill the server and restarted it safely. I followed these steps:
ps aux | grep java . this will help me to find the PID , Process ID
kill -9 PID
If you want to kill all the tomcat processes you can do
pkill -9 -f tomcat
this will restart the server safely.
I'm setting up a gmod server on Linux but I get an error saying it failed to write app state. I read somewhere it was something to do with permission but I'm not sure how to fix it. What is causing this error and how can it be fixed?
Steam>force_install_dir /home/steam/gmod
Steam>app_update 4020
/home/buildbot/buildslave/steam_rel_client_linux/build/src/clientdll/applicationmanager.cpp (937) : Assertion Failed: Failed to write app state file /home/steam/gmod/b880344e252db2ff689623b22f39bb22fdbd1e01/appmanifest_4020.acf
/home/buildbot/buildslave/steam_rel_client_linux/build/src/clientdll/applicationmanager.cpp (937) : Assertion Failed: Failed to write app state file /home/steam/gmod/b880344e252db2ff689623b22f39bb22fdbd1e01/appmanifest_4020.acf
Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
Error! App '4020' state is 0x1 after update job.
I've resolved with root account. Launched steamcmd with root and then updated the app. No errors occurred. I hope could help someone.