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

Set the parameter timestamp_in_logfile_name=false cause log report wrong information for logrotate setups #4411

Closed
henry202108 opened this issue Jul 13, 2022 · 0 comments · Fixed by #4409
Labels
severity/minor Severity of bug type/bug Type: something is unexpected
Milestone

Comments

@henry202108
Copy link

Please check the FAQ documentation before raising an issue

Describe the bug (required)
When set the parameter timestamp_in_logfile_name=false , all the log except the storaged-stderr.log stopped recording and the storaged-stderr.log report the error message "COULD NOT CREATE LOGFILE :No such file or directory"

Your Environments (required)

  • OS: uname -a
  • Compiler: g++ --version or clang++ --version
  • CPU: lscpu
  • Commit id (e.g. a3ffc7d8)

Linux 192-168-8-191 3.10.0-1160.36.2.el7.x86_64 #1 SMP Wed Jul 21 11:57:15 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1

https://github.com/vesoft-inc/nebula-ent/commit/f8956326d327aa46246da583fa3cbd05e29c5c7d

How To Reproduce(required)

Steps to reproduce the behavior:

  1. Step 1
    set the parameter timestamp_in_logfile_name=false in the config file
  2. Step 2
    restart the related service
  3. Step 3
    tail the log file

Expected behavior
the log file should record information correctly

Additional context

@henry202108 henry202108 added the type/bug Type: something is unexpected label Jul 13, 2022
@Sophie-Xie Sophie-Xie linked a pull request Jul 14, 2022 that will close this issue
11 tasks
@Sophie-Xie Sophie-Xie added this to the v3.3.0 milestone Jul 14, 2022
@jinyingsunny jinyingsunny added the severity/minor Severity of bug label Nov 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/minor Severity of bug type/bug Type: something is unexpected
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants