Skip to content

[BUG] Log spams crond output on DSM Container Manager #83

Closed as not planned
Closed as not planned
[BUG] Log spams crond output on DSM Container Manager#83
Labels
closed-issue-activityno-issue-activity

Description

@Laibalion
Laibalion
opened on Oct 4, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Every minute crond outputs what it is doing to the container log in DSM Conainter Manager via the stdout stream, cause the log to be flooded with useless information:

crond[152]: line /bin/bash /app/update.sh
--
crond[152]: file abc:
crond[152]: file root:
crond[152]: wakeup dt=60
crond[152]: line /bin/bash /app/update.sh
crond[152]: file abc:
crond[152]: file root:
crond[152]: wakeup dt=60
crond[152]: line /bin/bash /app/update.sh
crond[152]: file abc:
crond[152]: file root:
crond[152]: wakeup dt=60
crond[152]: line /bin/bash /app/update.sh
crond[152]: file abc:
crond[152]: file root:
crond[152]: wakeup dt=60
crond[152]: line /bin/bash /app/update.sh
crond[152]: file abc:
crond[152]: file root:
crond[152]: wakeup dt=41
crond[152]: user:abc entry:10 */3 * * * /bin/bash /app/update.sh
[ls.io-init] done.
crond[152]: user:abc entry:10 */3 * * * /bin/bash /app/update.sh
crond[152]: crond (busybox 1.37.0) started, log level 5
[custom-init] No custom files found, skipping...
 
───────────────────────────────────────
Build-date: 2025-10-02T08:39:25+00:00
Linuxserver.io version: 5.5.0-ls276
───────────────────────────────────────
User GID: 100
User UID: 1026
 
───────────────────────────────────────
GID/UID
───────────────────────────────────────
 
https://www.linuxserver.io/donate/
To support LSIO projects visit:
 
───────────────────────────────────────
Brought to you by linuxserver.io
 
╚══════╝╚══════╝╚═╝ ╚═════╝
███████╗███████║██║╚██████╔╝
██║ ╚════██║██║██║ ██║
██║ ███████╗██║██║ ██║
██║ ██╔════╝██║██╔═══██╗
██╗ ███████╗██╗ ██████╗
 
───────────────────────────────────────
[migrations] no migrations found
[migrations] started

I have no idea why it is doing this or how to stop crond from send it's wakeup behavior to stdout.

Expected Behavior

crond doesn't output its wakeup output to stdout.

Steps To Reproduce

Just start container and observe logs

Environment

- OS:DSM
- Synology Container Manager: search for linuxserver/docker-webgrabplus from registry, download and then run it with defaults (and setting proper PGID and PUID to match DSM user, mount data and config dirs, and setting TZ).

CPU architecture

x86-64

Docker creation

No idea, this is done by Synology DSM Container manager

Container logs

linuxserver-webgrabplus
date	stream	content
2025/10/04 10:25:00	stdout	crond[152]:  line /bin/bash /app/update.sh
2025/10/04 10:25:00	stdout	crond[152]: file abc:
2025/10/04 10:25:00	stdout	crond[152]: file root:
2025/10/04 10:25:00	stdout	crond[152]: wakeup dt=60
2025/10/04 10:24:00	stdout	crond[152]:  line /bin/bash /app/update.sh
2025/10/04 10:24:00	stdout	crond[152]: file abc:
2025/10/04 10:24:00	stdout	crond[152]: file root:
2025/10/04 10:24:00	stdout	crond[152]: wakeup dt=60
2025/10/04 10:23:00	stdout	crond[152]:  line /bin/bash /app/update.sh
2025/10/04 10:23:00	stdout	crond[152]: file abc:
2025/10/04 10:23:00	stdout	crond[152]: file root:
2025/10/04 10:23:00	stdout	crond[152]: wakeup dt=60
2025/10/04 10:22:00	stdout	crond[152]:  line /bin/bash /app/update.sh
2025/10/04 10:22:00	stdout	crond[152]: file abc:
2025/10/04 10:22:00	stdout	crond[152]: file root:
2025/10/04 10:22:00	stdout	crond[152]: wakeup dt=60
2025/10/04 10:21:00	stdout	crond[152]:  line /bin/bash /app/update.sh
2025/10/04 10:21:00	stdout	crond[152]: file abc:
2025/10/04 10:21:00	stdout	crond[152]: file root:
2025/10/04 10:21:00	stdout	crond[152]: wakeup dt=60
2025/10/04 10:20:00	stdout	crond[152]:  line /bin/bash /app/update.sh
2025/10/04 10:20:00	stdout	crond[152]: file abc:
2025/10/04 10:20:00	stdout	crond[152]: file root:
2025/10/04 10:20:00	stdout	crond[152]: wakeup dt=60
2025/10/04 10:19:00	stdout	crond[152]:  line /bin/bash /app/update.sh
2025/10/04 10:19:00	stdout	crond[152]: file abc:
2025/10/04 10:19:00	stdout	crond[152]: file root:
2025/10/04 10:19:00	stdout	crond[152]: wakeup dt=60
2025/10/04 10:18:00	stdout	crond[152]:  line /bin/bash /app/update.sh
2025/10/04 10:18:00	stdout	crond[152]: file abc:
2025/10/04 10:18:00	stdout	crond[152]: file root:
2025/10/04 10:18:00	stdout	crond[152]: wakeup dt=60
2025/10/04 10:17:00	stdout	crond[152]:  line /bin/bash /app/update.sh
2025/10/04 10:17:00	stdout	crond[152]: file abc:
2025/10/04 10:17:00	stdout	crond[152]: file root:
2025/10/04 10:17:00	stdout	crond[152]: wakeup dt=60
2025/10/04 10:16:00	stdout	crond[152]:  line /bin/bash /app/update.sh
2025/10/04 10:16:00	stdout	crond[152]: file abc:
2025/10/04 10:16:00	stdout	crond[152]: file root:
2025/10/04 10:16:00	stdout	crond[152]: wakeup dt=41
2025/10/04 10:16:00	stdout	crond[152]: user:abc entry:10 */3 * * * /bin/bash /app/update.sh
2025/10/04 10:15:19	stdout	[ls.io-init] done.
2025/10/04 10:15:19	stdout	crond[152]: user:abc entry:10 */3 * * * /bin/bash /app/update.sh
2025/10/04 10:15:19	stdout	crond[152]: crond (busybox 1.37.0) started, log level 5
2025/10/04 10:15:19	stdout	[custom-init] No custom files found, skipping...
2025/10/04 10:15:19	stdout	    
2025/10/04 10:15:19	stdout	───────────────────────────────────────
2025/10/04 10:15:19	stdout	Build-date: 2025-10-02T08:39:25+00:00
2025/10/04 10:15:19	stdout	Linuxserver.io version: 5.5.0-ls276
2025/10/04 10:15:19	stdout	───────────────────────────────────────
2025/10/04 10:15:19	stdout	User GID:    100
2025/10/04 10:15:19	stdout	User UID:    1026
2025/10/04 10:15:19	stdout	
2025/10/04 10:15:19	stdout	───────────────────────────────────────
2025/10/04 10:15:19	stdout	GID/UID
2025/10/04 10:15:19	stdout	───────────────────────────────────────
2025/10/04 10:15:19	stdout	
2025/10/04 10:15:19	stdout	https://www.linuxserver.io/donate/
2025/10/04 10:15:19	stdout	To support LSIO projects visit:
2025/10/04 10:15:19	stdout	
2025/10/04 10:15:19	stdout	───────────────────────────────────────
2025/10/04 10:15:19	stdout	   Brought to you by linuxserver.io
2025/10/04 10:15:19	stdout	
2025/10/04 10:15:19	stdout	      ╚══════╝╚══════╝╚═╝ ╚═════╝
2025/10/04 10:15:19	stdout	      ███████╗███████║██║╚██████╔╝
2025/10/04 10:15:19	stdout	      ██║     ╚════██║██║██║   ██║
2025/10/04 10:15:19	stdout	      ██║     ███████╗██║██║   ██║
2025/10/04 10:15:19	stdout	      ██║     ██╔════╝██║██╔═══██╗
2025/10/04 10:15:19	stdout	      ██╗     ███████╗██╗ ██████╗
2025/10/04 10:15:19	stdout	
2025/10/04 10:15:19	stdout	───────────────────────────────────────
2025/10/04 10:15:19	stdout	[migrations] no migrations found
2025/10/04 10:15:19	stdout	[migrations] started

Activity

  1. LinuxServer-CI
    added this to Issue & PR Trackeron Oct 4, 2025
  2. LinuxServer-CI
    moved this to Issues in Issue & PR Trackeron Oct 4, 2025

  3. github-actions commented on Oct 4, 2025

    @github-actions
    github-actionsbot
    on Oct 4, 2025 – with GitHub Actions

    Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

  4. Roxedus commented on Oct 4, 2025

    @Roxedus
    Roxedus
    on Oct 4, 2025
    Member

    This happens because something attaches a tty (-t, on docker run) to the container, this only gets logged to a tty.

  5. Laibalion commented on Oct 4, 2025

    @Laibalion
    Laibalion
    on Oct 4, 2025
    Author

    Hmmm, any idea how I can tell Container Manager to not start with -t ? I've never enabled this, and strangely other linuxserver.io images that I run (for example tvheadend) don't exhibit the issue. I've exported both in Container Manager and don't seen anything that would indicate it need to start interactive or not.

  6. LinuxServer-CI commented on Nov 3, 2025

    @LinuxServer-CI
    LinuxServer-CI
    on Nov 3, 2025
    Contributor

    This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

  7. LinuxServer-CI
    added
    no-issue-activity
    on Nov 3, 2025
  8. LinuxServer-CI
    added
    closed-issue-activity
    on Jan 3, 2026
  9. LinuxServer-CI
    closed this as not plannedon Jan 3, 2026
  10. LinuxServer-CI
    moved this from Issues to Done in Issue & PR Trackeron Jan 3, 2026

  11. LinuxServer-CI commented on Feb 2, 2026

    @LinuxServer-CI
    LinuxServer-CI
    on Feb 2, 2026
    Contributor

    This issue is locked due to inactivity

  12. linuxserver
    locked as resolved and limited conversation to collaborators on Feb 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    closed-issue-activityno-issue-activity

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions