Control: retitle -1 syslog-ng: Remove dangling syslog.service symlink in preinst
Control: tag -1 help
The same dance will need to be done for syslog-ng-core (which ships
syslog-ng.service) that rsyslog will be doing (see #741496). It's
blocked until the proper steps to do the syslog.service transf
Am 05.09.2014 02:29, schrieb Michael Biebl:
> Please purge the rsyslog and syslog-ng package and make sure any
> dangling /etc/systemd/system/syslog.service* symlinks are removed.
You might also need to purge the syslog-ng-core package. Not quite sure
which of the syslog-ng* packages ships the sys
reassign 760426 syslog-ng-core
thanks
Am 05.09.2014 01:42, schrieb Vedran Furač:
> On 05.09.2014 01:09, Michael Biebl wrote:
>> Am 05.09.2014 00:59, schrieb Michael Biebl:
>>
>>> Apparently your syslog socket unit fails to start. Why is not clear yet.
>>> As said, please provide a complete debug
On 05.09.2014 01:09, Michael Biebl wrote:
> Am 05.09.2014 00:59, schrieb Michael Biebl:
>
>> Apparently your syslog socket unit fails to start. Why is not clear yet.
>> As said, please provide a complete debug log for the boot.
>
> Please also attache the output of
> ls -la /etc/systemd/system/sy
Am 05.09.2014 00:59, schrieb Michael Biebl:
> Apparently your syslog socket unit fails to start. Why is not clear yet.
> As said, please provide a complete debug log for the boot.
Please also attache the output of
ls -la /etc/systemd/system/syslog.service
--
Why is it that all of the instrume
Am 05.09.2014 00:52, schrieb Vedran Furač:
> So apparently rsyslog wasn't started on boot. I assumed this is
> intentional since journal would take its job.
Nope, this is not intentional. rsyslog should run just fine alongside
the journal.
>
>> Can you please reboot, add "systemd.log_level=debu
On 04.09.2014 23:38, Michael Biebl wrote:
> Am 04.09.2014 23:07, schrieb Vedran Furač:
>
> Well, something or someone stopped the rsyslog service on Sep 4
> 22:38:09. So it's obvious you don't get anymore updates to
> /var/log/syslog. Now we need to find out, why rsyslog.service (and
> syslog.soc
Am 04.09.2014 23:07, schrieb Vedran Furač:
> # logger -t TEST 1234
> # tail -1 /var/log/syslog
> Sep 4 22:38:09 hostname rsyslogd: [origin software="rsyslogd"
> swVersion="8.4.0" x-pid="2886" x-info="http://www.rsyslog.com";] exiting
> on signal 15.
>
> # journalctl --system|tail -1
> Ruj 04 22:
Hey, thanks for quick reply!
On 04.09.2014 02:18, Michael Biebl wrote:
> Am 04.09.2014 um 02:07 schrieb Vedran Furač:
>> Package: systemd
>> Severity: important
>>
>> By documentation I mean:
>>
>> - Package description (mentions that it replaces sysvinit only)
>> - README.Debian
>> - wiki.debian.
Am 04.09.2014 um 02:07 schrieb Vedran Furač:
> Package: systemd
> Severity: important
>
> Few days ago I noticed /var/log/syslog was empty. After some time I
> found out that this is due to systemd. However, I wasn't warned that
> replacing init system will silently break my logs, nor was this
> m
Package: systemd
Severity: important
Few days ago I noticed /var/log/syslog was empty. After some time I
found out that this is due to systemd. However, I wasn't warned that
replacing init system will silently break my logs, nor was this
mentioned in documentation. By documentation I mean:
- Pack
11 matches
Mail list logo
