juju debug-log broken in 1.17.6

[Kapil Thangavelu]

returns with

tail: cannot open '/var/log/juju/all-machines.log' for reading: No such file or directory

[John A Meinel (jameinel)]

 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
>

[John A Meinel (jameinel)]

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
>>
>
>

[Kapil Thangavelu (hazmat)]

that was with ec2 provider not local

On Sun, Mar 30, 2014 at 12:33 AM, John A Meinel <email address hidden>wrote:

> 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 <john@arbash-
> meinel.com>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
> >>
> >
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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
>

[Kapil Thangavelu (hazmat)]

oddly it works fine for me with manual with 1.17.7, the original error
report was reported by two other juju users using 1.17.6 against ec2

On Sun, Mar 30, 2014 at 12:21 PM, Kapil Thangavelu <
<email address hidden>> wrote:

> that was with ec2 provider not local
>
>
> On Sun, Mar 30, 2014 at 12:33 AM, John A Meinel <email address hidden>wrote:
>
>> 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 <john@arbash-
>> meinel.com>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
>> >>
>> >
>> >
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> 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
>>
>
>

[Kapil Thangavelu (hazmat)]

i take that back re manual provider.. only show's machine-0 logs there.

-k

On Sun, Mar 30, 2014 at 12:22 PM, Kapil Thangavelu <
<email address hidden>> wrote:

> oddly it works fine for me with manual with 1.17.7, the original error
> report was reported by two other juju users using 1.17.6 against ec2
>
>
>
> On Sun, Mar 30, 2014 at 12:21 PM, Kapil Thangavelu <
> <email address hidden>> wrote:
>
>> that was with ec2 provider not local
>>
>>
>> On Sun, Mar 30, 2014 at 12:33 AM, John A Meinel <email address hidden>wrote:
>>
>>> 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 <john@arbash-
>>> meinel.com>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
>>> >>
>>> >
>>> >
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> 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
>>>
>>
>>
>

[Tim Penhey (thumper)]

I'm fairly sure that this is now fix released due to a fix that axwalk landed last week.

We now explicitly chown the log dir as we were hitting race conditions with rsyslogd on the opening the log file for writing and the internal "become the syslog user" call, as the dir was originally owned by root.

If we can't reproduce with trunk, I'd mark this a fix released.

[Andrew Wilkins (axwalk)]

If there's something going wrong with logging in the manual provider, please file that as a separate bug. As thumper says, there was a permissions bug that was fixed in 1.17.7.