Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • E eos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • erlends-os
  • eos
  • Issues
  • #3

Closed
Open
Created Mar 20, 2019 by Erlend Sveen@erlendjsOwner

Failure after long uptimes

Could be a network issue, it used to be that a single program may block/clog the network if it does not read messages. This has been fixed, but some problems are still there. Sometimes restarting the network protocol translator on the Raspberry Pi solves the problem, other times it does not seem to solve it.

So far, the meter program on the power meter continues to refresh data, it does not look like a total lockup.

Edited Feb 29, 2020 by Erlend Sveen
Assignee
Assign to
Time tracking