[systemd-devel] journal-upload returning error by default

[Umut Tezduyar Lindskog]

Thanks for the answer.

I am more worried about the "failed" service entry on output of
systemctl. Maybe best not to fail if no configuration is set?

BTW, I figured out to disable it with --disable-libcurl (for now since
libcurl is only used by journal upload tool).

Umut

On Wed, Sep 24, 2014 at 2:56 PM, Zbigniew Jędrzejewski-Szmek
<zbyszek at in.waw.pl> wrote:
> On Tue, Sep 23, 2014 at 10:36:20AM +0200, Umut Tezduyar Lindskog wrote:
>> Hi,
>>
>> I am a bit confused about the service as it returns with error on systemd 216:
>>
>> ● systemd-journal-upload.service - Journal Remote Upload Service
>>    Loaded: loaded (/etc/systemd/system/systemd-journal-upload.service; enabled)
>>    Active: failed (Result: exit-code) since Sun 2006-10-01 06:34:59
>> GMT; 29min ago
>>   Process: 1712 ExecStart=/usr/lib/systemd/systemd-journal-upload
>> --save-state (code=exited, status=1/FAILURE)
>>  Main PID: 1712 (code=exited, status=1/FAILURE)
>>
>> [root at axis-00408cffffff /]2731#
>> /usr/lib/systemd/systemd-journal-upload --save-state
>> Required --url/-u option missing.
>>
>> So, the --url option is not optional but even the service,
>> systemd-journal-upload.service doesn't send the URL option.
>>
>> Looking further at the code, I can see that url option can be parsed
>> out from journal-upload.config but even the default
>> journal-upload.conf doesn't have anything for URL=.
>>
>> I haven't seen any change to this since v216. This service is enabled
>> by default but returns error by default. I am a bit confused, am I
>> missing something?
> This seems to be insufficiently documented. I'll try to make the man
> page and the messages clearer. Basically, systemd-journal-upload needs
> to be told where to upload the messages, it has now way of guessing. In
> addition, additional manual configuration is recommended, to set up
> a secure channel over https. So unfortunately it is not possible to
> make it work out of the box.
>
>> Also, I do not have microhttp and this binary/service is
>> built/installed anyways.
> To build it, µhttpd devel headers are necessary. You must have them
> since otherwise the build would fail. µhttp is just a library.
>
> Zbyszek