Comment 2 for bug 1298663

I'm not sure that this is *actually* a regression, since I don't think
debug-log has really ever worked with the local provider in juju-core.

On Sun, Mar 30, 2014 at 11:32 AM, John Meinel <email address hidden>wrote:

> The actual all-machines.log file is namespaced now, so it should be going
> to eg /var/log/juju-jameinel-local/all-machines.log
>
> I actually am getting the original failure of not being able to SSH to
> localhost, but I can see that it is trying to tail the wrong file even if I
> had sshd running:
> 2014-03-30 07:30:45 DEBUG juju.utils.ssh ssh_openssh.go:122 running: ssh
> -o "StrictHostKeyChecking no" -o "PasswordAuthentication no" -t -t -i
> /home/jameinel/.juju/ssh/juju_id_rsa -i /home/jameinel/.ssh/id_rsa
> ubuntu@localhost "tail -n 10 -f /var/log/juju/all-machines.log"
>
>
>
> On Fri, Mar 28, 2014 at 8:52 PM, William Reade <<email address hidden>
> > wrote:
>
>> ** Changed in: juju-core
>> Importance: High => Critical
>>
>> --
>> You received this bug notification because you are subscribed to juju-
>> core.
>> https://bugs.launchpad.net/bugs/1298663
>>
>> Title:
>> juju debug-log broken in 1.17.6
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/juju-core/+bug/1298663/+subscriptions
>>
>
>