cloud-init-output.log is increasing its size very quickly

[Aleksandra]

I use Linux machine on AWS EC2 instance with Red Hat Enterprise Linux 8.6 and my cloud-init-output.log is increasing its size very quickly causing my app logs to stop writing in one-two days even though I have 20GB of storage.

I changed logging level from default DEBUG to ERROR in /etc/cloud/cloud.cfg.d but it didn't help. Messages are also filling up fast.

I can see that app messages are written in cloud-init-output.log which is not something I want. Is there a way to turn it off?

/etc/cloud/cloud.cfg.d/05_logging.cfg is default.

[Scott Moser (smoser)]

Hi, thanks for taking the time to file a bug to help make cloud-init better.
Could you please run:

  cloud-init collect-logs

and attach the output.

Then once you've done that , set the 'Status' field back to 'New'.

Thanks.

[Aleksandra (algol30)]

Hi Scott,

Thanks for your reply.

Since this log would be from live system and as I can see it contains a lot
of info that I can not provide outside of the company, can you tell me what
exactly you need so I can maybe extract what you need to examine the issue?

Regards,
Aleksandra

On Mon, Jul 18, 2022 at 4:30 PM Scott Moser <email address hidden>
wrote:

> Hi, thanks for taking the time to file a bug to help make cloud-init
> better.
> Could you please run:
>
> cloud-init collect-logs
>
> and attach the output.
>
> Then once you've done that , set the 'Status' field back to 'New'.
>
> Thanks.
>
> ** Changed in: cloud-init
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1981960
>
> Title:
> cloud-init-output.log is increasing its size very quickly
>
> Status in cloud-init:
> Incomplete
>
> Bug description:
> I use Linux machine on AWS EC2 instance with Red Hat Enterprise Linux
> 8.6 and my cloud-init-output.log is increasing its size very quickly
> causing my app logs to stop writing in one-two days even though I have
> 20GB of storage.
>
> I changed logging level from default DEBUG to ERROR in
> /etc/cloud/cloud.cfg.d but it didn't help. Messages are also filling
> up fast.
>
> I can see that app messages are written in cloud-init-output.log which
> is not something I want. Is there a way to turn it off?
>
> /etc/cloud/cloud.cfg.d/05_logging.cfg is default.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-init/+bug/1981960/+subscriptions
>
>

--
--
------------------------------------------------------
Aleksandra Golubovic

Be the change you wish to see in the world

[Chad Smith (chad.smith)]

Aleksandra (algol30) generally cloud-init should not be emitting debug logs with a frequency that impacts your system in "one-two days". This points to something unexpected in the environment that logs would help us better understand. Ultimately, we want to understand what types of potentially repeated events seem to be saturating your logs.

  We may be able to get to that understanding a bit with some of the following:

  1. cloud-init --version
  2. cloud-nit status --long
  3. Are there repeated logs/tracebacks that seem to keep happening on the system (a bunch of failed retries/hotplug being enabled?
  4. cloud-init analyze show (Tells us how many boot events cloud-init has gone through on the system
  5. sudo cloud-init query --all (Note you will have to manually look through this JSON output specifically under the keys "ds" "merged_cfg" "vendordata", "userdata" to make sure you can change any securiry sensitive fields or passwords to REDACTED.

[Launchpad Janitor (janitor)]

[Expired for cloud-init because there has been no activity for 60 days.]

[James Falcon (falcojr)]

Tracked in Github Issues as https://github.com/canonical/cloud-init/issues/4000