I am using Docker to run start execution in a llel environment. but getting sudden stop of the image instance
OS : linux
ram : 12gb
image information
Node : selenium/node-firefox:4.5.0-20221004
hub : selenium/hub:4.5.0-20220929
logs of the hub container
1666067900551 Marionette DEBUG 1 -> [0,32,"WebDriver:ExecuteScript",{"args":[{"element-6066-11e4-a52e-4f735466cecf":"5fee5a46-fa46-4568-95ed-c5aae2588c43"},"valu ... '?window.navigator:null,document:typeof window!='undefined'?window.document:null}, arguments);}\n).apply(null, arguments);"}]
1666067900684 Marionette DEBUG 1 <- [1,32,null,{"value":"Qcq#2022!!fjls#2#*"}]
1666067900685 webdriver::server DEBUG <- 200 OK {"value":"Qcq#2022!!fjls#2#*"}
04:43:40.532 INFO [LocalNode.lambda$new$3] - Session id 22e6f563-b71a-4f05-bd2d-1165d58993ec timed out, stopping...
1666068220557 webdriver::server DEBUG -> DELETE /session/22e6f563-b71a-4f05-bd2d-1165d58993ec
1666068220566 Marionette DEBUG 1 -> [0,33,"Marionette:Quit",{"flags":["eForceQuit"]}]
1666068220569 Marionette INFO Stopped listening on port 46179
1666068220754 Marionette TRACE Received observer notification quit-application
1666068220758 Marionette TRACE Received observer notification quit-application
1666068220760 Marionette DEBUG Marionette stopped listening
1666068220760 RemoteAgent DEBUG Resetting recommended pref apz.content_response_timeout
1666068220761 RemoteAgent DEBUG Resetting recommended pref browser.contentblocking.introCount
1666068220761 RemoteAgent DEBUG Resetting recommended pref browser.download.panel.shown
1666068220761 RemoteAgent DEBUG Resetting recommended pref browser.newtabpage.enabled
1666068220817 RemoteAgent DEBUG Resetting recommended pref browser.pagethumbnails.capturing_disabled
1666068220818 RemoteAgent DEBUG Resetting recommended pref browser.search.update
1666068220820 RemoteAgent DEBUG Resetting recommended pref browser.startup.couldRestoreSession.count
1666068220821 RemoteAgent DEBUG Resetting recommended pref browser.tabs.closeWindowWithLastTab
1666068220822 RemoteAgent DEBUG Resetting recommended pref browser.tabs.disableBackgroundZombification
1666068220822 RemoteAgent DEBUG Resetting recommended pref browser.tabs.unloadOnLowMemory
1666068220822 RemoteAgent DEBUG Resetting recommended pref browser.tabs.warnOnClose
1666068220822 RemoteAgent DEBUG Resetting recommended pref browser.tabs.warnOnCloseOtherTabs
1666068220824 RemoteAgent DEBUG Resetting recommended pref browser.tabs.warnOnOpen
1666068220825 RemoteAgent DEBUG Resetting recommended pref browser.toolbars.bookmarks.visibility
1666068220826 RemoteAgent DEBUG Resetting recommended pref browser.usedOnWindows10.introURL
1666068220826 RemoteAgent DEBUG Resetting recommended pref browser.urlbar.merino.endpointURL
1666068220833 RemoteAgent DEBUG Resetting recommended pref browser.urlbar.suggest.searches
1666068220835 RemoteAgent DEBUG Resetting recommended pref datareporting.policy.dataSubmissionPolicyAccepted
1666068220835 RemoteAgent DEBUG Resetting recommended pref dom.disable_open_during_load
1666068220836 RemoteAgent DEBUG Resetting recommended pref dom.file.createInChild
1666068220836 RemoteAgent DEBUG Resetting recommended pref dom.max_chrome_script_run_time
1666068220836 RemoteAgent DEBUG Resetting recommended pref dom.max_script_run_time
1666068220841 RemoteAgent DEBUG Resetting recommended pref dom.push.connection.enabled
1666068220843 RemoteAgent DEBUG Resetting recommended pref extensions.getAddons.cache.enabled
1666068220843 RemoteAgent DEBUG Resetting recommended pref extensions.getAddons.discovery.api_url
1666068220844 RemoteAgent DEBUG Resetting recommended pref network.http.phishy-userpass-length
1666068220844 RemoteAgent DEBUG Resetting recommended pref network.http.prompt-temp-redirect
1666068220845 RemoteAgent DEBUG Resetting recommended pref privacy.trackingprotection.enabled
1666068220845 RemoteAgent DEBUG Resetting recommended pref security.fileuri.strict_origin_policy
1666068220846 RemoteAgent DEBUG Resetting recommended pref security.notification_enable_delay
1666068220846 RemoteAgent DEBUG Resetting recommended pref signon.autofillForms
1666068220852 RemoteAgent DEBUG Resetting recommended pref signon.rememberSignons
1666068220854 RemoteAgent DEBUG Resetting recommended pref browser.topsites.contile.enabled
1666068220854 RemoteAgent DEBUG Resetting recommended pref dom.disable_beforeunload
1666068220855 RemoteAgent DEBUG Resetting recommended pref browser.contentblocking.features.standard
1666068220856 RemoteAgent DEBUG Resetting recommended pref network.cookie.cookieBehavior
1666068220856 RemoteAgent TRACE Received observer notification quit-application
1666068220868 Marionette DEBUG 1 <- [1,33,null,{"cause":"shutdown","forced":false}]
1666068220958 RemoteAgent DEBUG Resetting recommended pref browser.contentblocking.features.standard
1666068220958 RemoteAgent DEBUG Resetting recommended pref network.cookie.cookieBehavior
1666068220958 webdriver::server DEBUG Teardown session
1666068220977 Marionette DEBUG Closed connection 1
1666068221362 geckodriver::browser DEBUG Browser process stopped: exit status: 0
1666068221391 webdriver::server DEBUG <- 200 OK {"value":null}
04:43:41.455 INFO [SessionSlot.stop] - Stopping session 22e6f563-b71a-4f05-bd2d-1165d58993ec
Related
I am using reactor kafka 1.3.11 receiveAutoAck() with DEBUG log enabled. I saw CommittableBatch No uncomitted offset,partition revoked?. log. I am trying to understand why it happened? Would those offsets get retried or override by the next success offset update?
log details:
Fetch from topic partition: INFO o.a.k.c.c.i.ConsumerCoordinator - thread=XXXX-1 [Consumer clientId=consumer-1, groupId=group-1] Setting offset for partition testtopic-4 to the committed offset FetchPosition{offset=115856...
DEBUG r.k.r.internals.CommittableBatch - thread=boundedElastic-2 No uncomitted offset for testtopic-4#115856, partition revoked?
Async committing success: DEBUG r.k.r.internals.ConsumerEventLoop - thread=XXXX-1 Async committing: { testtopic-4=OffsetAndMetadata{offset=115863...
I have an App Engine service I deploy a custom runtime in a flexible environment. Deployments functioned normally on 11/20. On 11/21 gcloud app deploy stopped using the Dockerfile and began treating it as a non-custom runtime. Neither the app.yaml nor the Dockerfile have changed.
Below is a sample log from 11/20 and 11/21 respectively. You will note Using Dockerfile found in... of the first log is not present in the second log.
First log, 11/20:
2020-11-20 11:12:02,202 DEBUG root Loaded Command Group: ['gcloud', 'app']
2020-11-20 11:12:02,547 DEBUG root Loaded Command Group: ['gcloud', 'app', 'deploy']
2020-11-20 11:12:02,551 DEBUG root Running [gcloud.app.deploy] with arguments: [--project: "distributed-computing-qa", --version: "9-2-0rc9"]
2020-11-20 11:12:02,621 INFO oauth2client.client Refreshing access_token
2020-11-20 11:12:03,043 DEBUG root Loading runtimes experiment config from [gs://runtime-builders/experiments.yaml]
2020-11-20 11:12:03,076 INFO root Reading [<googlecloudsdk.api_lib.storage.storage_util.ObjectReference object at 0x0000021920ECA548>]
2020-11-20 11:12:03,526 DEBUG root API endpoint: [https://appengine.googleapis.com/], API version: [v1]
2020-11-20 11:12:04,419 INFO ___FILE_ONLY___ Services to deploy:
2020-11-20 11:12:04,420 INFO ___FILE_ONLY___ descriptor: [C:\Users\Benjamin Filkins\Documents\Projects\Deployment\QA\dci\app.yaml]
source: [C:\Users\Benjamin Filkins\Documents\Projects\Deployment\QA\dci]
target project: [distributed-computing-qa]
target service: [default]
target version: [9-2-0rc9]
target url: [https://distributed-computing-qa.uc.r.appspot.com]
2020-11-20 11:12:05,272 DEBUG root No bucket specified, retrieving default bucket.
2020-11-20 11:12:05,274 DEBUG root Using bucket [gs://staging.distributed-computing-qa.appspot.com].
2020-11-20 11:12:05,941 DEBUG root Service [appengineflex.googleapis.com] is already enabled for project [distributed-computing-qa]
2020-11-20 11:12:06,109 INFO ___FILE_ONLY___ Beginning deployment of service [default]...
2020-11-20 11:12:06,123 INFO root Ignoring directory [node_modules]: Directory matches ignore regex.
2020-11-20 11:12:09,085 INFO root Ignoring directory [server\node_modules]: Directory matches ignore regex.
2020-11-20 11:12:09,679 INFO root Using Dockerfile found in C:\Users\Benjamin Filkins\Documents\Projects\Deployment\QA\dci
2020-11-20 11:12:09,679 INFO ___FILE_ONLY___ Building and pushing image for service [default]
2020-11-20 11:12:10,305 DEBUG root Could not call git with args ('config', '--get-regexp', 'remote\\.(.*)\\.url'): Command '['git', 'config', '--get-regexp', 'remote\\.(.*)\\.url']' returned non-zero exit status 1.
2020-11-20 11:12:10,305 INFO root Could not generate [source-context.json]: Could not list remote URLs from source directory: C:\Users\Benjamin Filkins\Documents\Projects\Deployment\QA\dci
2020-11-20 11:12:37,592 INFO root Uploading [C:\Users\BENJAM~1\AppData\Local\Temp\tmpwbdhi28f\src.tgz] to [staging.distributed-computing-qa.appspot.com/us.gcr.io/distributed-computing-qa/appengine/default.9-2-0rc9:latest]
2020-11-20 11:13:03,413 DEBUG root Using builder image: [gcr.io/cloud-builders/docker]
Second log, 11/21:
2020-11-21 05:10:39,041 DEBUG root Loaded Command Group: ['gcloud', 'app']
2020-11-21 05:10:39,177 DEBUG root Loaded Command Group: ['gcloud', 'app', 'deploy']
2020-11-21 05:10:39,181 DEBUG root Running [gcloud.app.deploy] with arguments: [--project: "distributed-computing-qa", --version: "9-2-0rc10"]
2020-11-21 05:10:39,203 DEBUG root Loading runtimes experiment config from [gs://runtime-builders/experiments.yaml]
2020-11-21 05:10:39,231 INFO root Reading [<googlecloudsdk.api_lib.storage.storage_util.ObjectReference object at 0x000001E60B3ED208>]
2020-11-21 05:10:39,522 DEBUG root API endpoint: [https://appengine.googleapis.com/], API version: [v1]
2020-11-21 05:10:40,196 INFO ___FILE_ONLY___ Services to deploy:
2020-11-21 05:10:40,198 INFO ___FILE_ONLY___ descriptor: [C:\Users\Benjamin
Filkins\Documents\Projects\Deployment\QA\dci\app.yaml]
source: [C:\Users\Benjamin Filkins\Documents\Projects\Deployment\QA\dci]
target project: [distributed-computing-qa]
target service: [default]
target version: [9-2-0rc10]
target url: [https://distributed-computing-qa.uc.r.appspot.com]
2020-11-21 05:10:44,749 DEBUG root No bucket specified, retrieving default bucket.
2020-11-21 05:10:44,758 DEBUG root Using bucket [gs://staging.distributed-computing-qa.appspot.com].
2020-11-21 05:10:45,460 DEBUG root Service [appengineflex.googleapis.com] is already enabled for project [distributed-computing-qa]
2020-11-21 05:10:45,645 INFO ___FILE_ONLY___ Beginning deployment of service [default]...
2020-11-21 05:10:45,658 INFO root Ignoring directory [node_modules]: Directory matches ignore regex.
2020-11-21 05:10:48,255 INFO root Ignoring directory [server\node_modules]: Directory matches ignore regex.
2020-11-21 05:10:57,261 DEBUG root Could not call git with args ('config', '--get-regexp', 'remote\\.(.*)\\.url'): Command '['git', 'config', '--get-regexp', 'remote\\.(.*)\\.url']' returned non-zero exit status 1.
2020-11-21 05:10:57,261 INFO root Could not find any remote repositories associated with [C:\Users\Benjamin Filkins\Documents\Projects\Deployment\QA\dci]. Cloud diagnostic tools may not be able to display the correct source code for this deployment.
2020-11-21 05:11:19,099 DEBUG root Skipping upload of [.env]
2020-11-21 05:11:19,099 INFO root Incremental upload skipped 100.0% of data
There are four separate projects this is now occurring on. A co-worker can also confirm the same behavior. What I have tried and can confirm:
Updated Google Cloud SDK to latest version (319.0.0)
Confirmed Cloud Build API is active
Confirmed the Cloud Build service account has the App Engine Admin, Cloud Build Service Account and Service Account User roles
App.yaml and Dockerfile present in root and unchanged between attempts
App.yaml contains runtime: custom and env: flex
What I cannot confirm with certainty or prove did not have an impact:
Changes in OS (Windows 10), though no update had occurred during this time period
Changes in my GCP service account roles/permissions, though given the spread across four distinct projects and impacting multiple users seems incredibly unlikely
Any additional insight into this issue or additional items I may have missed would be greatly appreciated.
I have solved the issue by downgrading to SDK version 271.0.0. My machine has both Python 2.7 and 3 and I noted 274 and above began support for using Python 3.
Upgrading to 274 or above results in the reported issue. 273 and below (I only went as far as 267) does not have the reported issues. While I am currently unable to provide concrete evidence, my suspicion would be down to the SDK's ability to determine which version of Python to prefer. As noted here support of Python 2 was deprecated on 09/30/2020.
Modern API for Logging is easy configurable in Terminal. However, Xcode seems to output all levels including INFO and DEBUG which is very annoying. Because most of the time you want to see only os_log_error and NSLog aka “something went wrong” and “this is important”.
So is there any way to display only particular levels in Xcode Console?
os_log_info(OS_LOG_DEFAULT, "Info");
os_log_debug(OS_LOG_DEFAULT, "Debug");
os_log_error(OS_LOG_DEFAULT, "Error");
os_log_fault(OS_LOG_DEFAULT, "Fault");
os_log(OS_LOG_DEFAULT, "Default");
NSLog(#"NSLog");
Current output:
2016-12-14 15:37:00.170807 Test[5681:2205834] Info
2016-12-14 15:37:00.170830 Test[5681:2205834] Debug
2016-12-14 15:37:00.170835 Test[5681:2205834] Error
2016-12-14 15:37:00.170839 Test[5681:2205834] Fault
2016-12-14 15:37:00.170860 Test[5681:2205834] Default
2016-12-14 15:37:00.170869 Test[5681:2205834] NSLog
Preferred output:
2016-12-14 15:37:00.170835 Test[5681:2205834] Error
2016-12-14 15:37:00.170839 Test[5681:2205834] Fault
2016-12-14 15:37:00.170860 Test[5681:2205834] Default
2016-12-14 15:37:00.170869 Test[5681:2205834] NSLog
I have used DTS and got the answer from an Apple engineer:
The new unified logging system is a relatively recent addition and, alas, Xcode has not yet caught up with it. If you'd like to see a future version of Xcode support log filtering, I encourage you to file an enhancement request describing your requirements.
So please duplicate rdar://28288063, the more requests the better. Thanks!
Update: As noted by Max below, you can modify visibility for custom logs:
os_log_t custom = os_log_create("com.acme.demo", "custom");
os_log_info(custom, "Info");
os_log_debug(custom, "Debug");
os_log_error(custom, "Error");
os_log_fault(custom, "Fault");
os_log(custom, "Default");
The following Terminal command will suppress “Info” and “Debug” strings in Xcode:
sudo log config --mode "level:default" --subsystem "com.acme.demo"
To reset system defaults:
sudo log config -reset --subsystem "com.acme.demo"
To check current status:
sudo log config --subsystem "com.acme.demo"
You can switch debug-level in terminal:
$ sudo log config --mode "level:debug" --subsystem com.your_company.your_subsystem_name
To check your current level:
$ sudo log config --status --subsystem com.your_company.your_subsystem_name
Mode for 'com.your_company.your_subsystem_name' DEBUG
For more information see Apple Documentation
I have managed to get the desired effect by setting the OS_ACTIVITY_MODE to default in the environment variables section of the scheme.
EDIT:
I see that this omits only the Debug log level. Info is still shown.
I set up a clean install of Yosemite and can't get guard to detect whenever a file is changed.
My Environment:
guard (2.6.1)
guard-minitest (2.2.0)
rubygems-bundler (1.4.4)
Ruby 1.9.3 and 2.0.0 both have been testing
Here is the output from debugging:
tom#Toms-MBP:~/Sites/tick (master)$ LISTEN_GEM_DEBUGGING=2 bundle exec guard -d
I, [2014-10-27T15:34:53.417196 #1059] INFO -- : Celluloid loglevel set to: 0
15:34:53 - DEBUG - Command execution: emacsclient --eval '1' 2> /dev/null || echo 'N/A'
15:34:53 - INFO - Guard is using TerminalTitle to send notifications.
15:34:53 - DEBUG - Command execution: hash stty
15:34:53 - DEBUG - Guard starts all plugins
15:34:53 - DEBUG - Hook :start_begin executed for Guard::Minitest
15:34:53 - INFO - Guard::Minitest 2.3.2 is running, with Minitest::Unit 4.7.5!
15:34:53 - DEBUG - Hook :start_end executed for Guard::Minitest
15:34:53 - INFO - Guard is now watching at '/Users/tom/Dropbox/Sites/tick'
15:34:53 - DEBUG - Command execution: sysctl -n hw.ncpu
D, [2014-10-27T15:34:53.517668 #1059] DEBUG -- : Adapter: considering TCP ...
D, [2014-10-27T15:34:53.517749 #1059] DEBUG -- : Adapter: considering polling ...
D, [2014-10-27T15:34:53.517776 #1059] DEBUG -- : Adapter: considering optimized backend...
I, [2014-10-27T15:34:53.587089 #1059] INFO -- : Record.build(): 0.06837701797485352 seconds
15:34:53 - DEBUG - Command execution: stty -g 2>/dev/null
15:34:53 - DEBUG - Start interactor
[1] guard(main)>
I am not sure how to test the underlying listen gem, but seems like it has to be related. I have confirmed that guard works correctly with polling (bundle exec guard start --force-polling).
I was able to resolve my issue by moving the files out of Dropbox. Once I saw this working, I knew that Dropbox was somehow causing the issue with the file system. I resolved it by removing the folder and re-adding it through Dropbox and now everything is working as before.
I had the same problem, and only thanks to a warning issued by the LiveReload application I fixed it.
Because the problem is not restrained to Dropbox and/or ruby on rails, I wanted to share what I did:
Rename problematic folder (in my case containing the Guardfile)
Create new folder with the old folders name
Move files from old to new folder
Other solutions mentioned by LiveReload are:
rebooting the computer
checking the disk and repairing permissions via Disk Utility
adding the folder to Spotlight privacy list (the list of folders to not index), and then removing from it, effectively forcing a
reindexing
renaming the folder, and then possibly renaming it back
re-creating the folder and moving the old contents back into it
Read more: http://feedback.livereload.com/knowledgebase/articles/86239
This not only fixed my Guard problem, but also allowed Compass watch to run again.
Did you add rb-fsevent gem ?
group :development, :test do
gem 'rb-fsevent' if `uname` =~ /Darwin/
end
if you're using OS X, it will be used OS X FSEvents API.
When i start yaws (yaws -i --conf config/yaws.conf) i get this line in the output:
Running with debug checks turned on (slower server)
It depends on the "-i" option? Or where did i turned on debug checks? No mention of debug in the config file...
thx
edoardo
In recent versions of yaws (1.85 and later) you can simply pass the --nodebug option on the command line:
yaws -i --nodebug
This will be because your flags setting in the global config has the debug bit (2) set. If GC_DEBUG is set in the global configuration this feature will be enabled.
These are the flags:
-define(GC_TTY_TRACE, 1).
-define(GC_DEBUG, 2).
-define(GC_AUTH_LOG, 4).
-define(GC_COPY_ERRLOG, 8).
-define(GC_BACKWARDS_COMPAT_PARSE, 16).
-define(GC_LOG_RESOLVE_HOSTNAME, 32).
-define(GC_FAIL_ON_BIND_ERR, 64).
-define(GC_PICK_FIRST_VIRTHOST_ON_NOMATCH, 128).
-define(GC_USE_FDSRV, 256).
-define(GC_USE_OLD_SSL, 512).
I think that in the yaws.config file this is actually un-set by setting the debug = false flag in the global part.
Updated - the debug parameter is part of the env settings of the app in the yaws.app file, so adding something like
-yaws debug false
to the real command line should work
After using command: "sudo yaws -i --nodebug", my website become a bit faster.