I'm using wolkenkit 1.2.0,
I'm starting wolkenkit this way:
wolkenkit start --shared-key 123456 --verbose
I'm sending commands and I can see them in the logs, but I'm not receiving events. Could it be related to the following error I'm seeing in the logs all the time:
Application failed unexpectedly. (fatal)
wolkenkit-flows::wolkenkit-flows#1.2.0::tailwind#1.0.1
(/wolkenkit/node_modules/tailwind/lib/TailwindApp.js)
12:07:50.298#2018-01-14 5#0
{
err: {
name: 'Error',
message: 'Could not connect to amqp://wolkenkit:123456#messagebus:5672.',
stack: 'Error: Could not connect to amqp://wolkenkit:123456#messagebus:5672.
at /wolkenkit/node_modules/hase/dist/hase.js:22:23
at /wolkenkit/node_modules/amqplib/callback_api.js:16:10
at Socket.<anonymous> (/wolkenkit/node_modules/amqplib/lib/connect.js:167:18)
at Object.onceWrapper (events.js:315:30)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at emitErrorNT (internal/streams/destroy.js:64:8)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)'
}
}
I've tried upgrading to 1.2.1 with no help.
I've deleted all the containers and started from the top. Still not working.
Edit:
Full Log of the basic chat app:
Failed to initialize application. (fatal)
wolkenkit-core::wolkenkit-core#1.2.0::tailwind#1.0.1 (/wolkenkit/node_modules/tailwind/lib/TailwindApp.js)
12:25:49.249#2018-01-14 5#0
{
err: {
name: 'Error',
message: 'connect ECONNREFUSED 172.18.0.4:5432',
stack: 'Error: connect ECONNREFUSED 172.18.0.4:5432
at Object._errnoException (util.js:1024:11)
at _exceptionWithHostPort (util.js:1046:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1182:14)'
}
}
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Application failed unexpectedly. (fatal)
wolkenkit-core::wolkenkit-core#1.2.0::tailwind#1.0.1 (/wolkenkit/node_modules/tailwind/lib/TailwindApp.js)
12:25:52.226#2018-01-14 5#0
{
err: {
name: 'Error',
message: 'Could not connect to amqp://wolkenkit:09a7458453d58c93d22a2b823bf2fccee3b704db#messagebus:5672.',
stack: 'Error: Could not connect to amqp://wolkenkit:09a7458453d58c93d22a2b823bf2fccee3b704db#messagebus:5672.
at /wolkenkit/node_modules/hase/dist/hase.js:22:23
at /wolkenkit/node_modules/amqplib/callback_api.js:16:10
at Socket.<anonymous> (/wolkenkit/node_modules/amqplib/lib/connect.js:167:18)
at Object.onceWrapper (events.js:315:30)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at emitErrorNT (internal/streams/destroy.js:64:8)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)'
}
}
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Application failed unexpectedly. (fatal)
wolkenkit-core::wolkenkit-core#1.2.0::tailwind#1.0.1 (/wolkenkit/node_modules/tailwind/lib/TailwindApp.js)
12:25:54.858#2018-01-14 5#0
{
err: {
name: 'Error',
message: 'Could not connect to amqp://wolkenkit:09a7458453d58c93d22a2b823bf2fccee3b704db#messagebus:5672.',
stack: 'Error: Could not connect to amqp://wolkenkit:09a7458453d58c93d22a2b823bf2fccee3b704db#messagebus:5672.
at /wolkenkit/node_modules/hase/dist/hase.js:22:23
at /wolkenkit/node_modules/amqplib/callback_api.js:16:10
at Socket.<anonymous> (/wolkenkit/node_modules/amqplib/lib/connect.js:167:18)
at Object.onceWrapper (events.js:315:30)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at emitErrorNT (internal/streams/destroy.js:64:8)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)'
}
}
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Application failed unexpectedly. (fatal)
wolkenkit-core::wolkenkit-core#1.2.0::tailwind#1.0.1 (/wolkenkit/node_modules/tailwind/lib/TailwindApp.js)
12:25:58.737#2018-01-14 5#0
{
err: {
name: 'Error',
message: 'Could not connect to amqp://wolkenkit:09a7458453d58c93d22a2b823bf2fccee3b704db#messagebus:5672.',
stack: 'Error: Could not connect to amqp://wolkenkit:09a7458453d58c93d22a2b823bf2fccee3b704db#messagebus:5672.
at /wolkenkit/node_modules/hase/dist/hase.js:22:23
at /wolkenkit/node_modules/amqplib/callback_api.js:16:10
at Socket.<anonymous> (/wolkenkit/node_modules/amqplib/lib/connect.js:167:18)
at Object.onceWrapper (events.js:315:30)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at emitErrorNT (internal/streams/destroy.js:64:8)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)'
}
}
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Running application. (info)
wolkenkit-core::wolkenkit-core#1.2.0::tailwind#1.0.1 (/wolkenkit/node_modules/tailwind/lib/TailwindApp.js)
12:26:02.761#2018-01-14 5#0
As discussed in the comments, I think that this problem is specific to your application, not to wolkenkit in general.
In my opinion I think that you need to figure out which command or event causes your application to not work properly. Unfortunately, I can't help with that too much, without having a closer look at the application's code.
I'm very sorry that I don't have a better answer for you.
However, I hope this at least helps to point you into the right direction.
Related
I am trying to install the package "react-native-webrtc" but getting this error (yarn install react-native-webrtc --verbose):
react-native-webrtc
verbose 189.970120017 Error: /Users/samwin/dev/MobileAgent/node_modules/react-native-webrtc: Command failed.
Exit code: 1
Command: node tools/downloadWebRTC.js
Arguments:
Directory: /Users/samwin/dev/MobileAgent/node_modules/react-native-webrtc
Output:
Downloading https://github.com/jitsi/webrtc/releases/download/v100.0.0/WebRTC.xcframework.tgz...
node:internal/process/promises:246
triggerUncaughtException(err, true /* fromPromise */);
^
Error: connect ECONNREFUSED 185.199.108.133:443
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16) {
errno: -61,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '185.199.108.133',
port: 443
}
at ProcessTermError.ExtendableBuiltin (/usr/local/Cellar/yarn/1.22.4/libexec/lib/cli.js:721:66)
at ProcessTermError.MessageError (/usr/local/Cellar/yarn/1.22.4/libexec/lib/cli.js:750:123)
at new ProcessTermError (/usr/local/Cellar/yarn/1.22.4/libexec/lib/cli.js:790:113)
at ChildProcess.<anonymous> (/usr/local/Cellar/yarn/1.22.4/libexec/lib/cli.js:25884:17)
at ChildProcess.emit (node:events:390:28)
at maybeClose (node:internal/child_process:1064:16)
at Socket.<anonymous> (node:internal/child_process:450:11)
at Socket.emit (node:events:390:28)
at Pipe.<anonymous> (node:net:687:12)
error /Users/samwin/dev/MobileAgent/node_modules/react-native-webrtc: Command failed.
Exit code: 1
Command: node tools/downloadWebRTC.js
Arguments:
Directory: /Users/samwin/dev/MobileAgent/node_modules/react-native-webrtc
Output:
Downloading https://github.com/jitsi/webrtc/releases/download/v100.0.0/WebRTC.xcframework.tgz...
node:internal/process/promises:246
triggerUncaughtException(err, true /* fromPromise */);
^
Error: connect ECONNREFUSED 185.199.108.133:443
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16) {
errno: -61,
code: 'ECONNREFUSED',
syscall: 'connect',
The folder react-native-webrtc exists in node_modules, but when I try to build the app in Xcode, then it throws error like described here.
BTW: I can download the file when opening the url in the browser.
Is there any solution for this issue?
My solution was to download the .tgz file manually (which should be done actually in tools/downloadWebRTC.js) and extracted it to corresponding location. Now the Xcode build works fine.
2022-06-20T10:22:26.412Z INFO #wdio/cli:launcher: Run onPrepare hook
2022-06-20T10:23:22.099Z ERROR #wdio/cli:utils: A service failed in the 'onPrepare' hook
Error: Appium exited before timeout (exit code: 1)
at ChildProcess.<anonymous> (C:\Users\Joyi\Downloads\webdriverio-appium-course-master\webdriverio-appium-course-master\node_modules\#wdio\appium-service\build\launcher.js:110:22)
at Object.onceWrapper (node:events:642:26)
at ChildProcess.emit (node:events:527:28)
at ChildProcess.emit (node:domain:475:12)
at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
I have an app running Parse server on AWS as the backend. It has crashed because the mongoDB appears to have stopped connecting with Parse at 127.0.0.1 but I am not sure how that happened since I didn't make any code changes. What I did do was try and update a certifiact using bncert tool.
I have to manually go in every 3 months or so to renew the certificates using sudo /opt/bitnami/bncert-tool where I then enter in my servername and email address. I just performed this perodic maintenance and restarted my server. This appears to have broken something in the parse connection to the mongoDB though. When I go to my parse dashboard it pulls up an error log that suggests something has been deprecated for how mongoDB connects to parse? Can someone provide any guidance as to how to fix this or how to figure out what could be going wrong? Some things I see in the log are errorLabels: [ 'TransientTransactionError' ] and
The log has the error:
2020-05-24T01:37:49.746Z - Uncaught internal server error. { MongoNetworkError: failed to connect to server [127.0.0.1:27017] on first connect [MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017]
at Pool.<anonymous> (/opt/bitnami/apps/parse/htdocs/node_modules/mongodb-core/lib/topologies/server.js:564:11)
at emitOne (events.js:116:13)
at Pool.emit (events.js:211:7)
at Connection.<anonymous> (/opt/bitnami/apps/parse/htdocs/node_modules/mongodb-core/lib/connection/pool.js:317:12)
at Object.onceWrapper (events.js:317:30)
at emitTwo (events.js:126:13)
at Connection.emit (events.js:214:7)
at Socket.<anonymous> (/opt/bitnami/apps/parse/htdocs/node_modules/mongodb-core/lib/connection/connection.js:246:50)
at Object.onceWrapper (events.js:315:30)
at emitOne (events.js:116:13)
name: 'MongoNetworkError',
errorLabels: [ 'TransientTransactionError' ],
[Symbol(mongoErrorContextSymbol)]: {} } MongoNetworkError: failed to connect to server [127.0.0.1:27017] on first connect [MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017]
at Pool.<anonymous> (/opt/bitnami/apps/parse/htdocs/node_modules/mongodb-core/lib/topologies/server.js:564:11)
at emitOne (events.js:116:13)
at Pool.emit (events.js:211:7)
at Connection.<anonymous> (/opt/bitnami/apps/parse/htdocs/node_modules/mongodb-core/lib/connection/pool.js:317:12)
at Object.onceWrapper (events.js:317:30)
at emitTwo (events.js:126:13)
at Connection.emit (events.js:214:7)
at Socket.<anonymous> (/opt/bitnami/apps/parse/htdocs/node_modules/mongodb-core/lib/connection/connection.js:246:50)
at Object.onceWrapper (events.js:315:30)
at emitOne (events.js:116:13)
2020-05-24T01:37:38.156Z - error getting auth for sessionToken
I figured it out... but posting here in case someone runs into the same error. I noticed that when I logged on to my bitami ubuntu instance with parse there was a message that a system restart was required. I also noticed that that the letsencrypt tool had an updated version. I restarted the ubuntu instance, stopped my apache server with sudo service apache2 stop, reran the lets encrypt certificate tool with sudo /opt/bitnami/bncert-tool and then restarted my parse server.js. When I did that everything started working again!
I managed to get the appium running. Unfortunately, I couldn't get a test to run successfully. Once the appium test finishes I only get only one unique error message which is the following:
[XCUITest] Error: Command '/bin/bash Scripts/bootstrap.sh -d' exited with code 134
at ChildProcess.<anonymous> (../../lib/teen_process.js:66:19)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:192:7)
at maybeClose (internal/child_process.js:890:16)
at Socket.<anonymous> (internal/child_process.js:334:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:189:7)
at Pipe._handle.close [as _onclose] (net.js:501:12)
{ Error: Command '/bin/bash Scripts/bootstrap.sh -d' exited with code 134
at ChildProcess.<anonymous> (../../lib/teen_process.js:66:19)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:192:7)
at maybeClose (internal/child_process.js:890:16)
at Socket.<anonymous> (internal/child_process.js:334:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:189:7)
at Pipe._handle.close [as _onclose] (net.js:501:12)
stdout: '\u001b[1mFetching dependencies\n',
stderr: 'dyld: Symbol not found: __TMV6Result8AnyError\n Referenced from: /usr/local/Cellar/carthage/0.19.1/bin/../Frameworks/CarthageKit.framework/Versions/Current/Frameworks/ReactiveSwift.framework/ReactiveSwift\n Expected in: /Library/Frameworks/CarthageKit.framework/Versions/Current/Frameworks/Result.framework/Versions/A/Result\n in /usr/local/Cellar/carthage/0.19.1/bin/../Frameworks/CarthageKit.framework/Versions/Current/Frameworks/ReactiveSwift.framework/ReactiveSwift\nScripts/bootstrap.sh: line 45: 18795 Abort trap: 6 carthage bootstrap $USE_SSH\n',
code: 134 }
Could anyone shed light in this matter? Any input is greatly appreciated.
EDIT: I looked into this issue, and I found that there is something wrong with Carthage installed in the system, when I type in the following commands:
cd /usr/local/lib/node_modules/appium/node_modules/appium-xcuitest-driver/WebDriverAgent/
/bin/bash Scripts/bootstrap.sh -d
I get the following error:
Fetching dependencies
dyld: Symbol not found: __TMV6Result8AnyError
Referenced from: /usr/local/Cellar/carthage/0.19.1/bin/../Frameworks/CarthageKit.framework/Versions/Current/Frameworks/ReactiveSwift.framework/ReactiveSwift
Expected in: /Library/Frameworks/CarthageKit.framework/Versions/Current/Frameworks/Result.framework/Versions/A/Result
in /usr/local/Cellar/carthage/0.19.1/bin/../Frameworks/CarthageKit.framework/Versions/Current/Frameworks/ReactiveSwift.framework/ReactiveSwift
Scripts/bootstrap.sh: line 45: 26035 Abort trap: 6 carthage bootstrap $USE_SSH
Although I'm not sure how to fix this. Any input is greatly appreciated.
This can occur if you have an old version of /Library/Frameworks/CarthageKit.framework. If you're using the Homebrew version of Carthage, you don't need that copy of the framework, so it can be safely deleted.
i.e., Delete the framework in /Library/Frameworks
Get the following error when protractor is about to run on a windows host via jenkins job. We run selenium hub on a linux host with the selenium node running off of windows
^
`Error: ECONNREFUSED connect ECONNREFUSED
at ClientRequest.<anonymous> (C:\dependencies-dashboard\node_modules\selenium-webdriver\http\index.js:172:16)
at ClientRequest.emit (events.js:107:17)
at Socket.socketErrorListener (_http_client.js:271:9)
at Socket.emit (events.js:107:17)
at net.js:459:14
at process._tickCallback (node.js:355:11)
From: Task: WebDriver.createSession()
at Function.webdriver.WebDriver.acquireSession_ (C:\dependencies-dashboard\node_modules\selenium-webdriver\lib\webdriver\webdriver.js:157:22)
at Function.webdriver.WebDriver.createSession (C:\dependencies-dashboard\node_modules\selenium-webdriver\lib\webdriver\webdriver.js:131:30)
at new Driver (C:\dependencies-dashboard\node_modules\selenium-webdriver\chrome.js:810:36)
at [object Object].DirectDriverProvider.getNewDriver (C:\dependencies-dashboard\node_modules\protractor\lib\driverProviders\direct.js:68:16)
at [object Object].Runner.createBrowser (C:\dependencies-dashboard\node_modules\protractor\lib\runner.js:182:37)
at C:\dependencies-dashboard\node_modules\protractor\lib\runner.js:263:21
at _fulfilled (C:\dependencies-dashboard\node_modules\protractor\node_modules\q\q.js:797:54)
at self.promiseDispatch.done (C:\dependencies-dashboard\node_modules\protractor\node_modules\q\q.js:826:30)
at Promise.promise.promiseDispatch (C:\dependencies-dashboard\node_modules\protractor\node_modules\q\q.js:759:13)
at C:\dependencies-dashboard\node_modules\protractor\node_modules\q\q.js:525:49
[launcher] Process exited with error code 1
events.js:85
throw er; // Unhandled 'error' event
^
Error: protractor exited with code 1
Build step 'Execute Windows batch command' marked build as failure
Finished: FAILURE`