Okay, we had a number of things go wrong last night and I received an email from zLinux system:
Subject: [abrt] systemd: systemd-journald killed by SIGABRT reason: systemd-journald killed by SIGABRT cmdline: /usr/lib/systemd/systemd-journald executable: /usr/lib/systemd/systemd-journald package: systemd-219-78.el7_9.5 component: systemd pid: 2575 pwd: / hostname: mflnxclef00.ailife.com count: 1 abrt_version: 2.1.11 analyzer: CCpp architecture: s390x event_log: Machine-ID generator 'sosreport_uploader-dmidecode' failed: Could not find dmidecode. It might not be available for this architecture. global_pid: 2575 kernel: 3.10.0-1160.62.1.el7.s390x last_occurrence: 1658220785 machineid: systemd=d02295ef486d45f287f9e07e98cc909a os_release: CentOS Linux release 7.9.2009 (AltArch) pkg_arch: s390x pkg_epoch: 0 pkg_fingerprint: AE6A EFA8 DCBB 4D09 pkg_name: systemd pkg_release: 78.el7_9.5 pkg_vendor: (none) pkg_version: 219 runlevel: N 3 time: Tue 19 Jul 2022 03:53:05 AM CDT type: CCpp uid: 0 ureports_counter: 1 username: root uuid: 0e9686a5bcfa698487a3eaefff9432cf6329b010 reported_to: :uReport: BTHASH=030e43eefa24cd13d00580b9aca94566e47e96d0 :ABRT Server: URL=https://retrace.fedoraproject.org/faf/reports/bthash/030e43eefa24cd13d00580b9aca94566e47e96d0 core_backtrace: :{ "signal": 6 :, "executable": "/usr/lib/systemd/systemd-journald" :, "stacktrace": : [ { "crash_thread": true : , "frames": : [ { "address": 2929931616800 : , "build_id": "31c2409412fbac500e6f1222fe75ae20cff878f2" : , "build_id_offset": 33312 : , "function_name": "server_read_dev_kmsg" : , "file_name": "/usr/lib/systemd/systemd-journald" : } : , { "address": 2929931741990 : , "build_id": "31c2409412fbac500e6f1222fe75ae20cff878f2" : , "build_id_offset": 158502 : , "function_name": "source_dispatch" : , "file_name": "/usr/lib/systemd/systemd-journald" : } : , { "address": 2929931745184 : , "build_id": "31c2409412fbac500e6f1222fe75ae20cff878f2" : , "build_id_offset": 161696 : , "function_name": "sd_event_dispatch" : , "file_name": "/usr/lib/systemd/systemd-journald" : } : , { "address": 2929931616032 : , "build_id": "31c2409412fbac500e6f1222fe75ae20cff878f2" : , "build_id_offset": 32544 : , "function_name": "main" : , "file_name": "/usr/lib/systemd/systemd-journald" : } ] : } ] :} cgroup: :10:pids:/ :9:perf_event:/ :8:blkio:/ :7:net_prio,net_cls:/ :6:freezer:/ :5:cpuacct,cpu:/ :4:devices:/system.slice/systemd-journald.service :3:cpuset:/ :2:memory:/ :1:name=systemd:/system.slice/systemd-journald.service ...(continued on 2nd part email)... Frank Ramaekers Jr. | Systems Senior Administrator | CIS Mainframe Services Unisys | O-(512) 387-3949 | M-(254) 214-1820 | [email protected]<mailto:[email protected]> [unisys_logo]<http://www.unisys.com/> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all devices. [Grey_LI]<http://www.linkedin.com/company/unisys> [Grey_TW] <http://twitter.com/unisyscorp> [Grey_GP] <https://plus.google.com/+UnisysCorp/posts> [Grey_YT] <http://www.youtube.com/theunisyschannel> [Grey_FB] <http://www.facebook.com/unisyscorp> [Grey_Vimeo] <https://vimeo.com/unisys> [Grey_UB] <http://blogs.unisys.com/> [Grey_Weibo] <https://weibo.com/unisyschina> ---------------------------------------------------------------------- This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at [email protected]. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
