I just upgraded my MapR Cluster and I am trying to start Streamsets. However I get the following Error:
Exception in thread "main" java.lang.ExceptionInInitializerError: Expected exactly 1 stage lib jar but found 0 with name streamsets-datacollector-mapr_6_0-mep4-lib Jun 12 09:48:56 BGDTEST5 streamsets[24543]: at com.streamsets.pipeline.SDCClassLoader.bringStageAndProtoLibsToFront(SDCClassLoader.java:186) Jun 12 09:48:56 BGDTEST5 streamsets[24543]: at com.streamsets.pipeline.SDCClassLoader.getOrderedURLsForClassLoader(SDCClassLoader.java:404) Jun 12 09:48:56 BGDTEST5 streamsets[24543]: at com.streamsets.pipeline.SDCClassLoader.(SDCClassLoader.java:119) Jun 12 09:48:56 BGDTEST5 streamsets[24543]: at com.streamsets.pipeline.SDCClassLoader.getStageClassLoader(SDCClassLoader.java:389) Jun 12 09:48:56 BGDTEST5 streamsets[24543]: at com.streamsets.pipeline.SDCClassLoader.getStageClassLoader(SDCClassLoader.java:383) Jun 12 09:48:56 BGDTEST5 streamsets[24543]: at com.streamsets.pipeline.BootstrapMain.main(BootstrapMain.java:291) Jun 12 09:48:56 BGDTEST5 systemd[1]: sdc.service: main process exited, code=exited, status=1/FAILURE Jun 12 09:48:56 BGDTEST5 systemd[1]: Unit sdc.service entered failed state. Jun 12 09:48:56 BGDTEST5 systemd[1]: sdc.service failed.
I can see the stage-lib in question in the streamsets-libs directory. This used to work seamlessly before. What am I doing wrong?
Related
I run a Google Compute Engine (GCE) instance with CentOS 8 on Google Cloud Platform. The problem is that this instance freezes at random times and the only way to make it work is to stop the instance and start it again. I tried to recreate an instance, this doesn't help.
Here are the screenshots from the GCE monitoring page (freeze from 21:04 Feb 9 to 09:29 Feb 10):
CPU utilization + Network bytes
RAM + Disk space utilization
Network packets
It's a 2vCPU instance with 2Gb RAM. It runs 2 docker containers (1 for Apache, 1 for FastAPI), it also runs 4 cron jobs every minute. When the machine freezes I can't ssh to it, I can't access any webpage, none of the 4 cron jobs sends any data to a logging server.
Any ideas how I can debug this issue?
Here is the /var/log/messages dump in case it's useful:
Feb 9 21:03:07 instance-prod-2 systemd[285938]: Stopped target Basic System.
Feb 9 21:03:07 instance-prod-2 systemd[285938]: Stopped target Paths.
Feb 9 21:03:07 instance-prod-2 systemd[285938]: Stopped target Timers.
Feb 9 21:03:07 instance-prod-2 systemd[285938]: grub-boot-success.timer: Succeeded.
Feb 9 21:03:07 instance-prod-2 systemd[285938]: Stopped Mark boot as successful after the user session has run 2 minutes.
Feb 9 21:03:07 instance-prod-2 systemd[285938]: Stopped target Sockets.
Feb 9 21:03:07 instance-prod-2 systemd[285938]: dbus.socket: Succeeded.
Feb 9 21:03:07 instance-prod-2 systemd[285938]: Closed D-Bus User Message Bus Socket.
Feb 9 21:03:07 instance-prod-2 systemd[285938]: Reached target Shutdown.
Feb 9 21:03:07 instance-prod-2 systemd[285938]: Starting Exit the Session...
Feb 9 21:03:07 instance-prod-2 systemd[1]: user#1000.service: Succeeded.
Feb 9 21:03:07 instance-prod-2 systemd[1]: Stopped User Manager for UID 1000.
Feb 9 21:03:07 instance-prod-2 systemd[1]: Stopping /run/user/1000 mount wrapper...
Feb 9 21:03:07 instance-prod-2 systemd[1]: Removed slice User Slice of UID 1000.
Feb 9 21:03:07 instance-prod-2 systemd[1]: run-user-1000.mount: Succeeded.
Feb 9 21:03:07 instance-prod-2 systemd[1]: user-runtime-dir#1000.service: Succeeded.
Feb 9 21:03:07 instance-prod-2 systemd[1]: Stopped /run/user/1000 mount wrapper.
Feb 9 21:03:39 instance-prod-2 collectd[1307]: write_gcm: can not take infinite value
Feb 9 21:03:39 instance-prod-2 collectd[1307]: write_gcm: wg_typed_value_create_from_value_t_inline failed for swap/percent/value! Continuing.
Feb 9 21:03:39 instance-prod-2 collectd[1307]: write_gcm: can not take infinite value
Feb 9 21:03:39 instance-prod-2 collectd[1307]: write_gcm: wg_typed_value_create_from_value_t_inline failed for swap/percent/value! Continuing.
Feb 9 21:03:39 instance-prod-2 collectd[1307]: write_gcm: can not take infinite value
Feb 9 21:03:39 instance-prod-2 collectd[1307]: write_gcm: wg_typed_value_create_from_value_t_inline failed for swap/percent/value! Continuing.
Feb 9 21:04:01 instance-prod-2 systemd[1]: Started /run/user/1000 mount wrapper.
Feb 9 21:04:01 instance-prod-2 systemd[1]: Created slice User Slice of UID 1000.
Feb 9 21:04:01 instance-prod-2 systemd[1]: Starting User Manager for UID 1000...
Feb 9 21:04:01 instance-prod-2 systemd[1]: Started Session 19719 of user user_12345.
Feb 9 21:04:01 instance-prod-2 systemd[1]: Started Session 19720 of user user_12345.
Feb 9 21:04:01 instance-prod-2 systemd[1]: Started Session 19721 of user user_12345.
Feb 9 21:04:01 instance-prod-2 systemd[1]: Started Session 19722 of user user_12345.
Feb 9 21:04:01 instance-prod-2 systemd[285996]: Started Mark boot as successful after the user session has run 2 minutes.
Feb 9 21:04:01 instance-prod-2 systemd[285996]: Reached target Paths.
Feb 9 21:04:01 instance-prod-2 systemd[285996]: Starting D-Bus User Message Bus Socket.
Feb 9 21:04:01 instance-prod-2 systemd[285996]: Reached target Timers.
Feb 9 21:04:01 instance-prod-2 systemd[285996]: Listening on D-Bus User Message Bus Socket.
Feb 9 21:04:01 instance-prod-2 systemd[285996]: Reached target Sockets.
Feb 9 21:04:01 instance-prod-2 systemd[285996]: Reached target Basic System.
Feb 9 21:04:01 instance-prod-2 systemd[285996]: Reached target Default.
Feb 9 21:04:01 instance-prod-2 systemd[285996]: Startup finished in 40ms.
Feb 9 21:04:01 instance-prod-2 systemd[1]: Started User Manager for UID 1000.
Feb 9 21:04:06 instance-prod-2 systemd[1]: session-19722.scope: Succeeded.
Feb 9 21:04:07 instance-prod-2 systemd[1]: session-19720.scope: Succeeded.
Feb 9 21:04:09 instance-prod-2 systemd[1]: session-19719.scope: Succeeded.
Feb 9 21:04:10 instance-prod-2 systemd[1]: session-19721.scope: Succeeded.
Feb 9 21:04:10 instance-prod-2 systemd[1]: Stopping User Manager for UID 1000...
Feb 9 21:04:10 instance-prod-2 systemd[285996]: Stopped target Default.
Feb 9 21:04:10 instance-prod-2 systemd[285996]: Stopped target Basic System.
Feb 9 21:04:10 instance-prod-2 systemd[285996]: Stopped target Sockets.
Feb 9 21:04:10 instance-prod-2 systemd[285996]: Stopped target Paths.
Feb 9 21:04:10 instance-prod-2 systemd[285996]: dbus.socket: Succeeded.
Feb 9 21:04:10 instance-prod-2 systemd[285996]: Closed D-Bus User Message Bus Socket.
Feb 9 21:04:10 instance-prod-2 systemd[285996]: Stopped target Timers.
Feb 9 21:04:10 instance-prod-2 systemd[285996]: grub-boot-success.timer: Succeeded.
Feb 9 21:04:10 instance-prod-2 systemd[285996]: Stopped Mark boot as successful after the user session has run 2 minutes.
Feb 9 21:04:10 instance-prod-2 systemd[285996]: Reached target Shutdown.
Feb 9 21:04:10 instance-prod-2 systemd[285996]: Starting Exit the Session...
Feb 9 21:04:11 instance-prod-2 systemd[1]: user#1000.service: Succeeded.
Feb 9 21:04:11 instance-prod-2 systemd[1]: Stopped User Manager for UID 1000.
Feb 9 21:04:11 instance-prod-2 systemd[1]: Stopping /run/user/1000 mount wrapper...
Feb 9 21:04:11 instance-prod-2 systemd[1]: Removed slice User Slice of UID 1000.
Feb 9 21:04:11 instance-prod-2 systemd[1]: run-user-1000.mount: Succeeded.
Feb 9 21:04:11 instance-prod-2 systemd[1]: user-runtime-dir#1000.service: Succeeded.
Feb 9 21:04:11 instance-prod-2 systemd[1]: Stopped /run/user/1000 mount wrapper.
####################### FROZEN #####################
Feb 10 09:29:18 instance-prod-2 kernel: Command line: BOOT_IMAGE=(hd0,gpt2)/boot/vmlinuz-4.18.0-240.10.1.el8_3.x86_64 root=UUID=0d7450f2-b70b-4208-bfe4-8>
Feb 10 09:29:18 instance-prod-2 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Feb 10 09:29:18 instance-prod-2 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Feb 10 09:29:18 instance-prod-2 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Feb 10 09:29:18 instance-prod-2 kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Feb 10 09:29:18 instance-prod-2 kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
Feb 10 09:29:18 instance-prod-2 kernel: BIOS-provided physical RAM map:
I am a newbie in IPFS. I am trying to install and run the IPFS service in my Ubuntu server and hosting on the MS Azure VM instance.
Everything went well, except for one thing when I run the IPFS as service using systemd.
Here is the error that I caught it from the log file.
Aug 17 01:56:25 UbuntuTest systemd[1]: Started IPFS daemon.
Aug 17 01:56:25 UbuntuTest systemd[1]: ipfs.service: Main process exited, code=exited, status=217/USER
Aug 17 01:56:25 UbuntuTest systemd[1]: ipfs.service: Unit entered failed state.
Aug 17 01:56:25 UbuntuTest systemd[1]: ipfs.service: Failed with result 'exit-code'.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Service hold-off time over, scheduling restart.
Aug 17 01:56:26 UbuntuTest systemd[1]: Stopped IPFS daemon.
Aug 17 01:56:26 UbuntuTest systemd[1]: Started IPFS daemon.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Main process exited, code=exited, status=217/USER
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Unit entered failed state.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Failed with result 'exit-code'.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Service hold-off time over, scheduling restart.
Aug 17 01:56:26 UbuntuTest systemd[1]: Stopped IPFS daemon.
Aug 17 01:56:26 UbuntuTest systemd[1]: Started IPFS daemon.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Main process exited, code=exited, status=217/USER
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Unit entered failed state.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Failed with result 'exit-code'.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Service hold-off time over, scheduling restart.
Aug 17 01:56:26 UbuntuTest systemd[1]: Stopped IPFS daemon.
Aug 17 01:56:26 UbuntuTest systemd[1]: Started IPFS daemon.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Main process exited, code=exited, status=217/USER
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Unit entered failed state.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Failed with result 'exit-code'.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Service hold-off time over, scheduling restart.
Aug 17 01:56:26 UbuntuTest systemd[1]: Stopped IPFS daemon.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Start request repeated too quickly.
Aug 17 01:56:26 UbuntuTest systemd[1]: Failed to start IPFS daemon
.
The log file it seems no longer generate info.
Why does that happen?
When I run with ipfs daemon and it works well without error.
Please advise.
Thank you
i am unable to start servers, the 'start servers'-icon flashes green for a second and nothing happens. This is what i get in the apache_error log:
[Mon Dec 26 03:36:16 2016] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Mon Dec 26 03:36:17 2016] [notice] Digest: generating secret for digest authentication ...
[Mon Dec 26 03:36:17 2016] [notice] Digest: done
[Mon Dec 26 03:36:18 2016] [notice] Apache/2.2.31 (Win32) DAV/2 mod_ssl/2.2.31 OpenSSL/1.0.2e mod_fcgid/2.3.9 mod_wsgi/3.4 Python/2.7.6 PHP/7.0.9 mod_perl/2.0.8 Perl/v5.16.3 configured -- resuming normal operations
[Mon Dec 26 03:36:18 2016] [notice] Server built: May 6 2016 10:19:53
[Mon Dec 26 03:36:18 2016] [crit] (22)Invalid argument: Parent: Failed to create the child process.
[Mon Dec 26 03:36:18 2016] [crit] (OS 6)Invalid reference. : master_main: create child process failed. Exiting.
I had the same problem on Windows 10 and disabling Perl worked for me:
C:\MAMP\conf\apache\httpd.conf
...
LoadModule perl_module modules/mod_perl.so
...
I hope this helps.
When i try to do base line index it is getting success but ProductCatalogOutputConfig returining zero results. I am using 11.2 version.
I have verified my switching datas and site ids for all(catalog,category,products,skus). all are being properly associated. even i able to generate the test data from ProductCatalogOutputConfig compononent in dyn/admin.
PreIndexing (Duration: 0:00:00)
/atg/commerce/endeca/index/CategoryTreeService COMPLETE (Succeeded) RepositoryExport (Duration: 0:00:11)
/atg/commerce/endeca/index/SchemaExporter *79* 0 COMPLETE (Succeeded)
/atg/commerce/endeca/index/CategoryToDimensionOutputConfig *18* 0 COMPLETE (Succeeded)
/atg/commerce/endeca/index/RepositoryTypeDimensionExporter *15* 0 COMPLETE (Succeeded)
/atg/commerce/search/ProductCatalogOutputConfig *0* 0 COMPLETE (Succeeded)
EndecaIndexing (Duration: 0:00:37)
/atg/commerce/endeca/index/EndecaScriptService COMPLETE (Succeeded)
I have enabled debug for bulk load component and noticed one error like in the below
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691248 /atg/search/repository/BulkLoader itemDescriptor: [ItemDesc: product]
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691249 /atg/search/repository/BulkLoader repositoryView: atg.adapter.gsa.GSAView#21be285c
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691250 /atg/search/repository/BulkLoader client calling take() with 0 items in item queue
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691250 /atg/search/repository/BulkLoader ProcessRanges() calling take() with 0 items in range queue
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691259 /atg/search/repository/BulkLoader Got: 4
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691259 /atg/search/repository/BulkLoader batchCount:20,000, startIndex:0, endIndex:20,000
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691266 /atg/search/repository/BulkLoader ii=0, lastItem=null, query options=range 0-20000<sortby>
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691266 /atg/search/repository/BulkLoader <sortbyvalue value="id" dir=ascending case sensitive>
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691266 /atg/search/repository/BulkLoader </sortby>
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691275 /atg/search/repository/BulkLoader ids == [], size=0
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691277 /atg/search/repository/BulkLoader createIdRanges() thread is done
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691277 /atg/search/repository/BulkLoader ProcessRanges() took range: IdRange{firstItem:null, lastItem:null, inclusive?: false, terminal?:true}
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691280 /atg/search/repository/BulkLoader Put: 4
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691280 /atg/search/repository/BulkLoader First page returned 4 items.
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691281 /atg/search/repository/BulkLoader ProcessRanges() calling take() with 1 items in range queue
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691283 /atg/search/repository/BulkLoader ProcessRanges() took range: IdRange{firstItem:null, lastItem:null, inclusive?: false, terminal?:true}
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691285 /atg/search/repository/BulkLoader processRanges() thread is done
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691288 /atg/search/repository/BulkLoader processRanges() thread is done
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691289 /atg/search/repository/BulkLoader Interrupting taker thread: Thread[Thread-90,5,Pooled Threads]
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader Interrupted fetching via ThreadedItemQueue java.lang.InterruptedException
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2014)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2048)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.repository.search.indexing.ThreadedItemQueue.take(ThreadedItemQueue.java:383)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.repository.search.indexing.BulkLoaderImpl.fetchItemsUsingThreadedQueue(BulkLoaderImpl.java:530)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.repository.search.indexing.BulkLoaderImpl.loadPagedIteration(BulkLoaderImpl.java:599)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.repository.search.indexing.BulkLoaderImpl.bulkLoad(BulkLoaderImpl.java:997)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.repository.search.indexing.IndexingOutputConfig.bulkLoad(IndexingOutputConfig.java:1771)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.repository.search.indexing.IndexingOutputConfig.bulkLoadForDiagnostics(IndexingOutputConfig.java:1715)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.endeca.index.EndecaIndexingOutputConfig.performBaselineUpdate(EndecaIndexingOutputConfig.java:1197)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.endeca.index.admin.IndexingTask.doTask(IndexingTask.java:445)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.endeca.index.admin.IndexingTask.performTask(IndexingTask.java:388)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.endeca.index.admin.IndexingPhase$IndexingTaskJob.invoke(IndexingPhase.java:501)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.common.util.ThreadDispatcherThread.run(ThreadDispatcherThread.java:178)
Please help me out from this issue.
I deployed a site successfully a few days ago and was able to configure logins and do other stuff but today it is down. The strange thing is I deploy to a different location without any changes and now I couldn't even access the page to configure stuff. I don't really know how to debug these things. Here is the logs
[Wed Sep 11 2013 15:19:16 GMT+0000 (UTC)] INFO STATUS waiting -> starting
[Wed Sep 11 2013 15:19:16 GMT+0000 (UTC)] INFO STATUS starting -> running
[Wed Sep 11 2013 15:19:17 GMT+0000 (UTC)] WARNING timers.js:103
[Wed Sep 11 2013 15:19:17 GMT+0000 (UTC)] WARNING ^
[Wed Sep 11 2013 15:19:17 GMT+0000 (UTC)] WARNING if (!process.listeners('uncaughtException').length) throw e;
[Wed Sep 11 2013 15:19:17 GMT+0000 (UTC)] WARNING Error: Could not locate any valid servers in initial seed list
at MongoClient.connect.connectFunction (/meteor/containers/6c32717b-367c-bd8f-b229-ad69088fe830/bundle/programs/server/npm/mongo-livedata/main/node_modules/mongodb/lib/mongodb/mongo_client.js:281:52)
at Db.open (/meteor/containers/6c32717b-367c-bd8f-b229-ad69088fe830/bundle/programs/server/npm/mongo-livedata/main/node_modules/mongodb/lib/mongodb/db.js:267:16)
at Server.connect.connectionPool.on.server._serverState (/meteor/containers/6c32717b-367c-bd8f-b229-ad69088fe830/bundle/programs/server/npm/mongo-livedata/main/node_modules/mongodb/lib/mongodb/connection/server.js:499:7)
at EventEmitter.emit (events.js:126:20)
at connection.on._self._poolState (/meteor/containers/6c32717b-367c-bd8f-b229-ad69088fe830/bundle/programs/server/npm/mongo-livedata/main/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:168:15)
at EventEmitter.emit (events.js:99:17)
at Socket.timeoutHandler (/meteor/containers/6c32717b-367c-bd8f-b229-ad69088fe830/bundle/programs/server/npm/mongo-livedata/main/node_modules/mongodb/lib/mongodb/connection/connection.js:463:10)
at Socket.EventEmitter.emit (events.js:93:17)
at Socket._onTimeout (net.js:188:8)
at Timer.list.ontimeout (timers.js:101:19)
[Wed Sep 11 2013 15:19:17 GMT+0000 (UTC)] ERROR Application crashed with code: 1
[Wed Sep 11 2013 15:19:17 GMT+0000 (UTC)] INFO STATUS running -> waiting
Given the timing, looks like the very brief outage from this morning. Could you check it again and let me know if everything is back to normal?