Main process exited, code=killed, status=7/BUS

Installation
1

Hello!

Any of you experienced this error or know what causing it?

homeassistant.service: Main process exited, code=killed, status=7/BUS
homeassistant.service: Unit entered failed state.
homeassistant.service: Failed with result 'signal'.

It happens on two raspberry and a 16.04 ubuntu. New installation or old config. Same error. Happens on manual service start or randomly through the day. :frowning:

2

Different hardware?

3

On the pies, it happens when i restart hass from the webui.
On the ubuntu machine, when restarting hass from ssh or webui, rebooting, and if i manage to boot it up it crashes randomly after a while.

Is there any way to check a detailed error log?

edit: Strangly, these instances worked for months, (nearly a year). They are connected together by mosq mqtt.

4

I believe the TTS is whats killing my hass processes

This is the error msg i get when booting up HASS (it still boots fine, until tts is called)

pulseaudio[2679]: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
pulseaudio[2679]: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
5

Pulseaudio? What’re you using that’s trying to play media locally?

6

Amazon Polly!

Today i tried to play a test automation for TTS service (just a basic “helloworld”) when hass crashed. I couldnt even start it back up. It kept crashing at service startup with the status=7/BUS. I had to reboot the ubuntu server to succesfully start hass. :confused:

7

That suggests you’ve got a deeper issue, it might be related to installing the desktop environment, I’m unsure. I’d try a fresh Pi3 install of Hassbian, so that you’re not running any GUI on your server.

8

It was some pulseaudio problem. Reinstalled. Seems to be working now. Thank you.