Skip to content
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

LogViewer cannot read rescue.log.xz. #58

Closed
ghost opened this issue Mar 8, 2022 · 5 comments
Closed

LogViewer cannot read rescue.log.xz. #58

ghost opened this issue Mar 8, 2022 · 5 comments
Assignees
Labels

Comments

@ghost
Copy link

ghost commented Mar 8, 2022

I ran the simulation according to the README in this repository and got rescue.log.xz.
I ran LogViewer with rescue.log.xz as input and got the following error message:

スクリーンショット 2022-03-08 14 30 36

The following is a list of commands executed before this error occurred.

server side (rcrs-server)

$ cd rcrs-server/scripts
$ ./gradlew completeBuild
$ ./start.sh -m ../maps/test/map -c ../maps/test/config

After the simulation is over.

$./gradlew logViewer --args="'-c' 'maps/test/config/logviewer.cfg' 'logs/log/rescue.log.xz'"

client side (adf-sample-agent-java)

$ cd adf-sample-agent-java
$ ./gradlew clean
$ ./gradlew build
$ ./launch.sh -all

Please refer to the attached file: rcrs-sever/logs/log
logs.zip

@modaresimr
Copy link
Contributor

@mas-suzu Thank you for your complete log report.
I was wondered about this exception until I found out that one test commit has been pushed in to the repository
I think it is resolved now.

@ghost
Copy link
Author

ghost commented Mar 8, 2022

I downloaded the latest commit and re-ran the simulation.
And, I ran LogViewer using the simulation log, but the following message is output, which is different from the previous one.

スクリーンショット 2022-03-08 19 04 05

Please refer to the attached file: rcrs-sever/logs
logs.zip

@modaresimr
Copy link
Contributor

modaresimr commented Mar 8, 2022 via email

@ghost
Copy link
Author

ghost commented Mar 8, 2022

Thank you very much! I did exactly what you told me to fix the configuration file and it works fine.
I see it was using the default values to run in the script directory.
Best Regards,
Hiroya Suzuki

@gnardin gnardin added the bug label Mar 8, 2022
@modaresimr
Copy link
Contributor

modaresimr commented Mar 8, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants