Apollo: localhost/Dreamview not working

Created on 27 Apr 2018  ·  12Comments  ·  Source: ApolloAuto/apollo

I tried looking at older threads about the same issue but nothing solves mine.

-> Build process says "success" except some errors like :
INFO: From Executing genrule //modules/drivers/pandora:pandora_genrule:
CMake Error at cmake_install.cmake:54 (FILE):
file INSTALL cannot copy file
"/tmp/build_isolated/pandora_driver/catkin_generated/installspace/_setup_util.py"
to "/home/tmp/ros/_setup_util.py".

-> Also my dreamview.out file is empty to trace the issue it has.

-> "ps -ef | grep dreamview" - gives me
$user 15865 50 0 16:33 pts/19 00:00:00 grep --color=auto dreamview

-> "./scripts/dreamview.sh" start_fe throws
/apollo/scripts/apollo_base.sh: line 305: 15873 Illegal instruction /apollo/bazel-bin/modules/dreamview/dreamview --flagfile=modules/dreamview/conf/dreamview.conf --alsologtostderr --log_dir=/apollo/data/log

Help is really appreciated :)

HMI Question

Most helpful comment

@SyedShaQutub Great, you got it worked.

@vlin17 Okay, I will update the docs.

All 12 comments

Hi @SyedShaQutub,

With the given information, it seems like a ROS installation issue. Are you using the docker env we provide?

Could you run "ps -ef | grep ros" to see if your roscore and rosmater processes are running? If not, we need to see why, and according to the CMOS error you posted, maybe this one or this one can help.

Hi @vlin17,

Yes the ros cores are running perfectly fine.

120 1 1 08:17 pts/19 00:00:00 /usr/bin/python /home/tmp/ros/bin/roscore

157 120 2 08:17 ? 00:00:00 /usr/bin/python /home/tmp/ros/bin/rosmaster --core -p 11311 -w 3 __log:=/home/user/.ros/log/8419c094-4dd0-11e8-b84f-d4ae52c072a6/master.log

188 120 1 08:17 ? 00:00:00 /home/tmp/ros/lib/rosout/rosout __name:=rosout __log:=/home/user/.ros/log/8419c094-4dd0-11e8-b84f-d4ae52c072a6/rosout-1.log

243 50 0 08:18 pts/19 00:00:00 grep --color=auto ros

Please confirm is this normal. Normally it should be running without exiting the Dreamview, right ?

=>
qutub@in_dev_docker:/apollo$ bash scripts/bootstrap.sh
Started supervisord with dev conf
Start roscore...
voice_detector: started
Dreamview is running at http://localhost:8888
qutub@in_dev_docker:/apollo$

=>
the log info in - *.out files in path apollo/data/log/ are empty.

=> Could it be the issue with post installation steps of Docker " https://docs.docker.com/install/linux/linux-postinstall/ "

Also please let me know which of the post installation steps are mandatory to run Dreamview ?

@SyedShaQutub Hi, could you please paste:

  1. the gdb backtrace of dreamview;
  2. the output of grep flags /proc/cpuinfo | uniq.

since you've got the error: Illegal instruction.
Simply you can get gdb backtrace with:

source scripts/apollo_base.sh
start_gdb dreamview

Once gdb is launched, press r and enter key to run, if dreamview is crashed, then get the backtrace with bt.

If you find something related with lib pcl in the backtrace, you may want this and #3615 .

@vlin17 Eventually, I have found some clues about Illegal instruction, I have put them in the comment of issue #3615.

And how do you think about removing the log redirection in:
https://github.com/ApolloAuto/apollo/blob/8be5f938c594b115d7ec30a57965504d67273fc4/scripts/bootstrap.sh#L41

Then, the developers can get the errors immediately if dreamview fails to start.

Hi @zhxt ,

Thank for your detailed support.
Yes the issue is with PCL lib, but it turns out that my processor doesn't support FMA3 architecture( FYI @vlin17 )

FYI, I have pasted the bt below. I believe that I have solved the PCL Lib(as directed by you in other thread.

0 0x00007fffefcc7eec in _GLOBAL__sub_I_sac.cpp ()

from /usr/local/lib/libpcl_sample_consensus.so.1.7

1 0x00007ffff7dea2da in call_init (l=, argc=argc@entry=3,

argv=argv@entry=0x7fffffffe1c8, env=env@entry=0x7fffffffe1e8)
at dl-init.c:78

2 0x00007ffff7dea3c3 in call_init (env=,

argv=<optimized out>, argc=<optimized out>, l=<optimized out>)
at dl-init.c:36

3 _dl_init (main_map=0x7ffff7ffe1c8, argc=3, argv=0x7fffffffe1c8,

env=0x7fffffffe1e8) at dl-init.c:126

4 0x00007ffff7ddb29a in _dl_start_user () from /lib64/ld-linux-x86-64.so.2

5 0x0000000000000003 in ?? ()

6 0x00007fffffffe47b in ?? ()

7 0x00007fffffffe506 in ?? ()

8 0x00007fffffffe537 in ?? ()

9 0x0000000000000000 in ?? ()

(gdb)

Hi all,

Continued the process, and now stuck with this issue

terminate called after throwing an instance of 'CivetException' what(): null context when constructing CivetServer. Possible problem binding to port.

The issue is explained in the page


https://github.com/ApolloAuto/apollo/blob/master/docs/howto/how_to_debug_dreamview_start_problem.md
but this doesn't solve my issue. A direction to solve this is much helpful to me at this stage.

PS :
I have edited the TCP listening port to 8888 (docker.service) as suggested by Apollo - the post installation of docker

Hey, its working... happiest person right now.

Thanks guys for all your support. Cheers

May be this could be useful to others.

Lesson learnt :
follow the post installation steps of docker for linux except don't edit the daemon.json or docker.service file. This could be different with other users if they have changed the local server listening port in other packages.

@zhxt thank you for helping us identify the issue. I like the FAQ page you put up. Would you be interested in moving the content to https://github.com/ApolloAuto/apollo/tree/master/docs/FAQs or https://github.com/ApolloAuto/apollo/blob/master/docs/howto/how_to_debug_dreamview_start_problem.md to benefit the community?

Regarding the log redirection one, I agree, it could help the developers get the errors immediately. I will update the script.

@SyedShaQutub thanks for sharing the tips and verifying the solution provided from @zhxt, cheers!

@SyedShaQutub Great, you got it worked.

@vlin17 Okay, I will update the docs.

PR created #4088 .

Thank you all for the contribution. Since the issue has been resolved and documented, we will close the issue for now. If you have any additional question, please feel free to open a new issue.

Was this page helpful?
0 / 5 - 0 ratings