Version-Release number of selected component: cockpit-ws-201-1.fc30 Additional info: reporter: libreport-2.10.1 backtrace_rating: 4 cmdline: /usr/libexec/cockpit-tls crash_function: connection_init_ws executable: /usr/libexec/cockpit-tls journald_cursor: s=ceaa74da315c48cca3fc434be7e21bf2;i=1a095fe8;b=01ae240aa80942e59a6ba18ab41281b7;m=1a1919fb0ca;t=5922817e589a9;x=82f42cb9606ca4c0 kernel: 5.2.8-200.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 996 Truncated backtrace: Thread no. 1 (5 frames) #5 connection_init_ws at src/tls/server.c:256 #6 handle_connection_data_first at src/tls/server.c:376 #7 handle_connection_data at src/tls/server.c:406 #8 server_poll_event at src/tls/server.c:649 #9 server_run at src/tls/server.c:674
Created attachment 1614573 [details] File: backtrace
Created attachment 1614574 [details] File: cgroup
Created attachment 1614575 [details] File: core_backtrace
Created attachment 1614576 [details] File: cpuinfo
Created attachment 1614577 [details] File: dso_list
Created attachment 1614578 [details] File: environ
Created attachment 1614579 [details] File: limits
Created attachment 1614580 [details] File: maps
Created attachment 1614581 [details] File: mountinfo
Created attachment 1614582 [details] File: open_fds
Created attachment 1614583 [details] File: proc_pid_status
Created attachment 1614584 [details] File: var_log_messages
The logs have tons of TLS handshake failed: No supported cipher suites have been found. TLS handshake failed: Error in the pull function. reading from client fd 7 TLS connection failed: Decryption has failed. However, this isn't a crash, it would "just" lead to failed connections. Can you please describe exactly what you are trying to do, whether you did any modifications to GnuTLS, the browser TLS settings, etc., and give me the output of sudo systemctl status cockpit after such a failure happened? Thanks!
Only thing I see is a dnf update run just a couple of moments before. I found a core dump and saw this: Sep 9 20:33:20 systemd-coredump[32925]: Process 31833 (cockpit-tls) of user 996 dumped core. Stack trace of thread 31833: #0 0x00007f9c31f511d0 __libc_free (libc.so.6) #1 0x000055fcdf70143d n/a (cockpit-tls) #2 0x000055fcdf702662 n/a (cockpit-tls) #3 0x000055fcdf70281f n/a (cockpit-tls) #4 0x000055fcdf700c8c n/a (cockpit-tls) #5 0x00007f9c31eedf43 __libc_start_main (libc.so.6) #6 0x000055fcdf700cfe n/a (cockpit-tls) Sep 9 20:33:20 systemd[1]: systemd-coredump: Succeeded. Sep 9 20:33:22 abrt-notification[33004]: Process 31833 (cockpit-tls) crashed in __libc_free() Sep 9 20:33:24 kernel: RPC: fragment too large: 469762048 Here's a gdb backtrace: Reading symbols from /usr/libexec/cockpit-tls... Reading symbols from /usr/lib/debug/usr/libexec/cockpit-tls.debug... [New LWP 31833] Core was generated by `/usr/libexec/cockpit-tls'. Program terminated with signal SIGSEGV, Segmentation fault. (gdb) bt full #0 0x00007f9c31f511d0 in ?? () cockpit is disabled: systemctl status cockpit ● cockpit.service - Cockpit Web Service Loaded: loaded (/usr/lib/systemd/system/cockpit.service; static; vendor preset: disabled) Active: inactive (dead) since Mon 2019-09-09 20:46:28 EDT; 6 days ago Docs: man:cockpit-ws(8) Main PID: 40302 (code=exited, status=0/SUCCESS) Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. No symbol table info available. #1 0x000055fce0fd5280 in ?? () No symbol table info available. #2 0x00007f9c32110383 in ?? () No symbol table info available. #3 0x000055fce0fd52a0 in ?? () No symbol table info available. #4 0x000055fcdf70143d in ?? () No symbol table info available. #5 0x000055fce0fd5280 in ?? () No symbol table info available. #6 0x000055fcdf702662 in ?? () No symbol table info available. #7 0x0000000000000000 in ?? () No symbol table info available.
I'm afraid the backtrace is completely useless. What were you doing exactly in/with Cockpit at the time of the upgrade? Did you notice any visible malfunction? I tried a naive "sudo systemctl restart cockpit.socket cockpit.service" (the essence of what happens when upgrading the cockpit package) a few times, and it does not crash.
(In reply to Martin Pitt from comment #15) > I'm afraid the backtrace is completely useless. What were you doing exactly > in/with Cockpit at the time of the upgrade? Did you notice any visible > malfunction? > > I tried a naive "sudo systemctl restart cockpit.socket cockpit.service" (the > essence of what happens when upgrading the cockpit package) a few times, and > it does not crash. The dnf update was a regularly scheduled update via cron. Also note that cockipit is disabled on this server.
> note that cockipit is disabled on this server. How did you do this, and what did you mean to do? Clearly cockpit.service ran during that time, thus cockpit.socket ran as well. The cockpit-ws rpm script does not start these, only restart if they are running ("try-restart"). Can you check "systemctl status cockpit.socket cockpit.service"? Supposedly cockpit.socket is enabled, or possibly you ran "systemctl start cockpit.socket" manually?
(In reply to Martin Pitt from comment #17) > > note that cockipit is disabled on this server. > > How did you do this, and what did you mean to do? Clearly cockpit.service > ran during that time, thus cockpit.socket ran as well. The cockpit-ws rpm > script does not start these, only restart if they are running > ("try-restart"). Can you check "systemctl status cockpit.socket > cockpit.service"? Supposedly cockpit.socket is enabled, or possibly you ran > "systemctl start cockpit.socket" manually? Sorry about that I thought it was previously disabled. systemctl status cockpit.socket cockpit.service ● cockpit.socket - Cockpit Web Service Socket Loaded: loaded (/usr/lib/systemd/system/cockpit.socket; enabled; vendor preset: enabled) Active: active (listening) since Wed 2019-09-11 09:26:29 EDT; 1 weeks 1 days ago Docs: man:cockpit-ws(8) Listen: [::]:9090 (Stream) Tasks: 0 (limit: 7372) Memory: 2.1M CGroup: /system.slice/cockpit.socket Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. ● cockpit.service - Cockpit Web Service Loaded: loaded (/usr/lib/systemd/system/cockpit.service; static; vendor preset: disabled) Active: inactive (dead) since Mon 2019-09-16 20:28:22 EDT; 2 days ago Docs: man:cockpit-ws(8) Main PID: 16188 (code=exited, status=0/SUCCESS) Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.