You are not logged in.

#1 2021-02-18 09:28:46

linerman
Member
Registered: 2021-02-16
Posts: 8

proper reading of journal warning

Hi,

During reading warning messages, I have noticed that my journal is flooded with :

daemon/network[650]: manager_device.go:438: failed to get interface info: route ip+net: no such network interface 

Every second, same warning appears.

Is this warning a thing to worry about?

If yes, then I assume there is something wrong with my network configuration, although I think my net is working properly.
(enabled and active services: network-manager; systemd-resolved; wpa_supplicant)

I use mainly ethernet, and from time to time I switch to wi-fi

03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7850
        Flags: bus master, fast devsel, latency 0, IRQ 33
        I/O ports at d000 [size=256]
        Memory at f7200000 (64-bit, non-prefetchable) [size=4K]
        Memory at e2800000 (64-bit, prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: r8168
        Kernel modules: r8169, r8168

06:00.0 Network controller: Broadcom Inc. and subsidiaries Device 43c3 (rev 04)
        Subsystem: ASUSTeK Computer Inc. Device 86fb
        Flags: bus master, fast devsel, latency 0, IRQ 35
        Memory at f7000000 (64-bit, non-prefetchable) [size=32K]
        Memory at f6800000 (64-bit, non-prefetchable) [size=8M]
        Memory at e2400000 (64-bit, prefetchable) [size=4M]
        Capabilities: <access denied>
        Kernel driver in use: brcmfmac
        Kernel modules: brcmfmac

Offline

#2 2021-02-18 13:13:10

seth
Member
Registered: 2012-09-03
Posts: 18,895

Re: proper reading of journal warning

https://github.com/linuxdeepin/dde-daemon/issues/175

I assume there is something wrong with my network configuration

Alternatively, there's something wrong with deepin…

Offline

#3 2021-02-18 14:15:59

loqs
Member
Registered: 2014-03-06
Posts: 12,987

Re: proper reading of journal warning

Offline

#4 2021-02-22 15:48:32

linerman
Member
Registered: 2021-02-16
Posts: 8

Re: proper reading of journal warning

seth wrote:

Alternatively, there's something wrong with deepin…

You're right!

logs wrote:

You could locally remove https://github.com/linuxdeepin/dde-daem … ce.go#L438

That script looks old, and have some broken links to download to.
Nowhere to find newer versions.

Also, I think that if it is included in dde-daemon, it should work with the newest version I have installed. But it is not...

Offline

#5 2021-02-22 16:15:12

seth
Member
Registered: 2012-09-03
Posts: 18,895

Re: proper reading of journal warning

This is the current git master:
https://github.com/linuxdeepin/dde-daem … ce.go#L455

But I assume this is some compiled binary, check the process binary for the PID (650 in your OP, but oc. this might now be different)

Offline

#6 2021-02-22 20:00:31

loqs
Member
Registered: 2014-03-06
Posts: 12,987

Re: proper reading of journal warning

If deepin-daemon 5.12.0.18-1 still has the issue you could try the following,  which requires base-devel and git

git clone git://git.archlinux.org/svntogit/community.git --single-branch --branch "packages/deepin-daemon"
cd community/trunk/

Edit PKGBUILD as below

diff --git a/trunk/PKGBUILD b/trunk/PKGBUILD
index ed38a4c..3d0cdc2 100644
--- a/trunk/PKGBUILD
+++ b/trunk/PKGBUILD
@@ -48,6 +48,7 @@ prepare() {
          golang.org/x/xerrors github.com/mattn/go-sqlite3 github.com/fsnotify/fsnotify github.com/godbus/dbus
 
   sed -i 's#/usr/share/backgrounds/default_background.jpg#/usr/share/backgrounds/deepin/desktop.jpg#' accounts/user.go
+  sed -i '/logger.Warning("failed to get interface info:", err)/d' network/manager_device.go
 }
 
 build() {

Then

makepkg -rsi

See Makepkg for more details.

Last edited by loqs (2021-02-22 20:45:35)

Offline

#7 2021-02-23 08:46:17

linerman
Member
Registered: 2021-02-16
Posts: 8

Re: proper reading of journal warning

Thank you for the commitment to solve the issue.

seth wrote:

But I assume this is some compiled binary, check the process binary for the PID (650 in your OP, but oc. this might now be different)

I checked that script, but still it is connected to some gitub files which do not exist anymore.

Anyway, I killed the process, but it was only for a minute. After that it has started again under different PID.


logs wrote:

If deepin-daemon 5.12.0.18-1 still has the issue

Yes, I upgraded again the daemon (second upgrade of the file in 3 days), but the issue is unresolved.

logs wrote:

Edit PKGBUILD as below

I am not good at editing PKGBUILD files.
Am I supposed to add it to "prepare" section or swap existing "prepare" section?
Also should I add command git diff before diff --git ?

Offline

#8 2021-02-23 10:17:49

loqs
Member
Registered: 2014-03-06
Posts: 12,987

Re: proper reading of journal warning

You would add the line with the + to the the prepare function so it becomes:

prepare() {
  cd dde-daemon-$pkgver
  patch -p1 -i ../$pkgname-fix-vanilla-libinput.patch

  export GOPATH="$srcdir/build:/usr/share/gocode"

  # golang-deepin-lib's dependency, remove when go packaging resumes
  go get github.com/cryptix/wav

  go get github.com/axgle/mahonia github.com/msteinert/pam github.com/gosexy/gettext github.com/rickb777/date \
         github.com/jinzhu/gorm github.com/kelvins/sunrisesunset github.com/mozillazg/go-pinyin github.com/teambition/rrule-go \
         golang.org/x/xerrors github.com/mattn/go-sqlite3 github.com/fsnotify/fsnotify github.com/godbus/dbus

  sed -i 's#/usr/share/backgrounds/default_background.jpg#/usr/share/backgrounds/deepin/desktop.jpg#' accounts/user.go
  sed -i '/logger.Warning("failed to get interface info:", err)/d' network/manager_device.go
}

After you made the change executing git diff should produce the output I posted in #6.

Offline

#9 2021-02-23 12:56:46

linerman
Member
Registered: 2021-02-16
Posts: 8

Re: proper reading of journal warning

You are THE MAN!
That worked. No more warnings flood.

How to deal with that deepin-daemon in the future?
When the upgrade will come, should I take it?
If so, would the same modification of the file with git clone have to be made?
Using same method as above?

Offline

#10 2021-02-23 13:07:14

seth
Member
Registered: 2012-09-03
Posts: 18,895

Re: proper reading of journal warning

Yes, you'll have to build the package locally whenever you update deepin until upstream fixed the bug (which is not what this does - you're merely suppressing a warning)

Offline

#11 Yesterday 08:13:57

linerman
Member
Registered: 2021-02-16
Posts: 8

Re: proper reading of journal warning

seth wrote:

Yes, you'll have to build the package locally whenever you update deepin until upstream fixed the bug (which is not what this does - you're merely suppressing a warning)

Ok. You were both very helpful.
In the meantime there were 3 or 4 upgrades of the package, but none of them solved the issue.
So I edited PKGBUILD every single time. Fortunately, it works and stops journal warnings.

Offline

Board footer

Powered by FluxBB