Início / computer / Perguntas / 1427311
Accepted
nelaaro
Asked: 2019-04-20 01:31:03 +0800 CST

A ativação via systemd falhou para a unidade 'dbus-org.freedesktop.resolve1.service': Unidade dbus-org.freedesktop.resolve1.service não encontrada

  • 772

Estou usando manjaro / arch linux e vejo as seguintes mensagens de erro no log do sistema.

journalctl -f 
...
dbus-daemon[798]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.4' (uid=0 pid=799 comm="/usr/bin/>
dbus-daemon[798]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
...

Como faço para corrigir esse problema

linux dns

1 respostas

  1. Best Answer

    Este problema está relacionado com o network-managere systemd-resolved.service.

    Depois de ler os fóruns do manjaro e o arch wiki

    Você tem 2 opções

    configurar o gerenciador de rede para não usar o systemd-resolved.service

    vim /etc/NetworkManager/conf.d/no-systemd-resolved.conf

    Com este conteúdo:

    [main]
systemd-resolved=false

    Ative e use systemd-resolved.service

    verifique se está em execução e ativado

    systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
  Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled)
  Active: inactive (dead)
    Docs: man:systemd-resolved.service(8)
          https://www.freedesktop.org/wiki/Software/systemd/resolved
          https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
          https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients

    Habilite e inicie-o.

    systemctl enable systemd-resolved.service
Created symlink /etc/systemd/system/dbus-org.freedesktop.resolve1.service → /usr/lib/systemd/system/systemd-resolved.service.
Created symlink /etc/systemd/system/multi-user.target.wants/systemd-resolved.service → /usr/lib/systemd/system/systemd-resolved.service.
systemctl start systemd-resolved.service
systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
  Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
  Active: active (running) since Fri 2019-04-19 10:36:53 SAST; 32min ago
    Docs: man:systemd-resolved.service(8)
          https://www.freedesktop.org/wiki/Software/systemd/resolved
          https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
          https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Main PID: 21150 (systemd-resolve)
  Status: "Processing requests..."
    Tasks: 1 (limit: 4915)
  Memory: 5.0M
  CGroup: /system.slice/systemd-resolved.service
          └─21150 /usr/lib/systemd/systemd-resolved

    Isso resolveu os erros que surgiam nos logs.

    • 59

relate perguntas