Description of problem: I changed PostgreSQL settings to increase some buffers. The changes require more SHM but before increasing kernel.shmall and shmmax, I used to launch PostgreSQL to know exactly how much memory I must allocate (displayed in PostgreSQL logs on failure). On systemctl start postgresql.service, dbus and systemd have crashed. Version-Release number of selected component: systemd-197-1.fc18.1 Additional info: backtrace_rating: 4 cmdline: /usr/lib/systemd/systemd --switched-root --system --deserialize 22 crash_function: _IO_new_fclose executable: /usr/lib/systemd/systemd kernel: 3.7.4-204.fc18.x86_64 remote_result: NOTFOUND uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #8 _IO_new_fclose at iofclose.c:85 #9 get_parent_of_pid at src/shared/util.c:426 #10 cgroup_bonding_search_main_pid at src/core/cgroup.c:564 #11 cgroup_bonding_search_main_pid_list at src/core/cgroup.c:593 #12 service_search_main_pid at src/core/service.c:1455 #14 service_sigchld_event at src/core/service.c:3098 #15 manager_dispatch_sigchld at src/core/manager.c:1162 #16 manager_process_signal_fd at src/core/manager.c:1405 #17 process_event at src/core/manager.c:1430 #18 manager_loop at src/core/manager.c:1604
Created attachment 689720 [details] File: backtrace
Created attachment 689721 [details] File: cgroup
Created attachment 689722 [details] File: core_backtrace
Created attachment 689723 [details] File: dso_list
Created attachment 689724 [details] File: environ
Created attachment 689725 [details] File: limits
Created attachment 689726 [details] File: maps
Created attachment 689727 [details] File: open_fds
Created attachment 689728 [details] File: proc_pid_status
Created attachment 689729 [details] File: var_log_messages
This crash in get_parent_of_pid() is already fixed in this proposed update: https://admin.fedoraproject.org/updates/systemd-197-1.fc18.2
For the record, this upstream commit is the fix: commit 86ed7ec58b9b6a0907bbb3b8d07c930e52915de0 Author: Lennart Poettering <lennart> Date: Thu Jan 17 17:38:00 2013 +0100 util: fix bad memory access
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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.