marcin
Configure log directory for Phoenix app
Hello!
I’m deploying my Phoenix app using mix_systemd package, to run it as systemd unit file. The app’s runtime is in /srv/appname/current,
Problem: The app tries to create log files under /srv/appname/current/log/error.log and /srv/appname/current/console.log. I would like to configure it to create the log files under /var/log/appname.
I have no idea where this file creation comes from. My configuration does not contain logging to files:
Application.get_env :logger, :backends
[:console, Sentry.LoggerBackend]
Despite this, I’m getting these errors and the process crashes:
Jul 22 17:18:50 steinem proca[102362]: 17:18:50.230 [error] Failed to open log file log/error.log with error permission denied
Jul 22 17:18:50 steinem proca[102362]: 17:18:50.231 [error] Failed to open log file log/console.log with error permission denied
I do not know which elixir module emits these errors (no traceback). Is this some “standard” behaviour for releases? How can I control it?
Marked As Solved
marcin
… oh actually I can!
I spot lager library:
deps/lager/src/lager_file_backend.erl
131: ?INT_LOG(error, "Failed to open log file ~ts with error ~s", [Name, file:format_error(Reason)]),
692: "Failed to open log file " ++ TestLog ++ " with error permission denied",
739: "Failed to open log file " ++ TestLog ++ " with error permission denied",
lets investigate…
So lager is an erlang logger library pulled in by rabbitmq client package.
It needs to be configured in one of compiled config files, so config.exs or prod.exs for instance:
config :lager,
log_root: '/var/log/appname'
Also Liked
LostKobrakai
Starting a release as daemon will make it write logs to disk by default (as nobody is watching stdout). Your path doesn’t match that default though.
LostKobrakai
I’d also look if you actually need lager. It’s been replaced in recent versions by erlangs :logger and the integration of it into elixir.
hauleth
In the case of @marcin it is dependency of dependency (RabbitMQ). Hopefully in future lager will also be backed by logger so there will be only one place to configure logging (but we still will need to find a way to configure logger in development, but that is discussion for some other time).
Popular in Questions
Other popular topics
Latest on Elixir Forum
Sponsor Spotlight
Producing high quality Elixir screencasts since 2017.
Categories:
Sub Categories:
Forums
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Producing high quality Elixir screencasts since 2017.
Enabling companies to succeed by building software people love.
The deployment platform built for Elixir: PaaS ease, VPS control.
Courses that'll move you from confusion to "Aha, now I get it!"