I am new to Android bringup, Kernel boot seems successful and we arrive at console prompt but beyond that, logcat does not reveal what might be holding back Android-13 boot.
In terms of Software, we have a setup to build Android-12 succesfully for our specific lunch menu & device spec (arm64 based). For Android-13 we have used the same setup and pointed to the following source branches.
ANDROID_BRANCH=android-13.0.0_r18
KERNEL_BRANCH=common-android13-5.10-2022-12
Console trace ends up in a OnBootPhase_XXX loop continually incrementing with similar output repeating. Nothing obvious seem to stand out in the trace such as Fatal errors
01-17 12:43:14.120 2587 2587 I SystemServiceManager: Starting phase 500
01-17 12:43:14.122 2587 2587 D SystemServerTiming: OnBootPhase_500
01-17 12:43:14.124 2587 2587 D SystemServerTiming: OnBootPhase_500_com.android.server.security.FileIntegrityService
01-17 12:43:14.125 2587 2587 V SystemServerTiming: OnBootPhase_500_com.android.server.security.FileIntegrityService took to complete: 0ms
01-17 12:43:14.127 2587 2587 D SystemServerTiming: OnBootPhase_500_com.android.server.pm.Installer
01-17 12:43:14.129 2587 2587 V SystemServerTiming: OnBootPhase_500_com.android.server.pm.Installer took to complete: 0ms
01-17 12:43:14.130 2587 2587 D SystemServerTiming: OnBootPhase_500_com.android.server.os.DeviceIdentifiersPolicyService
01-17 12:43:14.132 2587 2587 V SystemServerTiming: OnBootPhase_500_com.android.server.os.DeviceIdentifiersPolicyService took to complete: 0ms
01-17 12:43:14.134 2587 2587 D SystemServerTiming: OnBootPhase_500_com.android.server.uri.UriGrantsManagerService$Lifecycle
01-17 12:43:14.161 2587 2587 V SystemServerTiming: OnBootPhase_500_com.android.server.uri.UriGrantsManagerService$Lifecycle took to complete: 26ms
01-17 12:43:14.163 2587 2587 D SystemServerTiming: OnBootPhase_500_com.android.server.powerstats.PowerStatsService
01-17 12:43:14.172 2587 2587 E StatsPullAtomCallbackImpl: Failed to start PowerStatsService statsd pullers
Eventually the following line in trace gives a hint that it has given up.
01-17 12:44:30.645 2160 2791 I keystore2: keystore2::watchdog: Watchdog thread idle -> terminating. Have a great day.
What is the usual process to debug Android Init-Loop using Console/Logcat trace output ?
Since we can rebuild the Software Stack, what is the best place in code to add trace to narrow down problem ?
Could we be missing a bugfix or patch when we fetch sources directly from android source branches android-13.0.0_r18 & kernel branch common-android13-5.10-2022-12 ?
Could there be a fundamental difference between Android-12 and Android-13 which might require update to device spec ?
I have compared device spec of google/cuttlefish between 12 & 13 but did not spot anything.
Any comments/suggestions much appreciated
Related
I am new to API Connect, and I have installed npm, node and apic in my local MacBook. Now I have created a loopback directory and trying to run the loopback application using apic Start. However, I am not understanding the error received from the logs:
MacBook-Pro-2:socialreviews Work$ apic start
Error: Service socialreviews started but did not initialize within the timeout period. Dumping log buffer.
[Tue Apr 30 12:02:42 2019] com.ibm.diagnostics.healthcenter.loader INFO: Node Application Metrics 3.1.3.201810251210 (Agent Core 3.2.6)
[Tue Apr 30 12:02:42 2019] com.ibm.diagnostics.healthcenter.mqtt INFO: Connecting to broker localhost:1883
strong-supervisor attaching dashboard at /appmetrics-dash
2019-04-30T09:02:42.694Z pid:44844 worker:0 INFO supervisor starting (pid 44844)
2019-04-30T09:02:42.697Z pid:44844 worker:0 INFO supervisor reporting metrics to internal:
2019-04-30T09:02:42.709Z pid:44844 worker:0 INFO supervisor size set to undefined
2019-04-30T09:02:42.905Z pid:44848 worker:1 [Tue Apr 30 12:02:42 2019] com.ibm.diagnostics.healthcenter.loader INFO: Node Application Metrics 3.1.3.201810251210 (Agent Core 3.2.6)
2019-04-30T09:02:42.959Z pid:44848 worker:1 [Tue Apr 30 12:02:42 2019] com.ibm.diagnostics.healthcenter.mqtt INFO: Connecting to broker localhost:1883
2019-04-30T09:02:42.995Z pid:44848 worker:1 strong-supervisor attaching dashboard at /appmetrics-dash
2019-04-30T09:02:45.017Z pid:44848 worker:1 Web server listening at: http://0.0.0.0:4004
2019-04-30T09:24:29.148Z pid:44844 worker:0 WARN received SIGTERM, shutting down
2019-04-30T09:24:29.148Z pid:44844 worker:0 INFO supervisor size set to undefined
2019-04-30T09:24:29.148Z pid:44844 worker:0 INFO supervisor stopped
Can someone help me with this issue please?
This issue is solved, however I am not 100% sure what was the exact issue. What I have done is ran apic edit command then when clicking on start it suddenly asked me to install docker. I have done so, then I started to have readable errors of some packages not installed. So I used npm commands to install them and my issue is fixed now! :)
I am using Ansible to install logging (EFK) in OpenShift 3.7 with below parameters,
openshift_logging_install_logging=true
openshift_logging_kibana_hostname=kibana.example.com
openshift_logging_es_cluster_size=3
openshift_logging_es_number_of_shards=3
openshift_logging_es_number_of_replicas=1
openshift_logging_es_nodeselector={"region":"infra"}
openshift_logging_kibana_nodeselector={"region":"infra"}
openshift_logging_curator_nodeselector={"region":"infra"}
But it fails with message, I am not sure why , I tried with openshift_logging_es_cluster_size=1 , it works fine that way. But I want cluster size to be 3. Can anyone help me on this-
2018-01-30 18:08:27,734 p=30740 u=root | FAILED - RETRYING: Waiting for logging-es-data-master-8bm7g3s4 to finish scaling up (60 retries left).
2018-01-30 18:08:59,582 p=30740 u=root | FAILED - RETRYING: Waiting for logging-es-data-master-8bm7g3s4 to finish scaling up (59 retries left).
2018-01-30 18:09:30,763 p=30740 u=root | FAILED - RETRYING: Waiting for logging-es-data-master-8bm7g3s4 to finish scaling up (58 retries left).
2018-01-30 18:10:02,003 p=30740 u=root | FAILED - RETRYING: Waiting for logging-es-data-master-8bm7g3s4 to finish scaling up (57 retries left).
2018-01-30 18:10:33,239 p=30740 u=root | FAILED - RETRYING: Waiting for logging-es-data-master-8bm7g3s4 to finish scaling up (56 retries left).
2018-01-30 18:11:04,456 p=30740 u=root | FAILED - RETRYING: Waiting for logging-es-data-master-8bm7g3s4 to finish scaling up (55 retries left)
You can use commandline to describe your logging-es-data-master-* pod,you may find that other two nodes are lacking in cpu or memory in events.
Because the logging-es-data-master-* pod needs 8G memory by default.
There may be other reasons.
I've got a gulpfile set up with both a series of tasks to bundle an Angular2 app using systemjs as well as with webpack. Unfortunately, I'm seeing that if I run one of them in my Powershell prompt (e.g. "gulp webpack" or "gulp systemjs" without the quotes), it will actually run through more of the tasks than specified in my desired task.
I won't list all the tasks I've got within this for brevity, but they all follow the standard approach, as in the following sample:
gulp.task("angular",
() => {
var angularDirs = "./Scripts/MyApp/src/**/*.{html,css}";
return gulp.src(angularDirs)
.pipe(copy(config.wwwroot, { prefix: 1 }))
.pipe(gulp.dest(config.wwwroot));
});
For example, here's what I've got for my webpack task:
gulp.task("webpack", runSequence(["cleanRoot", "cleanBuild"],
["ts:webpack", "restore", "less", "angular", "webpackHtml", "javascript:webpack"]));
...and here's what I've got in the systemjs task:
gulp.task("systemjs", runSequence(["cleanRoot", "cleanBuild"], "embedTemplates",
"ts:systemjs", ["less", "restore", "angular"], "cleanWrongIndex"));
So, there's some overlap in there, but that's intended. However, if I run "gulp systemjs", I would expect that it'll only actually run "cleanRoot" and "cleanBuild" together, then "embedTemplates", then "ts:systemjs", the "less", "restore" and "angular" tasks and finally "cleanWrongIndex" and none of the other tasks in the file. However...
PS C:\Code\MyApp> gulp systemjs
[22:56:59] Using gulpfile
[22:56:59] Starting 'systemjs'...
[22:56:59] Finished 'systemjs' after 128 μs
[22:57:00] Finished 'cleanBuild' after 1.12 s
[22:57:01] Starting 'embedTemplates'...
**[22:57:01] Starting 'ts:webpack'...**
[22:57:01] Starting 'restore'...
[22:57:01] Starting 'less'...
[22:57:01] Starting 'angular'...
**[22:57:01] Starting 'webpackHtml'...**
**[22:57:01] Finished 'webpackHtml' after 705 μs**
**[22:57:01] Starting 'javascript:webpack'...**
**[22:57:01] Finished 'javascript:webpack' after 1.5 ms**
[22:57:01] Finished 'cleanRoot' after 1.9 s
[22:57:01] Finished 'restore' after 68 ms
[22:57:06] Finished 'less' after 5.65 s
[22:57:07] Finished 'angular' after 6.26 s
**[22:57:13] Finished 'ts:webpack' after 12 s**
**[22:57:14] Starting 'ts:systemjs'...**
[22:57:14] Finished 'embedTemplates' after 13 s
[22:57:20] Starting 'less'....
[22:57:20] Starting 'restore'...
[22:57:20] Starting 'angular'...
**[22:57:20] Finished 'ts:systemjs' after 5.64 s**
[22:57:20] Finished 'restore' after 161 ms
[22:57:23] Finished 'less' after 3.32 s
[22:57:23] Finished 'angular' after 3.79 s
[22:57:38] Starting 'restore'...
[22:57:38] Starting 'cleanWrongIndex'...
[22:57:38] Finished 'restore' after 25 μs
[22:57:38] Finished 'cleanWrongIndex' after 4.97 ms
PS C:\Code\MyApp>
I differentiated the tasks in the above that shouldn't be there since they're in the webpack task and not specified in this one.
Why are tasks showing up that I didn't specify? Is there any way to force gulp to only run the tasks I specify?
Thanks!
I'm trying web-starter-kit. I followed installation instructions and I receive a error log that interpretation I'm not really sure about. I'm still in the getting started phase, I get the error running gulp in the web-starter-kit/app folder. I'm totally inexperienced with this technology and I'm working with the default resources included in the starting folder. I couldn't find anything useful on the internet. This is the error log:
[13:26:16] Working directory changed to ~/Desktop/web-starter-kit
[13:26:17] Using gulpfile ~/Desktop/web-starter-kit/gulpfile.js
[13:26:17] Starting 'clean'...
[13:26:17] Finished 'clean' after 4.43 ms
[13:26:17] Starting 'default'...
[13:26:17] Starting 'styles:components'...
[13:26:17] Starting 'styles:scss'...
[13:26:17] Starting 'styles:css'...
[13:26:17] gulp-size: 'styles:css' total 0 B
[13:26:17] Finished 'styles:css' after 94 ms
[13:26:17] gulp-size: 'styles:scss' total 0 B
[13:26:17] Finished 'styles:scss' after 110 ms
[13:26:17] [gulp-ruby-sass]
Syntax error: Mixin "medium" does not accept a content block.
on line 160 of /home/riccardo/Desktop/web-starter-kit/app/styles/components/_utils.scss, in `medium'
from line 160 of /home/riccardo/Desktop/web-starter-kit/app/styles/components/_utils.scss, in `container'
from line 32 of /home/riccardo/Desktop/web-starter-kit/app/styles/components/_global.scss
from line 10 of /home/riccardo/Desktop/web-starter-kit/app/styles/components/components.scss
events.js:72
throw er; // Unhandled 'error' event
^
Error in plugin 'gulp-ruby-sass'
Syntax error: Mixin "medium" does not accept a content block.
on line 160 of /home/riccardo/Desktop/web-starter-kit/app/styles/components/_utils.scss, in `medium'
from line 160 of /home/riccardo/Desktop/web-starter-kit/app/styles/components/_utils.scss, in `container'
from line 32 of /home/riccardo/Desktop/web-starter-kit/app/styles/components/_global.scss
from line 10 of /home/riccardo/Desktop/web-starter-kit/app/styles/components/components.scss
at ChildProcess.<anonymous> (/home/riccardo/Desktop/web-starter-kit/node_modules/gulp-ruby-sass/index.js:98:25)
at ChildProcess.emit (events.js:98:17)
at maybeClose (child_process.js:755:16)
at Process.ChildProcess._handle.onexit (child_process.js:822:5)
I mean it sounds really weird I haven't actually written any actual code and there it is a syntax error in code written by someone clever than me, but it's more plausible that I did something wrong.
It looks like you're missing the sass ruby gem. It compiles/converts easy to read code into css for you.
In a terminal/commandline go to the project folder and run gem install sass. (Assuming you have ruby installed). Then try running the gulp stuff again.
Hope that helps!
Magento DB query to large works the first time then crashes.
I have about 6000 products and I need to put my category's into alphabetical order. The first time I make a move it takes about 45 min and works. Then any after that fail. mySQL is still up and going on other sites. but if I restart mySQL then it will not start back up. I have to safe reboot twice.... wait a bit then it seems to reset and will work. how do i let it run a larger query or is there another way to move/organize the categories?
If any one can help I would appreciate it so much.
Thanks
P.s. any more info needed please ask.
Notification Type: failed
Notification: mysql failed # Mon Jul 1 13:27:34 2013. A restart was attempted automagically.
Service Check Method: [check command]
Number of Restart Attempts: 1
Service Check Raw Output:
mysql is not running
Restart Message:
Stuck on restart of mysql at /usr/local/cpanel/Cpanel/TailWatch/ChkServd.pm line 1013.
Startup Log:
Starting MySQL.... SUCCESS!
Memory Information:
Used: 348MB
Available: 3099MB
Installed: 3447MB
Load Information: 18.49 12.34 6.95
Uptime: 199 days, 16 hours, 39 seconds
IOStat Information:
avg-cpu: %user %nice %system %iowait %steal %idle
0.44 0.23 0.31 0.84 0.00 98.18
Device: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn
vda 30.25 103.89 151.29 1792508458 2610237768
vda1 30.25 103.89 151.29 1792508098 2610237768
vdb 0.01 0.19 0.25 3278144 4279560