View Issue Details

IDProjectCategoryView StatusLast Update
0003902mantisbtbugtrackerpublic2007-08-02 02:28
ReporterDan Langille Assigned Tograngeway  
PrioritynormalSeverityfeatureReproducibilityalways
Status closedResolutionfixed 
Fixed in Version1.1.0a4 
Summary0003902: all logins fail with "Cannot modify header information"
Description

[Sat May 29 07:09:09 2004] [error] PHP Warning: Cannot modify header information - headers already sent by (output started at /usr/websites/bugs.bacula.org/mantisbt-0.18.3/core/html_api.php:139) in /usr/websites/bugs.bacula.org/mantisbt-0.18.3/core/gpc_api.php on line 220
[Sat May 29 07:09:09 2004] [error] PHP Warning: Cannot modify header information - headers already sent by (output started at /usr/websites/bugs.bacula.org/mantisbt-0.18.3/core/html_api.php:139) in /usr/websites/bugs.bacula.org/mantisbt-0.18.3/core/print_api.php on line 37
[Sat May 29 07:09:09 2004] [error] PHP Warning: Cannot modify header information - headers already sent by (output started at /usr/websites/bugs.bacula.org/mantisbt-0.18.3/core/html_api.php:139) in /usr/websites/bugs.bacula.org/mantisbt-0.18.3/core/print_api.php on line 39
[Sat May 29 07:09:09 2004] [error] PHP Warning: Cannot modify header information - headers already sent by (output started at /usr/websites/bugs.bacula.org/mantisbt-0.18.3/core/html_api.php:139) in /usr/websites/bugs.bacula.org/mantisbt-0.18.3/core/print_api.php on line 44

Additional Information

This is a clean install of 0.18.3. The only customization is to config_inc.php (username, password, databasename). No other changes.

TagsNo tags attached.

Activities

grangeway

grangeway

2004-05-29 09:47

reporter   ~0005634

This is actually being generated when calling the error handler (Dan was getting a 401 db query failed), triggering error handler which was then failing with above messages

Dan Langille

Dan Langille

2004-05-29 10:30

reporter   ~0005635

The db_query problem was permissions related. Update was not granted. Once granted, all worked well.

Dan Langille

Dan Langille

2004-05-29 16:19

reporter   ~0005636

To be clear, this is a problem with error reporting. If you comment out set_error_handler( 'error_handler' ); at ~line4/5 of core/error_api.php, you'll see this in the error log:

[error] PHP Fatal error: 401 in core/database_api.php on line 86

mysql_error() returns nothing. mysql_errorno() returns nothing.

grangeway

grangeway

2007-07-11 18:23

reporter   ~0014933

I think my recent fix to fix the following backtrace would also be the resolution for my previous comment here:

Call Stack

Time Memory Function Location

1 0.0161 86936 {main}( ) ..(null):0
2 0.2951 10640712 file_add( ) ..(null):45
3 0.3240 13728480 db_query_bound( ) ..(null):669
4 0.3659 13731088 trigger_error ( ) ..(null):220
5 0.3659 13731088 error_handler( ) ..(null):0
6 0.3782 13739008 html_page_top2( ) ..(null):109
7 0.3857 13739328 html_login_info( ) ..(null):119
8 0.4003 13742400 print_project_option_list( ) ..(null):362
9 0.4003 13743176 project_cache_all( ) ..(null):372
10 0.4009 13743776 db_query( ) ..(null):83
11 0.4019 13744384 trigger_error ( ) ..(null):163