Fix whatever caused the queue to go down...
cades@builderqueue:~$ tail -f /home/queue/ContainerBuilder.log
2017-12-11 17:22:31.440361 (656) [128.219.164.233:43774] : Established connection
2017-12-11 17:22:31.542644 (657) [128.219.164.233:43774] : Connection initial request error received bad message type: Bad message
2017-12-11 17:22:31.542674 (658) [128.219.164.233:43774] : Ending connection
2017-12-11 17:22:31.644552 (659) [128.219.164.233:43850] : Established connection
2017-12-11 17:22:31.745598 (660) [128.219.164.233:43850] : Connection initial request error received bad message type: Bad message
2017-12-11 17:22:31.746069 (661) [128.219.164.233:43850] : Ending connection
2017-12-11 17:22:31.847465 (662) [128.219.164.233:43934] : Established connection
2017-12-11 17:22:32.954434 (663) Running command: /home/queue/GetBuilders
2017-12-11 17:22:35.700940 (664) Running command: /home/queue/GetBuilders
2017-12-11 17:22:38.649908 (665) Running command: /home/queue/GetBuilders
cades@builderqueue:~$ sudo systemctl status BuilderQueue
● BuilderQueue.service - BuilderQueue daemon
Loaded: loaded (/etc/systemd/system/BuilderQueue.service; enabled; vendor preset: enabled)
Active: failed (Result: core-dump) since Mon 2017-12-11 17:22:39 UTC; 20h ago
Main PID: 964 (code=dumped, signal=ABRT)
Dec 11 16:53:51 builderqueue systemd[1]: Started BuilderQueue daemon.
Dec 11 17:22:39 builderqueue BuilderQueue[964]: terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
Dec 11 17:22:39 builderqueue BuilderQueue[964]: what(): remote_endpoint: Transport endpoint is not connected
Dec 11 17:22:39 builderqueue systemd[1]: BuilderQueue.service: Main process exited, code=dumped, status=6/ABRT
Dec 11 17:22:39 builderqueue systemd[1]: BuilderQueue.service: Unit entered failed state.
Dec 11 17:22:39 builderqueue systemd[1]: BuilderQueue.service: Failed with result 'core-dump'.
Edited by Simpson, Adam B