Ruben Safir wrote:

On Thu, Nov 05, 2015 at 09:47:54PM +0100, Carlos E. R. wrote:

...

On 2015-11-05 20:21, Ruben Safir wrote:

...

where did the postfix mail log files go?

They have not gone anywhere. That is, they go to wherever syslog goes, which by default now means systemd journal.

Alternatively, install a traditional syslog daemon.

For some reason, postfix stopped logging on Oct 30th and I have ZERO idea why. The enties in jounalctl and the log was identical. I tried restarting everything through systemctl, no change

I upgraded postfix, no change I upgraded rsyslog and it is working now.

Is it a bug or a hack?

I have seen similar issues where I have had to restart syslog-ng. In my cases, it's been just on just one system and I suspect hardware issues. -- Per Jessen, Zürich (12.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Friday 06 Nov 2015 15:23:07 Ruben Safir wrote:

On 11/06/2015 04:00 AM, Per Jessen wrote:

...

Ruben Safir wrote:

...

On Thu, Nov 05, 2015 at 09:47:54PM +0100, Carlos E. R. wrote:

...

On 2015-11-05 20:21, Ruben Safir wrote:

...

where did the postfix mail log files go?

They have not gone anywhere. That is, they go to wherever syslog goes, which by default now means systemd journal.

Alternatively, install a traditional syslog daemon.

For some reason, postfix stopped logging on Oct 30th and I have ZERO idea why. The enties in jounalctl and the log was identical. I tried restarting everything through systemctl, no change

I upgraded postfix, no change I upgraded rsyslog and it is working now.

Is it a bug or a hack?

I have seen similar issues where I have had to restart syslog-ng. In my cases, it's been just on just one system and I suspect hardware issues.

I couldn't restart it, I had to upgrade the rsyslog and postfix. It was logging through systemd, evidently from the jounralctl record

Is systemd venerable? Not sure what you mean with that question. I think that the latest versions of syslog-ng and rsyslog have been upgraded to extract log records from journald files by themselves, its no longer important to configure journald.conf to forward logs to syslog. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Op vrijdag 6 november 2015 14:08:13 schreef John Andersen:

On 11/6/2015 1:54 PM, ianseeks wrote:

...

Not sure what you mean with that question. I think that the latest versions of syslog-ng and rsyslog have been upgraded to extract log records from journald files by themselves, its no longer important to configure journald.conf to forward logs to syslog.

Since when? What release? I have no syslogs in /var/log but 488 megs of binry journals in /var/log/journal (OS 13.2)

I just use journalctl to view logs, which seems sufficient for my purposes. Is it safe to just delete some of these older journals? or is there a process for that somewhere?

You can change /etc/systemd/journald.conf to limit the amount of space used on disk and temporary storage. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 11/06/2015 02:31 PM, Patrick Shanahan wrote:

* John Andersen [11-06-15 17:10]:

...

On 11/6/2015 1:54 PM, ianseeks wrote:

...

Not sure what you mean with that question. I think that the latest versions of syslog-ng and rsyslog have been upgraded to extract log records from journald files by themselves, its no longer important to configure journald.conf to forward logs to syslog.

Since when? What release? I have no syslogs in /var/log but 488 megs of binry journals in /var/log/journal (OS 13.2)

Only because you haven't install one of the syslogs.

Which is true because i neither need nor want any of the syslogs. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Friday 06 Nov 2015 14:08:13 John Andersen wrote:

On 11/6/2015 1:54 PM, ianseeks wrote:

...

Not sure what you mean with that question. I think that the latest versions of syslog-ng and rsyslog have been upgraded to extract log records from journald files by themselves, its no longer important to configure journald.conf to forward logs to syslog.

Since when? What release? I have no syslogs in /var/log but 488 megs of binry journals in /var/log/journal (OS 13.2) Not sure when or if opensuse has implemented the correct versions, it was a comment made by LP that the ForwardtoSyslog is becoming irrelevant, unfortunately i didn't note where it was made but i think it was a systemd mailing list. I did a quick search for additional info and got these links. http://www.rsyslog.com/doc/v8-stable/configuration/modules/imjournal.html https://www.balabit.com/sites/default/files/documents/syslog-ng-ose-latest-g...

I just use journalctl to view logs, which seems sufficient for my purposes. Is it safe to just delete some of these older journals? or is there a process for that somewhere?

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-11-06 23:58, Ruben Safir wrote:

On 11/06/2015 04:54 PM, ianseeks wrote:

...

...

Is systemd venerable? Not sure what you mean with that question. is there a security hole is systemd...

None known. I guess you intended to write "vulnerable", not "venerable". - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlY9Oe0ACgkQja8UbcUWM1zKGwEAgvjvcQPlPLp+swUkovsgmsTU 6XIyjnfMRdeOJpi3YdIA/ilnwWkVn3osSyjtKmmdbnkuoYGhpde8V4YM4N/tZfrq =A9uL -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org