ApolloAuto
Why is there no new log information in the /apollo/data/log folder?
We appreciate you go through Apollo documentations and search previous issues before creating an new one. If neither of the sources helped you with your issues, please report the issue using the following form. Please note missing info can delay the response time.
System information
- OS Platform and Distribution:: Linux Ubuntu 18.04
- Apollo installed from: source
- *Apollo version: 8.0
- Output of
apollo.sh configif onmasterbranch: yes
Steps to reproduce the issue:
- Please use bullet points and include as much details as possible:
Hi, I'm using Apollo 8.0 with Carla 0.9.14. I noticed that the logs in the /data/log folder are sometimes not generated. Could you explain under what conditions a module generates a log file? Additionally, how can I debug this issue?
Supporting materials (screenshots, command lines, code/script snippets):
the log dir is determined by GLOG_log_dir env variable. log file name is determined by module name in BUILD file. when AINFO, AWARN, AERROR ... macro called will generate a log file if not exist.
the log dir is determined by GLOG_log_dir env variable. log file name is determined by module name in BUILD file. when AINFO, AWARN, AERROR ... macro called will generate a log file if not exist.
I have a log directory with existing old log files, but the issue is that when I launch Apollo again, it doesn't generate a new log file.
the real log file format: {module name}.log.INFO.{datatime}.{pid} , the {module name}.INFO is a symlink to the real file. if you start a new process, pid will changed, so a new log file will be created, it has always been so.
the real log file format: {module name}.log.INFO.{datatime}.{pid} , the {module name}.INFO is a symlink to the real file. if you start a new process, pid will changed, so a new log file will be created, it has always been so.
Sure, I got your point. I checked the real log file. The problem is that Apollo doesn't generate a new real log file. So I just wonder why and how can I fix it.
Make sure the environment variables are correct, I think it might be a problem with the environment variables.
bash source cyber/setup.bash
