Skip to content

.err logs have no timestamp #12887

Closed
Task
#12967
Closed
.err logs have no timestamp#12887
Task
#12967
Assignees
dheeraj12347
Labels
type:enhancement
Milestone
4.20.4

Description

@daviftorres
daviftorres
opened on Mar 25, 2026

The required feature described as a wish

It is very hard to troubleshoot by looking at the .err files of management server, agent, or usage if they do not have timestamps.

Activity

  1. github-actions
    added
    enhancement
    on Mar 25, 2026

  2. github-actions commented on Mar 25, 2026

    @github-actions
    github-actionsBot
    on Mar 25, 2026 – with GitHub Actions

    🏷️ Issue Triaged

    Hi @daviftorres! I've categorized this issue as enhancement based on the following analysis:

    Reasoning: This request improves existing logging functionality by adding timestamps to .err files, making troubleshooting easier. It enhances the observability of the system rather than fixing a broken feature.

    View Triage Details

    Analysis

    • Keywords detected: "feature", "wish", "troubleshoot", ".err files", "timestamps"
    • Issue type indicators: Request for improved logging capabilities in existing error log files (management server, agent, usage)
    • Confidence: High

    Recommended Next Steps

    • Consider implementing timestamps in a consistent format across all .err log files
    • Evaluate if this should apply to other log files as well for consistency
    • This could be a good opportunity to standardize logging format across CloudStack components

    References: Triage run §23546481442

    Generated by Issue Triage Agent

    To install this workflow, run gh aw add github/gh-aw/.github/workflows/issue-triage-agent.md@94662b1dee8ce96c876ba9f33b3ab8be32de82a4. View source at https://github.com/github/gh-aw/tree/94662b1dee8ce96c876ba9f33b3ab8be32de82a4/.github/workflows/issue-triage-agent.md.

  3. dheeraj12347 commented on Mar 26, 2026

    @dheeraj12347
    dheeraj12347
    on Mar 26, 2026
    Contributor

    Hi, I’d like to work on this.

    I plan to identify where .err logs are generated (management server, agent, usage) and ensure timestamps are consistently included in the logging output.

    Please let me know if there are any preferred logging formats or existing configurations I should follow.

  4. daviftorres commented on Mar 26, 2026

    @daviftorres
    daviftorres
    on Mar 26, 2026
    ContributorAuthor

    Dear @dheeraj12347, thank you for volunteering to help so quickly.

    I’m not a developer, so I may not be able to give detailed instructions. However, I suggest following the same format used for the .log file and applying it to the .err file.

    Regards,

  5. DaanHoogland
    added this to the 4.20.4 milestone on Mar 30, 2026
  6. DaanHoogland
    assigned
    dheeraj12347
    on Apr 1, 2026
  7. DaanHoogland
    added the
    Task
    issue type on Apr 1, 2026

  8. dheeraj12347 commented on Apr 6, 2026

    @dheeraj12347
    dheeraj12347
    on Apr 6, 2026
    Contributor

    Hi all,
    I’ve opened PR #12967 to address this issue by adding %d{DEFAULT} timestamps to the CONSOLE appenders in the management server, client and agent log4j-cloud.xml.in files, so that .err logs now follow the same timestamped pattern as the .log files.

    This replaces my earlier PR #12896, which had unrelated changes. The new PR is limited to just the three logging config files.

    When you have a moment, could you please review PR #12967 and let me know if any further adjustments are needed?

  9. DaanHoogland
    added this to Apache CloudStack BugFest - Issueson May 13, 2026
  10. DaanHoogland
    moved this to Dev In Progress in Apache CloudStack BugFest - Issueson May 13, 2026

  11. github-actions commented on Aug 5, 2026

    @github-actions
    github-actionsBot
    on Aug 5, 2026 – with GitHub Actions

    This issue is stale because it has been open for 120 days with no activity. It may be removed by administrators of this project at any time. Remove the stale label or comment to request for removal of it to prevent this.

  12. github-actions
    added
    no-issue-activity
    on Aug 5, 2026

  13. DaanHoogland commented on Aug 5, 2026

    @DaanHoogland
    DaanHoogland
    on Aug 5, 2026
    Contributor

    @daviftorres any chance to tst/review the PR? it’s getting orphaned a bit.

  14. github-actions
    removed
    no-issue-activity
    on Aug 6, 2026

  15. davift commented on Aug 7, 2026

    @davift
    davift
    on Aug 7, 2026

    @daviftorres any chance to tst/review the PR? it’s getting orphaned a bit.

    Hey @DaanHoogland, I could use some guidance on how to compile and run CloudStack with the changes that @dheeraj12347 introduced in #12967.

    I'm also wondering how I can intentionally trigger a few errors so I can see how they appear in the error logs now that they include timestamps.

  16. dheeraj12347 commented on Aug 8, 2026

    @dheeraj12347
    dheeraj12347
    on Aug 8, 2026
    Contributor

    @daviftorres any chance to tst/review the PR? it’s getting orphaned a bit.

    Hey @DaanHoogland, I could use some guidance on how to compile and run CloudStack with the changes that @dheeraj12347 introduced in #12967.

    I'm also wondering how I can intentionally trigger a few errors so I can see how they appear in the error logs now that they include timestamps.

    Hi @daviftorres , sure.

    For a quick build from the PR branch, you can use:

    mvn -pl server -am -DskipTests compile

    That should be enough to verify that the Management Server side compiles. For actually checking the .err output, you’ll need a running CloudStack environment with the changes from #12967 applied.

    The main thing to verify is that an ERROR-level message written to stderr appears in the corresponding .err file with a timestamp, similar to the format already used in the .log files. The PR also adds the same handling for the Usage server.

    For triggering an error, I don't want to suggest a specific operation without knowing which CloudStack setup you're using, since the easiest way to reproduce an ERROR depends on the environment/configuration.

    If you let me know whether you're testing with a local development setup, simulator, or an existing CloudStack installation, I can suggest a more specific way to test it.

  17. daviftorres commented on Aug 12, 2026

    @daviftorres
    daviftorres
    on Aug 12, 2026
    ContributorAuthor

    The compilations failed, but it could be an incompetence from my side. I can't say.

    [INFO] Reactor Summary for Apache CloudStack 4.23.0.0-SNAPSHOT:
[INFO]
[INFO] Apache CloudStack Developer Tools - Checkstyle Configuration SUCCESS [  0.229 s]
[INFO] Apache CloudStack .................................. SUCCESS [  0.349 s]
[INFO] Apache CloudStack Framework - Managed Context ...... SUCCESS [  0.911 s]
[INFO] Apache CloudStack Framework ........................ SUCCESS [  0.037 s]
[INFO] Apache CloudStack Framework - Certificate Authority  SUCCESS [  0.119 s]
[INFO] Apache CloudStack Utils ............................ SUCCESS [  8.753 s]
[INFO] Apache CloudStack Framework - Database ............. SUCCESS [  4.069 s]
[INFO] Apache CloudStack Framework - Configuration ........ SUCCESS [  2.040 s]
[INFO] Apache CloudStack Framework - Direct Download to Primary Storage SUCCESS [  1.330 s]
[INFO] Apache CloudStack API .............................. SUCCESS [ 13.824 s]
[INFO] Apache CloudStack Framework - REST ................. SUCCESS [  1.358 s]
[INFO] Apache CloudStack Framework - IPC .................. SUCCESS [  2.188 s]
[INFO] Apache CloudStack Cloud Engine ..................... SUCCESS [  0.017 s]
[INFO] Apache CloudStack Cloud Engine API ................. SUCCESS [  2.191 s]
[INFO] Apache CloudStack Cloud Engine Schema Component .... SUCCESS [ 14.815 s]
[INFO] Apache CloudStack Framework - Security ............. SUCCESS [  1.812 s]
[INFO] Apache CloudStack Core ............................. SUCCESS [  5.278 s]
[INFO] Apache CloudStack Framework - Clustering ........... SUCCESS [  2.204 s]
[INFO] Apache CloudStack Framework - Event Notification ... SUCCESS [  1.431 s]
[INFO] Apache CloudStack Framework - Jobs ................. SUCCESS [  2.744 s]
[INFO] Apache CloudStack Cloud Engine Internal Components API SUCCESS [  2.278 s]
[INFO] Apache CloudStack Agent Management Servers Load Balancer SUCCESS [  0.604 s]
[INFO] Apache CloudStack Framework - Storage Config Drive Component SUCCESS [  1.871 s]
[INFO] Apache CloudStack Framework - Extensions ........... SUCCESS [  2.614 s]
[INFO] Apache CloudStack Server ........................... FAILURE [  1.503 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:15 min
[INFO] Finished at: 2026-08-12T15:50:42-04:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project cloud-server: Could not resolve dependencies for project org.apache.cloudstack:cloud-server:jar:4.23.0.0-SNAPSHOT
[ERROR] dependency: org.apache.cloudstack:cloud-api:jar:tests:4.23.0.0-SNAPSHOT (test)
[ERROR]         Could not find artifact org.apache.cloudstack:cloud-api:jar:tests:4.23.0.0-SNAPSHOT in repo.jenkins-ci.org.public (https://repo.jenkins-ci.org/public/)
[ERROR]         Could not find artifact org.apache.cloudstack:cloud-api:jar:tests:4.23.0.0-SNAPSHOT in libvirt.org.maven2 (https://libvirt.org/maven2/)
[ERROR]         Could not transfer artifact org.apache.cloudstack:cloud-api:jar:tests:4.23.0.0-SNAPSHOT from/to maven-default-http-blocker (http://0.0.0.0/): Blocked mirror for repositories: [apache.snapshots (http://repository.apache.org/snapshots, default, snapshots)]
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :cloud-server

    I do not feel qualified to review the code, and I do not know how to how to trigger any error.

  18. DaanHoogland commented on Aug 13, 2026

    @DaanHoogland
    DaanHoogland
    on Aug 13, 2026
    Contributor

    @davift do you have a policy to block http://repository.apache.org/snapshots for package retrieval (or in general to browse to)?

  19. davift commented on Aug 13, 2026

    @davift
    davift
    on Aug 13, 2026

    @davift do you have a policy to block http://repository.apache.org/snapshots for package retrieval (or in general to browse to)?

    No policy or filter could block access to anything. I ran the build from an instance attached directly to the edge router with direct internet access. Does that answer your question?

  20. DaanHoogland commented on Aug 14, 2026

    @DaanHoogland
    DaanHoogland
    on Aug 14, 2026
    Contributor

    Blocked mirror for repositories: [apache.snapshots (http://repository.apache.org/snapshots, default, snapshots)]

    unfortunately

    No policy or filter could block access to anything. I ran the build from an instance attached directly to the edge router with direct internet access. Does that answer your question?

    No, it doesn’t.

    maybe there is a m2 configuration off? can you check that?

  21. DaanHoogland
    added
    type:enhancement
    and removed
    enhancement
    on Sep 5, 2026
  22. kiranchavala
    closed this as completedin #12967on Sep 9, 2026
  23. github-project-automation
    moved this from Dev In Progress to Done in Apache CloudStack BugFest - Issueson Sep 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

type:enhancement

Type

Task

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions