New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to upload trace file trace.tar.gz - Internal Server Error #8
Comments
What is the output of the command, and could you share the tarball? Note that it will reveal what processes are running on your machine, so only share it if that's ok with you. |
Thanks for the quick response. Not sure what happened there, but I have restarted the server and run again the trace.sh tool to obtain a new tarball. Now everything seems to be working fine, so I'm closing the issue. Thanks! |
There might be a bug revealed by the first tarball you created, as they are highly dependent on what is running on the machine. If you still have it, I'd like to take a look at it. |
I'm afraid I don't have it anymore. I did build and install kernelshark in between these two runs. But I believe I have not run trace-cmd during that time. I did run kernelshark with trace data collected using trace-cmd on an embedded device. |
I thought I wasn't, but I think I must have been using the wrong trace file when I got the 'Internal Server Error' message. What happens is that I've been trying to visualize the traces collected from two devices, my Linux desktop running Ubuntu, and an embedded device running an embedded Linux. For some reason, the traces collected from my embedded device are not compatible with schedviz. I've created a new tarball with traces from this device. Note that I had to modify the trace.sh script to remove bashisms as my device is running Busybox. Also, note that the device has a single-core CPU. The topology directory lives under:
I'm attaching both the traces tarball and the modified trace.sh script . |
I am also having this issue. I generated a trace on one host and would like to analyze it from another |
@sabarabc the actual error I get is:
|
@juanrubio Sorry for the delay. I took a look at your trace and it appears to have around 20 pages worth of garbage data before the first real page containing tracing data. Your trace also contains events that whose formats were not included in the tar (i.e. not specified in the shell script). I see events with format IDs 6 and 14, which are not the scheduling events. Could you confirm if your trace buffers are cleared before starting the trace and that nothing else is tracing at the same time? I've modified SchedViz to be able to handle 32 bit traces (you appear to be tracing on a 32 bit machine, is that correct?) and be more tolerant of missing formats (when passed the Also, we've added support for recording traces using ebpf which doesn't require the formats. You can try it by collecting a trace using the collect.sh script (you'll need to upload sched.bt and have bpftrace installed as well.) Let me know if this works for you. |
@tjake Can you create a new issue and share your trace.tar.gz file? |
Hi,
I'm getting 'Failed to upload trace file trace.tar.gz Reason: Internal Server Error' while trying to upload a tarball created with this command:
What am I missing?
Ubuntu 18.04
yarn 1.19.1
node 10.16.3
The text was updated successfully, but these errors were encountered: