I need to inspect an iOS app in appium inspector using real iphone device.
I am using 1.4.8 as appium version, physical device as iphone 6 and platform version as 8.3.
I have enabled Enable UI Automation option under Developer option settings.
I have given the following parameters in iOS settings menu.
App path: .zip format, Platform Version: 8.3, Force Device: iPhone and UDID: for that specific device
If I start appium server, I am getting the below log message.
Error Log:-
Launching Appium with command: '/Applications/Appium
.app/Contents/Resources/node/bin/node' lib/server/main.js
--command-timeout "7200" --pre-launch --debug-log-spacing --platform-version "8.3" --platform-name "iOS" --app "/Users/valar/work/sample_App.zip" --udid
"4a9b4ad142c7f308bfd3217d2fae43f9a4bc8e00" --show-ios-log
--device-name "iPhone 6"
info: [debug] Starting Appium in pre-launch mode
info: Pre-launching app info: *************************************
info: ************************************* info:
************************************* info: ************************************* info: ************************************* info: ************************************* info: ************************************* info: ************************************* info: **** NEW SESSION * info: **** NEW SESSION * info: **** NEW SESSION * info: **** NEW SESSION *
info: **** NEW SESSION * info: **** NEW
SESSION * info: **** NEW SESSION *
info: **** NEW SESSION * info:
************************************* info: ************************************* info: ************************************* info: ************************************* info: ************************************* info: ************************************* info: ************************************* info: *************************************
info: [debug] Using local .zip from command line:
/Users/valar/work/sample_App.zip info: [debug] Copying local zip to
tmp dir
info: [debug] /Users/valar/work/sample_App.zip copied to
/var/folders/7g/_4s8f5kx4cs1875_psp3rps00000gn/T/115725-3663-1b0sdz4/appium-app.zip
info: [debug] Unzipping
/var/folders/7g/_4s8f5kx4cs1875_psp3rps00000gn/T/115725-3663-1b0sdz4/appium-app.zip
info: [debug] Testing zip archive:
/var/folders/7g/_4s8f5kx4cs1875_psp3rps00000gn/T/115725-3663-1b0sdz4/appium-app.zip
info: [debug] Zip archive tested clean
info: [debug] Unzip successful
info: [debug] Using locally extracted app:
/var/folders/7g/_4s8f5kx4cs1875_psp3rps00000gn/T/115725-3663-1b0sdz4/sample_App.app
info: [debug] Creating new appium session
ab360b32-08b6-4f6b-889e-78fe9a6b88f3 info: [debug] Removing any
remaining instruments sockets info: [debug] Cleaned up instruments
socket /tmp/instruments_sock info: [debug] Auto-detecting iOS udid...
info: [debug] Not auto-detecting udid, running on sim
info: [debug] Parsed app Info.plist (as binary)
info: [debug] Parsed app Localizable.strings info: [debug] Getting
bundle ID from app
info: [debug] Parsed app Info.plist (as binary) info: [debug] Creating
instruments info: [debug] Preparing uiauto bootstrap info: [debug]
Dynamic bootstrap dir: /Users/valar/Library/Application
Support/appium/bootstrap info: [debug] Dynamic env:
{"nodePath":"/Applications/Appium
.app/Contents/Resources/node/bin/node","commandProxyClientPath":"/Applications/Appium
.app/Contents/Resources/node_modules/appium/node_modules/appium-uiauto/bin/command-proxy-client.js","instrumentsSock":"/tmp/instruments_sock","interKeyDelay":null,"justLoopInfinitely":false,"autoAcceptAlerts":false,"autoDismissAlerts":false,"sendKeyStrategy":"grouped"}
info: [debug] Dynamic bootstrap code: // This file is automatically
generated. Do not manually modify! ... info: [debug] Dynamic bootstrap
path: /Users/valar/Library/Application
Support/appium/bootstrap/bootstrap-f2765f8569503e7c.js
info: [debug] Reusing dynamic bootstrap:
/Users/valar/Library/Application
Support/appium/bootstrap/bootstrap-f2765f8569503e7c.js info: [debug]
Attempting iOS device log capture via libimobiledevice idevicesyslog
info: [debug] Creating iDevice object with udid
4a9b4ad142c7f308bfd3217d2fae43f9a4bc8e00
info: [IOS_SYSLOG_ROW ] Aug 25 11:37:49 iPhone-6 syslog_relay[177]
: syslog_relay found the ASL prompt. Starting...
info: [debug] App is installed.
info: [debug] fullReset not requested. No need to install. info:
[debug] Starting command proxy.
info: [debug] Instruments socket server started at
/tmp/instruments_sock info: [debug] Starting instruments
info: [debug] Instruments is at:
/Applications/Xcode.app/Contents/Developer/usr/bin/instruments
info: Launching instruments
info: [debug] Attempting to run app on real device with UDID
4a9b4ad142c7f308bfd3217d2fae43f9a4bc8e00 info: [debug] Spawning
instruments with command:
/Applications/Xcode.app/Contents/Developer/usr/bin/instruments -t
/Applications/Xcode.app/Contents/Applications/Instruments.app/Contents/PlugIns/AutomationInstrument.xrplugin/Contents/Resources/Automation.tracetemplate
-D /tmp/appium-instruments/instrumentscli0.trace -w 4a9b4ad142c7f308bfd3217d2fae43f9a4bc8e00 com.company.iphone.
sample_App -e UIASCRIPT "/Users/valar/Library/Application
Support/appium/bootstrap/bootstrap-f2765f8569503e7c.js" -e
UIARESULTSPATH /tmp/appium-instruments info: [debug] And extra
without-delay env: {} info: [debug] And launch timeouts (in ms):
{"global":90000}
info: [debug] [INSTSERVER] Instruments exited with code 253
info: [debug] Killall instruments
info: [debug] Instruments crashed on startup info: [debug] Attempting
to retry launching instruments, this is retry #1 info: [debug] Killall
iOS Simulator info: [IOS_SYSLOG_ROW ] Aug 25 11:37:50 iPhone-6
DTMobileIS[191] : Could not create service named
com.apple.instruments.server.services.processcontrol.posixspawn info:
[IOS_SYSLOG_ROW ] Aug 25 11:37:50 iPhone-6 DTMobileIS[191] :
Could not create service named
com.apple.instruments.server.services.launchdaemon
info: [IOS_SYSLOG_ROW ] Aug 25 11:37:50 iPhone-6
notification_proxy[175] : 0x100494000 -[MNPLockdownConnection
receiveMessage]: lockdown_receive_message error!
info: [IOS_SYSLOG_ROW ] Aug 25 11:37:50 iPhone-6
notification_proxy[175] : 0x100494000 -[MNPLockdownConnection
receiveMessage]: lockdown_receive_message error!
info: [IOS_SYSLOG_ROW ] Aug 25 11:37:52 iPhone-6 locationd[61]
: Location icon should now be in state 'Active'
info: [IOS_SYSLOG_ROW ] Aug 25 11:37:53 iPhone-6 CLTM[20] :
CLTM: _subscription 0x0, _subscribedChannels 0x0
info: [IOS_SYSLOG_ROW ] Aug 25 11:37:55 iPhone-6 sample_App[151]
: NewRelic(4.186,0x174675e80): NRTimer.m:94 -[NRTimer
timeElapsedInSeconds]
info: [IOS_SYSLOG_ROW ] NRMATimer has a negative duration:
1440482874430.621094 => 0.000000
info: Launching instruments
info: [debug] Attempting to run app on real device with UDID
4a9b4ad142c7f308bfd3217d2fae43f9a4bc8e00
info: [debug] Spawning instruments with command:
/Applications/Xcode.app/Contents/Developer/usr/bin/instruments -t
/Applications/Xcode.app/Contents/Applications/Instruments.app/Contents/PlugIns/AutomationInstrument.xrplugin/Contents/Resources/Automation.tracetemplate
-D /tmp/appium-instruments/instrumentscli0.trace -w 4a9b4ad142c7f308bfd3217d2fae43f9a4bc8e00 com.company.iphone.sample_App
-e UIASCRIPT "/Users/valar/Library/Application Support/appium/bootstrap/bootstrap-f2765f8569503e7c.js" -e
UIARESULTSPATH /tmp/appium-instruments info: [debug] And extra
without-delay env: {} info: [debug] And launch timeouts (in ms):
{"global":90000}
info: [debug] [INSTSERVER] Instruments exited with code 253 info:
[debug] Killall instruments
info: [debug] Instruments crashed on startup
info: [debug] Attempting to retry launching instruments, this is retry
2 info: [debug] Killall iOS Simulator info: [IOS_SYSLOG_ROW ] Aug 25 11:37:56 iPhone-6 DTMobileIS[191] : Could not create service
named com.apple.instruments.server.services.launchdaemon info:
[IOS_SYSLOG_ROW ] Aug 25 11:37:56 iPhone-6 DTMobileIS[191] :
Could not create service named
com.apple.instruments.server.services.processcontrol.posixspawn info:
[IOS_SYSLOG_ROW ] Aug 25 11:37:56 iPhone-6 notification_proxy[175]
: 0x100384000 -[MNPLockdownConnection receiveMessage]:
lockdown_receive_message error! info: [IOS_SYSLOG_ROW ] Aug 25
11:37:56 iPhone-6 notification_proxy[175] : 0x100384000
-[MNPLockdownConnection receiveMessage]: lockdown_receive_message error!
info: [IOS_SYSLOG_ROW ] Aug 25 11:37:58 iPhone-6 CLTM[20] :
CLTM: _subscription 0x0, _subscribedChannels 0x0
info: [IOS_SYSLOG_ROW ] Aug 25 11:38:01 iPhone-6 sample_App151]
: NewRelic(4.186,0x17487e440): NRTimer.m:94 -[NRTimer
timeElapsedInSeconds]
info: [IOS_SYSLOG_ROW ] NRMATimer has a negative duration:
1440482880235.167969 => 0.000000
info: Launching instruments
info: [debug] Attempting to run app on real device with UDID
4a9b4ad142c7f308bfd3217d2fae43f9a4bc8e00 info: [debug] Spawning
instruments with command:
/Applications/Xcode.app/Contents/Developer/usr/bin/instruments -t
/Applications/Xcode.app/Contents/Applications/Instruments.app/Contents/PlugIns/AutomationInstrument.xrplugin/Contents/Resources/Automation.tracetemplate
-D /tmp/appium-instruments/instrumentscli0.trace -w 4a9b4ad142c7f308bfd3217d2fae43f9a4bc8e00 com.company.iphone.
sample_App -e UIASCRIPT "/Users/valar/Library/Application
Support/appium/bootstrap/bootstrap-f2765f8569503e7c.js" -e
UIARESULTSPATH /tmp/appium-instruments info: [debug] And extra
without-delay env: {} info: [debug] And launch timeouts (in ms):
{"global":90000}
info: [debug] [INSTSERVER] Instruments exited with code 253
info: [debug] Killall instruments
info: [debug] Instruments crashed on startup info: [debug] Attempting
to retry launching instruments, this is retry #3 info: [debug] Killall
iOS Simulator info: [IOS_SYSLOG_ROW ] Aug 25 11:38:02 iPhone-6
DTMobileIS[191] : Could not create service named
com.apple.instruments.server.services.processcontrol.posixspawn info:
[IOS_SYSLOG_ROW ] Aug 25 11:38:02 iPhone-6 DTMobileIS[191] :
Could not create service named
com.apple.instruments.server.services.launchdaemon
info: [IOS_SYSLOG_ROW ] Aug 25 11:38:02 iPhone-6
notification_proxy[175] : 0x10040c000 -[MNPLockdownConnection
receiveMessage]: lockdown_receive_message error!
info: [IOS_SYSLOG_ROW ] Aug 25 11:38:02 iPhone-6
notification_proxy[175] : 0x10040c000 -[MNPLockdownConnection
receiveMessage]: lockdown_receive_message error!
info: [IOS_SYSLOG_ROW ] Aug 25 11:38:02 iPhone-6 locationd[61]
: Location icon should now be in state 'Region Monitoring'
info: [IOS_SYSLOG_ROW ] Aug 25 11:38:03 iPhone-6 CLTM[20] :
CLTM: _subscription 0x0, _subscribedChannels 0x0
info: [IOS_SYSLOG_ROW ] Aug 25 11:38:07 iPhone-6 sample_App[151]
: NewRelic(4.186,0x174675e80): NRTimer.m:94 -[NRTimer
timeElapsedInSeconds]
info: [IOS_SYSLOG_ROW ] NRMATimer has a negative duration:
1440482886151.112061 => 0.000000
info: Launching instruments
info: [debug] Attempting to run app on real device with UDID
4a9b4ad142c7f308bfd3217d2fae43f9a4bc8e00 info: [debug] Spawning
instruments with command:
/Applications/Xcode.app/Contents/Developer/usr/bin/instruments -t
/Applications/Xcode.app/Contents/Applications/Instruments.app/Contents/PlugIns/AutomationInstrument.xrplugin/Contents/Resources/Automation.tracetemplate
-D /tmp/appium-instruments/instrumentscli0.trace -w 4a9b4ad142c7f308bfd3217d2fae43f9a4bc8e00 com.company.iphone.
sample_App -e UIASCRIPT "/Users/valar/Library/Application
Support/appium/bootstrap/bootstrap-f2765f8569503e7c.js" -e
UIARESULTSPATH /tmp/appium-instruments info: [debug] And extra
without-delay env: {} info: [debug] And launch timeouts (in ms):
{"global":90000}
info: [debug] [INSTSERVER] Instruments exited with code 253
info: [debug] Killall instruments
info: [debug] Instruments crashed on startup info: [debug] We exceeded
the number of retries allowed for instruments to successfully start;
failing launch info: [debug] Stopping iOS log capture info: [debug]
Running ios sim reset flow info: [debug] Killing the simulator process
info: [debug] Killing any other simulator daemons info: [debug]
Killall iOS Simulator info: [IOS_SYSLOG_ROW ] Aug 25 11:38:07 iPhone-6
DTMobileIS[191] : Could not create service named
com.apple.instruments.server.services.launchdaemon info:
[IOS_SYSLOG_ROW ] Aug 25 11:38:07 iPhone-6 DTMobileIS[191] :
Could not create service named
com.apple.instruments.server.services.processcontrol.posixspawn info:
[debug] On a real device; cannot clean device state info: [debug]
Cleaning up appium session
error: Could not pre-launch appium: Error: Instruments crashed on
startup
Related
Environment:
Jenkins - Version 2.235.5 (LTS)
Kubernetes Jenkins Plugin - 1.27.7
K8s-Master & Worker Server Details:-
OS - CentOS Linux release 7.9.2009 (Core) & Kernal - 3.10.0-1160.6.1.el7.x86_64
Docker Version - 19.03.12
Client Version: v1.19.0
Server Version: v1.19.0
I am trying to mount a hostPathVolume through Jenkins Kubernetes-plugin podTemplate and when the pod gets kicked off via Jenkins master the path of my K8s worker not getting mounted on K8s pods(Jenkins Agent).
I have the below scripted pipeline.
podTemplate(label: 'mypod', containers: [
containerTemplate(name: 'git', image: 'ubuntu/16.04', ttyEnabled: true, command: 'cat'),
containerTemplate(name: 'maven', image: 'ubuntu/16.04', command: 'cat', ttyEnabled: true)
],
volumes: [
hostPathVolume(mountPath: '/var/run/docker.sock', hostPath: '/var/run/docker.sock'),
]
) {
node('mypod') {
stage('Check running containers') {
container('docker') {
// example to show you can run docker commands when you mount the socket
sh 'hostname'
sh 'hostname -i'
sh 'docker ps'
}
}
..... further stages....
K8s cluster Jenkins agent pod log
# kubectl logs -f jenkins_job-10-b04wk-dn4gf-llpbp -c jnlp
Dec 05, 2020 5:41:16 AM hudson.remoting.jnlp.Main createEngine
INFO: Setting up agent: jenkins_job-10-b04wk-dn4gf-llpbp
Dec 05, 2020 5:41:16 AM hudson.remoting.jnlp.Main$CuiListener <init>
INFO: Jenkins agent is running in headless mode.
Dec 05, 2020 5:41:16 AM hudson.remoting.Engine startEngine
INFO: Using Remoting version: 4.3
Dec 05, 2020 5:41:16 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
INFO: Using /home/jenkins/agent/remoting as a remoting work directory
Dec 05, 2020 5:41:16 AM org.jenkinsci.remoting.engine.WorkDirManager setupLogging
INFO: Both error and output logs will be printed to /home/jenkins/agent/remoting
Dec 05, 2020 5:41:16 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among [http://jenkins-server/jenkins/]
Dec 05, 2020 5:41:16 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]
Dec 05, 2020 5:41:16 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Agent discovery successful
Agent address: jenkins-server
Agent port: 40003
Identity: 23:66:a9:70:0b:f2:03:e0:47:44:0d:ee:7e:ce:8c:31
Dec 05, 2020 5:41:16 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Dec 05, 2020 5:41:16 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to jenkins-server:40003
Dec 05, 2020 5:41:16 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP4-connect
Dec 05, 2020 5:41:16 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Remote identity confirmed: 23:66:a9:70:0b:f2:03:e0:47:44:0d:ee:7e:ce:8c:31
Dec 05, 2020 5:41:17 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connected
Dec 05, 2020 5:41:21 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave$SlaveDisconnector call
INFO: Disabled slave engine reconnects.
Dec 05, 2020 5:41:21 AM hudson.util.ProcessTree get
WARNING: Error while determining if vetoers exist
hudson.remoting.RequestAbortedException: hudson.remoting.ChannelClosedException: Channel "unknown": Protocol stack cannot write data anymore. It is not open for write
at hudson.remoting.Request.abort(Request.java:340)
at hudson.remoting.Channel.terminate(Channel.java:1081)
at hudson.remoting.Channel.close(Channel.java:1482)
at hudson.remoting.Channel.close(Channel.java:1446)
at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1313)
at hudson.remoting.Channel$1.handle(Channel.java:606)
at hudson.remoting.AbstractByteBufferCommandTransport.processCommand(AbstractByteBufferCommandTransport.java:203)
at hudson.remoting.AbstractByteBufferCommandTransport.receive(AbstractByteBufferCommandTransport.java:189)
at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onRead(ChannelApplicationLayer.java:187)
at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecv(ApplicationLayer.java:206)
at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecv(ProtocolStack.java:668)
at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processRead(SSLEngineFilterLayer.java:369)
at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecv(SSLEngineFilterLayer.java:117)
at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecv(ProtocolStack.java:668)
at org.jenkinsci.remoting.protocol.NetworkLayer.onRead(NetworkLayer.java:136)
at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$2200(BIONetworkLayer.java:48)
at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:283)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:117)
at java.lang.Thread.run(Thread.java:748)
Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection to jenkins-server/10.20.30.35:40003
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788)
at hudson.remoting.Request.call(Request.java:202)
at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:288)
at com.sun.proxy.$Proxy5.fetch3(Unknown Source)
at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:211)
at java.lang.ClassLoader.loadClass(ClassLoader.java:419)
at java.lang.ClassLoader.loadClass(ClassLoader.java:352)
at jenkins.agents.AgentComputerUtil.getChannelToMaster(AgentComputerUtil.java:48)
at hudson.util.ProcessTree.get(ProcessTree.java:432)
at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:1100)
at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:1091)
at hudson.remoting.UserRequest.perform(UserRequest.java:211)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:369)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
... 4 more
Caused by: hudson.remoting.ChannelClosedException: Channel "unknown": Protocol stack cannot write data anymore. It is not open for write
at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer$ByteBufferCommandTransport.write(ChannelApplicationLayer.java:305)
at hudson.remoting.AbstractByteBufferCommandTransport.write(AbstractByteBufferCommandTransport.java:304)
at hudson.remoting.Channel.send(Channel.java:764)
at hudson.remoting.Channel.close(Channel.java:1479)
... 18 more
Dec 05, 2020 5:41:21 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Terminated
Dec 05, 2020 5:41:21 AM hudson.util.ProcessTree get
WARNING: Failed to load winp. Reverting to the default
java.lang.NoClassDefFoundError: hudson/util/ProcessTree$Linux$LinuxProcess
at hudson.util.ProcessTree.get(ProcessTree.java:451)
at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:1100)
at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:1091)
at hudson.remoting.UserRequest.perform(UserRequest.java:211)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:369)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:117)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.ClassNotFoundException: hudson.util.ProcessTree$Linux$LinuxProcess
at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:173)
at java.lang.ClassLoader.loadClass(ClassLoader.java:419)
at java.lang.ClassLoader.loadClass(ClassLoader.java:352)
... 12 more
Dec 05, 2020 5:41:21 AM hudson.remoting.Request$2 run
INFO: Failed to send back a reply to the request hudson.remoting.Request$2#1affe1cf: hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel#157a1c18:JNLP4-connect connection to jenkins-server/10.20.30.35:40003": channel is already closed
openjdk version "1.8.0_272" installed in (Jenkins master, K8s Master and K8s-Worker) systems, Also have restarted all three systems however still no success.
I expect the volume to be mounted in my pod, I have tried with K8s v1.19.4 and Kubernetes Jenkins Plugin - 1.27.0. Not sure what is causing the problem on CentOS-7.9. Whereas the same is working perfectly on CentOS - 8.2.2004 (Core) & 4.18.0-193.14.2.el8_2.x86_64 kernal of K8s master host's native OS.
I have upgraded my docker image from Ubuntu 16.04.6 LTS - 3.10.0-1160.6.1.el7.x86_64 to Ubuntu 16.04.7 to 3.10.0-1160.6.1.el7.x86_64 still didn't work. But it seems Kubernetes on CentOS-7.9 & with Kernal-3.10.0-1160.6.1.el7.x86_64 is having kernel specific issue. So i have upgraded my native host's OS to CentOS-8.2 with - 4.18.0-193.28.1.el8_2.x86_64 kernel, Now my pipeline build working fine.
I need to configure the [TRM240 modem][1] to work with a Raspbian system. I followed the procedure reported in the answer [here][2], but the connection isn't working.
I attach some screenshots documenting the procedure and the commands that I issued.
First, look for connected modems:
pi#raspberrypi:~ $ mmcli -L
Found 1 modems:
/org/freedesktop/ModemManager1/Modem/0 [QUALCOMM INCORPORATED] QUECTEL Mobile Broadband Module
Check the unique modem found:
pi#raspberrypi:~ $ mmcli -m 0
/org/freedesktop/ModemManager1/Modem/0 (device id 'e308f44de689f834e8cbc5b2122a4ffca8ddd3f5')
-------------------------
Hardware | manufacturer: 'QUALCOMM INCORPORATED'
| model: 'QUECTEL Mobile Broadband Module'
| revision: 'EC21ECGAR06A04M1G'
| supported: 'gsm-umts
| lte
| gsm-umts, lte'
| current: 'gsm-umts, lte'
| equipment id: '864394040056931'
-------------------------
System | device: '/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2'
| drivers: 'option1, qmi_wwan'
| plugin: 'Generic'
| primary port: 'cdc-wdm0'
| ports: 'ttyUSB0 (qcdm), ttyUSB2 (at), cdc-wdm0 (qmi), wwan0 (net), ttyUSB3 (at)'
-------------------------
Numbers | own : 'unknown'
-------------------------
Status | lock: 'unknown'
| unlock retries: 'unknown'
| state: 'failed'
| failed reason: 'sim-missing'
| power state: 'unknown'
| access tech: 'unknown'
| signal quality: '0' (cached)
-------------------------
Modes | supported: 'allowed: 2g, 3g, 4g; preferred: none'
| current: 'allowed: any; preferred: none'
-------------------------
Bands | supported: 'unknown'
| current: 'unknown'
-------------------------
IP | supported: 'ipv4, ipv6, ipv4v6'
-------------------------
SIM | path: 'none'
-------------------------
Bearers | paths: 'none'
Here, the Status section leaves me a little bit puzzled, but I try to go on.
I tried the following command using different options for ifname: cdc-wdm0, ttyUSB2 and ttyUSB3. They all end up to the same result.
pi#raspberrypi:~ $ sudo nmcli c add type gsm ifname cdc-wdm0 con-name modem apn mobile.vodafone.it
Connection 'modem' (9c34027f-5df5-4fd6-9792-223e225dfd41) successfully added.
Check the connections and try to take up modem:
pi#raspberrypi:~ $ nmcli con
NAME UUID TYPE DEVICE
br-12ff13c2c4e0 26450e11-6671-47c2-91af-6bf96405921b bridge br-12ff13c2c4e0
br-acc4bdcbe6e7 440cfcc0-5318-4a9e-9259-3fb8700cf240 bridge br-acc4bdcbe6e7
docker0 8af67071-3cb2-4235-882f-1cc1f50fa7ca bridge docker0
modem 9c34027f-5df5-4fd6-9792-223e225dfd41 gsm --
Try to take up:
pi#raspberrypi:~ $ nmcli con up modem
Error: Connection activation failed: No suitable device found for this connection.
Status of service NetworkManager:
pi#raspberrypi:~ $ systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2020-08-21 07:46:57 UTC; 2h 35min ago
Docs: man:NetworkManager(8)
Main PID: 710 (NetworkManager)
Tasks: 3 (limit: 4915)
Memory: 13.8M
CPU: 3.862s
CGroup: /system.slice/NetworkManager.service
└─710 /usr/sbin/NetworkManager --no-daemon
Aug 21 07:48:53 raspberrypi NetworkManager[710]: <info> [1597996133.0883] device (veth6ffb100): link connected
Aug 21 08:14:11 raspberrypi NetworkManager[710]: <error> [1597997651.4341] audit: failed to open auditd socket: Protocol not supported
Aug 21 08:14:11 raspberrypi NetworkManager[710]: <info> [1597997651.4343] audit: op="device-managed" arg="managed:1" pid=11841 uid=0 result="success"
Aug 21 08:16:48 raspberrypi NetworkManager[710]: <info> [1597997808.9388] audit: op="device-autoconnect" arg="autoconnect:1" pid=12910 uid=1000 result="fail" reason="Not authorized to perform this operat
Aug 21 08:17:41 raspberrypi NetworkManager[710]: <info> [1597997861.0575] audit: op="connection-add-activate" pid=13286 uid=1000 result="fail" reason="gsm: GSM mobile broadband connection requires a 'gsm
Aug 21 08:25:25 raspberrypi NetworkManager[710]: <info> [1597998325.2594] audit: op="connection-add-activate" pid=16224 uid=1000 result="fail" reason="gsm: GSM mobile broadband connection requires a 'gsm
Aug 21 10:06:31 raspberrypi NetworkManager[710]: <info> [1598004391.9223] audit: op="connection-activate" uuid="06583333-e03e-431f-9376-94c38b6b607d" name="modem" result="fail" reason="No suitable device
Aug 21 10:19:24 raspberrypi NetworkManager[710]: <info> [1598005164.3349] keyfile: add connection /etc/NetworkManager/system-connections/modem-9c34027f-5df5-4fd6-9792-223e225dfd41 (9c34027f-5df5-4fd6-979
Aug 21 10:19:24 raspberrypi NetworkManager[710]: <info> [1598005164.3386] audit: op="connection-add" uuid="9c34027f-5df5-4fd6-9792-223e225dfd41" name="modem" pid=27261 uid=0 result="success"
Aug 21 10:20:29 raspberrypi NetworkManager[710]: <info> [1598005229.6409] audit: op="connection-activate" uuid="06583333-e03e-431f-9376-94c38b6b607d" name="modem" result="fail" reason="No suitable device
lines 1-21/21 (END)
Here I see the error <error> [1597997651.4341] audit: failed to open auditd socket: Protocol not supported...
Status of service ModemManager (there are warnings, but not errors):
pi#raspberrypi:~ $ systemctl status ModemManager
● ModemManager.service - Modem Manager
Loaded: loaded (/lib/systemd/system/ModemManager.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2020-08-21 07:46:57 UTC; 2h 35min ago
Main PID: 712 (ModemManager)
Tasks: 5 (limit: 4915)
Memory: 8.7M
CPU: 4.123s
CGroup: /system.slice/ModemManager.service
├─712 /usr/sbin/ModemManager
└─884 /usr/lib/libqmi/qmi-proxy
Aug 21 07:47:19 raspberrypi ModemManager[712]: [/dev/cdc-wdm0] Registered 'nas' (version 1.25) client with ID '2'
Aug 21 07:47:20 raspberrypi ModemManager[712]: [/dev/cdc-wdm0] Allocating new client ID...
Aug 21 07:47:20 raspberrypi ModemManager[712]: [/dev/cdc-wdm0] Registered 'wms' (version 1.10) client with ID '1'
Aug 21 07:47:20 raspberrypi ModemManager[712]: [/dev/cdc-wdm0] Allocating new client ID...
Aug 21 07:47:20 raspberrypi ModemManager[712]: [/dev/cdc-wdm0] Registered 'uim' (version 1.46) client with ID '1'
Aug 21 07:47:20 raspberrypi ModemManager[712]: <warn> (ttyUSB2): port attributes not fully set
Aug 21 07:47:20 raspberrypi ModemManager[712]: <warn> couldn't load Supported Bands: 'QMI operation failed: Cannot send message: QMI service 'dms' version '1.1' required, got version '1.0''
Aug 21 07:47:20 raspberrypi ModemManager[712]: <warn> couldn't load Power State: 'QMI operation failed: Cannot send message: QMI service 'dms' version '1.1' required, got version '1.0''
Aug 21 07:47:55 raspberrypi ModemManager[712]: <warn> Modem couldn't be initialized: Couldn't check unlock status: Couldn't get SIM lock status after 6 retries
Aug 21 07:47:55 raspberrypi ModemManager[712]: <info> Modem: state changed (unknown -> failed)
System info:
pi#raspberrypi:~ $ uname -a
Linux raspberrypi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux
pi#raspberrypi:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 9.13 (stretch)
Release: 9.13
Codename: stretch
It may be that the SIM is not working properly or the modem is not recognizing it.
This is what the output
-------------------------
Status | lock: 'unknown'
| unlock retries: 'unknown'
| state: 'failed'
| failed reason: 'sim-missing'
| power state: 'unknown'
| access tech: 'unknown'
| signal quality: '0' (cached)
-------------------------
points out.
Check this answer.
(I didn't find it before posting my question.)
I am not quite sure what node is causing this behaviour and there are tooo many flows so I can not install from scratch and yes I do not have a backup of them.
I realized today in the morning that I can not access the http gui of my nodered instance any longer on my raspberrypi zero. Just edited some flows but nothing real serious.
I am trying to start my node red on my Rapsberry PI zere and no GUI and UI is starting up to access the node red instance. I don't know how to solve and troubleshoot this. What I am doing or trying to do is:
pi#nodered-pi:~/.node-red $ node-red-start
Start Node-RED
Once Node-RED has started, point a browser at http://192.168.1.42:1880
On Pi Node-RED works better with the Firefox or Chrome browser
Use node-red-stop to stop Node-RED
Use node-red-start to start Node-RED again
Use node-red-log to view the recent log output
Use sudo systemctl enable nodered.service to autostart Node-RED at every boot
Use sudo systemctl disable nodered.service to disable autostart on boot
To find more nodes and example flows - go to http://flows.nodered.org
Starting as a systemd service.
Started Node-RED graphical event wiring tool.
19 Aug 15:13:55 - [info]
Welcome to Node-RED
===================
19 Aug 15:13:55 - [info] Node-RED version: v0.18.7
19 Aug 15:13:55 - [info] Node.js version: v8.11.1
19 Aug 15:13:55 - [info] Linux 4.14.52+ arm LE
19 Aug 15:14:06 - [info] Loading palette nodes
19 Aug 15:14:37 - [info] Dashboard version 2.9.6 started at /ui
19 Aug 15:14:49 - [warn] ------------------------------------------------------
19 Aug 15:14:49 - [warn] [node-red-contrib-delta-timed/delta-time] 'delta' already registered by module node-red-contrib-change-detect
19 Aug 15:14:49 - [warn] ------------------------------------------------------
19 Aug 15:14:49 - [info] Settings file : /home/pi/.node-red/settings.js
19 Aug 15:14:49 - [info] User directory : /home/pi/.node-red
19 Aug 15:14:49 - [warn] Projects disabled : set editorTheme.projects.enabled=true to enable
19 Aug 15:14:49 - [info] Flows file : /home/pi/.node-red/flows_nodered-pi.json
19 Aug 15:14:50 - [info] Server now running at http://127.0.0.1:1880/
19 Aug 15:14:50 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
19 Aug 15:14:50 - [warn] Error loading credentials: SyntaxError: Unexpected token T in JSON at position 0
19 Aug 15:14:50 - [warn] Error loading flows: Error: Failed to decrypt credentials
19 Aug 15:14:51 - [info] Starting flows
19 Aug 15:15:01 - [warn] [telegram receiver:Telegram Receiver] bot not initialized
19 Aug 15:15:01 - [warn] [telegram sender:Temperatur Wetterstation] bot not initialized.
19 Aug 15:15:01 - [error] [function:Versorge mit Information] SyntaxError: Invalid or unexpected token
19 Aug 15:15:01 - [info] Started flows
19 Aug 15:15:02 - [info] [sonoff-server:166ef3ba.0029bc] SONOFF Server Started On Port 1080
19 Aug 15:15:02 - [red] Uncaught Exception:
19 Aug 15:15:02 - Error: listen EACCES 0.0.0.0:443
at Object._errnoException (util.js:1022:11)
at _exceptionWithHostPort (util.js:1044:20)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Unit entered failed state.
nodered.service: Failed with result 'exit-code'.
nodered.service: Service hold-off time over, scheduling restart.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.
19 Aug 15:15:20 - [info]
Welcome to Node-RED
===================
19 Aug 15:15:20 - [info] Node-RED version: v0.18.7
19 Aug 15:15:02 - Error: listen EACCES 0.0.0.0:443
at Object._errnoException (util.js:1022:11)
at _exceptionWithHostPort (util.js:1044:20)
This error implies that something else is already running on port 443. This could be an existing copy of Node-RED or something else. You can search what applications are listening on what ports with the following command
lsof -i :443
This will list what is listening on port 443
I have tried simple process variable example given at link http://community.bonitasoft.com/project/process-variable-example using BonitaBPMCommunity-7.3.1-Tomcat-7.0.67. Its working well in bonita studio. I have made .bar file of process and upload it in process tab in bonita tomcat bundle portal. But neither its fetching process variable values nor passing to next Step Step1/Step2. Process variable example is working fine with default h2 database configuration but when i configured tomcat bundle with Postgres database its not working with bonita ui forms. I have used database connection instructions given at link http://documentation.bonitasoft.com/?page=tomcat-bundle . There is no error in log file for postgres but when i run process it gives error at Step2 that
2016-11-23 08:32:49.078 +0500 INFO: org.restlet.Component.BonitaRestletApplication Error while validating expected inputs Explanations: Expected input [newVariableValue] is missing
Bonita Log file:
2016-11-23 08:20:27.182 +0500 INFO: org.bonitasoft.platform.setup.PlatformSetup System property org.bonitasoft.platform.setup.folder is set to C:\Users\User\Documents\BonitaBPMCommunity-7.3.1-Tomcat-7.0.67\setup
2016-11-23 08:20:27.226 +0500 INFO: org.bonitasoft.platform.setup.PlatformSetup Connected to 'postgres' database with url: 'jdbc:postgresql://localhost:5432/bonitaengine' with user: 'bonitaengine'
2016-11-23 08:20:27.229 +0500 INFO: org.bonitasoft.platform.setup.ScriptExecutor configuration for Database vendor: postgres
2016-11-23 08:20:27.415 +0500 INFO: org.bonitasoft.platform.setup.PlatformSetup Platform is already created. Nothing to do.
2016-11-23 08:20:27.627 +0500 INFO: org.bonitasoft.engine.EngineInitializer Initializing Bonita Engine...
2016-11-23 08:20:27.628 +0500 INFO: org.bonitasoft.engine.EngineInitializer Initializing Spring context...
2016-11-23 08:20:35.613 +0500 WARNING: org.hibernate.type.TypeFactory HHH000233: Scoping types to session factory org.hibernate.internal.SessionFactoryImpl#7423bec4 after already scoped org.hibernate.internal.SessionFactoryImpl#44308726
2016-11-23 08:20:41.867 +0500 INFO: org.bonitasoft.engine.EngineInitializer Starting platform...
2016-11-23 08:20:48.509 +0500 INFO: org.bonitasoft.engine.EngineInitializer Platform started successfully
2016-11-23 08:20:48.510 +0500 INFO: org.bonitasoft.engine.EngineInitializer Initialization of Bonita Engine done! ( took 20882ms)
2016-11-23 08:21:39.163 +0500 INFO: org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/bonita] RestletServlet: [Restlet] ServerServlet: component class is null
2016-11-23 08:21:39.533 +0500 INFO: org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/bonita] RestletServlet: [Restlet] Attaching application: org.bonitasoft.web.rest.server.BonitaRestletApplication#5efff180 to URI: /bonita/API
2016-11-23 08:21:39.557 +0500 INFO: org.restlet.Component.BonitaRestletApplication Starting org.bonitasoft.web.rest.server.BonitaRestletApplication application
2016-11-23 08:21:54.415 +0500 SEVERE: org.bonitasoft.console.common.server.login.credentials.LoginDatastore Error while logging in the engine API.
2016-11-23 08:24:47.160 +0500 INFO: org.restlet.Component.BonitaRestletApplication Error while validating expected inputs
Explanations:
Expected input [myInput] is missingExpected input [mysInput] is missingExpected input [myMultipleDocumentsContract] is missingExpected input [myMultipleDocumentsDeleteContract] is missingExpected input [brnchInput] is missingExpected input [secInput] is missing
2016-11-23 08:29:18.201 +0500 INFO: org.restlet.Component.BonitaRestletApplication Error while validating expected inputs
Explanations:
Expected input [newVariableValue] is missing
2016-11-23 08:32:49.078 +0500 INFO: org.restlet.Component.BonitaRestletApplication Error while validating expected inputs
Explanations:
Expected input [newVariableValue] is missing
catalina Server log file:
2016-11-23 08:20:16.487 +0500 INFO: org.apache.catalina.core.AprLifecycleListener The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jre1.8.0_101\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\Java\jdk1.8.0_101\bin;C:\Program Files (x86)\PuTTY\;E:\DevProgramm\maven\bin;C:\Program Files (x86)\SSH Communications Security\SSH Secure Shell;.
2016-11-23 08:20:17.317 +0500 INFO: org.apache.coyote.http11.Http11Protocol Initializing ProtocolHandler ["http-bio-8080"]
2016-11-23 08:20:17.353 +0500 INFO: org.apache.coyote.ajp.AjpProtocol Initializing ProtocolHandler ["ajp-bio-8009"]
2016-11-23 08:20:17.361 +0500 INFO: org.apache.catalina.startup.Catalina Initialization processed in 2175 ms
2016-11-23 08:20:17.362 +0500 INFO: bitronix.tm.integration.tomcat55.BTMLifecycleListener Starting Bitronix Transaction Manager
2016-11-23 08:20:17.396 +0500 INFO: bitronix.tm.BitronixTransactionManager Bitronix Transaction Manager version 2.1.3
2016-11-23 08:20:17.400 +0500 INFO: bitronix.tm.Configuration JVM unique ID:
2016-11-23 08:20:17.458 +0500 WARNING: bitronix.tm.journal.DiskJournal active log file is unclean, did you call BitronixTransactionManager.shutdown() at the end of the last run?
2016-11-23 08:20:17.464 +0500 INFO: bitronix.tm.resource.ResourceLoader reading resources configuration from C:\Users\User\Documents\BonitaBPMCommunity-7.3.1-Tomcat-7.0.67/conf/bitronix-resources.properties
2016-11-23 08:20:21.822 +0500 INFO: bitronix.tm.recovery.Recoverer recovery committed 0 dangling transaction(s) and rolled back 0 aborted transaction(s) on 2 resource(s) [jdbc/BusinessDataDSXA, jdbc/bonitaDSXA] (restricted to serverId 'bonita-tomcat-btm-node0')
2016-11-23 08:20:21.917 +0500 INFO: org.apache.catalina.core.StandardService Starting service Catalina
2016-11-23 08:20:21.918 +0500 INFO: org.apache.catalina.core.StandardEngine Starting Servlet Engine: Apache Tomcat/7.0.67
2016-11-23 08:20:21.945 +0500 INFO: org.apache.catalina.startup.HostConfig Deploying configuration descriptor C:\Users\User\Documents\BonitaBPMCommunity-7.3.1-Tomcat-7.0.67\conf\Catalina\localhost\bonita.xml
2016-11-23 08:20:48.292 +0500 INFO: org.quartz.core.SchedulerSignalerImpl Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
2016-11-23 08:20:48.293 +0500 INFO: org.quartz.core.QuartzScheduler Quartz Scheduler v.2.2.1 created.
2016-11-23 08:20:48.295 +0500 INFO: org.quartz.plugins.management.ShutdownHookPlugin Registering Quartz shutdown hook.
2016-11-23 08:20:48.300 +0500 INFO: org.quartz.core.QuartzScheduler Scheduler meta-data: Quartz Scheduler (v2.2.1) 'QuartzScheduler' with instanceId 'NON_CLUSTERED'
Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 5 threads.
Using job-store 'org.bonitasoft.engine.scheduler.impl.BonitaJobStoreCMT' - which supports persistence. and is not clustered.
2016-11-23 08:20:48.302 +0500 INFO: org.quartz.core.QuartzScheduler JobFactory set to: org.bonitasoft.engine.scheduler.impl.TransactionalSimpleJobFactory#26246754
2016-11-23 08:20:48.469 +0500 INFO: org.quartz.core.QuartzScheduler Scheduler QuartzScheduler_$_NON_CLUSTERED started.
2016-11-23 08:20:52.145 +0500 INFO: org.apache.catalina.startup.HostConfig Deployment of configuration descriptor C:\Users\User\Documents\BonitaBPMCommunity-7.3.1-Tomcat-7.0.67\conf\Catalina\localhost\bonita.xml has finished in 30,201 ms
2016-11-23 08:20:52.148 +0500 INFO: org.apache.catalina.startup.HostConfig Deploying web application directory C:\Users\User\Documents\BonitaBPMCommunity-7.3.1-Tomcat-7.0.67\webapps\manager
2016-11-23 08:20:52.324 +0500 INFO: org.apache.catalina.startup.HostConfig Deployment of web application directory C:\Users\User\Documents\BonitaBPMCommunity-7.3.1-Tomcat-7.0.67\webapps\manager has finished in 177 ms
2016-11-23 08:20:52.325 +0500 INFO: org.apache.catalina.startup.HostConfig Deploying web application directory C:\Users\User\Documents\BonitaBPMCommunity-7.3.1-Tomcat-7.0.67\webapps\ROOT
2016-11-23 08:20:52.462 +0500 INFO: org.apache.catalina.startup.HostConfig Deployment of web application directory C:\Users\User\Documents\BonitaBPMCommunity-7.3.1-Tomcat-7.0.67\webapps\ROOT has finished in 137 ms
2016-11-23 08:20:52.465 +0500 INFO: org.apache.coyote.http11.Http11Protocol Starting ProtocolHandler ["http-bio-8080"]
2016-11-23 08:20:52.500 +0500 INFO: org.apache.coyote.ajp.AjpProtocol Starting ProtocolHandler ["ajp-bio-8009"]
2016-11-23 08:20:52.503 +0500 INFO: org.apache.catalina.startup.Catalina Server startup in 35140 ms
there are 81 tables created in bonita databsase in postgres.
Actually the fact that variables is only available to administrator is a know limitation. It's documented in the REST API extension readme file under the "Known limitation" section.
You can change such behavior by customizing dynamic-permissions-checks.properties. Refer to REST API authorization documentation for more information.
I have a MeteorJS app that is not connecting to Mongo. It's been deployed using meteor deploy but for some reason it times out when trying to connect to the database :S I can still access the mongo database using meteor mongo and all of the data is present!
I am using Meteor 0.9.3.1 and here are my packages:
standard-app-packages
insecure
underscore
arunoda:npm#0.2.6
mrt:bootstrap-3
http
iron:router
mrt:q#0.9.7
mrt:moment#2.8.1
mrt:twilio-meteor
email
Here are the logs from meteor logs :
[Thu Oct 16 2014 17:39:25 GMT+0000 (UTC)] INFO Exception in setInterval callback: MongoError: connection to [production-db-a3.meteor.io:27017] timed out
at Object.Future.wait (/meteor/dev_bundles/0.3.55/lib/node_modules/fibers/future.js:326:15)
at _.extend._nextObject (packages/mongo/mongo_driver.js:858)
at _.extend.forEach (packages/mongo/mongo_driver.js:892)
at _.extend.map (packages/mongo/mongo_driver.js:902)
at _.extend.fetch (packages/mongo/mongo_driver.js:926)
at Cursor.(anonymous function) [as fetch] (packages/mongo/mongo_driver.js:741)
at Object.residentModel.getActiveResidents (app/shared/collections/residents.js:43:40)
at Object._.extend._run (app/server/services/deviceService/sensorChangeWatchdog.js:6:39)
at app/lib/watchdogFactory.js:7:12
at _.extend.withValue (packages/meteor/dynamics_nodejs.js:56)
- - - - -
at Object.toError (/meteor/containers/450809a5-5a17-5e6e-8233-85e6ad895366/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/utils.js:110:11)
at commandHandler (/meteor/containers/450809a5-5a17-5e6e-8233-85e6ad895366/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/cursor.js:679:63)
at null.<anonymous> (/meteor/containers/450809a5-5a17-5e6e-8233-85e6ad895366/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/db.js:1843:9)
at g (events.js:180:16)
at emit (events.js:98:17)
at Base.__executeAllServerSpecificErrorCallbacks (/meteor/containers/450809a5-5a17-5e6e-8233-85e6ad895366/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/connection/base.js:365:29)
at Server.<anonymous> (/meteor/containers/450809a5-5a17-5e6e-8233-85e6ad895366/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/connection/repl_set/ha.js:445:10)
at Server.g (events.js:180:16)
at Server.emit (events.js:98:17)
at null.<anonymous> (/meteor/containers/450809a5-5a17-5e6e-8233-85e6ad895366/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/connection/server.js:501:88)
[Thu Oct 16 2014 17:41:05 GMT+0000 (UTC)] INFO STATUS running -> killed
[Thu Oct 16 2014 17:41:05 GMT+0000 (UTC)] NOTICE Starting application on port 19159
[Thu Oct 16 2014 17:41:05 GMT+0000 (UTC)] INFO STATUS killed -> starting
[Thu Oct 16 2014 17:41:06 GMT+0000 (UTC)] INFO STATUS starting -> running
[Thu Oct 16 2014 17:41:07 GMT+0000 (UTC)] INFO init