I don't know what you mean by "there is correct form", but the bug is
still present, and thus hooks do not run. The environment variable
should be XDG_CONFIG_HOME, not XDH_CONFIG_HOME.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
To clarify, the line above occurs in /usr/bin/vcsh, and it's a 2-second
fix.
** Changed in: vcsh (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352280
Title:
Public bug reported:
On trusty tahr the system install of vcsh has a typo in the line that
sets the default value for VCSH_HOOK_D.
: ${VCSH_HOOK_D:=$XDH_CONFIG_HOME/vcsh/hooks-enabled}
XDH_CONFIG_HOME should clearly be XDG_CONFIG_HOME.
This results in user hooks not executing if VCSH_HOOK_D is
Has there been any attempt to resolve this bug in 2014? It's still
causing problems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/900792
Title:
Python 2.7 SocketServer socket shutdown is incompatib
I haven't used MAAS for about 6 months precisely because of this
issue. It may have been fixed in the interim.
On Tue, Oct 15, 2013 at 6:43 AM, Julian Edwards
<1153...@bugs.launchpad.net> wrote:
> Have any you seen this again lately?
>
> --
> You received this bug notification because you are subs
For the moment at least the system I had tried to install MAAS on is
in use. I may look at it again during the winter break.
On Tue, Oct 15, 2013 at 10:01 AM, Julian Edwards
<1153...@bugs.launchpad.net> wrote:
> On Tuesday 15 Oct 2013 08:48:08 you wrote:
>> I haven't used MAAS for about 6 months p
Public bug reported:
With the default MAAS install I was having a problem where celery would
become unresponsive and stop running new tasks (including powering
compute nodes on/off) after a while, and eventually the system would
have out of memory errors. The problem seems to have been that the qu
As an update, the problem does not go away actually, it just takes
longer to develop. So, for some reason a task is getting hung or
something, causing all tasks behind it to not be executed and filling
the queue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Unfortunately, due in part to this bug, we aren't currently using MAAS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1153077
Title:
rabbitmq queue fills up and celery stops executing tasks when
u
