Bug #49503 [Com]: failed to open semaphore file

2010-04-21 Thread tsisaruk dot v at gmail dot com
Edit report at http://bugs.php.net/bug.php?id=49503edit=1

 ID:   49503
 Comment by:   tsisaruk dot v at gmail dot com
 Reported by:  mike at fuelsaver-mpg dot com
 Summary:  failed to open semaphore file
 Status:   Closed
 Type: Bug
 Package:  Session related
 Operating System: Linux 2.6.9-023stab048.6-enterpr
 PHP Version:  5.2.11

 New Comment:

I added patch which fix trouble with creating semaphore file in /
directory, if sessions.save_path is undefined. It behaviour now is like
file session handle


Previous Comments:

[2009-10-08 17:57:56] mike at fuelsaver-mpg dot com

Thank you.


[2009-10-08 10:34:48] j...@php.net

Thanks for digging this. I have absolutely no idea why I had added this
warning there. Might have been either some debug code I put there while
testing or simply copy'n'paste error gone wild.. :(



I removed it now. And you can of course avoid the warning by setting the
session.save_path properly. :)


[2009-10-08 10:33:26] s...@php.net

Automatic comment from SVN on behalf of jani
Revision: http://svn.php.net/viewvc/?view=revisionrevision=289338
Log: - Fixed bug #49503 (invalid warning for failed semaphore file
creation)
# I have no idea why I had added this. Might have been some debug code..
:(


[2009-10-02 01:06:00] sriram dot natarajan at gmail dot com

i am just curious - how does this affect writing session to memcached ?


[2009-10-01 12:36:22] senker at gmail dot com

It also disables writing sessions to memcached, so if you are using
memcached, you have to stick to 5.2.9.



Please escalate this to higher priority, it's unbelievable such
important bug spans over two PHP versions already.




The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

http://bugs.php.net/bug.php?id=49503


-- 
Edit this bug report at http://bugs.php.net/bug.php?id=49503edit=1


#49503 [Com]: failed to open semaphore file

2009-10-01 Thread senker at gmail dot com
 ID:   49503
 Comment by:   senker at gmail dot com
 Reported By:  mike at fuelsaver-mpg dot com
 Status:   Open
 Bug Type: Session related
 Operating System: Linux 2.6.9-023stab048.6-enterpr
 PHP Version:  5.2.10
 New Comment:

It also disables writing sessions to memcached, so if you are using
memcached, you have to stick to 5.2.9.

Please escalate this to higher priority, it's unbelievable such
important bug spans over two PHP versions already.


Previous Comments:


[2009-09-30 00:11:39] phi...@php.net

There was some feedback, status-open.



[2009-09-18 23:18:37] jd at cpanel dot net

Sorry about the multiple comments.  bugs.php.net seemed to be having
some problems when I submitted them.



[2009-09-18 23:09:22] jd at cpanel dot net

Still present in 5.2.11.

This looks like it's identical to bugs 49401, 49427 and 49433 which
were incorrectly marked as bogus.

This happens when the mm session module tries to initialize itself. 
You don't need anything configured to use MM to hit the problem.  As
this particular bug illustrates, even a valid session.save_path setting
wont avoid running into the same spurious warning.

Ex:

j...@jd:~$ /usr/local/bin/php -i | grep -i session
PHP Warning:  PHP Startup: mm_create(0, /session_mm_cli32004) failed,
err mm:core: failed to open semaphore file (Permission denied) in
Unknown on line 0
session
Session Support = enabled
session.auto_start = Off = Off
session.bug_compat_42 = On = On
session.bug_compat_warn = On = On
session.cache_expire = 180 = 180
session.cache_limiter = nocache = nocache
session.cookie_domain = no value = no value
session.cookie_httponly = Off = Off
session.cookie_lifetime = 0 = 0
session.cookie_path = / = /
session.cookie_secure = Off = Off
session.entropy_file = no value = no value
session.entropy_length = 0 = 0
session.gc_divisor = 100 = 100
session.gc_maxlifetime = 1440 = 1440
session.gc_probability = 1 = 1
session.hash_bits_per_character = 4 = 4
session.hash_function = 0 = 0
session.name = PHPSESSID = PHPSESSID
session.referer_check = no value = no value
session.save_handler = files = files
session.save_path = no value = no value
session.serialize_handler = php = php
session.use_cookies = On = On
session.use_only_cookies = Off = Off
session.use_trans_sid = 0 = 0
WDDX Session Serializer = enabled


The change between 5.2.9 and 5.2.10 that makes the difference is the
warning added in revision 280733:

 r...@jd:/usr/local/svn/php/PHP_5_2# svn log -r280733 --verbose

r280733 | jani | 2009-05-18 12:23:42 -0500 (Mon, 18 May 2009) | 2
lines
Changed paths:
   M /php/php-src/branches/PHP_5_2/ext/session/mod_files.c
   M /php/php-src/branches/PHP_5_2/ext/session/mod_mm.c
   M /php/php-src/branches/PHP_5_2/ext/session/mod_user.c
   M /php/php-src/branches/PHP_5_2/ext/session/php_session.h
   M /php/php-src/branches/PHP_5_2/ext/session/session.c

MFH: Sync WS / CS changes where applicable




It's not really clear why the warning was added to the 5.2 branch
though, since it doesn't look like it was added to trunk or 5.3 in
revisions 280729 and 280728.

svn diff
http://svn.php.net/repository/php/php-src/branches/PHP_5_2/ext/session/mod_mm.c
http://svn.php.net/repository/php/php-src/trunk/ext/session/mod_mm.c



[2009-09-18 22:48:33] jd at cpanel dot net

Still present in 5.2.11.

This looks like it's identical to bugs 49401, 49427 and 49433 which
were incorrectly marked as bogus.

This happens when the mm session module tries to initialize itself. 
You don't need anything configured to use MM to hit the problem.  As
this particular bug illustrates, even a valid session.save_path setting
wont avoid running into the same spurious warning.

Ex:

j...@jd:~$ /usr/local/bin/php -i | grep -i session
PHP Warning:  PHP Startup: mm_create(0, /session_mm_cli32004) failed,
err mm:core: failed to open semaphore file (Permission denied) in
Unknown on line 0
session
Session Support = enabled
session.auto_start = Off = Off
session.bug_compat_42 = On = On
session.bug_compat_warn = On = On
session.cache_expire = 180 = 180
session.cache_limiter = nocache = nocache
session.cookie_domain = no value = no value
session.cookie_httponly = Off = Off
session.cookie_lifetime = 0 = 0
session.cookie_path = / = /
session.cookie_secure = Off = Off
session.entropy_file = no value = no value
session.entropy_length = 0 = 0
session.gc_divisor = 100 = 100
session.gc_maxlifetime = 1440 = 1440
session.gc_probability = 1 = 1
session.hash_bits_per_character = 4 = 4
session.hash_function = 0 = 0
session.name = PHPSESSID = 

#49503 [Com]: failed to open semaphore file

2009-10-01 Thread sriram dot natarajan at gmail dot com
 ID:   49503
 Comment by:   sriram dot natarajan at gmail dot com
 Reported By:  mike at fuelsaver-mpg dot com
 Status:   Open
 Bug Type: Session related
 Operating System: Linux 2.6.9-023stab048.6-enterpr
 PHP Version:  5.2.10
 New Comment:

i am just curious - how does this affect writing session to memcached ?


Previous Comments:


[2009-10-01 12:36:22] senker at gmail dot com

It also disables writing sessions to memcached, so if you are using
memcached, you have to stick to 5.2.9.

Please escalate this to higher priority, it's unbelievable such
important bug spans over two PHP versions already.



[2009-09-30 00:11:39] phi...@php.net

There was some feedback, status-open.



[2009-09-18 22:38:38] jd at cpanel dot net

Still present in 5.2.11.

This looks like it's identical to bugs 49401, 49427 and 49433 which
were incorrectly marked as bogus.

This happens when the mm session module tries to initialize itself. 
You don't need anything configured to use MM to hit the problem.  As
this particular bug illustrates, even a valid session.save_path setting
wont avoid running into the same spurious warning.

Ex:

j...@jd:~$ /usr/local/bin/php -i | grep -i session
PHP Warning:  PHP Startup: mm_create(0, /session_mm_cli32004) failed,
err mm:core: failed to open semaphore file (Permission denied) in
Unknown on line 0
session
Session Support = enabled
session.auto_start = Off = Off
session.bug_compat_42 = On = On
session.bug_compat_warn = On = On
session.cache_expire = 180 = 180
session.cache_limiter = nocache = nocache
session.cookie_domain = no value = no value
session.cookie_httponly = Off = Off
session.cookie_lifetime = 0 = 0
session.cookie_path = / = /
session.cookie_secure = Off = Off
session.entropy_file = no value = no value
session.entropy_length = 0 = 0
session.gc_divisor = 100 = 100
session.gc_maxlifetime = 1440 = 1440
session.gc_probability = 1 = 1
session.hash_bits_per_character = 4 = 4
session.hash_function = 0 = 0
session.name = PHPSESSID = PHPSESSID
session.referer_check = no value = no value
session.save_handler = files = files
session.save_path = no value = no value
session.serialize_handler = php = php
session.use_cookies = On = On
session.use_only_cookies = Off = Off
session.use_trans_sid = 0 = 0
WDDX Session Serializer = enabled


The change between 5.2.9 and 5.2.10 that makes the difference is the
warning added in revision 280733:

 r...@jd:/usr/local/svn/php/PHP_5_2# svn log -r280733 --verbose

r280733 | jani | 2009-05-18 12:23:42 -0500 (Mon, 18 May 2009) | 2
lines
Changed paths:
   M /php/php-src/branches/PHP_5_2/ext/session/mod_files.c
   M /php/php-src/branches/PHP_5_2/ext/session/mod_mm.c
   M /php/php-src/branches/PHP_5_2/ext/session/mod_user.c
   M /php/php-src/branches/PHP_5_2/ext/session/php_session.h
   M /php/php-src/branches/PHP_5_2/ext/session/session.c

MFH: Sync WS / CS changes where applicable




It's not really clear why the warning was added to the 5.2 branch
though, since it doesn't look like it was added to trunk or 5.3 in
revisions 280729 and 280728.

svn diff
http://svn.php.net/repository/php/php-src/branches/PHP_5_2/ext/session/mod_mm.c
http://svn.php.net/repository/php/php-src/trunk/ext/session/mod_mm.c



[2009-09-17 01:00:02] php-bugs at lists dot php dot net

No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to Open.



[2009-09-09 08:58:46] j...@php.net

Please try using this snapshot:

  http://snaps.php.net/php5.2-latest.tar.gz
 
For Windows:

  http://windows.php.net/snapshots/





The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/49503

-- 
Edit this bug report at http://bugs.php.net/?id=49503edit=1



#49503 [Com]: failed to open semaphore file

2009-09-18 Thread jd at cpanel dot net
 ID:   49503
 Comment by:   jd at cpanel dot net
 Reported By:  mike at fuelsaver-mpg dot com
 Status:   No Feedback
 Bug Type: Session related
 Operating System: Linux 2.6.9-023stab048.6-enterpr
 PHP Version:  5.2.10
 New Comment:

Still present in 5.2.11.

This looks like it's identical to bugs 49401, 49427 and 49433 which
were incorrectly marked as bogus.

This happens when the mm session module tries to initialize itself. 
You don't need anything configured to use MM to hit the problem.  As
this particular bug illustrates, even a valid session.save_path setting
wont avoid running into the same spurious warning.

Ex:

j...@jd:~$ /usr/local/bin/php -i | grep -i session
PHP Warning:  PHP Startup: mm_create(0, /session_mm_cli32004) failed,
err mm:core: failed to open semaphore file (Permission denied) in
Unknown on line 0
session
Session Support = enabled
session.auto_start = Off = Off
session.bug_compat_42 = On = On
session.bug_compat_warn = On = On
session.cache_expire = 180 = 180
session.cache_limiter = nocache = nocache
session.cookie_domain = no value = no value
session.cookie_httponly = Off = Off
session.cookie_lifetime = 0 = 0
session.cookie_path = / = /
session.cookie_secure = Off = Off
session.entropy_file = no value = no value
session.entropy_length = 0 = 0
session.gc_divisor = 100 = 100
session.gc_maxlifetime = 1440 = 1440
session.gc_probability = 1 = 1
session.hash_bits_per_character = 4 = 4
session.hash_function = 0 = 0
session.name = PHPSESSID = PHPSESSID
session.referer_check = no value = no value
session.save_handler = files = files
session.save_path = no value = no value
session.serialize_handler = php = php
session.use_cookies = On = On
session.use_only_cookies = Off = Off
session.use_trans_sid = 0 = 0
WDDX Session Serializer = enabled


The change between 5.2.9 and 5.2.10 that makes the difference is the
warning added in revision 280733:

 r...@jd:/usr/local/svn/php/PHP_5_2# svn log -r280733 --verbose

r280733 | jani | 2009-05-18 12:23:42 -0500 (Mon, 18 May 2009) | 2
lines
Changed paths:
   M /php/php-src/branches/PHP_5_2/ext/session/mod_files.c
   M /php/php-src/branches/PHP_5_2/ext/session/mod_mm.c
   M /php/php-src/branches/PHP_5_2/ext/session/mod_user.c
   M /php/php-src/branches/PHP_5_2/ext/session/php_session.h
   M /php/php-src/branches/PHP_5_2/ext/session/session.c

MFH: Sync WS / CS changes where applicable




It's not really clear why the warning was added to the 5.2 branch
though, since it doesn't look like it was added to trunk or 5.3 in
revisions 280729 and 280728.

svn diff
http://svn.php.net/repository/php/php-src/branches/PHP_5_2/ext/session/mod_mm.c
http://svn.php.net/repository/php/php-src/trunk/ext/session/mod_mm.c


Previous Comments:


[2009-09-17 01:00:02] php-bugs at lists dot php dot net

No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to Open.



[2009-09-09 08:58:46] j...@php.net

Please try using this snapshot:

  http://snaps.php.net/php5.2-latest.tar.gz
 
For Windows:

  http://windows.php.net/snapshots/





[2009-09-08 20:42:09] mike at fuelsaver-mpg dot com

Description:

When I upgraded to php 5.2.10, I had my error log growing to 100s of
MBs with error messages that it was unable to open its semaphore file. 
I un-commented the php.ini line:  session.save_path = , created a
directory that could be written to, and this resolved that particular
error.

However, I'm still getting the following errors, albeit on a less
frequent basis.  I got 53 of these in one day however:

[07-Sep-2009 00:24:46] PHP Warning:  PHP Startup: mm_create(0,
/home/fuelsa5/tmp/php/session_mm_cgi32010) failed, err mm:core: failed
to open semaphore file (File exists) in Unknown on line 0

There are files being created in the directory, so it's not a
permissions issue.  Per the warning, a duplicate file is attempting to
be created.

Expected result:

I expect not to get so many error messages.  I'm not even sure what's
breaking.






-- 
Edit this bug report at http://bugs.php.net/?id=49503edit=1



#49503 [Com]: failed to open semaphore file

2009-09-18 Thread jd at cpanel dot net
 ID:   49503
 Comment by:   jd at cpanel dot net
 Reported By:  mike at fuelsaver-mpg dot com
 Status:   No Feedback
 Bug Type: Session related
 Operating System: Linux 2.6.9-023stab048.6-enterpr
 PHP Version:  5.2.10
 New Comment:

Still present in 5.2.11.

This looks like it's identical to bugs 49401, 49427 and 49433 which
were incorrectly marked as bogus.

This happens when the mm session module tries to initialize itself. 
You don't need anything configured to use MM to hit the problem.  As
this particular bug illustrates, even a valid session.save_path setting
wont avoid running into the same spurious warning.

Ex:

j...@jd:~$ /usr/local/bin/php -i | grep -i session
PHP Warning:  PHP Startup: mm_create(0, /session_mm_cli32004) failed,
err mm:core: failed to open semaphore file (Permission denied) in
Unknown on line 0
session
Session Support = enabled
session.auto_start = Off = Off
session.bug_compat_42 = On = On
session.bug_compat_warn = On = On
session.cache_expire = 180 = 180
session.cache_limiter = nocache = nocache
session.cookie_domain = no value = no value
session.cookie_httponly = Off = Off
session.cookie_lifetime = 0 = 0
session.cookie_path = / = /
session.cookie_secure = Off = Off
session.entropy_file = no value = no value
session.entropy_length = 0 = 0
session.gc_divisor = 100 = 100
session.gc_maxlifetime = 1440 = 1440
session.gc_probability = 1 = 1
session.hash_bits_per_character = 4 = 4
session.hash_function = 0 = 0
session.name = PHPSESSID = PHPSESSID
session.referer_check = no value = no value
session.save_handler = files = files
session.save_path = no value = no value
session.serialize_handler = php = php
session.use_cookies = On = On
session.use_only_cookies = Off = Off
session.use_trans_sid = 0 = 0
WDDX Session Serializer = enabled


The change between 5.2.9 and 5.2.10 that makes the difference is the
warning added in revision 280733:

 r...@jd:/usr/local/svn/php/PHP_5_2# svn log -r280733 --verbose

r280733 | jani | 2009-05-18 12:23:42 -0500 (Mon, 18 May 2009) | 2
lines
Changed paths:
   M /php/php-src/branches/PHP_5_2/ext/session/mod_files.c
   M /php/php-src/branches/PHP_5_2/ext/session/mod_mm.c
   M /php/php-src/branches/PHP_5_2/ext/session/mod_user.c
   M /php/php-src/branches/PHP_5_2/ext/session/php_session.h
   M /php/php-src/branches/PHP_5_2/ext/session/session.c

MFH: Sync WS / CS changes where applicable




It's not really clear why the warning was added to the 5.2 branch
though, since it doesn't look like it was added to trunk or 5.3 in
revisions 280729 and 280728.

svn diff
http://svn.php.net/repository/php/php-src/branches/PHP_5_2/ext/session/mod_mm.c
http://svn.php.net/repository/php/php-src/trunk/ext/session/mod_mm.c


Previous Comments:


[2009-09-18 22:38:38] jd at cpanel dot net

Still present in 5.2.11.

This looks like it's identical to bugs 49401, 49427 and 49433 which
were incorrectly marked as bogus.

This happens when the mm session module tries to initialize itself. 
You don't need anything configured to use MM to hit the problem.  As
this particular bug illustrates, even a valid session.save_path setting
wont avoid running into the same spurious warning.

Ex:

j...@jd:~$ /usr/local/bin/php -i | grep -i session
PHP Warning:  PHP Startup: mm_create(0, /session_mm_cli32004) failed,
err mm:core: failed to open semaphore file (Permission denied) in
Unknown on line 0
session
Session Support = enabled
session.auto_start = Off = Off
session.bug_compat_42 = On = On
session.bug_compat_warn = On = On
session.cache_expire = 180 = 180
session.cache_limiter = nocache = nocache
session.cookie_domain = no value = no value
session.cookie_httponly = Off = Off
session.cookie_lifetime = 0 = 0
session.cookie_path = / = /
session.cookie_secure = Off = Off
session.entropy_file = no value = no value
session.entropy_length = 0 = 0
session.gc_divisor = 100 = 100
session.gc_maxlifetime = 1440 = 1440
session.gc_probability = 1 = 1
session.hash_bits_per_character = 4 = 4
session.hash_function = 0 = 0
session.name = PHPSESSID = PHPSESSID
session.referer_check = no value = no value
session.save_handler = files = files
session.save_path = no value = no value
session.serialize_handler = php = php
session.use_cookies = On = On
session.use_only_cookies = Off = Off
session.use_trans_sid = 0 = 0
WDDX Session Serializer = enabled


The change between 5.2.9 and 5.2.10 that makes the difference is the
warning added in revision 280733:

 r...@jd:/usr/local/svn/php/PHP_5_2# svn log -r280733 --verbose

r280733 | jani | 2009-05-18 12:23:42 -0500 (Mon, 18 May 2009) | 2
lines
Changed paths:
   M /php/php-src/branches/PHP_5_2/ext/session/mod_files.c
   M 

#49503 [Com]: failed to open semaphore file

2009-09-18 Thread jd at cpanel dot net
 ID:   49503
 Comment by:   jd at cpanel dot net
 Reported By:  mike at fuelsaver-mpg dot com
 Status:   No Feedback
 Bug Type: Session related
 Operating System: Linux 2.6.9-023stab048.6-enterpr
 PHP Version:  5.2.10
 New Comment:

Still present in 5.2.11.

This looks like it's identical to bugs 49401, 49427 and 49433 which
were incorrectly marked as bogus.

This happens when the mm session module tries to initialize itself. 
You don't need anything configured to use MM to hit the problem.  As
this particular bug illustrates, even a valid session.save_path setting
wont avoid running into the same spurious warning.

Ex:

j...@jd:~$ /usr/local/bin/php -i | grep -i session
PHP Warning:  PHP Startup: mm_create(0, /session_mm_cli32004) failed,
err mm:core: failed to open semaphore file (Permission denied) in
Unknown on line 0
session
Session Support = enabled
session.auto_start = Off = Off
session.bug_compat_42 = On = On
session.bug_compat_warn = On = On
session.cache_expire = 180 = 180
session.cache_limiter = nocache = nocache
session.cookie_domain = no value = no value
session.cookie_httponly = Off = Off
session.cookie_lifetime = 0 = 0
session.cookie_path = / = /
session.cookie_secure = Off = Off
session.entropy_file = no value = no value
session.entropy_length = 0 = 0
session.gc_divisor = 100 = 100
session.gc_maxlifetime = 1440 = 1440
session.gc_probability = 1 = 1
session.hash_bits_per_character = 4 = 4
session.hash_function = 0 = 0
session.name = PHPSESSID = PHPSESSID
session.referer_check = no value = no value
session.save_handler = files = files
session.save_path = no value = no value
session.serialize_handler = php = php
session.use_cookies = On = On
session.use_only_cookies = Off = Off
session.use_trans_sid = 0 = 0
WDDX Session Serializer = enabled


The change between 5.2.9 and 5.2.10 that makes the difference is the
warning added in revision 280733:

 r...@jd:/usr/local/svn/php/PHP_5_2# svn log -r280733 --verbose

r280733 | jani | 2009-05-18 12:23:42 -0500 (Mon, 18 May 2009) | 2
lines
Changed paths:
   M /php/php-src/branches/PHP_5_2/ext/session/mod_files.c
   M /php/php-src/branches/PHP_5_2/ext/session/mod_mm.c
   M /php/php-src/branches/PHP_5_2/ext/session/mod_user.c
   M /php/php-src/branches/PHP_5_2/ext/session/php_session.h
   M /php/php-src/branches/PHP_5_2/ext/session/session.c

MFH: Sync WS / CS changes where applicable




It's not really clear why the warning was added to the 5.2 branch
though, since it doesn't look like it was added to trunk or 5.3 in
revisions 280729 and 280728.

svn diff
http://svn.php.net/repository/php/php-src/branches/PHP_5_2/ext/session/mod_mm.c
http://svn.php.net/repository/php/php-src/trunk/ext/session/mod_mm.c


Previous Comments:


[2009-09-18 22:40:09] jd at cpanel dot net

Still present in 5.2.11.

This looks like it's identical to bugs 49401, 49427 and 49433 which
were incorrectly marked as bogus.

This happens when the mm session module tries to initialize itself. 
You don't need anything configured to use MM to hit the problem.  As
this particular bug illustrates, even a valid session.save_path setting
wont avoid running into the same spurious warning.

Ex:

j...@jd:~$ /usr/local/bin/php -i | grep -i session
PHP Warning:  PHP Startup: mm_create(0, /session_mm_cli32004) failed,
err mm:core: failed to open semaphore file (Permission denied) in
Unknown on line 0
session
Session Support = enabled
session.auto_start = Off = Off
session.bug_compat_42 = On = On
session.bug_compat_warn = On = On
session.cache_expire = 180 = 180
session.cache_limiter = nocache = nocache
session.cookie_domain = no value = no value
session.cookie_httponly = Off = Off
session.cookie_lifetime = 0 = 0
session.cookie_path = / = /
session.cookie_secure = Off = Off
session.entropy_file = no value = no value
session.entropy_length = 0 = 0
session.gc_divisor = 100 = 100
session.gc_maxlifetime = 1440 = 1440
session.gc_probability = 1 = 1
session.hash_bits_per_character = 4 = 4
session.hash_function = 0 = 0
session.name = PHPSESSID = PHPSESSID
session.referer_check = no value = no value
session.save_handler = files = files
session.save_path = no value = no value
session.serialize_handler = php = php
session.use_cookies = On = On
session.use_only_cookies = Off = Off
session.use_trans_sid = 0 = 0
WDDX Session Serializer = enabled


The change between 5.2.9 and 5.2.10 that makes the difference is the
warning added in revision 280733:

 r...@jd:/usr/local/svn/php/PHP_5_2# svn log -r280733 --verbose

r280733 | jani | 2009-05-18 12:23:42 -0500 (Mon, 18 May 2009) | 2
lines
Changed paths:
   M /php/php-src/branches/PHP_5_2/ext/session/mod_files.c
   M 

#49503 [Com]: failed to open semaphore file

2009-09-18 Thread jd at cpanel dot net
 ID:   49503
 Comment by:   jd at cpanel dot net
 Reported By:  mike at fuelsaver-mpg dot com
 Status:   No Feedback
 Bug Type: Session related
 Operating System: Linux 2.6.9-023stab048.6-enterpr
 PHP Version:  5.2.10
 New Comment:

Still present in 5.2.11.

This looks like it's identical to bugs 49401, 49427 and 49433 which
were incorrectly marked as bogus.

This happens when the mm session module tries to initialize itself. 
You don't need anything configured to use MM to hit the problem.  As
this particular bug illustrates, even a valid session.save_path setting
wont avoid running into the same spurious warning.

Ex:

j...@jd:~$ /usr/local/bin/php -i | grep -i session
PHP Warning:  PHP Startup: mm_create(0, /session_mm_cli32004) failed,
err mm:core: failed to open semaphore file (Permission denied) in
Unknown on line 0
session
Session Support = enabled
session.auto_start = Off = Off
session.bug_compat_42 = On = On
session.bug_compat_warn = On = On
session.cache_expire = 180 = 180
session.cache_limiter = nocache = nocache
session.cookie_domain = no value = no value
session.cookie_httponly = Off = Off
session.cookie_lifetime = 0 = 0
session.cookie_path = / = /
session.cookie_secure = Off = Off
session.entropy_file = no value = no value
session.entropy_length = 0 = 0
session.gc_divisor = 100 = 100
session.gc_maxlifetime = 1440 = 1440
session.gc_probability = 1 = 1
session.hash_bits_per_character = 4 = 4
session.hash_function = 0 = 0
session.name = PHPSESSID = PHPSESSID
session.referer_check = no value = no value
session.save_handler = files = files
session.save_path = no value = no value
session.serialize_handler = php = php
session.use_cookies = On = On
session.use_only_cookies = Off = Off
session.use_trans_sid = 0 = 0
WDDX Session Serializer = enabled


The change between 5.2.9 and 5.2.10 that makes the difference is the
warning added in revision 280733:

 r...@jd:/usr/local/svn/php/PHP_5_2# svn log -r280733 --verbose

r280733 | jani | 2009-05-18 12:23:42 -0500 (Mon, 18 May 2009) | 2
lines
Changed paths:
   M /php/php-src/branches/PHP_5_2/ext/session/mod_files.c
   M /php/php-src/branches/PHP_5_2/ext/session/mod_mm.c
   M /php/php-src/branches/PHP_5_2/ext/session/mod_user.c
   M /php/php-src/branches/PHP_5_2/ext/session/php_session.h
   M /php/php-src/branches/PHP_5_2/ext/session/session.c

MFH: Sync WS / CS changes where applicable




It's not really clear why the warning was added to the 5.2 branch
though, since it doesn't look like it was added to trunk or 5.3 in
revisions 280729 and 280728.

svn diff
http://svn.php.net/repository/php/php-src/branches/PHP_5_2/ext/session/mod_mm.c
http://svn.php.net/repository/php/php-src/trunk/ext/session/mod_mm.c


Previous Comments:


[2009-09-18 22:48:33] jd at cpanel dot net

Still present in 5.2.11.

This looks like it's identical to bugs 49401, 49427 and 49433 which
were incorrectly marked as bogus.

This happens when the mm session module tries to initialize itself. 
You don't need anything configured to use MM to hit the problem.  As
this particular bug illustrates, even a valid session.save_path setting
wont avoid running into the same spurious warning.

Ex:

j...@jd:~$ /usr/local/bin/php -i | grep -i session
PHP Warning:  PHP Startup: mm_create(0, /session_mm_cli32004) failed,
err mm:core: failed to open semaphore file (Permission denied) in
Unknown on line 0
session
Session Support = enabled
session.auto_start = Off = Off
session.bug_compat_42 = On = On
session.bug_compat_warn = On = On
session.cache_expire = 180 = 180
session.cache_limiter = nocache = nocache
session.cookie_domain = no value = no value
session.cookie_httponly = Off = Off
session.cookie_lifetime = 0 = 0
session.cookie_path = / = /
session.cookie_secure = Off = Off
session.entropy_file = no value = no value
session.entropy_length = 0 = 0
session.gc_divisor = 100 = 100
session.gc_maxlifetime = 1440 = 1440
session.gc_probability = 1 = 1
session.hash_bits_per_character = 4 = 4
session.hash_function = 0 = 0
session.name = PHPSESSID = PHPSESSID
session.referer_check = no value = no value
session.save_handler = files = files
session.save_path = no value = no value
session.serialize_handler = php = php
session.use_cookies = On = On
session.use_only_cookies = Off = Off
session.use_trans_sid = 0 = 0
WDDX Session Serializer = enabled


The change between 5.2.9 and 5.2.10 that makes the difference is the
warning added in revision 280733:

 r...@jd:/usr/local/svn/php/PHP_5_2# svn log -r280733 --verbose

r280733 | jani | 2009-05-18 12:23:42 -0500 (Mon, 18 May 2009) | 2
lines
Changed paths:
   M /php/php-src/branches/PHP_5_2/ext/session/mod_files.c
   M 

#49503 [Com]: failed to open semaphore file

2009-09-18 Thread jd at cpanel dot net
 ID:   49503
 Comment by:   jd at cpanel dot net
 Reported By:  mike at fuelsaver-mpg dot com
 Status:   No Feedback
 Bug Type: Session related
 Operating System: Linux 2.6.9-023stab048.6-enterpr
 PHP Version:  5.2.10
 New Comment:

Sorry about the multiple comments.  bugs.php.net seemed to be having
some problems when I submitted them.


Previous Comments:


[2009-09-18 23:09:22] jd at cpanel dot net

Still present in 5.2.11.

This looks like it's identical to bugs 49401, 49427 and 49433 which
were incorrectly marked as bogus.

This happens when the mm session module tries to initialize itself. 
You don't need anything configured to use MM to hit the problem.  As
this particular bug illustrates, even a valid session.save_path setting
wont avoid running into the same spurious warning.

Ex:

j...@jd:~$ /usr/local/bin/php -i | grep -i session
PHP Warning:  PHP Startup: mm_create(0, /session_mm_cli32004) failed,
err mm:core: failed to open semaphore file (Permission denied) in
Unknown on line 0
session
Session Support = enabled
session.auto_start = Off = Off
session.bug_compat_42 = On = On
session.bug_compat_warn = On = On
session.cache_expire = 180 = 180
session.cache_limiter = nocache = nocache
session.cookie_domain = no value = no value
session.cookie_httponly = Off = Off
session.cookie_lifetime = 0 = 0
session.cookie_path = / = /
session.cookie_secure = Off = Off
session.entropy_file = no value = no value
session.entropy_length = 0 = 0
session.gc_divisor = 100 = 100
session.gc_maxlifetime = 1440 = 1440
session.gc_probability = 1 = 1
session.hash_bits_per_character = 4 = 4
session.hash_function = 0 = 0
session.name = PHPSESSID = PHPSESSID
session.referer_check = no value = no value
session.save_handler = files = files
session.save_path = no value = no value
session.serialize_handler = php = php
session.use_cookies = On = On
session.use_only_cookies = Off = Off
session.use_trans_sid = 0 = 0
WDDX Session Serializer = enabled


The change between 5.2.9 and 5.2.10 that makes the difference is the
warning added in revision 280733:

 r...@jd:/usr/local/svn/php/PHP_5_2# svn log -r280733 --verbose

r280733 | jani | 2009-05-18 12:23:42 -0500 (Mon, 18 May 2009) | 2
lines
Changed paths:
   M /php/php-src/branches/PHP_5_2/ext/session/mod_files.c
   M /php/php-src/branches/PHP_5_2/ext/session/mod_mm.c
   M /php/php-src/branches/PHP_5_2/ext/session/mod_user.c
   M /php/php-src/branches/PHP_5_2/ext/session/php_session.h
   M /php/php-src/branches/PHP_5_2/ext/session/session.c

MFH: Sync WS / CS changes where applicable




It's not really clear why the warning was added to the 5.2 branch
though, since it doesn't look like it was added to trunk or 5.3 in
revisions 280729 and 280728.

svn diff
http://svn.php.net/repository/php/php-src/branches/PHP_5_2/ext/session/mod_mm.c
http://svn.php.net/repository/php/php-src/trunk/ext/session/mod_mm.c



[2009-09-18 22:48:33] jd at cpanel dot net

Still present in 5.2.11.

This looks like it's identical to bugs 49401, 49427 and 49433 which
were incorrectly marked as bogus.

This happens when the mm session module tries to initialize itself. 
You don't need anything configured to use MM to hit the problem.  As
this particular bug illustrates, even a valid session.save_path setting
wont avoid running into the same spurious warning.

Ex:

j...@jd:~$ /usr/local/bin/php -i | grep -i session
PHP Warning:  PHP Startup: mm_create(0, /session_mm_cli32004) failed,
err mm:core: failed to open semaphore file (Permission denied) in
Unknown on line 0
session
Session Support = enabled
session.auto_start = Off = Off
session.bug_compat_42 = On = On
session.bug_compat_warn = On = On
session.cache_expire = 180 = 180
session.cache_limiter = nocache = nocache
session.cookie_domain = no value = no value
session.cookie_httponly = Off = Off
session.cookie_lifetime = 0 = 0
session.cookie_path = / = /
session.cookie_secure = Off = Off
session.entropy_file = no value = no value
session.entropy_length = 0 = 0
session.gc_divisor = 100 = 100
session.gc_maxlifetime = 1440 = 1440
session.gc_probability = 1 = 1
session.hash_bits_per_character = 4 = 4
session.hash_function = 0 = 0
session.name = PHPSESSID = PHPSESSID
session.referer_check = no value = no value
session.save_handler = files = files
session.save_path = no value = no value
session.serialize_handler = php = php
session.use_cookies = On = On
session.use_only_cookies = Off = Off
session.use_trans_sid = 0 = 0
WDDX Session Serializer = enabled


The change between 5.2.9 and 5.2.10 that makes the difference is the
warning added in revision 280733:

 r...@jd:/usr/local/svn/php/PHP_5_2# svn log -r280733 --verbose