Open nick-schwarzenberg opened 3 years ago
Hi there,
I faced the same issue today. I could solve this by changing the download link in line 40. from the install-ubuntu.sh script.
Basically, I changed
in line 23: ws_ver=3.2.7 to: ws_ver=3.4.8
and in line 40: wget https://www.wireshark.org/download/src/all-versions/wireshark-${ws_ver}.tar.xz to: wget https://1.eu.dl.wireshark.org/src/wireshark-3.4.8.tar.xz
Now it's working for me on Ubuntu 21.04
Hello guys, I follow the steps and replace the wget links to get wireshark version 3.4.8, but still did not fix this problem, OS: ubuntu 20.04
Two ideas :
Did you also change ws_ver=3.2.7 to 3.4.8 ? And maybe check if the link (behind wget) actually starts the download. ( You can copy the link and start from a browser) If not you need to get a new link ( best from wireshark website) but then you have to make sure that the tar command has the correct file name in it
Maybe you need to delete wireshark first and then retry the script ?
sudo apt-get remove --purge wireshark
Andsudo apt-get autoremove
Can you try this new branch that we have updated Wireshark to 3.4. https://github.com/mobile-insight/mobileinsight-core/tree/dev-6.0
Originally, this issue was about inconveniences in the output of the script and missing packages. This doesn't seem to be fixed in branch dev-6.0. The above comments refer to downloading Wireshark sources, however, which is independent of the other problems.
Installing missed package libc-ares-dev
resolved the issue with Wireshark.
Thought there is another one:
[INFO] [LtePhyAnalyzer]: PUSCH_TX_POWER: {'tx power': 22, 'timestamp': '2016-03-23 21:55:49.302584'}
[INFO] [LtePhyAnalyzer]: PUCCH_TX_POWER: {'tx power': 1, 'timestamp': '2016-03-23 21:55:49.322533'}
[INFO] [LtePhyAnalyzer]: PUSCH_TX_POWER: {'tx power': 13, 'timestamp': '2016-03-23 21:55:49.342538'}
[INFO] [LtePhyAnalyzer]: PUCCH_TX_POWER: {'tx power': 1, 'timestamp': '2016-03-23 21:55:49.342538'}
[INFO] [LtePhyAnalyzer]: SR_EVENT: {'timestamp': '2016-03-23 21:55:49.342538', 'fn and subfn': 5738}
[INFO] [LtePhyAnalyzer]: PUSCH_CQI: {'WideBand CQI CW0': '10', 'WideBand CQI CW1': '0'}
[INFO] [LtePhyAnalyzer]: PUSCH_TX_POWER: {'tx power': 16, 'timestamp': '2016-03-23 21:55:49.362534'}
[INFO] [LtePhyAnalyzer]: PUSCH_TX_POWER: {'tx power': 17, 'timestamp': '2016-03-23 21:55:49.362534'}
[INFO] [LtePhyAnalyzer]: PUCCH_TX_POWER: {'tx power': 1, 'timestamp': '2016-03-23 21:55:49.362534'}
[INFO] [LtePhyAnalyzer]: PUCCH_TX_POWER: {'tx power': 1, 'timestamp': '2016-03-23 21:55:49.362534'}
Traceback (most recent call last):
File "/usr/local/lib/python3.8/dist-packages/MobileInsight-5.0.0-py3.8-linux-x86_64.egg/mobile_insight/monitor/offline_replayer.py", line 209, in run
self.send(event)
File "/usr/local/lib/python3.8/dist-packages/MobileInsight-5.0.0-py3.8-linux-x86_64.egg/mobile_insight/element.py", line 104, in send
self.to_list[i].recv(self, event)
File "/usr/local/lib/python3.8/dist-packages/MobileInsight-5.0.0-py3.8-linux-x86_64.egg/mobile_insight/analyzer/analyzer.py", line 234, in recv
self.source_callback[i](event)
File "/usr/local/lib/python3.8/dist-packages/MobileInsight-5.0.0-py3.8-linux-x86_64.egg/mobile_insight/analyzer/lte_rrc_analyzer.py", line 249, in __rrc_filter
self.__callback_sib_config(xml_msg)
File "/usr/local/lib/python3.8/dist-packages/MobileInsight-5.0.0-py3.8-linux-x86_64.egg/mobile_insight/analyzer/lte_rrc_analyzer.py", line 451, in __callback_sib_config
int(field_val['lte-rrc.utra_q_RxLevMin']) * 2,
TypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType'
Failed to run offline analysis example!
Exiting with status 4.
Versions
Description
We were trying to set up
mobileinsight-core
usinginstall-ubuntu.sh
on a fresh Debian 10 install (and reproduced the issue on a fresh Xubuntu 20.04). Runningcmake
on line 47 failed. When tracking down the cause, we noticed three problems:cmake
command and is a bit misleading, one could think that thecmake
binary is being looked for on the wrong path. Could be changed to:"Error when executing 'cmake -DBUILD_wireshark=OFF .' in ${WIRESHARK_SRC_PATH}/"
cmake
is suppressed (i.e., redirected to/dev/null
, includingstderr
) which makes troubleshooting harder than it has to be. Why is this done actually, the other commands log to the standard outputs as well?cmake
,build-essential
,git
, andlibgcrypt20-dev
(could be added to line 35)While the last point is the main problem, it might be worth to consider fixing the others as well.
Logs