New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 693175 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 691119
Owner:
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Invalid kwarg during crash dump

Project Member Reported by ayatane@chromium.org, Feb 16 2017

Issue description

From crbug.com/692134

ost4/metrics_daemon.20170214.115540.14286.dmp" "/usr/local/autotest/server/../../../lib/debug" > "/usr/local/autotest/results/hosts/chromeos1-row1-rack3-host4/586552-repair/20171402120338/crashinfo.chromeos1-row1-rack3-host4/metrics_daemon.20170214.115540.14286.dmp.txt"'
02/14 12:05:05.498 INFO | site_crashcollect:0104| Failed to generate stack trace locally for dump /usr/local/autotest/results/hosts/chromeos1-row1-rack3-host4/586552-repair/20171402120338/crashinfo.chromeos1-row1-rack3-host4/metrics_daemon.20170214.115540.14286.dmp (rc=127):
CmdError('minidump_stackwalk "/usr/local/autotest/results/hosts/chromeos1-row1-rack3-host4/586552-repair/20171402120338/crashinfo.chromeos1-row1-rack3-host4/metrics_daemon.20170214.115540.14286.dmp" "/usr/local/autotest/server/../../../lib/debug" > "/usr/local/autotest/results/hosts/chromeos1-row1-rack3-host4/586552-repair/20171402120338/crashinfo.chromeos1-row1-rack3-host4/metrics_daemon.20170214.115540.14286.dmp.txt"', * Command: 
    minidump_stackwalk "/usr/local/autotest/results/hosts/chromeos1-row1-rack
    3-host4/586552-repair/20171402120338/crashinfo.chromeos1-row1-rack3-host4/
    metrics_daemon.20170214.115540.14286.dmp"
    "/usr/local/autotest/server/../../../lib/debug" > "/usr/local/autotest/res
    ults/hosts/chromeos1-row1-rack3-host4/586552-repair/20171402120338/crashin
    fo.chromeos1-row1-rack3-host4/metrics_daemon.20170214.115540.14286.dmp.txt
    "
Exit status: 127
Duration: 0.00256013870239

stderr:
/bin/bash: minidump_stackwalk: command not found, 'Command returned non-zero exit status')
02/14 12:05:05.499 INFO | site_crashcollect:0108| Generating stack trace using devserver for /usr/local/autotest/results/hosts/chromeos1-row1-rack3-host4/586552-repair/20171402120338/crashinfo.chromeos1-row1-rack3-host4/metrics_daemon.20170214.115540.14286.dmp
02/14 12:05:07.834 DEBUG|        dev_server:0294| RPC call get_load has timed out on devserver 100.108.1.59.
02/14 12:05:07.835 ERROR|        dev_server:0427| Devserver call failed: "http://100.108.1.59:8082/check_health?", timeout: 2.0 seconds, Error: retry exception (label="get_load"), timeout = 2s
02/14 12:05:07.845 DEBUG|        dev_server:0294| RPC call get_load has timed out on devserver 172.24.190.211.
02/14 12:05:07.846 ERROR|        dev_server:0427| Devserver call failed: "http://172.24.190.211:8082/check_health?", timeout: 2.0 seconds, Error: retry exception (label="get_load"), timeout = 2s
02/14 12:05:07.856 DEBUG|        dev_server:0294| RPC call get_load has timed out on devserver 172.25.61.81.
02/14 12:05:07.857 ERROR|        dev_server:0427| Devserver call failed: "http://172.25.61.81:8082/check_health?", timeout: 2.0 seconds, Error: retry exception (label="get_load"), timeout = 2s
02/14 12:05:07.880 DEBUG|        dev_server:0294| RPC call get_load has timed out on devserver 172.25.66.216.
02/14 12:05:07.881 ERROR|        dev_server:0427| Devserver call failed: "http://172.25.66.216:8082/check_health?", timeout: 2.0 seconds, Error: retry exception (label="get_load"), timeout = 2s
02/14 12:05:07.888 DEBUG|        dev_server:2272| CPU load of devserver http://172.25.75.76:8082 is at 85.7%, which is higher than the threshold of 80.0%
02/14 12:05:07.889 ERROR|            repair:0037| Counter() got an unexpected keyword argument 'fields'
Traceback (most recent call last):
  File "/usr/local/autotest/server/control_segments/repair", line 30, in repair
    crashcollect.get_crashinfo(target, None)
  File "/usr/local/autotest/site-packages/chromite/lib/metrics.py", line 274, in wrapper
    return fn(*args, **kwargs)
  File "/usr/local/autotest/server/crashcollect.py", line 161, in get_crashinfo
    get_crashdumps(host, test_start_time)
  File "/usr/local/autotest/site-packages/chromite/lib/metrics.py", line 274, in wrapper
    return fn(*args, **kwargs)
  File "/usr/local/autotest/server/crashcollect.py", line 148, in get_crashdumps
    get_site_crashdumps(host, test_start_time)
  File "/usr/local/autotest/server/site_crashcollect.py", line 264, in get_site_crashdumps
    minidumps = find_and_generate_minidump_stacktraces(host_resultdir)
  File "/usr/local/autotest/server/site_crashcollect.py", line 147, in find_and_generate_minidump_stacktraces
    generate_stacktrace_for_file(file, host_resultdir)
  File "/usr/local/autotest/server/site_crashcollect.py", line 109, in generate_stacktrace_for_file
    crashserver_name = _resolve_crashserver()
  File "/usr/local/autotest/server/site_crashcollect.py", line 53, in _resolve_crashserver
    fields={'crash_server': crashserver_name})
  File "/usr/local/autotest/site-packages/chromite/lib/metrics.py", line 105, in wrapper
    return fn(*args, **kwargs)
  File "/usr/local/autotest/site-packages/chromite/lib/metrics.py", line 86, in AddToQueueIfPresent
    return fn(*args, **kwargs)
TypeError: Counter() got an unexpected keyword argument 'fields'
02/14 12:05:07.890 INFO |        server_job:0183| END FAIL	----	repair	timestamp=1487102707	localtime=Feb 14 12:05:07	
02/14 12:05:07.890 DEBUG|      abstract_ssh:0756| Nuking master_ssh_job.
02/14 12:05:08.892 DEBUG|      abstract_ssh:0762| Cleaning master_ssh_tempdir.
02/14 12:05:08.892 DEBUG|      abstract_ssh:0917| Terminated tunnel, pid 15953
02/14 12:05:08.892 DEBUG|      abstract_ssh:0756| Nuking master_ssh_job.
02/14 12:05:09.898 DEBUG|      abstract_ssh:0762| Cleaning master_ssh_tempdir.
02/14 12:05:09.898 ERROR|         traceback:0013| Traceback (most recent call last):
02/14 12:05:09.898 ERROR|         traceback:0013|   File "/usr/local/autotest/server/autoserv", line 530, in run_autoserv
02/14 12:05:09.898 ERROR|         traceback:0013|     job.repair(job_labels)
02/14 12:05:09.899 ERROR|         traceback:0013|   File "/usr/local/autotest/server/server_job.py", line 516, in repair
02/14 12:05:09.899 ERROR|         traceback:0013|     self._execute_code(REPAIR_CONTROL_FILE, namespace, protect=False)
02/14 12:05:09.899 ERROR|         traceback:0013|   File "/usr/local/autotest/server/server_job.py", line 1300, in _execute_code
02/14 12:05:09.899 ERROR|         traceback:0013|     execfile(code_file, namespace, namespace)
02/14 12:05:09.899 ERROR|         traceback:0013|   File "/usr/local/autotest/server/control_segments/repair", line 47, in <module>
02/14 12:05:09.900 ERROR|         traceback:0013|     job.parallel_simple(repair, machines)
02/14 12:05:09.900 ERROR|         traceback:0013|   File "/usr/local/autotest/server/server_job.py", line 624, in parallel_simple
02/14 12:05:09.900 ERROR|         traceback:0013|     return_results=return_results)
02/14 12:05:09.900 ERROR|         traceback:0013|   File "/usr/local/autotest/server/subcommand.py", line 93, in parallel_simple
02/14 12:05:09.901 ERROR|         traceback:0013|     function(arg)
02/14 12:05:09.901 ERROR|         traceback:0013|   File "/usr/local/autotest/server/control_segments/repair", line 41, in repair
02/14 12:05:09.901 ERROR|         traceback:0013|     raise Exception('')
02/14 12:05:09.901 ERROR|         traceback:0013| Exception
02/14 12:05:09.934 DEBUG|          monitors:0191| ts_mon: sending 6 metrics to PubSub
02/14 12:05:09.938 INFO |            client:0570| Attempting refresh to obtain initial access_token
02/14 12:05:09.974 INFO |            client:0872| Refreshing access_token
02/14 12:05:10.406 ERROR|          autoserv:0774| 1
Traceback (most recent call last):
  File "/usr/local/autotest/server/autoserv", line 770, in main
    use_ssp)
  File "/usr/local/autotest/server/autoserv", line 583, in run_autoserv
    sys.exit(exit_code)
SystemExit: 1


This is the repair log for host chromeos1-row1-rack3-host4. It seems failed to dump crash log.
 
Any reason this isn't a duplicate of  bug 691119 ?

Mergedinto: 691119
Status: Duplicate (was: Untriaged)
No, I was not aware of it.

Sign in to add a comment