[systemd-devel] character limit by using "/run/systemd/journal/syslog"
HI all, I'm not sure if it's systemd/journald issue, but maybe you can help me. We're logging apache error logs with "logger" so we can write them to specific file using rsyslog, if I run "logger" without any options - all are duplicated in journald and I can see them in "journalctl" overview what is no needed, I can tell "logger" to write to "/run/systemd/journal/syslog" directly and then I don't see them in journalctl but the logs are trimmed (about 437 characters what is strange number). So I don't understand if it's a "logger" bug or somehow related to journald or even rsyslog. Full option from apache config. ErrorLog "| /usr/bin/logger -p local1.info --socket /run/systemd/journal/syslog" Best, Stan ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Best approach to run python service in virtualenv with systemd
Hi all, I'm trying to run kallithea using virtualenv, it kinda works (I can stop/start service) with this unit file [Unit] Description=Start Kallithea service After=network.target [Service] Type=forking User=kallithea WorkingDirectory=/srv/kallithea ExecStart=/srv/kallithea/venv/bin/python2 /srv/kallithea/venv/bin/paster serve --daemon --pid-file=/srv/kallithea/kallithea.pid --log-file=/srv/kallithea/kallithea.log my.ini PIDFile=/srv/kallithea/kallithea.pid [Install] WantedBy=multi-user.target # but I always see "Failed to read PID from file /srv/kallithea/kallithea.pid: Invalid argument" in "systemctl status", I know that "PIDFile" option isn't a best practice and should be avoided, but withou it service doesn't running. Is there any better methods to run it or at least remove this pid error message? Thanks, Stan ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Don't log "logger" messages in to journald
Hi all, We have bunch of webservers, where we use "logger" to send apache access logs to remote rsyslog, unfortunately these access logs are landing in journald too. As we have a lot of requests it's pretty unusable to use "journalct" to show system logs. Is there a way to tell journald do not log "logger" messages or at least not to show them in "journalct" output? I'm using systemd 215 on Debian Jessie. Best, Stan ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
