Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • NetworkManager NetworkManager
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 164
    • Issues 164
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 18
    • Merge requests 18
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • NetworkManagerNetworkManager
  • NetworkManagerNetworkManager
  • Issues
  • #1041
Closed
Open
Issue created Jun 23, 2022 by Jonathan Kang@jonathankang

connectivity: system resolver returned no usable IPv4 addresses

Using latest openSUSE Tumbleweed with NM 1.38.2. Sometimes on startup, NM won't reach connected_global state due to failed connectivity check. And the limited connectivity remains till a reboot or restart of NetworkManager.service.

Suspicious logs:

connectivity: (enp1s0,IPv4,7) system resolver returned no usable IPv4 addresses

It looks like g_resolver_lookup_by_name_async() didn't return an IPv4 address somehow. Any idea on this?

Full journalctl -b -u NetworkManager attched. failed-journal

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking