Systemd - dbus gets killed

Hey all,
I recently switched to systemd. But now on some boots (not all) dbus gets killed after about a minute.
Here's the part in journalctl:
Aug 17 13:52:03 rhaego dbus-daemon[290]: dbus[290]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
Aug 17 13:52:03 rhaego dbus[290]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
Aug 17 13:52:03 rhaego dbus[290]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Aug 17 13:52:03 rhaego dbus-daemon[290]: dbus[290]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Aug 17 13:52:03 rhaego dbus-daemon[290]: process 290: arguments to dbus_message_set_reply_serial() were incorrect, assertion "reply_serial != 0" failed in file
Aug 17 13:52:03 rhaego dbus-daemon[290]: This is normally a bug in some application using the D-Bus library.
Aug 17 13:52:03 rhaego dbus-daemon[290]: D-Bus not built with -rdynamic so unable to print a backtrace
Aug 17 13:52:03 rhaego systemd[1]: dbus.service: main process exited, code=killed, status=6
full log: http://pastebin.com/1yBztRyu
Does anyone know why this is?
Or how to rebuild dbus with -rdynamic, I already tried adding --enable-rdynamic or -rdynamic to the ./configure line in the PKGBUILD, but that's not working..

Ok I "solved" this a while ago. MPD is trying to start avahi and that fails and causes dbus to crash... I don't know if the problem is that it can't find avahi-daemon.service, or something else.
I don't need avahi so now I have this in /etc/mpd.conf
zeroconf_enabled                "no"
EDIT: tried again without this line after an update. It's still failing to start avahi, but not crashing dbus anymore :
Sep 11 12:48:11 rhaego dbus-daemon[286]: dbus[286]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Sep 11 12:48:11 rhaego dbus[286]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Sep 11 12:48:11 rhaego dbus[286]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'sy
Sep 11 12:48:11 rhaego dbus-daemon[286]: dbus[286]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See s
Last edited by wildebeestje (2012-09-11 08:53:07)

Similar Messages

  • Systemd/user: tmux sessions get killed when stopping systemd session

    Following the wiki guide on systemd/user, I am now starting my X sessions using systemd unit files for my user.
    My problem: when I quit X or exit the systemd session (for example through $ systemctl --user exit), my tmux sessions get killed along with it. Note, I do not start tmux with unit files, but simply through invoking “tmux” in a virtual terminal. I have also tried detaching the tmux session before quitting the systemd session, but to no avail.
    How can I make my tmux sessions survive X closing?

    That is beacuse tmux becomes a child process of the systemd --user session.  So it gets caught up in the cgroup and everything.  What I have done is I start a system service of tmux as my user (I have creatively come up with the name "[email protected]").  Here is what I've got, that has been working for me:
    % cat /etc/systemd/system/[email protected]
    [Unit]
    Description=Start detached tmux session
    After=multi-user.target
    Before=shutdown.target
    [Service]
    Type=forking
    User=%I
    WorkingDirectory=%h
    ExecStart=/usr/bin/tmux new-session -d -s %u
    ExecStop=/usr/bin/tmux kill-session -t %u
    Restart=always
    [Install]
    WantedBy=multi-user.target
    Last edited by WonderWoofy (2013-04-27 22:35:27)

  • Restart automatically if application gets killed

    I have this issue for two precise applications:
    1. Mplayer - Wich I use as wallpaper but sometimes gets killed
    2. Osdlyrics - It gest killed for no special reason (Seg fault)
    I want to make a script so this applications be restarted in case they get killed, how could I track that and restart it?
    Thank you

    OK I'll show you what I have :
    [Service]
    Type=simple
    ExecStart=/usr/bin/wallpaper
    ExecStartPre=/usr/bin/xfdesktop
    Restart=always
    systemd status wallpaper.service throws:
    wallpaper.service
    Loaded: loaded (/etc/systemd/system/wallpaper.service; static)
    Active: failed (Result: start-limit) since sáb 2013-11-02 12:10:38 CST; 11s ago
    Process: 13911 ExecStartPre=/usr/bin/xfdesktop (code=exited, status=1/FAILURE)
    Main PID: 1743 (code=exited, status=0/SUCCESS)
    If I remove the line of xfdesktop the output shows as active but nothing is displaying
    THis is my /usr/bin/wallpaper :
    #!/bin/bash
    WIND=$(xwininfo -name Escritorio | egrep -E '0x' | cut -d':' -f3 | cut -d'"' -f1| cut -d' ' -f2)
    echo "Desktop is " $WIND
    mkfifo /tmp/mplayer-control
    touch /tmp/wallpaper-status
    DesktopMovie -wid $WIND -x 1366 -y 768 -slave -input file=/tmp/mplayer-control -shuffle -loop 0 -playlist /home/axelectrik/.config/wallpaper/playlist.m3u &> /tmp/wallpaper-status &
    echo "Playing" $WIND
    ANd the output of /tmp/wallpaper-status is:
    Cannot find HOME directory.
    The wid option must be an integer: -x
    Error parsing commandline option "-wid": Option parameter could not be parsed
    MPlayer2 2.0-726-g6c87a98 (C) 2000-2012 MPlayer Team
    So I don't know why the service cannot start xfdesktop, or if is already started why xwininfo is not giving the xfdesktop window ID so mplayer starts over there.
    Last edited by axelectrik (2013-11-02 18:23:21)

  • The app gets killed on navigating to one or two views without showing any crash logs. How to check the cause of crash?

    On launching the app, it works fine upto two or three pages and gets killed after some time. Currently not able to figure out what is the reason since its not showing any logs in device as well the project. In case there are memory issues , how can I fix them?
    logs:
    Apr 28 03:56:30 SETLPERV-iPad com.apple.launchd[1] (UIKitApplication:9K7XF2E952.com.infosys.mconnect[0x34ba][2294]) <Notice>: (UIKitApplication:9K7XF2E952.com.infosys.mconnect[0x34ba]) Bug: launchd_core_logic.c:3733 (25562):0
    Apr 28 03:56:30 SETLPERV-iPad UserEventAgent[12] <Notice>: jetsam: kernel termination snapshot being created
    Apr 28 03:56:30 SETLPERV-iPad com.apple.debugserver-64[2292] <Warning>: 1 [08f4/1303]: error: ::read ( 4, 0x2ff719d4, 1024 ) => -1 err = Bad file descriptor (0x00000009)
    Apr 28 03:56:30 SETLPERV-iPad com.apple.launchd[1] (UIKitApplication:9K7XF2E952.com.infosys.mconnect[0x34ba][2294]) <Notice>: (UIKitApplication:9K7XF2E952.com.infosys.mconnect[0x34ba]) Bug: launchd_core_logic.c:3732 (25562):3
    Apr 28 03:56:30 SETLPERV-iPad com.apple.launchd[1] (UIKitApplication:9K7XF2E952.com.infosys.mconnect[0x34ba][2294]) <Notice>: (UIKitApplication:9K7XF2E952.com.infosys.mconnect[0x34ba]) Assuming job exited: <rdar://problem/5020256>: 10: No child processes
    Apr 28 03:56:30 SETLPERV-iPad com.apple.launchd[1] (UIKitApplication:9K7XF2E952.com.infosys.mconnect[0x34ba][2294]) <Warning>: (UIKitApplication:9K7XF2E952.com.infosys.mconnect[0x34ba]) Job appears to have crashed: Segmentation fault: 11
    Apr 28 03:56:32 SETLPERV-iPad ReportCrash[2299] <Error>: libMobileGestalt computeUniqueDeviceID: total time for bb to return imei: 0
    Apr 28 03:56:32 SETLPERV-iPad ReportCrash[2299] <Notice>: Saved crashreport to /Library/Logs/CrashReporter/LowMemory-2014-04-28-035632.plist using uid: 0 gid: 0, synthetic_euid: 0 egid: 0

    Use Instruments to Profile the app.
    You can use Heapshots to see where memory is being allocated but not released.

  • Process not getting killed

    Hi ,
    I tried killing the process but still it is not getting killed.Used the below command.
    kill -9 <pid>
    sapkxdap10:orads2 9> ps -ef | grep sap
    sidadm   25255     1  0 Sep21 ?        01:00:18 dw.sapSID_DVEBMGS68 pf=/usr/sap/SID/SYS/profile/SID_DVEBMGS68_sapkxdap10
    I cannot understand what the second field means question mark is there.How to kill the process if they are hung.Thanks.

    > How should i proceed even after stopping sap if the process exists?
    I don't know - I have no clue under which circumstances something that like can occur. You can check using
    ipcs -m
    if there are any shared memory segments allocated. Also stop/kill "saposcol" and "sapstartsrv".
    > And what does that question mark indicate in the output..Thanks.
    Execute
    man ps
    The question mark means the process has no connected terminal (just read the headline when you execute ps -ef) and was started by another process.

  • How to prevent session getting  killed

    Hi All,
    I am trying to execute a procedure which contains a long running query .
    The query takes so much time to execute that the session gets killed .
    Can anybody please let me know what should I do to prevent my session being killed/
    Is there any parameter to be set to do so?
    Many thanks in advance.

    try to avoid posting 2 questions for the same subject
    Can I alter the default profile

  • Dock application gets killed itself on Lion, how to debug this issue?

    Hi, Dock application gets killed itself and it dissappears and relaunches itself after for few seconds, This is happening for every 5 min or so. it is quite annoying problem. how to debug this issue? any help?

    When I look the system logs - there is an exception each time I try to run the application or open a window:
    9/5/09 10:33:12 PM Linear[23545] Cannot create BOOL from object <Regression: 0x1461f0> of class Regression

  • Process getting killed automatically

    Hi
    I am using jdk 1.5 and java processes are getting killed automatically on server. Processes were working on test servers. Is anybody facing the same issue or knowledge about the same.
    Regards,
    Niraj

    Niraj,
    Can you explain your scenario a bit more clearer.?
    Mandrake

  • Java application getting killed automatically in Solaris

    Hi to all,
    I have developed a Java application for Solaris 10.
    But it is getting killed after some time.
    And at the terminal, I got message as Killed.
    I am new to Solaris.
    Can anybody help me?

    Nijai.Ashish wrote:
    Hi to all,
    I have developed a Java application for Solaris 10.
    But it is getting killed after some time.
    And at the terminal, I got message as Killed.
    I am new to Solaris.
    Can anybody help me?Are you hitting a resource limitation for your user account (e.g. only allotted a certain amount of CPU time)?

  • Kjs engine gets killed

    see server performance
    load averages: 0.27, 0.24, 0.25 18:08:44
    117 processes: 114 sleeping, 2 zombie, 1 on cpu
    CPU states: 90.5% idle, 2.4% user, 7.1% kernel, 0.0% iowait, 0.0% swap
    Memory: 2048M real, 128M free, 1619M swap in use, 3992M swap free
    PID USERNAME THR PRI NICE SIZE RES STATE TIME CPU COMMAND
    1473 root 55 12 0 270M 215M sleep 3:06 1.61% .kjs
    27817 root 69 58 0 304M 246M sleep 21:54 1.43% .kjs
    20332 root 57 58 0 436M 363M sleep 43:07 1.22% .kjs
    1571 root 55 11 0 265M 209M sleep 3:10 1.13% .kjs
    20363 root 57 58 0 372M 312M sleep 38:00 1.12% .kjs
    29370 root 1 43 0 2248K 1544K cpu/0 1:09 0.66% top
    20322 root 31 58 0 41M 39M sleep 9:02 0.39% .kxs
    but ks engines killed automatically in iplanet apps server.No specifice errors
    Below errors comes and engines gets killed
    [17/Feb/2005 12:30:13:1] warning: UTIL-013: GXGUID: NameTrans lookup failed (Applogic Servlet com_EmployeeReferralFriendsViewJobsAtIntra)
    [17/Feb/2005 12:33:20:5] warning: UTIL-013: GXGUID: NameTrans lookup failed (Applogic Servlet com_EmployeeReferralFriendsViewJobsAtIntra)
    [17/Feb/2005 14:14:02:9] warning: UTIL-013: GXGUID: NameTrans lookup failed (Applogic Servlet com_EmployeeReferralFriendsViewJobsAtIntra)
    [17/Feb/2005 15:25:59:3] error: CONN-003: socket receive error (RecvBuffer 1) (conn 0x10c72d8, sock 24, host 0xac8312f, port 0)
    [17/Feb/2005 15:25:59:3] error: CONN-003: socket receive error (RecvBuffer 1) (conn 0x10f7be8, sock 34, host 0xac8312f, port 10824)
    [17/Feb/2005 16:53:05:0] error: CONN-003: socket receive error (RecvBuffer 1) (conn 0x1575978, sock 28, host 0xac8312f, port 10822)
    [17/Feb/2005 16:53:05:0] error: CONN-003: socket receive error (RecvBuffer 1) (conn 0x14cd6c8, sock 32, host 0xac8312f, port 0)
    [17/Feb/2005 16:54:24:0] error: CONN-003: socket receive error (RecvBuffer 1) (conn 0xab08d8, sock 34, host 0xac8312f, port 10824)
    [17/Feb/2005 16:54:24:1] error: CONN-003: socket receive error (RecvBuffer 1) (conn 0xa655a0, sock 26, host 0xac8312f,.Pls suggest me what could be the problem.

    You might have more luck posting your question in the Sun ONE Application Server 6 forum.

  • Does this application in memory get killed over a period?

    Hi I am a Iphone 4G owner recently, want check if someone already knows about. I know someone must have had this question before. In this new multitasking, we open multiple apps and it appears back and forth when we press home button two times.
    Is this apps gets killed over a period of time automatically? or do we need to kill them manually? Or is there any apps can take care off it.
    I am on IOS 4

    Read here to understand the multitasking bar:
    http://whenwillapple.com/blog/2010/04/19/iphone-os-4-multitasking-explained-agai n/

  • Kjs Engine gets killed frequently

    sir ,
    i have posted before the same problem but i found very poor response even after assighning duke dollers.Why its getting delayed ???
    My qurey is i have iplanet webserver 4.1 and appserver 6.0 installed on separate sun servers.In the app server i am seeing my kjs engines gets killed frequently even my server load and no of connections are normal.What could be the possible reasons for this???
    Pls respond immedietly....
    Regards
    Suresh.

    You might have more luck posting your question in the Sun ONE Application Server 6 forum.

  • Upgrading systemd Error getting authority

    Hmm, upgrading today  got me this
    pacman -Syu bind
    (12/41) upgrading systemd
    upgrading systemd Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)
    does this mean an install broke, or what..

    This post seems to be related to your question.
    https://bbs.archlinux.org/viewtopic.php?id=153610

  • Weblogic threads getting killed

    Hi,
    We are facing a problem where after few hours of usage all the threads
    in the 'default' queue are getting killed i.e the server hangs and if
    you take a thread dump, none of the threads in the default queue are
    visible ...
    Using WL 6.1 SP 3 on RH Linux.
    What could be the reasons why this would happen ?
    Any inputs would be appreiciated.
    Regards
    Vipul Kapadia

    Hi Gautier,
    We were able to solve the problem. It was to do with the JVM
    configuration.
    We were using Sun JDK 1.3.1_03.
    Set the parameter in the Java command line
    -XX:MaxPermSize=128m
    See if this works for you.
    Also go thru the Weblogic Server Performance and tuning guides which
    has some useful information.
    Regards
    Vipul Kapadia
    "Gautier Lobry" <[email protected]> wrote in message news:<3def348d$[email protected]>...
    We are facing the same Problem for ten days and could not find out what leads to
    that. For some reason, a number of the pool's threads are getting lost within
    a few minutes, after the server had been running for hours.
    If you've found something, it would be nice if you could help.
    Thanks
    Gautier
    "Cameron Purdy" <[email protected]> wrote:
    We are facing a problem where after few hours of usage all the threads
    in the 'default' queue are getting killed i.e the server hangs andif
    you take a thread dump, none of the threads in the default queue are
    visible ...
    Using WL 6.1 SP 3 on RH Linux.Check your WL logs.
    Typically this points to a serious JVM or config issue.
    Peace,
    Cameron Purdy
    Tangosol, Inc.
    http://www.tangosol.com/coherence.jsp
    Tangosol Coherence: Clustered Replicated Cache for Weblogic
    "Vipul Kapadia" <[email protected]> wrote in message
    news:[email protected]..
    >

  • Java API - EventHandler threads not getting killed

    Hello everybody,
    I didn't know whether to post this in the PI forum or in the MDM forum. I use the following scenario:
    We run an EJB session bean in the Java Proxy environment of PI 7.1. In this bean we create an MDM session, log on to a repository and then attach a RecordListener that reacts to any change of the records. When an interesting change took place, the record is distributed to PI.
    The code looks like this:
    EventDispatcher evDis = new EventDispatcher(servername);
    RecordListener recLis = new RecordListener();
    evDis.registerDataNotifications(username, password, repIdent, regions[0]);
    evDis.addListener(recLis);
    The problem arises when we try to undeploy or stop the application. You would assume that it would stop everything connected to the application. However, it does not. The mentioned EventDispatcher creates a thread object when invoked, and this thread is never killed. The consequence: Records keep getting distributed as if nothing had happened, although the application is gone (even undeploying doesn't help). But when we redeploy the application, a new thread is created. So after some development you get 10 or more threads firing every change to PI. The only thing that helps is a restart of the J2EE engine.
    So, my question: Has anybody here made a similar experience? Is this common for MDM or is rather PI the cause of this issue?
    Any comments on that are very welcome.
    Best regards,
    Jörg

    Hi Veera,
    thanks a lot, that pot me on the right track! In fact, it's the @PreDestroy annotation which has to be used for some cleanup method. When we execute this and included the coding you mentioned the threads are killed properly.
    Currently we're facing the issue that somehow the commit status of the bean is not set to "Committed" and from the second message on we get exceptions. If anybody came across this, help is appreciated.
    Best regards,
    Jörg

Maybe you are looking for