Bug#866098: waagent: Walinuxagent could not start after enable LDAP authentication

2017-06-27 Thread Bastian Blank
On Tue, Jun 27, 2017 at 04:11:51PM +0400, Lozenkov Sergei wrote: > 1. After reboot it was no logs at all: > # journalctl -b -u walinuxagent I asked to "journalctl -b", not "journalctl -b -u walinuxagent". Bastian -- Bastian Blank Berater Telefon: +49 2166 9901-194 E-Mail: bastian.bl...@credati

Bug#866098: waagent: Walinuxagent could not start after enable LDAP authentication

2017-06-27 Thread Lozenkov Sergei
Good day. 1. After reboot it was no logs at all: # journalctl -b -u walinuxagent -- Logs begin at Tue 2017-06-27 11:19:35 UTC, end at Tue 2017-06-27 12:01:51 UTC. -- And waagent.log after booting contains only several strings: 2017/06/27 11:15:40.977124 INFO Agent WALinuxAgent-2.2.2 forwarding si

Bug#866098: waagent: Walinuxagent could not start after enable LDAP authentication

2017-06-27 Thread Bastian Blank
Hi Sergey On Tue, Jun 27, 2017 at 11:12:51AM +, Sergey Lozenkov wrote: > 2017/06/27 07:03:52 - is time of the last reboot of VM. > If I try to execute 'systemctl start walinuxagent' the comand is hanging and > nothing happens. Please provide the complete journal since the last boot (try "jou

Bug#866098: waagent: Walinuxagent could not start after enable LDAP authentication

2017-06-27 Thread Sergey Lozenkov
Package: waagent Version: 2.2.2-2~bpo8+1 Severity: important Dear Maintainer, I have installed VM of Debian 8 in Microsoft Azure. On clean system service walinuxagent works well. But after I applied some customization needed for me (install packages, customize sshd service, enabling LDAP authen