Public bug reported:
The file /etc/check_mk/logwatch.cfg contains the following stanza:
/var/log/syslog /var/log/kern.log
I registered panic notifier
C panic
C Oops
W generic protection rip
W .*Unrecovered read error - auto reallocate failed
the "C panic" line sometimes fools Check_MK to
Specifically this bug:
https://bugs.php.net/bug.php?id=71187
"PHP 7.0 and up does not allow buggy return values from user save
handler"
Maybe a php7.0-memcached package using 3.0.4?
https://pecl.php.net/package/memcached/3.0.4
** Bug watch added: bugs.php.net/ #71187
@Phillip, Sorry for the slow reply. I borrowed another windows PC for my
urgent problem.
Here's the output:
chris:~$ sudo efibootmgr
BootCurrent: 0003
Timeout: 2 seconds
BootOrder: 0003,0005,0004,0002,0001,
Boot* Windows Boot Manager
Boot0001* HDD0:
Boot0002* HDD0:
Boot0003* ubuntu
I have the same problem. Since upgrade from 13.10 to 14.04, I've run
Boot Repair which failed. I do recall some issues getting grub working
when I originally installed 13.04 but don't have a record of how I got
it working. Upgrade from 13.04 to 13.10 went OK.
I've spent the last five hours
Public bug reported:
I can reproduce https://bugs.php.net/bug.php?id=63142 in an up-to-date
Ubuntu 12.04.3 LTS
Package: php5-memcache
Priority: optional
Section: universe/web
Installed-Size: 151
Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com
Original-Maintainer: Sergey B
Public bug reported:
I can reproduce https://bugs.php.net/bug.php?id=63142 in an up-to-date
Ubuntu 12.04.3 LTS
Package: php5-memcache
Priority: optional
Section: universe/web
Installed-Size: 151
Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com
Original-Maintainer: Sergey B
Public bug reported:
PHP in Ubuntu 10.04.2 LTS includes /etc/cron.d/php5:
09,39 * * * * root [ -x /usr/lib/php5/maxlifetime ] [ -d
/var/lib/php5 ] find /var/lib/php5/ -type f -cmin
+$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm
$ dpkg -S /etc/cron.d/php5
php5-common:
Public bug reported:
PHP in Ubuntu 10.04.2 LTS includes /etc/cron.d/php5:
09,39 * * * * root [ -x /usr/lib/php5/maxlifetime ] [ -d
/var/lib/php5 ] find /var/lib/php5/ -type f -cmin
+$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm
$ dpkg -S /etc/cron.d/php5
php5-common:
I had a similar issue to Phil. A web server was generating PHP sessions
faster than they were being deleted by the cron job. This caused the
disk on which /var/lib/php5 was located to run out of inodes, and thence
to a loss of service.
It is caused by this upstream workaround, which is poor:
I had a similar issue to Phil. A web server was generating PHP sessions
faster than they were being deleted by the cron job. This caused the
disk on which /var/lib/php5 was located to run out of inodes, and thence
to a loss of service.
It is caused by this upstream workaround, which is poor:
Thanks. Then I'll ask PHP to update their documentation. You link to a
page that states: When running PHP from the command line the default
setting is 0. It is not sufficiently clear that this value cannot be
overridden in php.ini. However, it does say so here:
Thanks. Then I'll ask PHP to update their documentation. You link to a
page that states: When running PHP from the command line the default
setting is 0. It is not sufficiently clear that this value cannot be
overridden in php.ini. However, it does say so here:
Public bug reported:
Binary package hint: php5
Using PHP 5.2.3-1ubuntu6.4 (cli) (built: Jul 23 2008 06:20:35) on Ubuntu
7.10
Steps to reproduce:
Edit /etc/php5/cli/php.ini
Change max_execution_time to a non-zero value, e.g. 10
Change max_input_time to a non-zero value, e.g. 10
php -i | grep
Public bug reported:
Binary package hint: php5
Using PHP 5.2.3-1ubuntu6.4 (cli) (built: Jul 23 2008 06:20:35) on Ubuntu
7.10
Steps to reproduce:
Edit /etc/php5/cli/php.ini
Change max_execution_time to a non-zero value, e.g. 10
Change max_input_time to a non-zero value, e.g. 10
php -i | grep
This is the relevant line from /etc/fail2ban.conf when fail2ban 0.6.0-3
is installed on Ubuntu 6.06 LTS (Dapper).
failregex = : (?:(?:Authentication failure|Failed [-/\w+]+) for(?:
[iI](?:llegal|nvalid) user)?|[Ii](?:llegal|nvalid) user) .* from
(?:::f{4,6}:)?(?Phost\S*)
This seems to allow any
** Description changed:
Binary package hint: fail2ban
According to CVE 2006-6302
(http://nvd.nist.gov/nvd.cfm?cvename=CVE-2006-6302) fail2ban 0.6.1 and
below is vulnerable to log injection techniques, which can lead to the
wrong IP address being banned. This can result in denial of
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2006-6302
--
Denial of service through log injection in fail2ban
https://bugs.launchpad.net/bugs/121374
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
17 matches
Mail list logo
