You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 18, 2023. It is now read-only.
With the current systemd service units deployed, mesos produced logs end up with "invalid-user" in the filename, and I believe I've seen that elsewhere. USER and GROUP aren't getting set on the mesos process's environment, which causes this behavior in glogs at least. Modifying to systemd unit to something like
[Service]
[...]
User=root
Group=root
fixes the problem. I'm noticing this problem on Ubuntu 16.04, where current log file names look like "mesos-{process}.{hostname}.invalid-user.log.{level}.{timestamp}". Making this change results in the user showing up as "root".
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
With the current systemd service units deployed, mesos produced logs end up with "invalid-user" in the filename, and I believe I've seen that elsewhere. USER and GROUP aren't getting set on the mesos process's environment, which causes this behavior in glogs at least. Modifying to systemd unit to something like
fixes the problem. I'm noticing this problem on Ubuntu 16.04, where current log file names look like "mesos-{process}.{hostname}.invalid-user.log.{level}.{timestamp}". Making this change results in the user showing up as "root".
The text was updated successfully, but these errors were encountered: