Systemd-resolved

[jarmo]

Won't start, claims something about memory,
sorry, can't specify, made local resolv.conf
to get network running..

It is enabled by default, I disabled to get
self edited dns query working..
Fedora 41 xfce4

Jarmo

[Barry]

> On 7 Nov 2024, at 15:08, jarmo  wrote:
>
> Won't start, claims something about memory,
> sorry, can't specify, made local resolv.conf
> to get network running..

What is the output of systemctl status systemd-networkd?
> It is enabled by default, I disabled to get
> self edited dns query working..
> Fedora 41 xfce4
> Jarmo
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Barry]

> On 7 Nov 2024, at 17:31, Barry  wrote:
>
> What is the output of systemctl status systemd-networkd?

Sorry i mean the output of systemctl status systemd-resolved !

Barry

[jarmo]

Thu, 7 Nov 2024 22:10:31 +0000
Barry  kirjoitti:
> > On 7 Nov 2024, at 17:31, Barry  wrote:
> >
> > What is the output of systemctl status systemd-networkd?
>
> Sorry i mean the output of systemctl status systemd-resolved !
>
> Barry

systemctl status systemd-resolved
× systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: exit-code) since Fri 2024-11-08 07:52:25 EET; 1min 47s ago
 Invocation: 10909696893143d699f8742876947b82
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             https://systemd.io/WRITING_NETWORK_CONFIGURATION_MANAGERS
             https://systemd.io/WRITING_RESOLVER_CLIENTS
    Process: 19413 ExecStart=/usr/lib/systemd/systemd-resolved (code=exited, status=1/FAILURE)
   Main PID: 19413 (code=exited, status=1/FAILURE)
      Error: 12 (Muistin varaaminen ei onnistu)

marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at>
marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: systemd-resolved.service: Start request repeated too quickly.
marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.

and

journalctl -xeu systemd-resolved.service
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An ExecStart= process belonging to unit systemd-resolved.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit systemd-resolved.service has entered the 'failed' state with result 'exit-code'.
marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
░░ Subject: A start job for unit systemd-resolved.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit systemd-resolved.service has finished with a failure.
░░ 
░░ The job identifier is 12559 and the job result is failed.
marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at>
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ Automatic restarting of the unit systemd-resolved.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: systemd-resolved.service: Start request repeated too quickly.
marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit systemd-resolved.service has entered the 'failed' state with result 'exit-code'.
marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
░░ Subject: A start job for unit systemd-resolved.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit systemd-resolved.service has finished with a failure.
░░ 
░░ The job identifier is 12590 and the job result is failed.

So, I disable systemd-resolved and manually create /etc/resolv.conf
to get my network working.

Jarmo

[Jeffrey Walton]

On Fri, Nov 8, 2024 at 1:02 AM jarmo  wrote:
> [...]
>
> So, I disable systemd-resolved and manually create /etc/resolv.conf
> to get my network working.

Disabling a service only lasts until the next (re)boot. And it does
not stop currently executing services, and the service can still be
started in the current session.

If you want to permanently disable the service, you must mask it.

Also see the systemctl docs,
https://www.freedesktop.org/software/systemd/man/latest/systemctl.html.

Jeff

[jarmo]

Fri, 8 Nov 2024 01:19:34 -0500
Jeffrey Walton  kirjoitti:

get my network working.
> Disabling a service only lasts until the next (re)boot. And it does
> not stop currently executing services, and the service can still be
> started in the current session.
>
> If you want to permanently disable the service, you must mask it.
>
> Also see the systemctl docs,
> https://www.freedesktop.org/software/systemd/man/latest/systemctl.html.
>
> Jeff

Don't get me wrong, I want that service also working, but
I have no idea, how to do.
So I made this temporary solution... In case someone else
turns into this and find..
By default it does not wor for me..

Jarmo

[Barry]

> On 8 Nov 2024, at 06:02, jarmo  wrote:
>
> Process: 19413 ExecStart=/usr/lib/systemd/systemd-resolved (code=exited, status=1/FAILURE)
>   Main PID: 19413 (code=exited, status=1/FAILURE)
>      Error: 12 (Muistin varaaminen ei onnistu)

This is ENOMEM and that implies your do not have enough RAM to run Fedora.
What is the output of ’inxi -Fzxx`?

Barry

[jarmo]

Fri, 8 Nov 2024 09:06:46 +0000
Barry  kirjoitti:
> > On 8 Nov 2024, at 06:02, jarmo  wrote:
> >
> > Process: 19413 ExecStart=/usr/lib/systemd/systemd-resolved
> > (code=exited, status=1/FAILURE) Main PID: 19413 (code=exited,
> > status=1/FAILURE) Error: 12 (Muistin varaaminen ei onnistu)
>
> This is ENOMEM and that implies your do not have enough RAM to run
> Fedora. What is the output of ’inxi -Fzxx`?
>
> Barry

Should be enough ram

free
               total        used        free      shared  buff/cache   available
Mem:         7993668     3603712     1372532      755204     4080012     4389956
Swap:        7993340           0     7993340

Jarmo

[Barry Scott]

> On 8 Nov 2024, at 09:44, jarmo  wrote:
>
> Fri, 8 Nov 2024 09:06:46 +0000
> Barry  kirjoitti:
> > > On 8 Nov 2024, at 06:02, jarmo  wrote:
> > >
> > > Process: 19413 ExecStart=/usr/lib/systemd/systemd-resolved
> > > (code=exited, status=1/FAILURE) Main PID: 19413 (code=exited,
> > > status=1/FAILURE) Error: 12 (Muistin varaaminen ei onnistu)
> >
> > This is ENOMEM and that implies your do not have enough RAM to run
> > Fedora. What is the output of ’inxi -Fzxx`?
> >
> > Barry
>
> Should be enough ram
>
> free
>               total        used        free      shared  buff/cache   available
> Mem:         7993668     3603712     1372532      755204     4080012     4389956
> Swap:        7993340           0     7993340

I asked for `inxi -Fzxx` that will provide a lot of info beyond RAM
can you provide that?

FYI I use `free -h` so that the numbers are easier to read.

Barry
> Jarmo
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[jarmo]

Fri, 8 Nov 2024 12:58:16 +0000
Barry Scott  kirjoitti:
> I asked for `inxi -Fzxx` that will provide a lot of info beyond RAM
> can you provide that?
>
> FYI I use `free -h` so that the numbers are easier to read.
>
> Barry

Had to install inxi first :)
Below is with systemd-resolved

System:
  Kernel: 6.11.6-300.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.43.1-2.fc41
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.43 wm: xfwm4 dm: LightDM
    Distro: Fedora Linux 41 (Xfce)
Machine:
  Type: Desktop System: Hewlett-Packard product: HP Compaq Pro 6300 SFF v: N/A
    serial: <filter> Chassis: type: 4 serial: <filter>
  Mobo: Hewlett-Packard model: 339A serial: <filter> part-nu: QV985AV
    BIOS: Hewlett-Packard v: K01 v02.90 date: 07/16/2013
Battery:
  Device-1: hidpp_battery_0 model: Logitech M510 serial: <filter>
    charge: 55% (should be ignored) status: discharging
CPU:
  Info: quad core model: Intel Core i7-3770K bits: 64 type: MT MCP
    arch: Ivy Bridge rev: 9 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 1597 min/max: 1600/3900 cores: 1: 1597 2: 1597 3: 1597
    4: 1597 5: 1597 6: 1597 7: 1597 8: 1597 bogomips: 55872
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
  Device-1: Intel IvyBridge GT2 [HD Graphics 4000] vendor: Hewlett-Packard
    driver: i915 v: kernel arch: Gen-7 ports: active: VGA-1 empty: DP-1,HDMI-A-1
    bus-ID: 00:02.0 chip-ID: 8086:0162
  Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4
    compositor: xfwm4 v: 4.18.0 driver: X: loaded: modesetting
    alternate: fbdev,vesa dri: crocus gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96
  Monitor-1: VGA-1 model: Philips PHL 273V5 res: 1920x1080 dpi: 82
    diag: 686mm (27")
  API: OpenGL v: 4.2 vendor: intel mesa v: 24.2.6 glx-v: 1.4 es-v: 3.0
    direct-render: yes renderer: Mesa Intel HD Graphics 4000 (IVB GT2)
    device-ID: 8086:0162
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio
    vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:1e20
  Device-2: Texas Instruments PCM2903C Audio CODEC
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 bus-ID: 1-1.2.4:9 chip-ID: 08bb:29c3
  API: ALSA v: k6.11.6-300.fc41.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.2.6 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Intel 82579LM Gigabit Network vendor: Hewlett-Packard
    driver: e1000e v: kernel port: f080 bus-ID: 00:19.0 chip-ID: 8086:1502
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 920.37 GiB used: 124.66 GiB (13.5%)
  ID-1: /dev/sda vendor: Kingston model: SA400S37240G size: 223.57 GiB
    speed: 6.0 Gb/s serial: <filter> temp: 27 C
  ID-2: /dev/sdb vendor: A-Data model: SX900 size: 119.24 GiB
    speed: 3.0 Gb/s serial: <filter> temp: 28 C
  ID-3: /dev/sdc vendor: Kingston model: SV300S37A120G size: 111.79 GiB
    speed: 3.0 Gb/s serial: <filter> temp: 29 C
  ID-4: /dev/sdd vendor: Seagate model: ST500DM002-1BD142 size: 465.76 GiB
    type: USB rev: 3.0 spd: 5 Gb/s lanes: 1 serial: <filter>
Partition:
  ID-1: / size: 198.82 GiB used: 54.37 GiB (27.3%) fs: ext4 dev: /dev/sda2
Swap:
  ID-1: swap-1 type: zram size: 7.62 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 35.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 8 GiB available: 7.62 GiB used: 3.89 GiB (51.0%) igpu: 64 MiB
  Processes: 577 Power: uptime: 22h 49m wakeups: 0 Init: systemd v: 256
    target: graphical (5) default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm Compilers: gcc: 14.2.1
    Shell: Bash v: 5.2.32 running-in: xfce4-terminal inxi: 3.3.36

And next with self configured resolv.conf system-resolved disabled

System:
  Kernel: 6.11.6-300.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.43.1-2.fc41
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.43 wm: xfwm4 dm: LightDM
    Distro: Fedora Linux 41 (Xfce)
Machine:
  Type: Desktop System: Hewlett-Packard product: HP Compaq Pro 6300 SFF v: N/A
    serial: <filter> Chassis: type: 4 serial: <filter>
  Mobo: Hewlett-Packard model: 339A serial: <filter> part-nu: QV985AV
    BIOS: Hewlett-Packard v: K01 v02.90 date: 07/16/2013
Battery:
  Device-1: hidpp_battery_0 model: Logitech M510 serial: <filter>
    charge: 55% (should be ignored) status: discharging
CPU:
  Info: quad core model: Intel Core i7-3770K bits: 64 type: MT MCP
    arch: Ivy Bridge rev: 9 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 3852 min/max: 1600/3900 cores: 1: 3852 2: 3852 3: 3852
    4: 3852 5: 3852 6: 3852 7: 3852 8: 3852 bogomips: 55872
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
  Device-1: Intel IvyBridge GT2 [HD Graphics 4000] vendor: Hewlett-Packard
    driver: i915 v: kernel arch: Gen-7 ports: active: VGA-1 empty: DP-1,HDMI-A-1
    bus-ID: 00:02.0 chip-ID: 8086:0162
  Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4
    compositor: xfwm4 v: 4.18.0 driver: X: loaded: modesetting
    alternate: fbdev,vesa dri: crocus gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96
  Monitor-1: VGA-1 model: Philips PHL 273V5 res: 1920x1080 dpi: 82
    diag: 686mm (27")
  API: OpenGL v: 4.2 vendor: intel mesa v: 24.2.6 glx-v: 1.4 es-v: 3.0
    direct-render: yes renderer: Mesa Intel HD Graphics 4000 (IVB GT2)
    device-ID: 8086:0162
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio
    vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:1e20
  Device-2: Texas Instruments PCM2903C Audio CODEC
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 bus-ID: 1-1.2.4:9 chip-ID: 08bb:29c3

Jarmo
  API: ALSA v: k6.11.6-300.fc41.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.2.6 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Intel 82579LM Gigabit Network vendor: Hewlett-Packard
    driver: e1000e v: kernel port: f080 bus-ID: 00:19.0 chip-ID: 8086:1502
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 920.37 GiB used: 124.66 GiB (13.5%)
  ID-1: /dev/sda vendor: Kingston model: SA400S37240G size: 223.57 GiB
    speed: 6.0 Gb/s serial: <filter> temp: 27 C
  ID-2: /dev/sdb vendor: A-Data model: SX900 size: 119.24 GiB
    speed: 3.0 Gb/s serial: <filter> temp: 28 C
  ID-3: /dev/sdc vendor: Kingston model: SV300S37A120G size: 111.79 GiB
    speed: 3.0 Gb/s serial: <filter> temp: 28 C
  ID-4: /dev/sdd vendor: Seagate model: ST500DM002-1BD142 size: 465.76 GiB
    type: USB rev: 3.0 spd: 5 Gb/s lanes: 1 serial: <filter>
Partition:
  ID-1: / size: 198.82 GiB used: 54.37 GiB (27.3%) fs: ext4 dev: /dev/sda2
Swap:
  ID-1: swap-1 type: zram size: 7.62 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 36.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 8 GiB available: 7.62 GiB used: 3.9 GiB (51.2%) igpu: 64 MiB
  Processes: 323 Power: uptime: 22h 53m wakeups: 0 Init: systemd v: 256
    target: graphical (5) default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm Compilers: gcc: 14.2.1
    Shell: Bash v: 5.2.32 running-in: xfce4-terminal inxi: 3.3.36

[Tim]

On Fri, 2024-11-08 at 01:19 -0500, Jeffrey Walton wrote:
> Disabling a service only lasts until the next (re)boot. And it does
> not stop currently executing services, and the service can still be
> started in the current session.

Not quite the full picture, not in general, even if that was a specific
example of some service that will not quite do what you expect. 
Disabling means setting it so it's not started up (by your
preferences).

Something else could start a disabled service, such as some other
service that wants/needs it.  Rebooting *may* but doesn't necessarily
mean it will.
> If you want to permanently disable the service, you must mask it.

That's certainly true.

Enabled - I want this to be started (usually after booting)
Disabled - I don't want this to be started by default
Masked - I really don't want this to be started, and obey me, dammit!

Stop - stop it now, but do not change the above preferences
Start - start it now, but do not change the above preferences

[Barry]

> On 8 Nov 2024, at 13:19, jarmo  wrote:
>
> Had to install inxi first :)

Thanks for the info.

Do you see systemd-resolved failing immediately after you first login?
Or does if fail after you have been using the system for a little while?
After it fails do you see any journal logs about the oom killer running?

Barry

[jarmo]

Fri, 8 Nov 2024 23:14:57 +0000
Barry  kirjoitti:
> > On 8 Nov 2024, at 13:19, jarmo  wrote:
> >
> > Had to install inxi first :)
>
> Thanks for the info.
>
> Do you see systemd-resolved failing immediately after you first login?
> Or does if fail after you have been using the system for a little
> while? After it fails do you see any journal logs about the oom
> killer running?
>
> Barry

I see no network, after starting computer, which I do very seldom,
only when there comes kernel update.
So network does not start at all and when doing journal query I get
this, what I sent before...

journalctl -xeu systemd-resolved.service
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An ExecStart= process belonging to unit systemd-resolved.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit systemd-resolved.service has entered the 'failed' state with result 'exit-code'.
marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
░░ Subject: A start job for unit systemd-resolved.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit systemd-resolved.service has finished with a failure.
░░ 
░░ The job identifier is 12559 and the job result is failed.
marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at>
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ Automatic restarting of the unit systemd-resolved.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: systemd-resolved.service: Start request repeated too quickly.
marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit systemd-resolved.service has entered the 'failed' state with result 'exit-code'.
marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
░░ Subject: A start job for unit systemd-resolved.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit systemd-resolved.service has finished with a failure.
░░ 
░░ The job identifier is 12590 and the job result is failed.

What is strange, I have two laptops and there all is ok...
I wish I could "speak nerd" :):)

Jarmo

[Barry]

> On 10 Nov 2024, at 08:04, jarmo  wrote:
>
> I see no network, after starting computer

What does `ip addr` report when you have “no network”?

I wonder if you have a hardware problem?
Might be worth running memtest diagnostic to eliminate RAM issues.

Barry

[jarmo]

Sun, 10 Nov 2024 09:27:46 +0000
Barry  kirjoitti:
> > On 10 Nov 2024, at 08:04, jarmo  wrote:
> >
> > I see no network, after starting computer
>
> What does `ip addr` report when you have “no network”?
>
> I wonder if you have a hardware problem?
> Might be worth running memtest diagnostic to eliminate RAM issues.
>
> Barry

When I upgraded into F41, everything worked fine, no problem.
But afterward came some updates, started this systemd-resolved
problem.
I think, if there is HW problem, it should effect also, when I'm using
this locally edited resolv.conf, think?

Jarmo

[Jonathan Billings]

On Nov 10, 2024, at 03:04, jarmo  wrote:
> I see no network, after starting computer, which I do very seldom,
> only when there comes kernel update.
> So network does not start at all and when doing journal query I get
> this, what I sent before...
>
> journalctl -xeu systemd-resolved.service
> ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> ░░
> ░░ An ExecStart= process belonging to unit systemd-resolved.service has exited.
> ░░
> ░░ The process' exit code is 'exited' and its exit status is 1.
> marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
> ░░ Subject: Unit failed
> ░░ Defined-By: systemd
> ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> …

Sadly, your excerpt from the journal starts *just* after anything useful might have been recorded. It’s just systemd noise about the service not failing and how it isn’t restarting it.

But I can’t comment further because apparently you don’t “speak nerd” and it would be pointless.

--
Jonathan Billings

[jarmo]

Sun, 10 Nov 2024 07:44:54 -0500
Jonathan Billings  kirjoitti:
> > Sadly, your excerpt from the journal starts *just* after anything
>
> useful might have been recorded. It’s just systemd noise about the
> service not failing and how it isn’t restarting it.
>
> But I can’t comment further because apparently you don’t “speak nerd”
> and it would be pointless.
>
> --
> Jonathan Billings

Should journalctl -xeu systemd-resolved.service tell, what
went wrong?

Even I dont speak nerd, I'm good to take GOOD advices and given
for NOOB, not high standing developer, who propably can already.
Sorry, if I frustated you..

Jarmo