[Eisfair] [E1 64bit] Failed to start Route service

Martin Faderbauer martin at fmit.at
Mo Okt 6 17:00:36 CEST 2025



Am 06.10.2025 um 15:33 schrieb Marcus Röckrath:
> Hallo Martin,
> 
> Martin Faderbauer wrote:
> 
>>>> Seit dem letzten update erhalte ich beim booten immer:
>>>
>>> Welches? Welche?
>>>
>> eigentlich war es das letzte Kernel update da danach ein Reboot
>> notwendig war. Da ist es mir dann beim Booten aufgefallen.
>>
>> 6.6.106-eisfair-64-VIRT
> 
> Du kannst noch den Vorkernel booten?
> 
> Tritt der Fehler dort bestimmt nicht auf?
> 
>> fmsrv03 # ip r
>> default via 172.30.101.1 dev enx000c299f719a
>> 172.30.1.0/24 dev enx000c299f7190 proto kernel scope link src 172.30.1.12
>> 172.30.101.0/24 dev enx000c299f719a proto kernel scope link src
>> 172.30.101.12
> 
> Also zwei Netzwerkkarten.
Ja eine für Samba und die andere für Mail und Web
> 
> Hast du weitere spezielle Netzwerkpakete laufen?

eigentlich nichts ungewöhnliches


             1. Haveged Service
             2. LPRng
             3. Perl module handling
             4. Certs Service
             5. Apache2 Webserver
             6. Xinetd administration
             7. Mail Service
             8. Database server administration
             9. ipcalc
            10. PHP7 Command Line Interface
            11. Nextcloud Service
            12. Samba
            13. Name server BIND 9
            14. brute_force_blocking
            15. ttytter
            16. DHCP Server
            17. proftpd daemon
            18. Tftpd service
            19. PHP8 Command Line Interface
            20. ClamAV
            21. Update Checker
            22. QEMU Guest Agent Service
            23. Redis Server
             0. Exit

fmsrv03 # ps -e
  PID TTY          TIME CMD
    1 ?        00:00:05 systemd
    2 ?        00:00:00 kthreadd
    3 ?        00:00:00 pool_workqueue_release
    4 ?        00:00:00 kworker/R-rcu_g
    5 ?        00:00:00 kworker/R-rcu_p
    6 ?        00:00:00 kworker/R-slub_
    7 ?        00:00:00 kworker/R-netns
    9 ?        00:00:00 kworker/0:0H-kblockd
   12 ?        00:00:00 kworker/R-mm_pe
   13 ?        00:00:00 rcu_tasks_kthread
   14 ?        00:00:00 rcu_tasks_trace_kthread
   15 ?        00:00:07 ksoftirqd/0
   16 ?        00:00:44 rcu_preempt
   17 ?        00:00:00 migration/0
   18 ?        00:00:00 cpuhp/0
   19 ?        00:00:00 cpuhp/1
   20 ?        00:00:00 migration/1
   21 ?        00:00:07 ksoftirqd/1
   23 ?        00:00:00 kworker/1:0H-events_highpri
   24 ?        00:00:00 cpuhp/2
   25 ?        00:00:00 migration/2
   26 ?        00:00:07 ksoftirqd/2
   28 ?        00:00:00 kworker/2:0H-events_highpri
   29 ?        00:00:00 cpuhp/3
   30 ?        00:00:00 migration/3
   31 ?        00:00:07 ksoftirqd/3
   33 ?        00:00:00 kworker/3:0H-events_highpri
   34 ?        00:00:00 cpuhp/4
   35 ?        00:00:00 migration/4
   36 ?        00:00:07 ksoftirqd/4
   38 ?        00:00:00 kworker/4:0H-events_highpri
   39 ?        00:00:00 cpuhp/5
   40 ?        00:00:00 migration/5
   41 ?        00:00:07 ksoftirqd/5
   43 ?        00:00:00 kworker/5:0H-events_highpri
   44 ?        00:00:00 kdevtmpfs
   45 ?        00:00:00 kworker/R-inet_
   46 ?        00:00:00 oom_reaper
   47 ?        00:00:00 kworker/R-write
   48 ?        00:00:02 kcompactd0
   49 ?        00:00:00 ksmd
   51 ?        00:00:00 kworker/R-kinte
   52 ?        00:00:00 kworker/R-kbloc
   53 ?        00:00:00 kworker/R-blkcg
   54 ?        00:00:00 kworker/R-md
   55 ?        00:00:00 kworker/R-md_bi
   56 ?        00:00:00 kworker/R-devfr
   57 ?        00:00:00 watchdogd
   60 ?        00:00:00 kswapd0
   61 ?        00:00:00 kworker/0:1H
   62 ?        00:00:00 kworker/R-kthro
   63 ?        00:00:00 kworker/R-acpi_
   68 ?        00:00:00 kworker/R-raid5
   69 ?        00:00:00 kworker/R-kstrp
   71 ?        00:00:00 kworker/3:1H-kblockd
   72 ?        00:00:00 kworker/R-mld
   74 ?        00:00:00 kworker/R-ipv6_
   79 ?        00:00:03 kworker/1:1H-kblockd
   95 ?        00:00:00 kworker/2:1H-kblockd
  131 ?        00:00:00 kworker/4:1H-kblockd
  278 ?        00:00:00 kworker/R-crypt
  279 ?        00:00:00 kworker/R-ata_s
  280 ?        00:00:00 scsi_eh_0
  281 ?        00:00:00 kworker/R-scsi_
  282 ?        00:00:00 scsi_eh_1
  283 ?        00:00:00 kworker/R-scsi_
  287 ?        00:00:00 scsi_eh_2
  288 ?        00:00:00 kworker/R-scsi_
  289 ?        00:00:00 scsi_eh_3
  290 ?        00:00:00 kworker/R-scsi_
  291 ?        00:00:00 scsi_eh_4
  292 ?        00:00:00 kworker/R-scsi_
  293 ?        00:00:00 scsi_eh_5
  294 ?        00:00:00 kworker/R-scsi_
  295 ?        00:00:00 scsi_eh_6
  296 ?        00:00:00 kworker/R-scsi_
  297 ?        00:00:00 scsi_eh_7
  298 ?        00:00:00 kworker/R-scsi_
  305 ?        00:00:00 scsi_eh_8
  306 ?        00:00:00 kworker/R-scsi_
  307 ?        00:00:00 kworker/R-vmw_p
  323 ?        00:00:00 kworker/5:2H-kblockd
  349 ?        00:00:01 jbd2/sdb2-8
  350 ?        00:00:00 kworker/R-ext4-
  383 ?        00:00:01 haveged
  390 ?        00:00:02 systemd-journal
  422 ?        00:00:00 systemd-timesyn
  428 ?        00:00:00 systemd-udevd
  469 ?        00:00:00 kworker/R-ttm
  486 ?        00:00:00 kworker/R-edac-
  497 ?        00:00:02 jbd2/sda3-8
  498 ?        00:00:00 jbd2/sdb1-8
  499 ?        00:00:00 kworker/R-ext4-
  500 ?        00:00:00 kworker/R-ext4-
  501 ?        00:00:00 jbd2/sdd1-8
  502 ?        00:00:00 jbd2/sda2-8
  503 ?        00:00:00 kworker/R-ext4-
  504 ?        00:00:00 kworker/R-ext4-
  505 ?        00:00:00 jbd2/sda1-8
  506 ?        00:00:00 kworker/R-ext4-
  507 ?        00:00:00 jbd2/sdc1-8
  508 ?        00:00:00 kworker/R-ext4-
  520 ?        00:00:00 dbus-broker-lau
  521 ?        00:00:00 dbus-broker
  526 ?        00:00:40 qemu-ga
  529 ?        00:00:00 systemd-logind
  579 ?        00:00:00 bacula-fd
  798 ?        00:02:14 redis-server
  826 ?        00:00:02 proftpd
  829 ?        00:00:00 xinetd
  886 ?        00:00:00 freshclam
  905 ?        00:00:02 syslogd
  929 ?        00:00:50 mariadbd
  951 ?        00:00:32 sshd
 1030 ?        00:00:06 named
 1070 ?        00:00:04 apache2
 1073 ?        00:00:10 htcacheclean
 1075 ?        00:00:02 nmbd
 1078 ?        00:00:00 smbd
 1081 ?        00:00:00 smbd-notifyd
 1082 ?        00:00:00 smbd-cleanupd
 1086 ?        00:00:02 winbindd
 1088 ?        00:00:02 wb[FMSRV03]
 1089 ?        00:00:00 wb[FMIT]
 1175 ?        00:00:11 apache2
 1652 ?        00:14:38 brute_force_blo
 2238 ?        00:00:00 kworker/5:1-mm_percpu_wq
 2286 ?        00:00:00 kworker/2:2
 4145 ?        00:00:00 wb-idmap
 5127 ?        00:00:00 imap-login
 5129 ?        00:00:00 imap-login
 5132 ?        00:00:00 imap
 5133 ?        00:00:00 imap
 5242 ?        00:00:00 kworker/R-tls-s
 5974 ?        00:00:13 apache2
 5990 ?        00:00:14 apache2
 6077 ?        00:00:00 kworker/1:1-cgroup_destroy
 6647 ?        00:00:00 sshd-session
 8082 ?        00:00:00 systemd
 8087 ?        00:00:00 (sd-pam)
 8088 ?        00:00:00 kworker/4:1-cgroup_destroy
 8096 ?        00:00:00 sshd-session
 8102 pts/0    00:00:00 bash
 8685 ?        00:00:00 kworker/u12:3-iou_exit
 9165 ?        00:00:00 kworker/2:1-mm_percpu_wq
 9220 ?        00:00:00 kworker/0:1-cgroup_destroy
 9675 ?        00:00:00 systemd
 9680 ?        00:00:00 (sd-pam)
 9770 ?        00:00:00 gpg-agent
 9772 ?        00:00:00 scdaemon
10886 ?        00:00:08 apache2
11308 ?        00:00:00 kworker/u12:0-events_unbound
11309 ?        00:00:00 kworker/u12:4-ext4-rsv-conversion
11318 ?        00:00:00 kworker/u12:5
11461 ?        00:00:00 fcron
11483 ?        00:00:00 kworker/3:1-cgroup_destroy
12369 ?        00:00:00 kworker/u12:2-events_unbound
12525 ?        00:00:00 kworker/0:0-mm_percpu_wq
12922 ?        00:00:00 imap-login
12932 ?        00:00:23 clamd
12970 ?        00:00:00 imap
13194 ?        00:00:00 imap-login
13195 ?        00:00:00 imap
13603 ?        00:00:00 exim
13979 ?        00:00:00 kworker/1:3-mm_percpu_wq
14267 ?        00:00:00 dovecot
14269 ?        00:00:00 anvil
14270 ?        00:00:00 log
14271 ?        00:00:00 config
15243 ?        00:00:00 stats
15360 ?        00:00:05 apache2
15587 ?        00:00:00 kworker/u12:1-flush-8:0
17749 ?        00:00:00 imap-login
17750 ?        00:00:00 imap
18433 ?        00:00:06 apache2
19089 ?        00:00:07 apache2
20309 ?        00:00:00 samba-dcerpcd
20318 ?        00:00:00 rpcd_lsad
20320 ?        00:00:00 rpcd_lsad
21099 ?        00:00:01 kworker/3:2-events_power_efficient
22518 ?        00:00:00 kworker/4:2-mm_percpu_wq
22750 ?        00:00:00 kworker/5:2-cgroup_destroy
22886 ?        00:00:06 apache2
23977 ?        00:00:00 smbd[172.30.1.2
24796 ?        00:00:07 apache2
25546 ?        00:00:00 kworker/3:0-cgroup_destroy
27277 ?        00:00:00 kworker/R-dio/s
28426 tty1     00:00:00 agetty
29299 ?        00:00:00 sleep
29308 ?        00:00:00 sleep
29309 pts/0    00:00:00 ps
30060 ?        00:00:02 spamd
30062 ?        00:00:01 spamd child
30064 ?        00:00:01 spamd child
30065 ?        00:00:00 spamd child
30066 ?        00:00:00 spamd child
30067 ?        00:00:00 spamd child
30068 ?        00:00:02 spamd child
30069 ?        00:00:04 spamd child
30070 ?        00:00:00 spamd child
30071 ?        00:00:00 spamd child
30072 ?        00:00:00 spamd child
30554 ?        00:00:00 antispam-contro
30781 ?        00:00:08 apache2
fmsrv03 #


> 
>> Oct 05 19:56:38 fmsrv03 route[32732]: RTNETLINK answers: File exists
>>
>> kann eine stehengebliebene Datei dran schuld sein?
> 
> IMHO wird die Routenkonfiguration nur flüchtig gespeichert und geht beim 
> Runterfahren verloren.
> 
> Nach Google-Suche kann der Fehler auch dadurch getriggert werden, wenn eine 
> Route mittels route add gesetzt werden soll, die schon gesetzt ist, deshalb 
> auch meine obige Frage nach anderen Netzwerkpaketen.
> 



Mehr Informationen über die Mailingliste Eisfair