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

salt-api stops logging after logrotate #54212

Open
mpascual opened this issue Aug 14, 2019 · 4 comments
Open

salt-api stops logging after logrotate #54212

mpascual opened this issue Aug 14, 2019 · 4 comments
Labels
Bug broken, incorrect, or confusing behavior Salt-API severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around

Comments

@mpascual
Copy link

Description of Issue

It looks like after logrotate runs the log rotation, salt-api stops logging.

ls -l

total 822188
-rw-r----- 1 root root 0 Jun 30 03:43 api
-rw-r----- 1 root root 38578 May 12 03:16 api-20190512.gz
-rw-r----- 1 root root 112280 May 17 18:47 api-20190519.gz
-rw-r----- 1 root root 228 May 22 17:20 api-20190526.gz
-rw-r----- 1 root root 122 May 30 07:02 api-20190602.gz
-rw-r----- 1 root root 122 Jun 12 16:53 api-20190613.gz
-rw-r----- 1 root root 123 Jun 24 14:24 api-20190625.gz
-rw-r----- 1 root root 186 Jun 25 17:56 api-20190630.gz

sudo lsof | grep salt | grep deleted | grep api

/usr/bin/ 11988 11993 /usr/bin/ root 3w REG 259,3 519 1051236 /var/log/salt/api-20190630 (deleted)

Similar to old issues:

Versions Report

(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)

salt --versions-report

Salt Version:
Salt: 2019.2.0

Dependency Versions:
cffi: 1.11.4
cherrypy: 3.8.0
dateutil: 2.6.1
docker-py: 3.7.1
gitdb: Not Installed
gitpython: Not Installed
ioflo: Not Installed
Jinja2: 2.10.1
libgit2: 0.26.8
libnacl: 1.6.1
M2Crypto: 0.31.0
Mako: Not Installed
msgpack-pure: Not Installed
msgpack-python: 0.6.1
mysql-python: 1.4.2.post1
pycparser: 2.14
pycrypto: 3.6.6
pycryptodome: Not Installed
pygit2: 0.26.4
Python: 2.7.15 (default, Mar 30 2019, 22:09:42)
python-gnupg: 0.4.3
PyYAML: 5.1
PyZMQ: 17.1.0
RAET: Not Installed
smmap: Not Installed
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.3.1

System Versions:
dist: gentoo 2.6
locale: UTF-8
machine: x86_64
release: 4.19.27-gentoo-r1
system: Linux
version: Gentoo Base System 2.6

@dmurphy18 dmurphy18 added this to the Approved milestone Aug 16, 2019
@dmurphy18
Copy link
Contributor

Possibly related to #54142 and/or #48125

@stale
Copy link

stale bot commented Jan 8, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

@stale stale bot added the stale label Jan 8, 2020
@mpascual
Copy link
Author

mpascual commented Jan 8, 2020

Leaving a comment to leave this open.

@stale
Copy link

stale bot commented Jan 8, 2020

Thank you for updating this issue. It is no longer marked as stale.

@stale stale bot removed the stale label Jan 8, 2020
@sagetherage sagetherage added the Bug broken, incorrect, or confusing behavior label Jan 9, 2020
@sagetherage sagetherage added Salt-API Phosphorus v3005.0 Release code name and version severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around labels Jun 16, 2021
@sagetherage sagetherage modified the milestones: Approved, Phosphorus Jun 16, 2021
@Ch3LL Ch3LL removed the Phosphorus v3005.0 Release code name and version label Mar 30, 2022
@anilsil anilsil removed this from the Chlorine v3007.0 milestone May 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior Salt-API severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around
Projects
None yet
Development

No branches or pull requests

6 participants