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

Logs being written to /var/log/syslog instead of /var/log/sympa/sympa.log #2

Open
clonm opened this issue Jan 14, 2019 · 2 comments
Open
Labels
non-breaking bug bugs that aren't causing user-facing problems

Comments

@clonm
Copy link
Member

clonm commented Jan 14, 2019

After upgrading (#1), had to start rsyslog manually (service rsyslog start), and it's not writing sympa logs in the right place.

@clonm clonm added the non-breaking bug bugs that aren't causing user-facing problems label Jan 14, 2019
@clonm
Copy link
Member Author

clonm commented Jan 15, 2019

Independently (?), it had crashed. I chown'd /var/log/sympa/sympa.log to syslog:adm inside the container and ran service sympa restart - the first time, it said could not stop sympa_msg because it wasn't running. the msg directory in /var/spool/sympa had a backlog, so that explains that. now the sympa logs get written both places. I'm not sure whether whatever caused the underlying problem is fixed

@clonm
Copy link
Member Author

clonm commented Jan 20, 2019

For now, this seems to be an effective workaround:

  1. exec into the sympa container
  2. running service rsyslog start
  3. make sure var/log/sympa/sympa.log exists; ls -lha /var/log/sympa/sympa.log should begin with -rw-r--r-- 1 syslog adm
  4. service sympa restart

However, this is clunky - logs should be handled automatically by runit and not have to be started manually. #TODO

ecawthon added a commit to clonm/docker-sympa that referenced this issue Sep 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
non-breaking bug bugs that aren't causing user-facing problems
Projects
None yet
Development

No branches or pull requests

1 participant