-
Notifications
You must be signed in to change notification settings - Fork 99
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
Incomplete rosout.log #204
Comments
Original comment by Nate Koenig (Bitbucket: Nathan Koenig). We are copying all the ROS logs, as recorded by ROS. If something doesn't appear in the logs, then the most likely culprit is something other than the logs and the logging system. I'd like to reproduce your problem to see what going on. What docker image are you using, and how are you submitting you solution? You can share private information through [email protected]. |
Original comment by Martin Dlouhy (Bitbucket: robotikacz). The |
Original comment by Martin Dlouhy (Bitbucket: robotikacz). Can you enable basic logging of deployed docker - I mean no ROS and no Ignition, just what is the low level docker output? I am willing to change the rights or what ever is needed - it was possible 4 years ago in Google cloud so it must be possible to do also on AWS. We had aggregation of all outputs of all running instances (not 1 but 100 or more) without loosing a single output line, sigh. “just for fun” I run the identical docker for the 2nd time (tag
so again the beginning of You can run as many independent processes you want in the ROS or not? They do not have to be all listed in one launch file or they do? p.s. how other teams scoring 0 points (“Coordinated Robotics”, “Kankanwadi”, “MTRI”) in “Simple Tunnel 02” are doing? I suppose that locally it works for them too?? p.s.2 you are allowed to run only 1 simulation a time (info for others):
|
Original comment by Martin Dlouhy (Bitbucket: robotikacz).
It seems to me now, that the problem is related to multiple "launches" of ROS nodes. I plan to fallback to a single C++ node, where I currently do not see this problem. |
Original comment by Sarah Kitchen (Bitbucket: snkitche). It seems we are not seeing most of our console output in the logs. |
Original comment by Martin Dlouhy (Bitbucket: robotikacz). Are you using one or more ROS nodes? Do you have them all specified in the launch file? I believe that there is some issue with more nodes or when they start at different times (?). I use the workaround with single C++ ROS node and ZeroMQ to communicate with it … |
Original comment by Sarah Kitchen (Bitbucket: snkitche). Multiple nodes. I posted here to let them know you are not uniquely experiencing this issue. |
Original comment by Martin Dlouhy (Bitbucket: robotikacz). :slight_smile: OK, thanks |
Original comment by Martin Dlouhy (Bitbucket: robotikacz).
the issue persists for multiple ROS nodes (also reported by Sarah) |
Original comment by Martin Dlouhy (Bitbucket: robotikacz).
|
Original comment by Nate Koenig (Bitbucket: Nathan Koenig). I'm trying to reproduce the problem. Does anyone have a more concrete example launch file and setup that I could test with? There might be a buffering issue: ros/rosconsole#5 and related question: https://answers.ros.org/question/200593/why-in-this-simple-sample-my-logs-are-not-written-in-logfile-or-is-there-a-way-to-control-the-flushing-period-of-the-log-files/ |
Original comment by Sarah Kitchen (Bitbucket: snkitche). Nate, are you able to pull the images we’ve submitted to the cloudsim? If so, I can give you examples over the subt-help email. |
Original comment by Nate Koenig (Bitbucket: Nathan Koenig). I am able to pull the images. |
Original comment by Martin Dlouhy (Bitbucket: robotikacz). Is the “rosout.log” cyclic buffer?! I am trying to dump OSGAR log at the end of simulation (few MB) and the content starts with:
?!! robotika, ver22b-92728081-1a56-4559-9cb5-0c483199dee1-A0F40F100F400L.tar |
Original comment by Martin Dlouhy (Bitbucket: robotikacz). The same for the 2nd robot:
ver22b-92728081-1a56-4559-9cb5-0c483199dee1-B10F40F100F400R.tar.gz 😞 |
Original comment by Martin Dlouhy (Bitbucket: robotikacz).
It is hard to develop/test anything without any log/feedback 😞 |
Original comment by Martin Dlouhy (Bitbucket: robotikacz). I just got output for ver22d with 3 rosout.log files:
:slight_smile: thanks a lot! |
Original comment by Martin Dlouhy (Bitbucket: robotikacz). p.s. I am very sorry - I am blind - even the previous ver22b had |
Original comment by Martin Dlouhy (Bitbucket: robotikacz).
there are multiple rosout.log files generated, thanks |
Original comment by Martin Dlouhy (Bitbucket: robotikacz).
|
Original report (archived issue) by Martin Dlouhy (Bitbucket: robotikacz).
“rosout.log” is the only way how we can check our deployment on AWS (correct me, if I am wrong), and it is not complete! 😞
I run 3 simulations (robotika, [ver4, ver5, ver6], Simple Tunnel 02) last night and today. Just to be sure that everything is initialized (see 6 minutes issue #202) I added extra pure ROS code originally waiting for all necessary topics, which are later used in the main navigation program. They all first print “begin” and at the end “end” to ROS info. The last simulation (ver6, cab6fd44-2448-4fa7-bd38-a44d94250182) even failed to pass “Wait for /X2/front/image_raw/compressed” :frowning2:
Code snippet:
Ver6 rosout.log
Ver5 (did not wait for the master published topics)
See END without BEGIN and missing previously reported topics …
The text was updated successfully, but these errors were encountered: