Kernel segfault pmgdaemon

F

fw116

New Member
Apr 24, 2024
19
0
1
Feb 18 13:23:59 nemo kernel: pmgdaemon worke[26764]: segfault at 7a20b52cd000 ip 00007a20b5a3e60a sp 00007ffe01833888 error 4 in libc.so.6[7a20b59c2000+155000] likely on CPU 1 (core 1, socket 0)
Feb 18 13:23:59 nemo kernel: Code: d9 66 0f d7 c3 48 83 c7 40 85 c0 0f 85 2f 01 00 00 48 89 f9 48 83 e7 c0 83 e1 3f 48 01 ca 66 90 48 83 ea 40 0f 86 86 00 00 00 <66> 0f 6f 07 66 0f 6f 57 10 66 0f 6f 5f 20 66 0f 6f 67 30 66 0f 74

Kein Kernel Experte und keine Ahnung ob ich den Code hier so posten sollte.

Der PMG läuft als VM auf einem PVE. Erstaunlicherweise der erste Segfault den ich sehe.
Die VM läuft mit PVE defaults
Als Network ist eine vmbr mit Intel E1000E

was wird genau gerbaucht zur analayse ?
 
Last edited:
Hallo fw116! Kannst du bitte einen längeren output vom Journal posten? Und zwar mit journalctl --since <TIME>, am besten 30 Minuten vor dem Crash. Es wäre interessant, den vollen Call Stack zu sehen, oder ob auch weitere Fehler im Journal zu finden sind.

Noch ein paar Fragen:
  1. Auf welcher Hardware läuft die PVE-Installation?
  2. Ist es ein neuer Server, oder ist der Server schon länger ohne Probleme gelaufen?
  3. Was ist der Output von pmgversion -v?
 
l.leahu-vladucu said:
Hallo fw116! Kannst du bitte einen längeren output vom Journal posten? Und zwar mit journalctl --since <TIME>, am besten 30 Minuten vor dem Crash. Es wäre interessant, den vollen Call Stack zu sehen, oder ob auch weitere Fehler im Journal zu finden sind.

Noch ein paar Fragen:
  1. Auf welcher Hardware läuft die PVE-Installation?
  2. Ist es ein neuer Server, oder ist der Server schon länger ohne Probleme gelaufen?
  3. Was ist der Output von pmgversion -v?
Click to expand...
Die Hardware ist schon älter, der Server läuft schon länger.

description: Motherboard
product: 990XA-GD55 (MS-7640)
vendor: MSI
capabilities: pci upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi
*-cpu
description: CPU
product: AMD Phenom(tm) II X6 1100T Processor
vendor: Advanced Micro Devices [AMD]
physical id: 4
bus info: cpu@0
version: 16.10.0
serial: To Be Filled By O.E.M.
slot: CPU 1
size: 3266MHz
capacity: 3300MHz
width: 64 bits
clock: 200MHz
capabilities: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp x86-64 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt nodeid_msr cpb hw_pstate vmmcall npt lbrv svm_lock nrip_save pausefilter cpufreq
configuration: cores=6 enabledcores=6 microcode=16777407 threads=6

description: System Memory
physical id: 27
slot: System board or motherboard
size: 32GiB
capabilities: ecc
configuration: errordetection=multi-bit-ecc
*-bank:0
description: DIMM DDR3 Synchronous 667 MHz (1.5 ns)
product: Array1_PartNumber0
vendor: A1_Manufacturer0
physical id: 0
serial: A1_SerNum0
slot: A1_DIMM0
size: 8GiB
width: 64 bits
clock: 667MHz (1.5ns)

pmgversion -v
proxmox-mailgateway: 8.1.0 (API: 8.1.6/6bbc2221e977, running kernel: 6.8.12-8-pve)
pmg-api: 8.1.6
pmg-gui: 4.1.2
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-8
proxmox-kernel-6.8.12-8-pve-signed: 6.8.12-8
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
proxmox-kernel-6.5.13-1-pve-signed: 6.5.13-1
clamav-daemon: 1.0.7+dfsg-1~deb12u1
ifupdown2: 3.2.0-1+pmx11
libarchive-perl: 3.6.2
libjs-extjs: 7.0.0-5
libjs-framework7: 4.4.7-2
libproxmox-acme-perl: 1.5.1
libproxmox-acme-plugins: 1.5.1
libpve-apiclient-perl: 3.3.2
libpve-common-perl: 8.2.9
libpve-http-server-perl: 5.1.2
libxdgmime-perl: 1.1.0
lvm2: 2.03.16-2
pmg-docs: 8.1.2
pmg-i18n: 3.3.3
pmg-log-tracker: 2.5.0
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-spamassassin: 4.0.1-1
proxmox-widget-toolkit: 4.3.4
pve-firmware: 3.14-3
pve-xtermjs: 5.3.0-3
zfsutils-linux: 2.2.7-pve1
 
Da der noch nicht produktiv ist und "mitläuft" ist das relativ einfach
hier das logfile:

Feb 18 12:58:40 nemo pmgproxy[727]: worker 28491 started
Feb 18 13:00:40 nemo pmg-smtp-filter[24373]: starting database maintenance
Feb 18 13:00:40 nemo pmg-smtp-filter[24373]: end database maintenance (11 ms)
Feb 18 13:00:40 nemo systemd[1]: Starting pmg-hourly.service - Hourly Proxmox Mail Gateway activities...
Feb 18 13:00:41 nemo pmgpolicy[702]: Received a SIG HUP
Feb 18 13:00:41 nemo systemd[1]: Reloading pmgpolicy.service - Proxmox Mail Gateway Policy Daemon...
Feb 18 13:00:41 nemo systemd[1]: Reloaded pmgpolicy.service - Proxmox Mail Gateway Policy Daemon.
Feb 18 13:00:41 nemo pmgpolicy[702]: 2025/02/18-13:00:41 Server closing!
Feb 18 13:00:41 nemo pmgpolicy[702]: 2025/02/18-13:00:41 Re-exec server during HUP
Feb 18 13:00:42 nemo pmgpolicy[702]: WARNING: Pid_file created by this same process. Doing nothing.
Feb 18 13:00:42 nemo pmgpolicy[702]: WARNING: Pid_file created by this same process. Doing nothing.
Feb 18 13:00:42 nemo pmgpolicy[702]: 2025/02/18-13:00:42 main (type Net::Server::PreForkSimple) starting! pid(702)
Feb 18 13:00:42 nemo pmgpolicy[702]: Binding open file descriptors
Feb 18 13:00:42 nemo pmgpolicy[702]: Binding to TCP port 10022 on host 127.0.0.1 with IPv4
Feb 18 13:00:42 nemo pmgpolicy[702]: Reassociating file descriptor 8 with TCP on [127.0.0.1]:10022, using IPv4
Feb 18 13:00:42 nemo pmgpolicy[702]: Group Not Defined. Defaulting to EGID '0'
Feb 18 13:00:42 nemo pmgpolicy[702]: User Not Defined. Defaulting to EUID '0'
Feb 18 13:00:42 nemo pmgpolicy[702]: Setting up serialization via flock
Feb 18 13:00:42 nemo pmgpolicy[702]: Policy daemon (re)started
Feb 18 13:00:42 nemo pmgpolicy[702]: Beginning prefork (5 processes)
Feb 18 13:00:42 nemo pmgpolicy[702]: Starting "5" children
Feb 18 13:00:44 nemo systemd[1]: pmg-hourly.service: Deactivated successfully.
Feb 18 13:00:44 nemo systemd[1]: Finished pmg-hourly.service - Hourly Proxmox Mail Gateway activities.
Feb 18 13:00:44 nemo systemd[1]: pmg-hourly.service: Consumed 3.943s CPU time.
Feb 18 13:02:40 nemo pmg-smtp-filter[24373]: starting database maintenance
Feb 18 13:02:40 nemo pmg-smtp-filter[24373]: end database maintenance (9 ms)
Feb 18 13:02:52 nemo pmgpolicy[702]: starting policy database maintenance (greylist, rbl)
Feb 18 13:02:52 nemo pmgpolicy[702]: end policy database maintenance (15 ms, 2 ms)
Feb 18 13:04:40 nemo pmg-smtp-filter[24373]: starting database maintenance
Feb 18 13:04:40 nemo pmg-smtp-filter[24373]: end database maintenance (9 ms)
Feb 18 13:05:02 nemo pmgpolicy[702]: starting policy database maintenance (greylist, rbl)
Feb 18 13:05:02 nemo pmgpolicy[702]: end policy database maintenance (17 ms, 3 ms)
Feb 18 13:06:40 nemo pmg-smtp-filter[24373]: starting database maintenance
Feb 18 13:06:40 nemo pmg-smtp-filter[24373]: end database maintenance (9 ms)
Feb 18 13:06:48 nemo pmgdaemon[24834]: successful auth for user 'root@pam'
Feb 18 13:07:12 nemo pmgpolicy[702]: starting policy database maintenance (greylist, rbl)
Feb 18 13:07:12 nemo pmgpolicy[702]: end policy database maintenance (15 ms, 2 ms)
Feb 18 13:07:15 nemo pmgproxy[17495]: worker exit
Feb 18 13:07:15 nemo pmgproxy[727]: worker 17495 finished
Feb 18 13:07:15 nemo pmgproxy[727]: starting 1 worker(s)
Feb 18 13:07:15 nemo pmgproxy[727]: worker 29179 started
Feb 18 13:08:40 nemo pmg-smtp-filter[24373]: starting database maintenance
Feb 18 13:08:40 nemo pmg-smtp-filter[24373]: end database maintenance (10 ms)
Feb 18 13:09:22 nemo pmgpolicy[702]: starting policy database maintenance (greylist, rbl)
Feb 18 13:09:22 nemo pmgpolicy[702]: end policy database maintenance (14 ms, 2 ms)
Feb 18 13:10:40 nemo pmg-smtp-filter[24373]: starting database maintenance
Feb 18 13:10:40 nemo pmg-smtp-filter[24373]: end database maintenance (8 ms)
Feb 18 13:11:32 nemo pmgpolicy[702]: starting policy database maintenance (greylist, rbl)
Feb 18 13:11:32 nemo pmgpolicy[702]: end policy database maintenance (14 ms, 2 ms)
Feb 18 13:12:41 nemo pmg-smtp-filter[24373]: starting database maintenance
Feb 18 13:12:41 nemo pmg-smtp-filter[24373]: end database maintenance (8 ms)
Feb 18 13:13:33 nemo pmgpolicy[702]: starting policy database maintenance (greylist, rbl)
Feb 18 13:13:33 nemo pmgpolicy[702]: end policy database maintenance (15 ms, 2 ms)
Feb 18 13:14:41 nemo pmg-smtp-filter[24373]: starting database maintenance
Feb 18 13:14:41 nemo pmg-smtp-filter[24373]: end database maintenance (11 ms)
Feb 18 13:15:43 nemo pmgpolicy[702]: starting policy database maintenance (greylist, rbl)
Feb 18 13:15:43 nemo pmgpolicy[702]: end policy database maintenance (14 ms, 2 ms)
Feb 18 13:16:41 nemo pmg-smtp-filter[24373]: starting database maintenance
Feb 18 13:16:41 nemo pmg-smtp-filter[24373]: end database maintenance (8 ms)
Feb 18 13:17:01 nemo CRON[30884]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 18 13:17:01 nemo CRON[30885]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Feb 18 13:17:01 nemo CRON[30884]: pam_unix(cron:session): session closed for user root
Feb 18 13:17:13 nemo postfix/postscreen[30920]: CONNECT from [170.203.20.9]:38557 to [xxx.xxx.xxx.150]:25
Feb 18 13:17:19 nemo postfix/postscreen[30920]: PASS NEW [170.203.20.9]:38557
Feb 18 13:17:27 nemo postfix/smtpd[30938]: connect from kl-203-20-9.kmta.shared.klaviyomail.com[170.203.20.9]
Feb 18 13:17:28 nemo postfix/smtpd[30938]: Anonymous TLS connection established from kl-203-20-9.kmta.shared.klaviyomail.com[170.203.20.9]: TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256
Feb 18 13:17:28 nemo pmgpolicy[28768]: reloading configuration Proxmox_ruledb
Feb 18 13:17:28 nemo pmgpolicy[28768]: SPF says pass
Feb 18 13:17:28 nemo postfix/smtpd[30938]: NOQUEUE: client=kl-203-20-9.kmta.shared.klaviyomail.com[170.203.20.9]
Feb 18 13:17:29 nemo pmg-smtp-filter[24389]: 2025/02/18-13:17:29 CONNECT TCP Peer: "[127.0.0.1]:39154" Local: "[127.0.0.1]:10024"
Feb 18 13:17:29 nemo pmg-smtp-filter[24389]: 40A0F67B47A5971A14: new mail message-id=<mid-01JMCFSCZBFN34H9TYFBK23Z1D@rxtqed.shared.klaviyomail.com>
Feb 18 13:17:35 nemo pmg-smtp-filter[24389]: 40A0F67B47A5971A14: SA score=2/5 time=5.592 bayes=undefined autolearn=disabled hits=DKIMWL_WL_MED(-0.001),DKIM_SIGNED(0.1),DKIM_VALID(-0.1),DMARC_MISSING(0.1),HEADER_FROM_DIFFERENT_DOMAINS(0.001),HTML_MESSAGE(0.001),KAM_BODY_MARKETINGBL_PCCC(0.001),KAM_MARKETINGBL_PCCC(1),RCVD_IN_HOSTKARMA_BL(1.5),RCVD_IN_MSPIKE_H3(0.001),RCVD_IN_MSPIKE_WL(0.001),SPF_HELO_NONE(0.001),SPF_PASS(-0.001)
Feb 18 13:17:35 nemo postfix/smtpd[30994]: connect from nemo.xxx.xxx[127.0.0.1]
Feb 18 13:17:35 nemo postfix/smtpd[30994]: 37B7C40A10: client=nemo.xxx.xxx[127.0.0.1], orig_client=kl-203-20-9.kmta.shared.klaviyomail.com[170.203.20.9]
Feb 18 13:17:35 nemo postfix/cleanup[30995]: 37B7C40A10: message-id=<mid-01JMCFSCZBFN34H9TYFBK23Z1D@rxtqed.shared.klaviyomail.com>
Feb 18 13:17:35 nemo postfix/qmgr[14416]: 37B7C40A10: from=<bounce-kl_27062345648-kl_101101jmcd9b7882rajn-h-8e6f276b8d=2@rxtqed.shared.klaviyomail.com>, size=74711, nrcpt=1 (queue active)
Feb 18 13:17:35 nemo pmg-smtp-filter[24389]: 40A0F67B47A5971A14: accept mail to <xxxxx@xxx.xxx> (37B7C40A10) (rule: default-accept)
Feb 18 13:17:35 nemo postfix/smtpd[30994]: disconnect from nemo.xxx.xxx[127.0.0.1] ehlo=1 xforward=1 mail=1 rcpt=1 data=1 commands=5
Feb 18 13:17:35 nemo pmg-smtp-filter[24389]: 40A0F67B47A5971A14: processing time: 5.814 seconds (5.592, 0.103, 0)
Feb 18 13:17:35 nemo postfix/smtpd[30938]: proxy-accept: END-OF-MESSAGE: 250 2.5.0 OK (40A0F67B47A5971A14); from=<bounce-kl_27062345648-kl_101101jmcd9b7882rajn-h-8e6f276b8d=2@rxtqed.shared.klaviyomail.com> to=<xxxxx@xxx.xxx> proto=ESMTP helo=<kl-203-20-9.kmta.shared.klaviyomail.com>
Feb 18 13:17:35 nemo postfix/smtp[30996]: Untrusted TLS connection established to xxx.xxx.xxx.151[xxx.xxx.xxx.151]:25: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256
Feb 18 13:17:35 nemo postfix/smtpd[30938]: disconnect from kl-203-20-9.kmta.shared.klaviyomail.com[170.203.20.9] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7
Feb 18 13:17:36 nemo postfix/smtp[30996]: 37B7C40A10: to=<xxxxx@xxx.xxx>, relay=xxx.xxx.xxx.151[xxx.xxx.xxx.151]:25, delay=1.6, delays=0.06/0.06/0.06/1.4, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 6E31F1BD0BC2)
Feb 18 13:17:36 nemo postfix/qmgr[14416]: 37B7C40A10: removed
Feb 18 13:17:46 nemo postfix/postscreen[30920]: CONNECT from [162.19.131.235]:35955 to [xxx.xxx.xxx.150]:25
Feb 18 13:17:52 nemo postfix/postscreen[30920]: PASS NEW [162.19.131.235]:35955
Feb 18 13:17:53 nemo postfix/smtpd[30938]: connect from s235.peligoss.com[162.19.131.235]
Feb 18 13:17:53 nemo pmgpolicy[702]: starting policy database maintenance (greylist, rbl)
Feb 18 13:17:53 nemo pmgpolicy[702]: end policy database maintenance (16 ms, 2 ms)
Feb 18 13:17:53 nemo postfix/smtpd[30938]: Anonymous TLS connection established from s235.peligoss.com[162.19.131.235]: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256
Feb 18 13:17:53 nemo pmgpolicy[28768]: SPF says pass
Feb 18 13:17:53 nemo postfix/cleanup[30995]: C187F40A0F: message-id=<20250218121753.C187F40A0F@nemo.xxx.xxx>
Feb 18 13:17:53 nemo postfix/qmgr[14416]: C187F40A0F: from=<double-bounce@nemo.xxx.xxx>, size=243, nrcpt=1 (queue active)
Feb 18 13:17:53 nemo postfix/smtp[30996]: Untrusted TLS connection established to xxx.xxx.xxx.151[xxx.xxx.xxx.151]:25: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)
Feb 18 13:17:53 nemo postfix/smtp[30996]: C187F40A0F: to=<xxx@xxx.de>, relay=xxx.xxx.xxx.151[xxx.xxx.xxx.151]:25, delay=0.07, delays=0/0/0.05/0.01, dsn=2.1.5, status=deliverable (250 2.1.5 Ok)
Feb 18 13:17:53 nemo postfix/qmgr[14416]: C187F40A0F: removed
Feb 18 13:17:56 nemo postfix/smtpd[30938]: NOQUEUE: client=s235.peligoss.com[162.19.131.235]
Feb 18 13:17:56 nemo pmg-smtp-filter[24390]: 2025/02/18-13:17:56 CONNECT TCP Peer: "[127.0.0.1]:48112" Local: "[127.0.0.1]:10024"
Feb 18 13:17:56 nemo pmg-smtp-filter[24390]: 40A0F67B47A74CE0FE: new mail message-id=<e645b73d15db81b08eee062c21d66a740c38f2@peligoss.com>
Feb 18 13:17:57 nemo pmg-smtp-filter[24390]: 40A0F67B47A74CE0FE: SA score=5/5 time=0.883 bayes=undefined autolearn=disabled hits=DKIM_SIGNED(0.1),DKIM_VALID(-0.1),DKIM_VALID_AU(-0.1),DKIM_VALID_EF(-0.1),DMARC_PASS(-0.1),FSL_BULK_SIG(0.001),HTML_IMAGE_ONLY_24(1.282),HTML_MESSAGE(0.001),MIME_HTML_ONLY(0.1),RAZOR2_CF_RANGE_51_100(2.43),RAZOR2_CHECK(1.729),SPF_HELO_NONE(0.001),SPF_PASS(-0.001)
Feb 18 13:17:57 nemo pmg-smtp-filter[24390]: 40A0F67B47A74CE0FE: moved mail for <xxx@xxx.de> to spam quarantine - 40A1067B47A75C1934 (rule: Quarantine/Mark Spam (Level 5))
Feb 18 13:17:57 nemo pmg-smtp-filter[24390]: 40A0F67B47A74CE0FE: processing time: 0.959 seconds (0.883, 0.038, 0)
Feb 18 13:17:57 nemo postfix/smtpd[30938]: proxy-accept: END-OF-MESSAGE: 250 2.5.0 OK (40A0F67B47A74CE0FE); from=<topzinsen@peligoss.com> to=<xxx@xxx.de> proto=ESMTP helo=<s235.peligoss.com>
Feb 18 13:17:57 nemo postfix/smtpd[30938]: disconnect from s235.peligoss.com[162.19.131.235] ehlo=2 starttls=1 mail=1 rcpt=1 bdat=1 quit=1 commands=7
Feb 18 13:18:47 nemo pmg-smtp-filter[24373]: starting database maintenance
Feb 18 13:18:47 nemo pmg-smtp-filter[24373]: end database maintenance (29 ms)
Feb 18 13:20:03 nemo pmgpolicy[702]: starting policy database maintenance (greylist, rbl)
Feb 18 13:20:03 nemo pmgpolicy[702]: end policy database maintenance (16 ms, 2 ms)
Feb 18 13:20:48 nemo pmg-smtp-filter[24373]: starting database maintenance
Feb 18 13:20:48 nemo pmg-smtp-filter[24373]: end database maintenance (10 ms)
Feb 18 13:21:08 nemo pmgproxy[22124]: worker exit
Feb 18 13:21:08 nemo pmgproxy[727]: worker 22124 finished
Feb 18 13:21:08 nemo pmgproxy[727]: starting 1 worker(s)
Feb 18 13:21:08 nemo pmgproxy[727]: worker 31613 started
Feb 18 13:21:17 nemo postfix/anvil[30965]: statistics: max connection rate 1/60s for (smtpd:170.203.20.9) at Feb 18 13:17:27
Feb 18 13:21:17 nemo postfix/anvil[30965]: statistics: max connection count 1 for (smtpd:170.203.20.9) at Feb 18 13:17:27
Feb 18 13:21:17 nemo postfix/anvil[30965]: statistics: max cache size 2 at Feb 18 13:17:53
Feb 18 13:21:45 nemo pmgdaemon[24834]: worker exit
Feb 18 13:21:45 nemo pmgdaemon[720]: worker 24834 finished
Feb 18 13:21:45 nemo pmgdaemon[720]: starting 1 worker(s)
Feb 18 13:21:45 nemo pmgdaemon[720]: worker 31718 started
Feb 18 13:21:49 nemo pmgdaemon[26764]: successful auth for user 'root@pam'
Feb 18 13:22:13 nemo pmgpolicy[702]: starting policy database maintenance (greylist, rbl)
Feb 18 13:22:13 nemo pmgpolicy[702]: end policy database maintenance (14 ms, 2 ms)
Feb 18 13:22:48 nemo pmg-smtp-filter[24373]: starting database maintenance
Feb 18 13:22:48 nemo pmg-smtp-filter[24373]: end database maintenance (9 ms)
Feb 18 13:23:59 nemo kernel: pmgdaemon worke[26764]: segfault at 7a20b52cd000 ip 00007a20b5a3e60a sp 00007ffe01833888 error 4 in libc.so.6[7a20b59c2000+155000] likely on CPU 1 (core 1, socket 0)
Feb 18 13:23:59 nemo kernel: Code: d9 66 0f d7 c3 48 83 c7 40 85 c0 0f 85 2f 01 00 00 48 89 f9 48 83 e7 c0 83 e1 3f 48 01 ca 66 90 48 83 ea 40 0f 86 86 00 00 00 <66> 0f 6f 07 66 0f 6f 57 10 66 0f 6f 5f 20 66 0f 6f 67 30 66 0f 74
 
Danke für die Infos! Kannst du bitte sicherheitshalber noch die VM-Konfiguration posten?

Ich hätte gehofft, dass wir mehr Infos zum Segfault im Journal finden. Normalerweise passieren solche Segfaults, wenn das System instabil ist, z.B. durch kaputten RAM oder CPU-Probleme - insbesondere, wenn die Fehlermeldung nicht sinnvoll aussieht, wie hier. Aber dann würde ich mir Crashes auch am Host oder in anderen VMs erwarten.

Wäre es möglich, memtest86+ laufen zu lassen?
 
auf jeden fall die hardware durchchecken
- disks, filesysteme und files
- memory
- cpu

segfaults in perl code sind fast immer ein hardware problem..
 
  • Like
Reactions: Stoiko Ivanov
You must log in or register to reply here.
Top Bottom