Public bug reported:
split-logfile fails with an error message (tested with Saucy and
Trusty):
$ split-logfile other_vhosts_access.log
Can't use string (example.org:80) as a symbol ref while strict refs in use
at /usr/sbin/split-logfile line 58, STDIN line 1.
** Affects: apache2 (Ubuntu)
I just submitted this bug to upstream including a patch:
https://issues.apache.org/bugzilla/show_bug.cgi?id=56329
** Bug watch added: Apache Software Foundation Bugzilla #56329
http://issues.apache.org/bugzilla/show_bug.cgi?id=56329
--
You received this bug notification because you are a
When will the fix be rolled out? I got some updates to PHP since ondrej
proposed a fix in comment 6, but this bug still exists. There are only 3
weeks until the Trusty LTS release...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5
I have put together a package for dovecot 2.0.8 including pigeonhole
sieve 0.2.2 in my PPA https://launchpad.net/~mauermann/+archive/testing.
It forks fine for me in production without any issues.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
1.4.4 is in the repos now
** Changed in: munin (Ubuntu)
Status: Confirmed = Fix Released
--
[FFe] Please merge munin 1.4.4-1 from Debian testing
https://bugs.launchpad.net/bugs/538594
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
This may be related to upstart and bridge_utils (bug #498245). Try
setting bridge_maxwait=0 in /etc/network/interfaces and see if this
fixes the problem.
--
autostart almost always fails on boot time host
https://bugs.launchpad.net/bugs/495394
You received this bug notification because you are a
Public bug reported:
Binary package hint: bridge-utils
With upstart all services are started in parallel, so bridge_maxwait at
its default value or set to something greater than 0 may cause some
trouble... For example, I had a problem with a service not starting at
boot because the address it
For me it also does not start at boot. It seems that munin-node is
started to early - before the network interfaces are ready - and then
fails if the address to bind to doesn't exist.
/etc/munin/munin-node.conf:
...
# Which address to bind to;
host 10.0.1.50
...
/var/log/munin/munin-node.log:
