chili-epfl / ros4nao

Helpers to compile and distribute ROS for Aldebaran's Nao
MIT License
3 stars 2 forks source link

http://chili-research.epfl.ch is down #9

Open rqg0717 opened 7 years ago

rqg0717 commented 7 years ago

http://chili-research.epfl.ch is down. Please update the bootstrap.sh. Thank you.

severin-lemaignan commented 7 years ago

@WafaJohal do you know who is maintaining the server? could you have a look?

WafaJohal commented 7 years ago

@kshitijkshitij is in charge of the maintenance I believe. I sent an email to 1234 to see what is the problem. Thank you for reporting it.

severin-lemaignan commented 7 years ago

Well, http://chili-research.epfl.ch/ is not really down: it answers, but it just looks like a fresh new install... Has someone just wiped out the content of the server?

kshitijkshitij commented 7 years ago

Yes It was updated a week ago. And I dint know that the chili research was running there. Before updating there was no sign of chili research

Sent from my iPhone

On 09 Dec 2016, at 11:55, S?verin Lemaignan notifications@github.com<mailto:notifications@github.com> wrote:

Well, http://chili-research.epfl.ch/ is not down: it answers. But it just looks like a fresh new install... Has someone just wiped out the content of the server?

- You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/chili-epfl/ros4nao/issues/9#issuecomment-265987088, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGQCvc19rr2LuDjjU4KKBSEvWMtCJ8hkks5rGTN5gaJpZM4LIeqb.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/chili-epfl/ros4nao","title":"chili-epfl/ros4nao","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/chili-epfl/ros4nao"}},"updates":{"snippets":[{"icon":"PERSON","message":"@severin-lemaignan in #9: Well, http://chili-research.epfl.ch/ is not down: it answers. But it just looks like a fresh new install... Has someone just wiped out the content of the server?"}],"action":{"name":"View Issue","url":"https://github.com/chili-epfl/ros4nao/issues/9#issuecomment-265987088"}}}

severin-lemaignan commented 7 years ago

Hum, this is unfortunate (but not entirely unexpected, as we've never properly documented what was important on that server).

@rqg0717 I fear that this means that the OpenNAO/Gentoo's portage tree that I was offering on chili-research.epfl.ch is gone. Making it available again requires a largely undocumented process (basically, installing ROS on a Nao VM with robotpkg and copying the non-default OpenNAO system packages that are installed during the process (+ a few other packages that are only available on the OpenNAO VM image like `emerge') onto a new server.

I'm not working at EPFL anymore, and I can not really commit to set it up somewhere else for the time being. I'm happy to help if someone else wants to step in.

rqg0717 commented 7 years ago

@severin-lemaignan I would like to give it a try. I was wondering if you could help me to establish the new server. Please let me know. Thanks a lot.

severin-lemaignan commented 7 years ago

@rqg0717 I can try to help a little bit, yes, but I don't have much time to devote, I fear. Essentially, you need host a portage server that can be used by emerge to download to package binaries. As far as I remember, the rough procedure is as follow:

Voila. Hopefully, it gives you some initial pointers to play with that.

rqg0717 commented 7 years ago

@severin-lemaignan Thank you for your instructions. Actually I have tried to compile ROS from the source but failed. I think the tutorial is out of date. Anyway, I will try another option using robotpkg.

severin-lemaignan commented 7 years ago

On 11/01/17 22:27, James Ren wrote:

@severin-lemaignan Thank you for your instructions. Actually I have tried to compile ROS from the source but failed. I think the tutorial is out of date. Anyway, I will try another option using robotpkg.

I wouldn't be surprised that the instructions are out of date: they are 2-3 years old... Please update the ROS wiki as needed!


[http://www.plymouth.ac.uk/images/email_footer.gif]http://www.plymouth.ac.uk/worldclass

This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, Plymouth University accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. Plymouth University does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.

rqg0717 commented 7 years ago

@severin-lemaignan I followed the instruction from ROS from source for NAO to install ROS on my robot. Everything went well first and I had "roscore" running on virtualnao without any error. Then I transferred the compiled file to real robot and after installed some missing library, I can execute "roslaunch nao_bringup nao_full.launch" to ask robot speak or get picture from NAO's camera. However when I tried to run "roslaunch nao_apps speech.launch" to enable speech recognition, it always died with a exit code -11. Here is the full output:

root@nao [0] nao # !sour
source /home/nao/ros/setup.bash
root@nao [0] nao # roslaunch nao_apps speech.launch nao_ip:=192.168.1.2 roscore_ip:=192.168.1.4
... logging to /root/.ros/log/acd9a650-e7d5-11e6-815c-48a9d2969cc8/roslaunch-nao-4938.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://localhost:42594/

SUMMARY
========

PARAMETERS
 * /rosdistro: indigo
 * /rosversion: 1.11.20

NODES
  /
    nao_speech (nao_apps/nao_speech.py)

ROS_MASTER_URI=http://192.168.1.4:11311

setting /run_id to acd9a650-e7d5-11e6-815c-48a9d2969cc8
process[rosout-1]: started with pid [4951]
started core service [/rosout]
process[nao_speech-2]: started with pid [4952]
================================================================================REQUIRED process [nao_speech-2] has died!
process has died [pid 4952, exit code -11, cmd /home/nao/ros/lib/nao_apps/nao_speech.py --pip=192.168.1.2 --pport=9559 __name:=nao_speech __log:=/root/.ros/log/acd9a650-e7d5-11e6-815c-48a9d2969cc8/nao_speech-2.log].
log file: /root/.ros/log/acd9a650-e7d5-11e6-815c-48a9d2969cc8/nao_speech-2*.log
Initiating shutdown!
================================================================================
[nao_speech-2] killing on exit
[rosout-1] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done
root@nao [0] nao #

I thought the error is from some python library so when I wanted to import naoqi or qi library directly from python, it also returned a segmentation error:

root@nao [0] nao # python
Python 2.7.3 (default, Apr 20 2015, 13:39:57)
[GCC 4.5.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import naoqi
Segmentation fault
root@nao [err 139] nao #
root@nao [0] nao # python
Python 2.7.3 (default, Apr 20 2015, 13:39:57)
[GCC 4.5.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import qi
Segmentation fault
root@nao [err 139] nao #

I was wondering if you had experienced the similar issue before. Please let me know. Thanks a lot.

Sincerely, James

severin-lemaignan commented 7 years ago

Hum, no. I've never played with the speech recognition. The segfault is a bit surprising... can you try to run python from gdb to get a stacktrace?