[Bug 1263065] [NEW] php5-memcache segfaults with object (un)serialization

2013-12-20 Thread Chris Fryer
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 Kirpichev skirpic...@gmail.com
Architecture: amd64
Source: php-memcache
Version: 3.0.6-1
Depends: libc6 (= 2.7), phpapi-20090626
Suggests: memcached
Filename: pool/universe/p/php-memcache/php5-memcache_3.0.6-1_amd64.deb
Size: 47062
MD5sum: 7d3bf387e029e1d7fe43ab9996842aa3
SHA1: d0f30749170e789311ae062c5346092881190a49
SHA256: de3fad7fe68a68e61ccf55ad923364d9578b0125353e3d24986b2ec0d9c158e0
Description-en: memcache extension module for PHP5
 Memcached is a caching daemon designed especially for dynamic web applications
 to decrease database load by storing objects in memory.
 .
 This extension allows you to work with memcached through handy OO and
 procedural interfaces in your php5 applications.
Homepage: http://pecl.php.net/package/memcache
Description-md5: 58db38616cd7be3fdacd6d17d7baf2e8
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Origin: Ubuntu

The test case at bugs.php.net is reproduced below:

?php
echo Test: PHP-.phpversion()./memcache-.phpversion('memcache');
$obj = new StdClass;
$obj-obj = $obj;
$memcache = new Memcache;
$memcache-connect('127.0.0.1', 11211);
$memcache-set('x', $obj, false, 300);
$x = $memcache-get('x'); echo .;
$x = $memcache-get('x'); echo .;
$x = $memcache-get('x'); echo .;
$x = $memcache-get('x'); echo .;
$x = $memcache-get('x'); echo .;
$x = $memcache-get('x'); echo .;
$x = $memcache-get('x'); echo .;
$x = $memcache-get('x'); echo .;
$x = $memcache-get('x'); echo .\n;

chris@home:~$ php memcache.php 
Test: PHP-5.3.10-1ubuntu3.9/memcache-3.0.6.
Segmentation fault (core dumped)

** Affects: php-memcache (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: precise

** Tags added: precise

** Package changed: php5 (Ubuntu) = php-memcache (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1263065

Title:
  php5-memcache segfaults with object (un)serialization

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-memcache/+bug/1263065/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 802565] [NEW] Arbitrary file limit in garbage-collection cron script causes loss of service

2011-06-27 Thread Chris Fryer
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: /etc/cron.d/php5

if your server generates PHP sessions faster than they can be deleted by
the cron job, the disk on which /var/lib/php5 is located will run out of
inodes, and thence to a loss of service.

It is caused by this upstream workaround:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461755#20

The latest version of the cron job that does PHP session garbage
collection is here:

http://anonscm.debian.org/gitweb/?p=pkg-
php/php.git;a=blob;f=debian/php5-common.php5.cron.d;hb=HEAD

This is related to Bug #316441 and Bug #482720

** Affects: php5 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/802565

Title:
  Arbitrary file limit in garbage-collection cron script causes loss of
  service

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/802565/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 316441] Re: PHP session garbage collection

2011-06-24 Thread Chris Fryer
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:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461755#20

The latest version of the cron job that does PHP session garbage
collection is here:

http://anonscm.debian.org/gitweb/?p=pkg-
php/php.git;a=blob;f=debian/php5-common.php5.cron.d;hb=HEAD

It would probably be a good idea to backport to this LTS release,
because it fixes Phil's issue, among other security concerns.

** Bug watch added: Debian Bug tracker #461755
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461755

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/316441

Title:
  PHP session garbage collection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/316441/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 282674] Re: max_execution_time and max_input_time settings in php.ini are ignored by php cli

2008-10-14 Thread Chris Fryer
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:

http://www.php.net/manual/en/features.commandline.php

Sorry I didn't spot that earlier.

-- 
max_execution_time and max_input_time settings in php.ini are ignored by php cli
https://bugs.launchpad.net/bugs/282674
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 282674] [NEW] max_execution_time and max_input_time settings in php.ini are ignored by php cli

2008-10-13 Thread Chris Fryer
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 max_

max_execution_time = 0 = 0
max_input_time = -1 = -1

The file is definitely being read:

php -i | head -n 20

phpinfo()
PHP Version = 5.2.3-1ubuntu6.4

System = Linux testubuntu.lse.ac.uk 2.6.22-15-server #1 SMP Wed Aug 20 
19:08:24 UTC 2008 i686
Build Date = Jul 23 2008 06:18:41
Server API = Command Line Interface
Virtual Directory Support = disabled
Configuration File (php.ini) Path = /etc/php5/cli
Loaded Configuration File = /etc/php5/cli/php.ini
Scan this dir for additional .ini files = /etc/php5/cli/conf.d
additional .ini files parsed = /etc/php5/cli/conf.d/apc.ini,
/etc/php5/cli/conf.d/curl.ini,
/etc/php5/cli/conf.d/gd.ini,
/etc/php5/cli/conf.d/ldap.ini,
/etc/php5/cli/conf.d/mysql.ini,
/etc/php5/cli/conf.d/mysqli.ini,
/etc/php5/cli/conf.d/pdo.ini,
/etc/php5/cli/conf.d/pdo_mysql.ini,
/etc/php5/cli/conf.d/xmlrpc.ini

A quick check to see if max_execution_time is set elsewhere:

grep -R max_execution /etc/php

/etc/php5/apache2/php.ini:max_execution_time = 30 ; Maximum execution time 
of each script, in seconds
/etc/php5/cli/php.ini:max_execution_time = 10 ; Maximum execution time of 
each script, in seconds

So it is not being specified in any configuration files read by the
command-line interpreter

Test case:

nano test.php

?php

while (true) {
echo AA!\n;
}

?

php test.php  /dev/null

top -d 1

Watch php continue to execute past 10 seconds of CPU time.  You will
have to stop php manually, e.g. fg, then ^C, or killall php

Return to the test case, and add

ini_set('max_execution_time', 10);

to the top of the file, then repeat the test.  Watching top will show
php exits after 10 seconds.  If you have configured error logging, you
will see PHP Fatal error:  Maximum execution time of 10 seconds
exceeded in /home/testuser/test.php in whatever you have specified for
error_log

** Affects: php5 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
max_execution_time and max_input_time settings in php.ini are ignored by php cli
https://bugs.launchpad.net/bugs/282674
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs