Appium Uiautomator keeps crashing due to mjpegserver crash - appium
Appium logs:
I ran this test on a real android device.
I changed the language and the country of the device using appium settings app, and some apps got updated like google play services.
After that appium create session is not working.
Need help .
I have attached the appium logs of the uiautomator crash.
2023-02-14 10:32:38:705 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 start-server'
2023-02-14 10:32:38:721 [AndroidDriver] Retrieving device list
2023-02-14 10:32:38:721 [ADB] Trying to find a connected android device
2023-02-14 10:32:38:721 [ADB] Getting connected devices
2023-02-14 10:32:38:733 [ADB] Connected devices: [{"udid":"aa44739a","state":"device"},{"udid":"8f86991d","state":"device"},{"udid":"98895a43524e315a31","state":"device"},{"udid":"8735ebee","state":"device"},{"udid":"R5CRA1SQC1R","state":"device"},{"udid":"RF8N51NZA6X","state":"device"},{"udid":"R5CT234SCAD","state":"device"},{"udid":"R5CT23583SJ","state":"device"},{"udid":"RZCN800LKJL","state":"device"},{"udid":"RZ8M816Z9TJ","state":"device"},{"udid":"R5CNC13ANEW","state":"device"},{"udid":"c3d3f2be","state":"device"},{"udid":"19271FDF60046F","state":"device"},{"udid":"149dddc90706","state":"device"},{"udid":"R5CR11301JB","state":"device"},{"udid":"RZ8N813K1VH","state":"device"},{"udid":"MZGE5HNNEMZ5AYI7","state":"device"},{"udid":"2ab07a1d473f7ece","state":"device"},{"udid":"R28M317C9BR","state":"device"},{"udid":"RZ8N80A11NN","state":"device"},{"udid":"R5CT21L5MYW","state":"device"},{"udid":"R5CT31BJ3TD","state":"device"}]
2023-02-14 10:32:38:733 [AndroidDriver] Using device: R5CRA1SQC1R
2023-02-14 10:32:38:734 [ADB] Using 'adb' from '/usr/lib/android-sdk/platform-tools/adb'
2023-02-14 10:32:38:735 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 start-server'
2023-02-14 10:32:38:745 [ADB] Setting device id to R5CRA1SQC1R
2023-02-14 10:32:38:746 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell getprop ro.build.version.sdk'
2023-02-14 10:32:38:811 [ADB] Current device property 'ro.build.version.sdk': 30
2023-02-14 10:32:38:812 [ADB] Getting device platform version
2023-02-14 10:32:38:813 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell getprop ro.build.version.release'
2023-02-14 10:32:38:862 [ADB] Current device property 'ro.build.version.release': 11
2023-02-14 10:32:38:862 [ADB] Device API level: 30
2023-02-14 10:32:38:862 [UiAutomator2] Relaxing hidden api policy
2023-02-14 10:32:38:864 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell 'settings put global hidden_api_policy_pre_p_apps 1;settings put global hidden_api_policy_p_apps 1;settings put global hidden_api_policy 1''
2023-02-14 10:32:39:058 [AndroidDriver] No app sent in, not parsing package/activity
2023-02-14 10:32:39:060 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R wait-for-device'
2023-02-14 10:32:39:087 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell echo ping'
2023-02-14 10:32:39:122 [AndroidDriver] Pushing settings apk to device...
2023-02-14 10:32:39:123 [ADB] Getting install status for io.appium.settings
2023-02-14 10:32:39:123 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell dumpsys package io.appium.settings'
2023-02-14 10:32:39:455 [ADB] 'io.appium.settings' is installed
2023-02-14 10:32:39:455 [ADB] Getting package info for 'io.appium.settings'
2023-02-14 10:32:39:456 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell dumpsys package io.appium.settings'
2023-02-14 10:32:39:578 [ADB] The version code of the installed 'io.appium.settings' is greater than the application version code (48 > 30)
2023-02-14 10:32:39:578 [ADB] There is no need to downgrade 'io.appium.settings'
2023-02-14 10:32:39:578 [ADB] Getting IDs of all 'io.appium.settings' processes
2023-02-14 10:32:39:579 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell 'pgrep --help; echo $?''
2023-02-14 10:32:39:639 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell pgrep -f \(\[\[:blank:\]\]\|\^\)io\.appium\.settings\(\[\[:blank:\]\]\|\$\)'
2023-02-14 10:32:39:758 [AndroidDriver] io.appium.settings is already running. There is no need to reset its permissions.
2023-02-14 10:32:39:759 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell appops set io.appium.settings android:mock_location allow'
2023-02-14 10:32:39:848 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell getprop persist.sys.locale'
2023-02-14 10:32:39:899 [ADB] Current device property 'persist.sys.locale': en-US
2023-02-14 10:32:39:900 [ADB] Current locale: 'en-US'; requested locale: 'en-GB'
2023-02-14 10:32:39:901 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell am broadcast -a io.appium.settings.locale -n io.appium.settings/.receivers.LocaleSettingReceiver --es lang en --es country GB'
2023-02-14 10:32:40:805 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell getprop persist.sys.locale'
2023-02-14 10:32:40:906 [ADB] Current device property 'persist.sys.locale': en-GB
2023-02-14 10:32:40:906 [ADB] Requested locale is equal to current locale: 'en-gb'
2023-02-14 10:32:40:908 [Logcat] Starting logs capture with command: /usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R logcat -v threadtime
2023-02-14 10:32:40:990 [AndroidDriver] Enabling Unicode keyboard support
2023-02-14 10:32:40:991 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell settings get secure default_input_method'
2023-02-14 10:32:41:187 [AndroidDriver] Unsetting previous IME com.samsung.android.honeyboard/.service.HoneyBoardService
2023-02-14 10:32:41:188 [AndroidDriver] Setting IME to 'io.appium.settings/.UnicodeIME'
2023-02-14 10:32:41:188 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell ime enable io.appium.settings/.UnicodeIME'
2023-02-14 10:32:41:336 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell ime set io.appium.settings/.UnicodeIME'
2023-02-14 10:32:41:517 [UiAutomator2] Forwarding UiAutomator2 Server port 6790 to local port 12332
2023-02-14 10:32:41:525 [ADB] Forwarding system: 12332 to device: 6790
2023-02-14 10:32:41:525 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R forward tcp:12332 tcp:6790'
2023-02-14 10:32:41:540 [ADB] Getting install status for io.appium.uiautomator2.server
2023-02-14 10:32:41:541 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell dumpsys package io.appium.uiautomator2.server'
2023-02-14 10:32:41:696 [ADB] 'io.appium.uiautomator2.server' is installed
2023-02-14 10:32:41:697 [ADB] Getting package info for 'io.appium.uiautomator2.server'
2023-02-14 10:32:41:697 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell dumpsys package io.appium.uiautomator2.server'
2023-02-14 10:32:41:968 [ADB] The version name of the installed 'io.appium.uiautomator2.server' is greater or equal to the application version name ('4.27.0' >= '4.27.0')
2023-02-14 10:32:41:968 [UiAutomator2] io.appium.uiautomator2.server installation state: sameVersionInstalled
2023-02-14 10:32:41:969 [ADB] Checking app cert for /home/ltadmin/Documents/appium/latest/node_modules/appium/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-v4.27.0.apk
2023-02-14 10:32:42:005 [ADB] Using 'apksigner.jar' from '/usr/lib/android-sdk/build-tools/27.0.1/apksigner.jar'
2023-02-14 10:32:42:006 [ADB] Starting apksigner: /usr/lib/jvm/java-11-openjdk-amd64/bin/java -Xmx1024M -Xss1m -jar /usr/lib/android-sdk/build-tools/27.0.1/apksigner.jar verify --print-certs /home/ltadmin/Documents/appium/latest/node_modules/appium/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-v4.27.0.apk
2023-02-14 10:32:42:534 [ADB] apksigner stdout: Signer #1 certificate DN: EMAILADDRESS=android#android.com, CN=Android, OU=Android, O=Android, L=Mountain View, ST=California, C=US
2023-02-14 10:32:42:535 [ADB] Signer #1 certificate SHA-256 digest: a40da80a59d170caa950cf15c18c454d47a39b26989d8b640ecd745ba71bf5dc
2023-02-14 10:32:42:535 [ADB] Signer #1 certificate SHA-1 digest: 61ed377e85d386a8dfee6b864bd85b0bfaa5af81
2023-02-14 10:32:42:535 [ADB] Signer #1 certificate MD5 digest: e89b158e4bcf988ebd09eb83f5378e87
2023-02-14 10:32:42:535 [ADB]
2023-02-14 10:32:42:537 [ADB] sha256 hash did match for 'appium-uiautomator2-server-v4.27.0.apk'
2023-02-14 10:32:42:538 [ADB] '/home/ltadmin/Documents/appium/latest/node_modules/appium/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-v4.27.0.apk' is signed with the default certificate
2023-02-14 10:32:42:540 [ADB] Getting install status for io.appium.uiautomator2.server.test
2023-02-14 10:32:42:542 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell dumpsys package io.appium.uiautomator2.server.test'
2023-02-14 10:32:42:709 [ADB] 'io.appium.uiautomator2.server.test' is installed
2023-02-14 10:32:42:709 [ADB] Checking app cert for /home/ltadmin/Documents/appium/latest/node_modules/appium/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-debug-androidTest.apk
2023-02-14 10:32:42:716 [ADB] Starting apksigner: /usr/lib/jvm/java-11-openjdk-amd64/bin/java -Xmx1024M -Xss1m -jar /usr/lib/android-sdk/build-tools/27.0.1/apksigner.jar verify --print-certs /home/ltadmin/Documents/appium/latest/node_modules/appium/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-debug-androidTest.apk
2023-02-14 10:32:42:914 [ADB] apksigner stdout: Signer #1 certificate DN: EMAILADDRESS=android#android.com, CN=Android, OU=Android, O=Android, L=Mountain View, ST=California, C=US
2023-02-14 10:32:42:914 [ADB] Signer #1 certificate SHA-256 digest: a40da80a59d170caa950cf15c18c454d47a39b26989d8b640ecd745ba71bf5dc
2023-02-14 10:32:42:914 [ADB] Signer #1 certificate SHA-1 digest: 61ed377e85d386a8dfee6b864bd85b0bfaa5af81
2023-02-14 10:32:42:915 [ADB] Signer #1 certificate MD5 digest: e89b158e4bcf988ebd09eb83f5378e87
2023-02-14 10:32:42:915 [ADB]
2023-02-14 10:32:42:915 [ADB] sha256 hash did match for 'appium-uiautomator2-server-debug-androidTest.apk'
2023-02-14 10:32:42:915 [ADB] '/home/ltadmin/Documents/appium/latest/node_modules/appium/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-debug-androidTest.apk' is signed with the default certificate
2023-02-14 10:32:42:916 [UiAutomator2] Server packages are not going to be (re)installed
2023-02-14 10:32:42:920 [UiAutomator2] Waiting up to 30000ms for services to be available
2023-02-14 10:32:42:921 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell pm list instrumentation'
2023-02-14 10:32:43:109 [UiAutomator2] Instrumentation target 'io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner' is available
2023-02-14 10:32:43:115 [ADB] Adding packages ["io.appium.settings","io.appium.uiautomator2.server","io.appium.uiautomator2.server.test"] to Doze whitelist
2023-02-14 10:32:43:116 [ADB] Got the following command chunks to execute: [["dumpsys","deviceidle","whitelist","+io.appium.settings",";","dumpsys","deviceidle","whitelist","+io.appium.uiautomator2.server",";","dumpsys","deviceidle","whitelist","+io.appium.uiautomator2.server.test",";"]]
2023-02-14 10:32:43:116 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell dumpsys deviceidle whitelist +io.appium.settings ; dumpsys deviceidle whitelist +io.appium.uiautomator2.server ; dumpsys deviceidle whitelist +io.appium.uiautomator2.server.test ;'
2023-02-14 10:32:43:402 [UiAutomator2] No app capability. Assuming it is already on the device
2023-02-14 10:32:43:403 [ADB] Getting install status for com.viator.mobile.android.prerelease
2023-02-14 10:32:43:403 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell dumpsys package com.viator.mobile.android.prerelease'
2023-02-14 10:32:43:633 [ADB] 'com.viator.mobile.android.prerelease' is installed
2023-02-14 10:32:43:634 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell am force-stop com.viator.mobile.android.prerelease'
2023-02-14 10:32:43:986 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell pm clear com.viator.mobile.android.prerelease'
2023-02-14 10:32:44:357 [AndroidDriver] Performed fast reset on the installed 'com.viator.mobile.android.prerelease' application (stop and clear)
2023-02-14 10:32:44:358 [UiAutomator2] Performing shallow cleanup of automation leftovers
2023-02-14 10:32:44:385 [UiAutomator2] No obsolete sessions have been detected (read ECONNRESET)
2023-02-14 10:32:44:385 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell am force-stop io.appium.uiautomator2.server.test'
2023-02-14 10:32:44:590 [UiAutomator2] Starting UIAutomator2 server 4.27.0
2023-02-14 10:32:44:590 [UiAutomator2] Using UIAutomator2 server from '/home/ltadmin/Documents/appium/latest/node_modules/appium/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-v4.27.0.apk' and test from '/home/ltadmin/Documents/appium/latest/node_modules/appium/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-debug-androidTest.apk'
2023-02-14 10:32:44:591 [UiAutomator2] Waiting up to 60000ms for UiAutomator2 to be online...
2023-02-14 10:32:44:592 [ADB] Creating ADB subprocess with args: ["-P",5037,"-s","R5CRA1SQC1R","shell","am","instrument","-w","-e","disableAnalytics",true,"io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner"]
2023-02-14 10:32:44:603 [WD Proxy] Matched '/status' to command name 'getStatus'
2023-02-14 10:32:44:605 [WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:12332/wd/hub/status] with no body
2023-02-14 10:32:44:635 [WD Proxy] Error: read ECONNRESET
2023-02-14 10:32:44:635 [WD Proxy] at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
2023-02-14 10:32:45:638 [WD Proxy] Matched '/status' to command name 'getStatus'
2023-02-14 10:32:45:639 [WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:12332/wd/hub/status] with no body
2023-02-14 10:32:45:657 [WD Proxy] Error: read ECONNRESET
2023-02-14 10:32:45:658 [WD Proxy] at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
2023-02-14 10:32:46:658 [WD Proxy] Matched '/status' to command name 'getStatus'
2023-02-14 10:32:46:659 [WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:12332/wd/hub/status] with no body
2023-02-14 10:32:46:668 [WD Proxy] Error: read ECONNRESET
2023-02-14 10:32:46:668 [WD Proxy] at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
2023-02-14 10:32:46:871 [Instrumentation] io.appium.uiautomator2.server.test.AppiumUiAutomator2Server:
2023-02-14 10:32:47:670 [WD Proxy] Matched '/status' to command name 'getStatus'
2023-02-14 10:32:47:670 [WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:12332/wd/hub/status] with no body
2023-02-14 10:32:47:682 [WD Proxy] Error: read ECONNRESET
2023-02-14 10:32:47:682 [WD Proxy] at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
2023-02-14 10:32:47:903 [Instrumentation] Error in startServer(io.appium.uiautomator2.server.test.AppiumUiAutomator2Server):
2023-02-14 10:32:47:904 [Instrumentation] java.lang.ExceptionInInitializerError
2023-02-14 10:32:47:904 [Instrumentation] at io.appium.uiautomator2.server.mjpeg.MjpegScreenshotServer.<init>(MjpegScreenshotServer.java:41)
2023-02-14 10:32:47:904 [Instrumentation] at io.appium.uiautomator2.server.mjpeg.MjpegScreenshotServer.<init>(MjpegScreenshotServer.java:35)
2023-02-14 10:32:47:904 [Instrumentation] at io.appium.uiautomator2.server.ServerInstrumentation.startMjpegServer(ServerInstrumentation.java:241)
2023-02-14 10:32:47:904 [Instrumentation] at io.appium.uiautomator2.server.test.AppiumUiAutomator2Server.startServer(AppiumUiAutomator2Server.java:31)
2023-02-14 10:32:47:905 [Instrumentation] ... 27 trimmed
2023-02-14 10:32:47:905 [Instrumentation] Caused by: java.lang.IllegalStateException: UiAutomationService android.accessibilityservice.IAccessibilityServiceClient$Stub$Proxy#a4fc225already registered!
2023-02-14 10:32:47:905 [Instrumentation] at android.os.Parcel.createExceptionOrNull(Parcel.java:2393)
2023-02-14 10:32:47:905 [Instrumentation] at android.os.Parcel.createException(Parcel.java:2369)
2023-02-14 10:32:47:906 [Instrumentation] at android.os.Parcel.readException(Parcel.java:2352)
2023-02-14 10:32:47:906 [Instrumentation] at android.os.Parcel.readException(Parcel.java:2294)
2023-02-14 10:32:47:906 [Instrumentation] at android.app.IUiAutomationConnection$Stub$Proxy.connect(IUiAutomationConnection.java:427)
2023-02-14 10:32:47:906 [Instrumentation] at android.app.UiAutomation.connect(UiAutomation.java:243)
2023-02-14 10:32:47:906 [Instrumentation] at android.app.Instrumentation.getUiAutomation(Instrumentation.java:2189)
2023-02-14 10:32:47:907 [Instrumentation] at androidx.test.uiautomator.UiDevice.getUiAutomation(UiDevice.java:1129)
2023-02-14 10:32:47:907 [Instrumentation] at androidx.test.uiautomator.QueryController.<init>(QueryController.java:95)
2023-02-14 10:32:47:907 [Instrumentation] at androidx.test.uiautomator.UiDevice.<init>(UiDevice.java:109)
2023-02-14 10:32:47:907 [Instrumentation] at androidx.test.uiautomator.UiDevice.getInstance(UiDevice.java:261)
2023-02-14 10:32:47:907 [Instrumentation] at io.appium.uiautomator2.utils.Device.getUiDevice(Device.java:33)
2023-02-14 10:32:47:908 [Instrumentation] at io.appium.uiautomator2.model.internal.CustomUiDevice.<init>(CustomUiDevice.java:70)
2023-02-14 10:32:47:908 [Instrumentation] at io.appium.uiautomator2.model.internal.CustomUiDevice.getInstance(CustomUiDevice.java:80)
2023-02-14 10:32:47:908 [Instrumentation] at io.appium.uiautomator2.server.mjpeg.MjpegScreenshotStream.<clinit>(MjpegScreenshotStream.java:43)
2023-02-14 10:32:47:908 [Instrumentation] ... 32 more
2023-02-14 10:32:47:952 [Instrumentation] INSTRUMENTATION_RESULT: shortMsg=Process crashed.
2023-02-14 10:32:47:952 [Instrumentation] INSTRUMENTATION_CODE: 0
2023-02-14 10:32:48:443 [Instrumentation] The process has exited with code 0
2023-02-14 10:32:48:684 [UiAutomator2] The instrumentation process has been unexpectedly terminated. Retrying UiAutomator2 startup (#1 of 1)
2023-02-14 10:32:48:684 [UiAutomator2] Performing strict cleanup of automation leftovers
2023-02-14 10:32:48:707 [UiAutomator2] No obsolete sessions have been detected (read ECONNRESET)
2023-02-14 10:32:48:707 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell am force-stop io.appium.uiautomator2.server.test'
2023-02-14 10:32:48:812 [ADB] Attempting to kill all uiautomator processes
2023-02-14 10:32:48:812 [ADB] Getting IDs of all 'uiautomator' processes
2023-02-14 10:32:48:813 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell pgrep -f \(\[\[:blank:\]\]\|\^\)uiautomator\(\[\[:blank:\]\]\|\$\)'
2023-02-14 10:32:48:959 [ADB] No 'uiautomator' process has been found
2023-02-14 10:32:51:960 [UiAutomator2] Waiting up to 60000ms for UiAutomator2 to be online...
2023-02-14 10:32:51:961 [ADB] Creating ADB subprocess with args: ["-P",5037,"-s","R5CRA1SQC1R","shell","am","instrument","-w","-e","disableAnalytics",true,"io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner"]
2023-02-14 10:32:51:974 [WD Proxy] Matched '/status' to command name 'getStatus'
2023-02-14 10:32:51:975 [WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:12332/wd/hub/status] with no body
2023-02-14 10:32:52:000 [WD Proxy] Error: read ECONNRESET
2023-02-14 10:32:52:000 [WD Proxy] at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
2023-02-14 10:32:53:002 [WD Proxy] Matched '/status' to command name 'getStatus'
2023-02-14 10:32:53:002 [WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:12332/wd/hub/status] with no body
2023-02-14 10:32:53:015 [WD Proxy] Error: read ECONNRESET
2023-02-14 10:32:53:015 [WD Proxy] at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
2023-02-14 10:32:53:856 [Instrumentation] io.appium.uiautomator2.server.test.AppiumUiAutomator2Server:
2023-02-14 10:32:54:016 [WD Proxy] Matched '/status' to command name 'getStatus'
2023-02-14 10:32:54:017 [WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:12332/wd/hub/status] with no body
2023-02-14 10:32:54:028 [WD Proxy] Error: read ECONNRESET
2023-02-14 10:32:54:028 [WD Proxy] at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
2023-02-14 10:32:54:895 [Instrumentation] Error in startServer(io.appium.uiautomator2.server.test.AppiumUiAutomator2Server):
2023-02-14 10:32:54:895 [Instrumentation] java.lang.ExceptionInInitializerError
2023-02-14 10:32:54:895 [Instrumentation] at io.appium.uiautomator2.server.mjpeg.MjpegScreenshotServer.<init>(MjpegScreenshotServer.java:41)
2023-02-14 10:32:54:895 [Instrumentation] at io.appium.uiautomator2.server.mjpeg.MjpegScreenshotServer.<init>(MjpegScreenshotServer.java:35)
2023-02-14 10:32:54:896 [Instrumentation] at io.appium.uiautomator2.server.ServerInstrumentation.startMjpegServer(ServerInstrumentation.java:241)
2023-02-14 10:32:54:896 [Instrumentation] at io.appium.uiautomator2.server.test.AppiumUiAutomator2Server.startServer(AppiumUiAutomator2Server.java:31)
2023-02-14 10:32:54:896 [Instrumentation] ... 27 trimmed
2023-02-14 10:32:54:896 [Instrumentation] Caused by: java.lang.IllegalStateException: UiAutomationService android.accessibilityservice.IAccessibilityServiceClient$Stub$Proxy#939608dalready registered!
2023-02-14 10:32:54:897 [Instrumentation] at android.os.Parcel.createExceptionOrNull(Parcel.java:2393)
2023-02-14 10:32:54:897 [Instrumentation] at android.os.Parcel.createException(Parcel.java:2369)
2023-02-14 10:32:54:897 [Instrumentation] at android.os.Parcel.readException(Parcel.java:2352)
2023-02-14 10:32:54:897 [Instrumentation] at android.os.Parcel.readException(Parcel.java:2294)
2023-02-14 10:32:54:897 [Instrumentation] at android.app.IUiAutomationConnection$Stub$Proxy.connect(IUiAutomationConnection.java:427)
2023-02-14 10:32:54:898 [Instrumentation] at android.app.UiAutomation.connect(UiAutomation.java:243)
2023-02-14 10:32:54:898 [Instrumentation] at android.app.Instrumentation.getUiAutomation(Instrumentation.java:2189)
2023-02-14 10:32:54:898 [Instrumentation] at androidx.test.uiautomator.UiDevice.getUiAutomation(UiDevice.java:1129)
2023-02-14 10:32:54:898 [Instrumentation] at androidx.test.uiautomator.QueryController.<init>(QueryController.java:95)
2023-02-14 10:32:54:898 [Instrumentation] at androidx.test.uiautomator.UiDevice.<init>(UiDevice.java:109)
2023-02-14 10:32:54:899 [Instrumentation] at androidx.test.uiautomator.UiDevice.getInstance(UiDevice.java:261)
2023-02-14 10:32:54:899 [Instrumentation] at io.appium.uiautomator2.utils.Device.getUiDevice(Device.java:33)
2023-02-14 10:32:54:899 [Instrumentation] at io.appium.uiautomator2.model.internal.CustomUiDevice.<init>(CustomUiDevice.java:70)
2023-02-14 10:32:54:899 [Instrumentation] at io.appium.uiautomator2.model.internal.CustomUiDevice.getInstance(CustomUiDevice.java:80)
2023-02-14 10:32:54:899 [Instrumentation] at io.appium.uiautomator2.server.mjpeg.MjpegScreenshotStream.<clinit>(MjpegScreenshotStream.java:43)
2023-02-14 10:32:54:900 [Instrumentation] ... 32 more
2023-02-14 10:32:54:968 [Instrumentation] INSTRUMENTATION_RESULT: shortMsg=Process crashed.
2023-02-14 10:32:54:978 [Instrumentation] INSTRUMENTATION_CODE: 0
2023-02-14 10:32:55:028 [WD Proxy] Matched '/status' to command name 'getStatus'
2023-02-14 10:32:55:028 [WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:12332/wd/hub/status] with no body
2023-02-14 10:32:55:039 [WD Proxy] Error: read ECONNRESET
2023-02-14 10:32:55:040 [WD Proxy] at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
2023-02-14 10:32:55:440 [Instrumentation] The process has exited with code 0
2023-02-14 10:32:56:042 [UiAutomator2] The instrumentation process cannot be initialized. Make sure the application under test does not crash and investigate the logcat output.
2023-02-14 10:32:56:043 [UiAutomator2] Deleting UiAutomator2 session
2023-02-14 10:32:56:044 [UiAutomator2] Deleting UiAutomator2 server session
2023-02-14 10:32:56:045 [UiAutomator2] Did not get confirmation UiAutomator2 deleteSession worked; Error was: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'DELETE /' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
2023-02-14 10:32:56:045 [UiAutomator2] Resetting IME to 'com.samsung.android.honeyboard/.service.HoneyBoardService'
2023-02-14 10:32:56:046 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell ime set com.samsung.android.honeyboard/.service.HoneyBoardService'
2023-02-14 10:32:56:175 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell am force-stop com.viator.mobile.android.prerelease'
2023-02-14 10:32:56:339 [Logcat] Stopping logcat capture
2023-02-14 10:32:56:341 [ADB] Removing forwarded port socket connection: 12332
2023-02-14 10:32:56:342 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R forward --remove tcp:12332'
2023-02-14 10:32:56:361 [UiAutomator2] Restoring hidden api policy to the device default configuration
2023-02-14 10:32:56:362 [ADB] Running '/usr/lib/android-sdk/platform-tools/adb -P 5037 -s R5CRA1SQC1R shell 'settings delete global hidden_api_policy_pre_p_apps;settings delete global hidden_api_policy_p_apps;settings delete global hidden_api_policy''
2023-02-14 10:32:56:580 [BaseDriver] Event 'newSessionStarted' logged at 1676370776579 (10:32:56 GMT+0000 (Greenwich Mean Time))
2023-02-14 10:32:56:633 [MJSONWP] Encountered internal error running command: Error: The instrumentation process cannot be initialized. Make sure the application under test does not crash and investigate the logcat output.
2023-02-14 10:32:56:633 [MJSONWP] at Object.errorAndThrow (/home/ltadmin/Documents/appium/latest/node_modules/appium/node_modules/appium-support/lib/logging.js:94:35)
2023-02-14 10:32:56:633 [MJSONWP] at UiAutomator2Server.startSession (/home/ltadmin/Documents/appium/latest/node_modules/appium/node_modules/appium-uiautomator2-driver/lib/uiautomator2.js:247:13)
2023-02-14 10:32:56:633 [MJSONWP] at AndroidUiautomator2Driver.startUiAutomator2Session (/home/ltadmin/Documents/appium/latest/node_modules/appium/node_modules/appium-uiautomator2-driver/lib/driver.js:416:5)
2023-02-14 10:32:56:633 [MJSONWP] at AndroidUiautomator2Driver.createSession (/home/ltadmin/Documents/appium/latest/node_modules/appium/node_modules/appium-uiautomator2-driver/lib/driver.js:229:7)
2023-02-14 10:32:56:633 [MJSONWP] at AppiumDriver.createSession (/home/ltadmin/Documents/appium/latest/node_modules/appium/lib/appium.js:387:35)
2023-02-14 10:32:56:636 [HTTP] <-- POST /wd/hub/session 500 18071 ms - 274
2023-02-14 10:32:56:636 [HTTP]
2023-02-14 10:32:58:582 [HTTP] --> DELETE /wd/hub/session/
2023-02-14 10:32:58:582 [HTTP] {}
2023-02-14 10:32:58:596 [HTTP] No route found for /wd/hub/session/
2023-02-14 10:32:58:597 [HTTP] <-- DELETE /wd/hub/session/ 404 15 ms - 211
2023-02-14 10:32:58:597 [HTTP]
Related
Infinite Loop when deploying to Elastic Beanstalk
I would like to deploy a Docker image containing Keycloak to Elastic Beanstalk.
To do so I created a Dockerfile like this.
FROM bitnami/keycloak:19.0.2
EXPOSE 5000
This deploys successfully when running eb deploy.
I would now like to compile some Java code and copy it into the Keycloak image.
FROM gradle:7.5.0-jdk11-alpine AS spi
COPY --chown=gradle:gradle ./spi /spi
WORKDIR /spi
RUN gradle build --no-daemon
FROM bitnami/keycloak:19
COPY --from=spi /spi/build/libs/* /opt/keycloak/providers/keycloak-spi-0.0.1-SNAPSHOT.jar
EXPOSE 5000
This builds successfully using docker build --no-cache -t keycloak . and can be run using docker run locally.
If I try deploying this to Elastic Beanstalk it deploys indefinitely. I can't cancel the deployment and have to force it to stop by setting the Auto Scaling Group capacity to 0.
----------------------------------------
/var/log/eb-hooks.log
----------------------------------------
----------------------------------------
/var/log/nginx/access.log
----------------------------------------
172.31.15.133 - - [29/Sep/2022:17:05:19 +0000] "GET / HTTP/1.1" 502 157 "-" "ELB-HealthChecker/2.0" "-"
172.31.35.107 - - [29/Sep/2022:17:05:19 +0000] "GET / HTTP/1.1" 502 157 "-" "ELB-HealthChecker/2.0" "-"
172.31.15.133 - - [29/Sep/2022:17:05:32 +0000] "GET / HTTP/1.1" 502 559 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/106.0.0.0 Safari/537.36" "86.11.104.152"
172.31.15.133 - - [29/Sep/2022:17:05:34 +0000] "GET / HTTP/1.1" 502 157 "-" "ELB-HealthChecker/2.0" "-"
172.31.35.107 - - [29/Sep/2022:17:05:34 +0000] "GET / HTTP/1.1" 502 157 "-" "ELB-HealthChecker/2.0" "-"
----------------------------------------
/var/log/nginx/error.log
----------------------------------------
2022/09/29 17:05:19 [error] 4202#4202: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.31.15.133, server: , request: "GET / HTTP/1.1", upstream: "http://172.17.0.2:5000/", host: "172.31.7.44"
2022/09/29 17:05:19 [error] 4202#4202: *3 connect() failed (111: Connection refused) while connecting to upstream, client: 172.31.35.107, server: , request: "GET / HTTP/1.1", upstream: "http://172.17.0.2:5000/", host: "172.31.7.44"
2022/09/29 17:05:32 [error] 4202#4202: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.31.15.133, server: , request: "GET / HTTP/1.1", upstream: "http://172.17.0.2:5000/", host: "keycloak-dev.eu-west-2.elasticbeanstalk.com"
2022/09/29 17:05:34 [error] 4202#4202: *7 connect() failed (111: Connection refused) while connecting to upstream, client: 172.31.15.133, server: , request: "GET / HTTP/1.1", upstream: "http://172.17.0.2:5000/", host: "172.31.7.44"
2022/09/29 17:05:34 [error] 4202#4202: *9 connect() failed (111: Connection refused) while connecting to upstream, client: 172.31.35.107, server: , request: "GET / HTTP/1.1", upstream: "http://172.17.0.2:5000/", host: "172.31.7.44"
----------------------------------------
/var/log/eb-docker/containers/eb-current-app/eb-48320d59a48b-stdouterr.log
----------------------------------------
[38;5;6mkeycloak [38;5;5m17:05:06.31 [0m
[38;5;6mkeycloak [38;5;5m17:05:06.32 [0m[1mWelcome to the Bitnami keycloak container[0m
[38;5;6mkeycloak [38;5;5m17:05:06.32 [0mSubscribe to project updates by watching [1mhttps://github.com/bitnami/containers[0m
[38;5;6mkeycloak [38;5;5m17:05:06.32 [0mSubmit issues and feature requests at [1mhttps://github.com/bitnami/containers/issues[0m
[38;5;6mkeycloak [38;5;5m17:05:06.32 [0m
[38;5;6mkeycloak [38;5;5m17:05:06.32 [0m[38;5;2mINFO [0m ==> ** Starting keycloak setup **
[38;5;6mkeycloak [38;5;5m17:05:06.33 [0m[38;5;2mINFO [0m ==> Validating settings in KEYCLOAK_* env vars...
[38;5;6mkeycloak [38;5;5m17:05:06.35 [0m[38;5;2mINFO [0m ==> Trying to connect to PostgreSQL server awseb-e-2mwnvjecwe-stack-awsebrdsdatabase-qb51rlaqbaxv.czdgrvr4inhi.eu-west-2.rds.amazonaws.com...
[38;5;6mkeycloak [38;5;5m17:05:06.38 [0m[38;5;2mINFO [0m ==> Found PostgreSQL server listening at awseb-e-2mwnvjecwe-stack-awsebrdsdatabase-qb51rlaqbaxv.czdgrvr4inhi.eu-west-2.rds.amazonaws.com:5432
[38;5;6mkeycloak [38;5;5m17:05:06.38 [0m[38;5;2mINFO [0m ==> Configuring database settings
[38;5;6mkeycloak [38;5;5m17:05:06.41 [0m[38;5;2mINFO [0m ==> Enabling statistics
[38;5;6mkeycloak [38;5;5m17:05:06.41 [0m[38;5;2mINFO [0m ==> Configuring http settings
[38;5;6mkeycloak [38;5;5m17:05:06.42 [0m[38;5;2mINFO [0m ==> Configuring hostname settings
[38;5;6mkeycloak [38;5;5m17:05:06.43 [0m[38;5;2mINFO [0m ==> Configuring cache count
[38;5;6mkeycloak [38;5;5m17:05:06.43 [0m[38;5;2mINFO [0m ==> Configuring log level
[38;5;6mkeycloak [38;5;5m17:05:06.44 [0m[38;5;2mINFO [0m ==> Configuring proxy
[38;5;6mkeycloak [38;5;5m17:05:06.45 [0m[38;5;2mINFO [0m ==> ** keycloak setup finished! **
[38;5;6mkeycloak [38;5;5m17:05:06.46 [0m[38;5;2mINFO [0m ==> ** Starting keycloak **
Updating the configuration and installing your custom providers, if any. Please wait.
2022-09-29 17:05:19,703 WARN [org.keycloak.services] (build-43) KC-SERVICES0047: metrics (org.jboss.aerogear.keycloak.metrics.MetricsEndpointFactory) is implementing the internal SPI realm-restapi-extension. This SPI is internal and may change without notice
2022-09-29 17:05:21,233 WARN [org.keycloak.services] (build-43) KC-SERVICES0047: metrics-listener (org.jboss.aerogear.keycloak.metrics.MetricsEventListenerFactory) is implementing the internal SPI eventsListener. This SPI is internal and may change without notice
2022-09-29 17:05:32,212 INFO [io.quarkus.deployment.QuarkusAugmentor] (main) Quarkus augmentation completed in 21445ms
2022-09-29 17:05:35,762 INFO [org.keycloak.quarkus.runtime.hostname.DefaultHostnameProvider] (main) Hostname settings: Base URL: <unset>, Hostname: <request>, Strict HTTPS: false, Path: <request>, Strict BackChannel: false, Admin URL: <unset>, Admin: <request>, Port: -1, Proxied: true
2022-09-29 17:05:38,486 INFO [org.keycloak.common.crypto.CryptoIntegration] (main) Detected crypto provider: org.keycloak.crypto.def.DefaultCryptoProvider
----------------------------------------
/var/log/docker-events.log
----------------------------------------
2022-09-29T17:05:03.177179628Z image pull bitnami/keycloak:19 (name=bitnami/keycloak, org.opencontainers.image.authors=https://bitnami.com/contact, org.opencontainers.image.description=Application packaged by Bitnami, org.opencontainers.image.ref.name=19.0.2-debian-11-r4, org.opencontainers.image.source=https://github.com/bitnami/containers/tree/main/bitnami/keycloak, org.opencontainers.image.title=keycloak, org.opencontainers.image.vendor=VMware, Inc., org.opencontainers.image.version=19.0.2)
2022-09-29T17:05:03.398516443Z container create edf1b48a9117e98a17c3c65139a2c3131ba40c31cc036faba9d7e541eb1308a4 (image=sha256:2a52f7074b400c46837253be0cd6719054373aa15c556a2505cfc4875c732191, name=crazy_keldysh, org.opencontainers.image.authors=https://bitnami.com/contact, org.opencontainers.image.description=Application packaged by Bitnami, org.opencontainers.image.ref.name=19.0.2-debian-11-r4, org.opencontainers.image.source=https://github.com/bitnami/containers/tree/main/bitnami/keycloak, org.opencontainers.image.title=keycloak, org.opencontainers.image.vendor=VMware, Inc., org.opencontainers.image.version=19.0.2)
2022-09-29T17:05:03.467499766Z container destroy edf1b48a9117e98a17c3c65139a2c3131ba40c31cc036faba9d7e541eb1308a4 (image=sha256:2a52f7074b400c46837253be0cd6719054373aa15c556a2505cfc4875c732191, name=crazy_keldysh, org.opencontainers.image.authors=https://bitnami.com/contact, org.opencontainers.image.description=Application packaged by Bitnami, org.opencontainers.image.ref.name=19.0.2-debian-11-r4, org.opencontainers.image.source=https://github.com/bitnami/containers/tree/main/bitnami/keycloak, org.opencontainers.image.title=keycloak, org.opencontainers.image.vendor=VMware, Inc., org.opencontainers.image.version=19.0.2)
2022-09-29T17:05:03.471362994Z image tag sha256:5d99cf30b3aec76495a2db5b6e5292125f31f29ddfe7aca21789abd2f13fc30c (name=aws_beanstalk/staging-app:latest, org.opencontainers.image.authors=https://bitnami.com/contact, org.opencontainers.image.description=Application packaged by Bitnami, org.opencontainers.image.ref.name=19.0.2-debian-11-r4, org.opencontainers.image.source=https://github.com/bitnami/containers/tree/main/bitnami/keycloak, org.opencontainers.image.title=keycloak, org.opencontainers.image.vendor=VMware, Inc., org.opencontainers.image.version=19.0.2)
2022-09-29T17:05:05.646632020Z container create 48320d59a48b027ab5d08531271a2cd0c4cafac5e80f322fa7fc98c0849ba5b4 (image=5d99cf30b3ae, name=cool_pasteur, org.opencontainers.image.authors=https://bitnami.com/contact, org.opencontainers.image.description=Application packaged by Bitnami, org.opencontainers.image.ref.name=19.0.2-debian-11-r4, org.opencontainers.image.source=https://github.com/bitnami/containers/tree/main/bitnami/keycloak, org.opencontainers.image.title=keycloak, org.opencontainers.image.vendor=VMware, Inc., org.opencontainers.image.version=19.0.2)
2022-09-29T17:05:05.718178496Z network connect b4145308580fd568a5789e6f5345557a657c66187a05059e0e1d0e7d0813bab6 (container=48320d59a48b027ab5d08531271a2cd0c4cafac5e80f322fa7fc98c0849ba5b4, name=bridge, type=bridge)
2022-09-29T17:05:06.289309003Z container start 48320d59a48b027ab5d08531271a2cd0c4cafac5e80f322fa7fc98c0849ba5b4 (image=5d99cf30b3ae, name=cool_pasteur, org.opencontainers.image.authors=https://bitnami.com/contact, org.opencontainers.image.description=Application packaged by Bitnami, org.opencontainers.image.ref.name=19.0.2-debian-11-r4, org.opencontainers.image.source=https://github.com/bitnami/containers/tree/main/bitnami/keycloak, org.opencontainers.image.title=keycloak, org.opencontainers.image.vendor=VMware, Inc., org.opencontainers.image.version=19.0.2)
2022-09-29T17:05:12.038251773Z image tag sha256:5d99cf30b3aec76495a2db5b6e5292125f31f29ddfe7aca21789abd2f13fc30c (name=aws_beanstalk/current-app:latest, org.opencontainers.image.authors=https://bitnami.com/contact, org.opencontainers.image.description=Application packaged by Bitnami, org.opencontainers.image.ref.name=19.0.2-debian-11-r4, org.opencontainers.image.source=https://github.com/bitnami/containers/tree/main/bitnami/keycloak, org.opencontainers.image.title=keycloak, org.opencontainers.image.vendor=VMware, Inc., org.opencontainers.image.version=19.0.2)
2022-09-29T17:05:12.101612937Z image untag sha256:5d99cf30b3aec76495a2db5b6e5292125f31f29ddfe7aca21789abd2f13fc30c (name=sha256:5d99cf30b3aec76495a2db5b6e5292125f31f29ddfe7aca21789abd2f13fc30c, org.opencontainers.image.authors=https://bitnami.com/contact, org.opencontainers.image.description=Application packaged by Bitnami, org.opencontainers.image.ref.name=19.0.2-debian-11-r4, org.opencontainers.image.source=https://github.com/bitnami/containers/tree/main/bitnami/keycloak, org.opencontainers.image.title=keycloak, org.opencontainers.image.vendor=VMware, Inc., org.opencontainers.image.version=19.0.2)
2022-09-29T17:05:13.916310158Z image tag sha256:5d99cf30b3aec76495a2db5b6e5292125f31f29ddfe7aca21789abd2f13fc30c (name=aws_beanstalk/current-app:latest, org.opencontainers.image.authors=https://bitnami.com/contact, org.opencontainers.image.description=Application packaged by Bitnami, org.opencontainers.image.ref.name=19.0.2-debian-11-r4, org.opencontainers.image.source=https://github.com/bitnami/containers/tree/main/bitnami/keycloak, org.opencontainers.image.title=keycloak, org.opencontainers.image.vendor=VMware, Inc., org.opencontainers.image.version=19.0.2)
2022-09-29T17:05:14.010857853Z image tag sha256:2a52f7074b400c46837253be0cd6719054373aa15c556a2505cfc4875c732191 (name=bitnami/keycloak:19, org.opencontainers.image.authors=https://bitnami.com/contact, org.opencontainers.image.description=Application packaged by Bitnami, org.opencontainers.image.ref.name=19.0.2-debian-11-r4, org.opencontainers.image.source=https://github.com/bitnami/containers/tree/main/bitnami/keycloak, org.opencontainers.image.title=keycloak, org.opencontainers.image.vendor=VMware, Inc., org.opencontainers.image.version=19.0.2)
----------------------------------------
/var/log/eb-docker-process.log
----------------------------------------
2022/09/29 17:05:12.516005 [INFO] Loading Manifest...
2022/09/29 17:05:12.553556 [INFO] Running command /bin/sh -c /opt/aws/bin/cfn-get-metadata -s arn:aws:cloudformation:eu-west-2:882618350644:stack/awseb-e-2mwnvjecwe-stack/e6e0d050-3f75-11ed-a0e9-0a1f03d7e8a8 -r AWSEBAutoScalingGroup --region eu-west-2
2022/09/29 17:05:14.188072 [INFO] Running command /bin/sh -c /opt/aws/bin/cfn-get-metadata -s arn:aws:cloudformation:eu-west-2:882618350644:stack/awseb-e-2mwnvjecwe-stack/e6e0d050-3f75-11ed-a0e9-0a1f03d7e8a8 -r AWSEBBeanstalkMetadata --region eu-west-2
2022/09/29 17:05:15.706457 [INFO] Checking if docker is running...
2022/09/29 17:05:15.706480 [INFO] Fetch current app container id...
2022/09/29 17:05:15.706802 [INFO] Running command /bin/sh -c docker ps | grep 48320d59a48b
2022/09/29 17:05:15.851077 [INFO] 48320d59a48b 5d99cf30b3ae "/opt/bitnami/script…" 10 seconds ago Up 9 seconds 5000/tcp cool_pasteur
2022/09/29 17:05:15.851106 [INFO] Running command /bin/sh -c docker wait 48320d59a48b
----------------------------------------
/var/log/docker
----------------------------------------
Sep 29 17:04:41 ip-172-31-7-44 docker: time="2022-09-29T17:04:41.522348910Z" level=info msg="Starting up"
Sep 29 17:04:41 ip-172-31-7-44 docker: time="2022-09-29T17:04:41.546445360Z" level=info msg="parsed scheme: \"unix\"" module=grpc
Sep 29 17:04:41 ip-172-31-7-44 docker: time="2022-09-29T17:04:41.546469970Z" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
Sep 29 17:04:41 ip-172-31-7-44 docker: time="2022-09-29T17:04:41.546492925Z" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock <nil> 0 <nil>}] <nil> <nil>}" module=grpc
Sep 29 17:04:41 ip-172-31-7-44 docker: time="2022-09-29T17:04:41.546507007Z" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Sep 29 17:04:41 ip-172-31-7-44 docker: time="2022-09-29T17:04:41.585273534Z" level=info msg="parsed scheme: \"unix\"" module=grpc
Sep 29 17:04:41 ip-172-31-7-44 docker: time="2022-09-29T17:04:41.585318052Z" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
Sep 29 17:04:41 ip-172-31-7-44 docker: time="2022-09-29T17:04:41.585339847Z" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock <nil> 0 <nil>}] <nil> <nil>}" module=grpc
Sep 29 17:04:41 ip-172-31-7-44 docker: time="2022-09-29T17:04:41.585350796Z" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Sep 29 17:04:41 ip-172-31-7-44 docker: time="2022-09-29T17:04:41.870138260Z" level=info msg="Loading containers: start."
Sep 29 17:04:42 ip-172-31-7-44 docker: time="2022-09-29T17:04:42.576967756Z" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
Sep 29 17:04:42 ip-172-31-7-44 docker: time="2022-09-29T17:04:42.737972210Z" level=info msg="Loading containers: done."
Sep 29 17:04:43 ip-172-31-7-44 docker: time="2022-09-29T17:04:43.044803469Z" level=info msg="Docker daemon" commit=a89b842 graphdriver(s)=overlay2 version=20.10.17
Sep 29 17:04:43 ip-172-31-7-44 docker: time="2022-09-29T17:04:43.045249096Z" level=info msg="Daemon has completed initialization"
Sep 29 17:04:43 ip-172-31-7-44 docker: time="2022-09-29T17:04:43.082693306Z" level=info msg="API listen on /run/docker.sock"
Sep 29 17:05:03 ip-172-31-7-44 docker: time="2022-09-29T17:05:03.459921076Z" level=info msg="Layer sha256:35c7205075f4f3bd7f9b0e488668782fa244a75cccb6a6ef6a3b14251b55236d cleaned up"
----------------------------------------
/var/log/eb-engine.log
----------------------------------------
2022/09/29 17:05:11.511727 [INFO] Running command /bin/sh -c systemctl show -p PartOf nginx.service
2022/09/29 17:05:11.523154 [INFO] register process nginx
2022/09/29 17:05:11.523176 [INFO] Running command /bin/sh -c systemctl show -p PartOf nginx.service
2022/09/29 17:05:11.537946 [INFO] Running command /bin/sh -c systemctl daemon-reload
2022/09/29 17:05:11.659032 [INFO] Running command /bin/sh -c systemctl reset-failed
2022/09/29 17:05:11.666538 [INFO] Running command /bin/sh -c systemctl enable nginx.service
2022/09/29 17:05:11.786233 [INFO] Created symlink from /etc/systemd/system/multi-user.target.wants/nginx.service to /usr/lib/systemd/system/nginx.service.
2022/09/29 17:05:11.786293 [INFO] Running command /bin/sh -c systemctl show -p PartOf nginx.service
2022/09/29 17:05:11.802086 [INFO] Running command /bin/sh -c systemctl restart nginx.service
2022/09/29 17:05:11.904366 [INFO] Running command /bin/sh -c service iptables save
2022/09/29 17:05:11.966054 [INFO] iptables: Saving firewall rules to /etc/sysconfig/iptables: [ OK ]
2022/09/29 17:05:11.966069 [INFO] Traffic forward set-up completed.
2022/09/29 17:05:11.966074 [INFO] making STAGING app container current...
2022/09/29 17:05:11.966088 [INFO] Running command /bin/sh -c docker tag 5d99cf30b3ae aws_beanstalk/current-app
2022/09/29 17:05:12.041952 [INFO] Running command /bin/sh -c docker rmi aws_beanstalk/staging-app
2022/09/29 17:05:12.106692 [INFO] Untagged: aws_beanstalk/staging-app:latest
2022/09/29 17:05:12.106769 [INFO] Running command /bin/sh -c systemctl show -p PartOf eb-docker.service
2022/09/29 17:05:12.118591 [INFO] Running command /bin/sh -c systemctl daemon-reload
2022/09/29 17:05:12.242722 [INFO] Running command /bin/sh -c systemctl reset-failed
2022/09/29 17:05:12.250703 [INFO] Running command /bin/sh -c systemctl enable eb-docker.service
2022/09/29 17:05:12.365666 [INFO] Running command /bin/sh -c systemctl show -p PartOf eb-docker.service
2022/09/29 17:05:12.382129 [INFO] Running command /bin/sh -c systemctl is-active eb-docker.service
2022/09/29 17:05:12.390717 [INFO] Running command /bin/sh -c systemctl start eb-docker.service
2022/09/29 17:05:12.465476 [INFO] Running command /bin/sh -c systemctl show -p PartOf eb-docker-log.service
2022/09/29 17:05:12.479384 [INFO] Running command /bin/sh -c systemctl daemon-reload
2022/09/29 17:05:12.620319 [INFO] Running command /bin/sh -c systemctl reset-failed
2022/09/29 17:05:12.638521 [INFO] Running command /bin/sh -c systemctl enable eb-docker-log.service
2022/09/29 17:05:12.787312 [INFO] Created symlink from /etc/systemd/system/eb-docker.service.wants/eb-docker-log.service to /etc/systemd/system/eb-docker-log.service.
2022/09/29 17:05:12.787345 [INFO] Running command /bin/sh -c systemctl show -p PartOf eb-docker-log.service
2022/09/29 17:05:12.803790 [INFO] Running command /bin/sh -c systemctl is-active eb-docker-log.service
2022/09/29 17:05:12.814626 [INFO] Running command /bin/sh -c systemctl start eb-docker-log.service
2022/09/29 17:05:12.939662 [INFO] docker container 48320d59a48b is running aws_beanstalk/current-app
2022/09/29 17:05:12.939681 [INFO] Executing instruction: Clean up Docker
2022/09/29 17:05:12.939710 [INFO] Running command /bin/sh -c docker ps -aq
2022/09/29 17:05:13.129931 [INFO] 48320d59a48b
2022/09/29 17:05:13.129970 [INFO] Running command /bin/sh -c docker images | sed 1d
2022/09/29 17:05:13.282274 [INFO] aws_beanstalk/current-app latest 5d99cf30b3ae 10 seconds ago 622MB
bitnami/keycloak 19 2a52f7074b40 3 days ago 622MB
2022/09/29 17:05:13.282303 [INFO] save docker tag command: docker tag 5d99cf30b3ae aws_beanstalk/current-app:latest
2022/09/29 17:05:13.282309 [INFO] save docker tag command: docker tag 2a52f7074b40 bitnami/keycloak:19
2022/09/29 17:05:13.282321 [INFO] Running command /bin/sh -c docker rm `docker ps -aq`
2022/09/29 17:05:13.529450 [INFO] Error response from daemon: You cannot remove a running container 48320d59a48b027ab5d08531271a2cd0c4cafac5e80f322fa7fc98c0849ba5b4. Stop the container before attempting removal or force remove
2022/09/29 17:05:13.529511 [INFO] Running command /bin/sh -c docker rmi `docker images -aq`
2022/09/29 17:05:13.789049 [INFO] Error response from daemon: conflict: unable to delete 5d99cf30b3ae (cannot be forced) - image is being used by running container 48320d59a48b
Error response from daemon: conflict: unable to delete 2a52f7074b40 (cannot be forced) - image has dependent child images
2022/09/29 17:05:13.789067 [INFO] restore docker image name with command: docker tag 5d99cf30b3ae aws_beanstalk/current-app:latest
2022/09/29 17:05:13.789078 [INFO] Running command /bin/sh -c docker tag 5d99cf30b3ae aws_beanstalk/current-app:latest
2022/09/29 17:05:13.918414 [INFO] restore docker image name with command: docker tag 2a52f7074b40 bitnami/keycloak:19
2022/09/29 17:05:13.918438 [INFO] Running command /bin/sh -c docker tag 2a52f7074b40 bitnami/keycloak:19
2022/09/29 17:05:14.013863 [INFO] Executing instruction: start X-Ray
2022/09/29 17:05:14.013880 [INFO] X-Ray is not enabled.
2022/09/29 17:05:14.013885 [INFO] Executing instruction: configureSqsd
2022/09/29 17:05:14.013891 [INFO] This is a web server environment instance, skip configure sqsd daemon ...
2022/09/29 17:05:14.013896 [INFO] Executing instruction: startSqsd
2022/09/29 17:05:14.013900 [INFO] This is a web server environment instance, skip start sqsd daemon ...
2022/09/29 17:05:14.013905 [INFO] Executing instruction: Track pids in healthd
2022/09/29 17:05:14.013910 [INFO] This is an enhanced health env...
2022/09/29 17:05:14.013939 [INFO] Running command /bin/sh -c systemctl show -p ConsistsOf aws-eb.target | cut -d= -f2
2022/09/29 17:05:14.032650 [INFO] eb-docker.service healthd.service nginx.service eb-docker-events.service cfn-hup.service eb-docker-log.service docker.service
2022/09/29 17:05:14.032683 [INFO] Running command /bin/sh -c systemctl show -p ConsistsOf eb-app.target | cut -d= -f2
2022/09/29 17:05:14.055602 [INFO]
2022/09/29 17:05:14.057747 [INFO] Executing instruction: Configure Docker Container Logging
2022/09/29 17:05:14.066518 [INFO] Executing instruction: RunAppDeployPostDeployHooks
2022/09/29 17:05:14.066536 [INFO] Executing platform hooks in .platform/hooks/postdeploy/
2022/09/29 17:05:14.066560 [INFO] The dir .platform/hooks/postdeploy/ does not exist
2022/09/29 17:05:14.066564 [INFO] Finished running scripts in /var/app/current/.platform/hooks/postdeploy
2022/09/29 17:05:14.066572 [INFO] Executing cleanup logic
2022/09/29 17:05:14.068115 [INFO] Platform Engine finished execution on command: self-startup
2022/09/29 17:05:39.149172 [INFO] Starting...
2022/09/29 17:05:39.149959 [INFO] Starting EBPlatform-PlatformEngine
2022/09/29 17:05:39.149999 [INFO] reading event message file
2022/09/29 17:05:39.151835 [INFO] Engine received EB command cfn-hup-exec
2022/09/29 17:05:39.291599 [INFO] Running command /bin/sh -c /opt/aws/bin/cfn-get-metadata -s arn:aws:cloudformation:eu-west-2:882618350644:stack/awseb-e-2mwnvjecwe-stack/e6e0d050-3f75-11ed-a0e9-0a1f03d7e8a8 -r AWSEBAutoScalingGroup --region eu-west-2
2022/09/29 17:05:40.014546 [INFO] Running command /bin/sh -c /opt/aws/bin/cfn-get-metadata -s arn:aws:cloudformation:eu-west-2:882618350644:stack/awseb-e-2mwnvjecwe-stack/e6e0d050-3f75-11ed-a0e9-0a1f03d7e8a8 -r AWSEBBeanstalkMetadata --region eu-west-2
2022/09/29 17:05:40.681829 [INFO] checking whether command tail-log is applicable to this instance...
2022/09/29 17:05:40.681845 [INFO] this command is applicable to the instance, thus instance should execute command
2022/09/29 17:05:40.681850 [INFO] Engine command: (tail-log)
2022/09/29 17:05:40.682976 [INFO] Executing instruction: GetTailLogs
2022/09/29 17:05:40.682984 [INFO] Tail Logs...
2022/09/29 17:05:40.685700 [INFO] Running command /bin/sh -c tail -n 100 /var/log/eb-hooks.log
2022/09/29 17:05:40.687855 [INFO] Running command /bin/sh -c tail -n 100 /var/log/nginx/access.log
2022/09/29 17:05:40.689449 [INFO] Running command /bin/sh -c tail -n 100 /var/log/nginx/error.log
2022/09/29 17:05:40.693994 [INFO] Running command /bin/sh -c tail -n 100 /var/log/eb-docker/containers/eb-current-app/eb-48320d59a48b-stdouterr.log
2022/09/29 17:05:40.695588 [INFO] Running command /bin/sh -c tail -n 100 /var/log/docker-events.log
2022/09/29 17:05:40.702009 [INFO] Running command /bin/sh -c tail -n 100 /var/log/eb-docker-process.log
2022/09/29 17:05:40.703972 [INFO] Running command /bin/sh -c tail -n 100 /var/log/docker
2022/09/29 17:05:40.707914 [INFO] Running command /bin/sh -c tail -n 100 /var/log/eb-engine.log
The logs show that it is unable to delete the current docker images as the container is still running. I don't how I've caused that.
What is likely causing this?
Can't start the local fabric in VSC environment when trying to deploy smart contract
When using the IBM Blockchain Extension for VS Code; I wrote a sample smart contract and packaged it. But when I try to start the local fabric environment, I get an error saying: Failed to start Local Fabric: Failed to execute command "cmd" with arguments "/c, start.cmd" return code 1 I was following the IBM tutorials for blockchain and installed all required software tools for the extension as listed by IBM in the following link: N/A This is part of the error: [9/2/2019 8:09:46 PM] [INFO] C:\Users\sufij\.fabric-vscode\environments\local_fabric>echo Hyperledger Fabric started in seconds. [9/2/2019 8:09:46 PM] [INFO] Hyperledger Fabric started in seconds [9/2/2019 8:09:46 PM] [INFO] C:\Users\sufij\.fabric-vscode\environments\local_fabric>rem Check to see if the channel already exists [9/2/2019 8:09:46 PM] [INFO] C:\Users\sufij\.fabric-vscode\environments\local_fabric>docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/users/Admin#org1.example.com/msp" fabricvscodelocalfabric_peer0.org1.example.com peer channel getinfo -c mychannel [9/2/2019 8:09:46 PM] [INFO] Error: No such container: fabricvscodelocalfabric_peer0.org1.example.com [9/2/2019 8:09:46 PM] [INFO] C:\Users\sufij\.fabric-vscode\environments\local_fabric>if errorlevel 1 [9/2/2019 8:09:46 PM] [INFO] ( [9/2/2019 8:09:46 PM] [INFO] rem Create the channel [9/2/2019 8:09:46 PM] [INFO] docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/users/Admin#org1.example.com/msp" fabricvscodelocalfabric_peer0.org1.example.com peer channel create -o orderer.example.com:17050 -c mychannel -f /etc/hyperledger/configtx/channel.tx [9/2/2019 8:09:46 PM] [INFO] rem Update the channel with the anchor peers [9/2/2019 8:09:46 PM] [INFO] docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/users/Admin#org1.example.com/msp" fabricvscodelocalfabric_peer0.org1.example.com peer channel update -o orderer.example.com:17050 -c mychannel -f /etc/hyperledger/configtx/Org1MSPanchors.tx [9/2/2019 8:09:46 PM] [INFO] rem Join peer0.org1.example.com to the channel. [9/2/2019 8:09:46 PM] [INFO] docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/users/Admin#org1.example.com/msp" fabricvscodelocalfabric_peer0.org1.example.com peer channel join -b mychannel.block [9/2/2019 8:09:46 PM] [INFO] ) [9/2/2019 8:09:46 PM] [INFO] Error: No such container: fabricvscodelocalfabric_peer0.org1.example.com [9/2/2019 8:09:46 PM] [INFO] Error: No such container: fabricvscodelocalfabric_peer0.org1.example.com [9/2/2019 8:09:46 PM] [INFO] Error: No such container: fabricvscodelocalfabric_peer0.org1.example.com [9/2/2019 8:09:46 PM] [ERROR] Failed to start Local Fabric: Error: Failed to execute command "cmd" with arguments "/c, start.cmd" return code 1
install docker on debian - 'overlay' is not supported over overlayfs
I created a docker image for my build pipeline and I am trying to run docker build -t someTag . However, I am getting this error. DEBU[0000] Listener created for HTTP on unix (/var/run/docker.sock) INFO[0000] libcontainerd: new containerd process, pid: 1026 DEBU[0000] Permission denied writing "-500" to /proc/1026/oom_score_adj DEBU[0000] containerd: grpc api on /var/run/docker/libcontainerd/docker-containerd.sock DEBU[0000] containerd: read past events count=0 DEBU[0000] containerd: supervisor running cpus=2 memory=976 runtime=docker-runc runtimeArgs=[] stateDir="/var/run/docker/libcontainerd/containerd" DEBU[0000] libcontainerd: containerd health check returned error: rpc error: code = 14 desc = grpc: the connection is unavailable DEBU[0001] Permission denied writing "-500" to /proc/self/oom_score_adj DEBU[0001] Using default logging driver json-file DEBU[0001] Golang's threads limit set to 6840 DEBU[0001] [zfs] zfs command is not available: exec: "zfs": executable file not found in $PATH ERRO[0001] 'overlay' is not supported over overlayfs DEBU[0001] Using graph driver vfs DEBU[0001] Max Concurrent Downloads: 3 DEBU[0001] Max Concurrent Uploads: 5 INFO[0001] Graph migration to content-addressability took 0.00 seconds INFO[0001] Loading containers: start. DEBU[0001] Option Experimental: false DEBU[0001] Option DefaultDriver: bridge DEBU[0001] Option DefaultNetwork: bridge WARN[0001] Running modprobe bridge br_netfilter failed with message: , error: exec: "modprobe": executable file not found in $PATH WARN[0001] Running modprobe nf_nat failed with message: ``, error: exec: "modprobe": executable file not found in $PATH WARN[0001] Running modprobe xt_conntrack failed with message: ``, error: exec: "modprobe": executable file not found in $PATH DEBU[0001] Fail to initialize firewalld: Failed to connect to D-Bus system bus: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory, using raw iptables instead DEBU[0001] /usr/sbin/iptables, [-t nat -D PREROUTING -m addrtype --dst-type LOCAL -j DOCKER] DEBU[0001] /usr/sbin/iptables, [-t nat -D OUTPUT -m addrtype --dst-type LOCAL ! --dst 127.0.0.0/8 -j DOCKER] DEBU[0001] /usr/sbin/iptables, [-t nat -D OUTPUT -m addrtype --dst-type LOCAL -j DOCKER] DEBU[0001] /usr/sbin/iptables, [-t nat -D PREROUTING] DEBU[0001] /usr/sbin/iptables, [-t nat -D OUTPUT] DEBU[0001] /usr/sbin/iptables, [-t nat -F DOCKER] DEBU[0001] /usr/sbin/iptables, [-t nat -X DOCKER] DEBU[0001] /usr/sbin/iptables, [-t filter -F DOCKER] DEBU[0001] /usr/sbin/iptables, [-t filter -X DOCKER] DEBU[0001] /usr/sbin/iptables, [-t filter -F DOCKER-ISOLATION] DEBU[0001] /usr/sbin/iptables, [-t filter -X DOCKER-ISOLATION] DEBU[0001] /usr/sbin/iptables, [-t nat -n -L DOCKER] DEBU[0001] /usr/sbin/iptables, [-t nat -N DOCKER] DEBU[0001] start clean shutdown of all containers with a 15 seconds timeout... DEBU[0001] Cleaning up old mountid : start. DEBU[0001] Cleaning up old mountid : done. Here is the info of my Dockerfile that is installing docker. I found these steps here. FROM debian:latest ENV DEBIAN_FRONTEND noninteractive ENV JENKINS_HOME /var/jenkins_home USER root WORKDIR $JENKINS_HOME RUN apt-get update RUN apt-get install \ apt-transport-https \ ca-certificates \ curl \ gnupg2 \ software-properties-common -y RUN curl -fsSL https://download.docker.com/linux/debian/gpg | apt-key add - RUN apt-get install -y iptables RUN wget https://download.docker.com/linux/debian/dists/jessie/pool/stable/amd64/docker-ce_17.06.0~ce-0~debian_amd64.deb RUN dpkg -i docker-ce_17.06.0~ce-0~debian_amd64.deb What I have tried: I have tried starting dockerd. From my best guess, it looks like I need dockerd to start. root#90302deb48a0:/var/jenkins_home# ps -ef | grep docker root 6 1 0 14:47 ? 00:00:00 grep docker I have looked into updating I have tried updating my iptables root#e898473347a2:/var/jenkins_home# apt-get install -y iptables Reading package lists... Done Building dependency tree Reading state information... Done iptables is already the newest version (1.6.0+snapshot20161117-6). 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. I have verified that I am root and the directories are owned by root. root#e898473347a2:/var/jenkins_home# whoami root I have tried to research where to post this. Please tell me if this needs to be moved somewhere else. I will kindly move this if this doesn't classify as "programming".
It sounds like you are trying to do Docker in Docker (DinD). It requires some hacks and changing the storage driver (you can't do overlay on overlay). See the Dockerfile and entrypoint script at https://github.com/docker-library/docker/tree/a73d96e731e2dd5d6822c99a9af4dcbfbbedb2be/19.03/dind for more information. It has information on where it gets the dind script and the necessary entrypoint changes to run dockerd. However, there are official dind tagged images on Docker Hub that you may be better off building from. See https://hub.docker.com/_/docker/. You could just use image docker:17.05.0-dind or base your image off of it if you need customizations.
Jenkins Android Emulator Plugin not connecting
I am having problems with the Android Emulator Plugin in Jenkins. I am trying to start an emulator, but most of the times, it will just wait until the device is online, resulting in a timeout. The errorcode can be seen here: $ C:\Users\Administrator\Documents\Jenkins\AndroidSDK/platform-tools/adb.exe connect localhost:6086 connected to localhost:6086 [android] Waiting for emulator to finish booting... $ C:\Users\Administrator\Documents\Jenkins\AndroidSDK/platform-tools/adb.exe -s localhost:6086 shell getprop init.svc.bootanim error: device offline $ C:\Users\Administrator\Documents\Jenkins\AndroidSDK/platform-tools/adb.exe connect localhost:6086 $ C:\Users\Administrator\Documents\Jenkins\AndroidSDK/platform-tools/adb.exe -s localhost:6086 shell getprop init.svc.bootanim error: device offline $ C:\Users\Administrator\Documents\Jenkins\AndroidSDK/platform-tools/adb.exe connect localhost:6086 $ C:\Users\Administrator\Documents\Jenkins\AndroidSDK/platform-tools/adb.exe -s localhost:6086 shell getprop init.svc.bootanim error: device offline $ C:\Users\Administrator\Documents\Jenkins\AndroidSDK/platform-tools/adb.exe disconnect localhost:6086 $ C:\Users\Administrator\Documents\Jenkins\AndroidSDK/platform-tools/adb.exe connect localhost:6086 $ C:\Users\Administrator\Documents\Jenkins\AndroidSDK/platform-tools/adb.exe -s localhost:6086 shell getprop init.svc.bootanim error: device offline $ C:\Users\Administrator\Documents\Jenkins\AndroidSDK/platform-tools/adb.exe connect localhost:6086 $ C:\Users\Administrator\Documents\Jenkins\AndroidSDK/platform-tools/adb.exe -s localhost:6086 shell getprop init.svc.bootanim error: device offline ... A LOT of repeating ... $ C:\Users\Administrator\Documents\Jenkins\AndroidSDK/platform-tools/adb.exe connect localhost:6086 $ C:\Users\Administrator\Documents\Jenkins\AndroidSDK/platform-tools/adb.exe -s localhost:6086 shell getprop init.svc.bootanim error: device offline $ C:\Users\Administrator\Documents\Jenkins\AndroidSDK/platform-tools/adb.exe connect localhost:6086 $ C:\Users\Administrator\Documents\Jenkins\AndroidSDK/platform-tools/adb.exe -s localhost:6086 shell getprop init.svc.bootanim error: device offline $ C:\Users\Administrator\Documents\Jenkins\AndroidSDK/platform-tools/adb.exe connect localhost:6086 [android] Timed-out after waiting 720 seconds for emulator Does anyone know how to fix this?
no module named OpenSSL
I try to get working SET on my iPhone for a week with no success. iPhone5S IOS 7.0.4 I try to do a credential harvester attack (site clone) but I always have the error message : No module named OpenSSL OpenSSL is installed on my iPhone (with cydia). Nestat is also installed. A lot of other tools : bigboss recommended tools, gcc, ruby 1.8.6... The error message no module named OpenSSL appears just after the cloning phase where it should normally say waiting for connection something like that, the error : Something went wrong, printing the error: No module named OpenSSL netstat: option requires an argument -- p Usage: netstat [-AaLlnW] [-f address_family | -p protocol] netstat [-gilns] [-f address_family] netstat -i | -I interface [-w wait] [-abdgt] netstat -s [-s] [-f address_family | -p protocol] [-w wait] netstat -i | -I interface -s [-f address_family | -p protocol] netstat -m [-m] netstat -r [-Aaln] [-f address_family] netstat -rs [-s] netstat: option requires an argument -- p Usage: netstat [-AaLlnW] [-f address_family | -p protocol] netstat [-gilns] [-f address_family] netstat -i | -I interface [-w wait] [-abdgt] netstat -s [-s] [-f address_family | -p protocol] [-w wait] netstat -i | -I interface -s [-f address_family | -p protocol] netstat -m [-m] netstat -r [-Aaln] [-f address_family] netstat -rs [-s] I tried to install pyopenssl manually (not the one from Cydia) with no success : /var/mobile/Downloads/pyOpenSSL-0.9 root# python setup.py install running install running build running build_py running build_ext building 'OpenSSL.crypto' extension /usr/bin/arm-apple-darwin9-gcc-4.2.1 -fno-strict-aliasing -I/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS4.2.sdk/usr/include/ -I/Users/linusyang/Documents/Code/python/python-for-ios/prelib/usr/include -arch armv6 -pipe -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I/sw/include -I/usr/include/python2.7 -c src/crypto/crypto.c -o build/temp.darwin-10.5-arm-2.7/src/crypto/crypto.o error: command '/usr/bin/arm-apple-darwin9-gcc-4.2.1' terminated by signal 4 thanks
iOS (and OSX) developer tools does not ship with a OpenSSL library. If you need OpenSSL you will have to get the source and compile it yourself. In most cases the Apple supplied Common Crypto provides a solution. The reason stated by Apple is because OpenSSL in many cases is not backward compatible to earlier, even recent, minor change versions. Thus a developer on compiling with a later version of an Apple supplied OpenSSL would have his code break. By not shipping the developer will have to select the version he uses and it will not change without warning and break the code. Theree were a substantial number of problems in this area. (This info was from a WWDC session a couple of years ago).