Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

debian12 cloud-init fails with SEGV

Ask for help with issues regarding the Installations of the Debian O/S.
Post Reply
Message
Author
uvisg
Posts: 2
Joined: 2024-04-19 11:07

debian12 cloud-init fails with SEGV

#1 Post by uvisg »

Hi guys.

I have issues to deploy Debian 12 on KVMs servers. I have tried different versions of images for Debian 12 and also different versions of KVMs and no success. In the same time Debian 11 deploys absolutely without any issues, while Debian 12 always gets cloud-init servic SEGV error. Tried to install different cloud-init versions and result always the same. Anybody here have faced the same issue?

Thank You in advance.

Regards,
Uvis

uvisg
Posts: 2
Joined: 2024-04-19 11:07

python3.11.2 segv cloud-init

#2 Post by uvisg »

Hi,

Am I only one here to face bug on python3.11.2 on Debian12? I can only use cloud init when install python3.9.x and cloud-init version which works with python3.9.x, but with 3.11.2 also tried latest 3.11.9 it all the times fails with SEGV. For me by viewing different logs it seems that issue is with libc6 package. But I am not expert at this, just what i see.

Code: Select all

root@debian:/home/debian# systemctl status cloud-init
× cloud-init.service - Initial cloud-init job (metadata service crawler)
     Loaded: loaded (/lib/systemd/system/cloud-init.service; enabled; preset: enabled)
     Active: failed (Result: signal) since Mon 2024-04-22 15:53:58 UTC; 57min ago
    Process: 500 ExecStart=/usr/bin/cloud-init init (code=killed, signal=SEGV)
   Main PID: 500 (code=killed, signal=SEGV)
        CPU: 4ms

Apr 22 15:53:58 debian systemd[1]: Starting cloud-init.service - Initial cloud-init job (metadata service crawler)...
Apr 22 15:53:58 debian systemd[1]: cloud-init.service: Main process exited, code=killed, status=11/SEGV
Apr 22 15:53:58 debian systemd[1]: cloud-init.service: Failed with result 'signal'.
Apr 22 15:53:58 debian systemd[1]: Failed to start cloud-init.service - Initial cloud-init job (metadata service crawler).
root@debian:/home/debian# 
In dmesg logs:

Code: Select all

[    3.983698] systemd-journald[264]: Received client request to flush runtime journal.
[    4.006907] cloud-init[456]: segfault at 34ba1da60 ip 00000000004fd56c sp 00007ffffc5830f0 error 4 in python3.11[41f000+2b3000] likely on CPU 0 (core 0, socket 0)
[    4.006923] Code: ec 18 48 83 05 f4 e5 53 00 01 48 8b 05 0d e4 55 00 48 8b 50 10 8b 82 28 14 00 00 85 c0 74 5f 83 e8 01 89 82 28 14 00 00 48 98 <48> 8b 84 c2 a8 11 00 00 8b 15 ca c9 53 00 85 d2 75 56 48 c7 00 01
[    4.176813] cloud-init[500]: segfault at 34ba1da60 ip 00000000004fd56c sp 00007ffe32ca4360 error 4 in python3.11[41f000+2b3000] likely on CPU 2 (core 0, socket 2)
[    4.176841] Code: ec 18 48 83 05 f4 e5 53 00 01 48 8b 05 0d e4 55 00 48 8b 50 10 8b 82 28 14 00 00 85 c0 74 5f 83 e8 01 89 82 28 14 00 00 48 98 <48> 8b 84 c2 a8 11 00 00 8b 15 ca c9 53 00 85 d2 75 56 48 c7 00 01
[    4.451246] cloud-init[503]: segfault at 34ba1da60 ip 00000000004fd56c sp 00007ffc6bec37a0 error 4 in python3.11[41f000+2b3000] likely on CPU 2 (core 0, socket 2)
[    4.451259] Code: ec 18 48 83 05 f4 e5 53 00 01 48 8b 05 0d e4 55 00 48 8b 50 10 8b 82 28 14 00 00 85 c0 74 5f 83 e8 01 89 82 28 14 00 00 48 98 <48> 8b 84 c2 a8 11 00 00 8b 15 ca c9 53 00 85 d2 75 56 48 c7 00 01
[    4.643899] cloud-init[521]: segfault at 34ba1da60 ip 00000000004fd56c sp 00007ffe500a6370 error 4 in python3.11[41f000+2b3000] likely on CPU 1 (core 0, socket 1)
[    4.643961] Code: ec 18 48 83 05 f4 e5 53 00 01 48 8b 05 0d e4 55 00 48 8b 50 10 8b 82 28 14 00 00 85 c0 74 5f 83 e8 01 89 82 28 14 00 00 48 98 <48> 8b 84 c2 a8 11 00 00 8b 15 ca c9 53 00 85 d2 75 56 48 c7 00 01
root@debian:/home/debian
Debug from gdb:

Code: Select all

(gdb) run /usr/bin/cloud-init
Starting program: /usr/bin/python3 /usr/bin/cloud-init
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x00000000004fd56c in PyDict_New ()
(gdb) bt
#0  0x00000000004fd56c in PyDict_New ()
#1  0x00000000004fd096 in ?? ()
#2  0x000000000062ca4b in ?? ()
#3  0x00000000004f939c in ?? ()
#4  0x0000000000628926 in ?? ()
#5  0x000000000062863b in Py_InitializeFromConfig ()
#6  0x00000000006278e9 in ?? ()
#7  0x0000000000627730 in ?? ()
#8  0x00000000006275c7 in Py_BytesMain ()
#9  0x00007ffff7cdc24a in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#10 0x00007ffff7cdc305 in __libc_start_main ()
   from /lib/x86_64-linux-gnu/libc.so.6
#11 0x0000000000627461 in _start ()

Aki
Global Moderator
Global Moderator
Posts: 3080
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 76 times
Been thanked: 417 times

Re: debian12 cloud-init fails with SEGV

#3 Post by Aki »

Moderator edit: merged discussions on the same topic
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

Post Reply