I have properly configured and secured the private file system for Backup and Migrate to use it. After I updated to the 2.0 release I now get the below items logged:
http://www.example.com/system/files/backup_migrate/manual/test.txt
The above gets logged one time.
Warning: Cannot modify header information - headers already sent by (output started at [path]/includes/bootstrap.inc:1193) in drupal_serve_page_from_cache() (line 1177 of [path]/includes/bootstrap.inc).
This gets logged 12 times and the file location is referring to the test.txt above.
The backups seems to work as they are stored in the private directory set up for manual backups, also the test.txt is there.
This is with Drupal 7 RC4. I am in the process of upgrading the site to 7.0, but wanted to update modules to latest versions yet. I will update this issue if it remains after the core update.
| Comment | File | Size | Author |
|---|---|---|---|
| #15 | Screen-Shot.jpg | 34.21 KB | smptebars1 |
Comments
Comment #1
tsvenson commentedError messages still there are update to Drupal 7.0.
Comment #2
ronan commentedLet me know if this is still happening with the final D7 release. This shouldn't affect the module since this file is designed to be unreadable via the web (it's a test to make sure your files aren't readable).
A future version will eliminate or reduce the frequency of this check.
Comment #3
tsvenson commentedYes, still happening with 7.0 as reported in #1. Also, the test.txt is logged as page not found, forgot to mention that in my OP.
Comment #4
muczy commentedI have the same problem in an upgraded (6.20 -> 7.8) site. Do you need any information/help to debug/solve this issue?
Comment #5
jriddiough@gmail.com commentedsame error here but I am not using backup and migrate.
Comment #6
ropaolle commentedI also have the same problem, but it is not related to Backup and Migrate. It happens when an anonymous users tries to access a protected file.
This happens when drupal_serve_page_from_cache is called in bootstrap.inc, but only if page cache is activated (admin/config/development/performance).
EDIT: It seems like this is related to the mysql version or something else releted to our web hotel FS Data (http://drupal.org/node/1085580#comment-4892768). Becase
Comment #7
tvn commentedI can confirm this happening on Drupal 7.9, Backup and Migrate 7.x-2.2, hosted on PHP 5.2.17.
It indeed is connected to page cache. When "Cache pages for anonymous users" is enabled, I get the same messages as tsvenson:
first - Access denied at "example.com/system/files/backup_migrate/manual/test.txt"
And then 12 times message:
Warning: Cannot modify header information - headers already sent by (output started at [path]/includes/bootstrap.inc:1364) in drupal_serve_page_from_cache() (line 1308 of [path]/includes/bootstrap.inc).
When page caching is disabled I get only first Access denied message, without 12 warnings.
Comment #8
dgorton commentedCan likewise confirm this on Drupal 7.10, BAM 7.x-2.2
Comment #9
mermentau commentedI noticed that with 3 Drupal 7.10 installs 2 out of 3 have the warnings as mentioned here. They are configured to put the scheduled backups in /sites/default/private-files/backup_migrate/scheduled. The one install that does not have the problem has the backups stored above the web root in /home/myaccount/private/backup_migrate/scheduled.
This is with Backup and Migrate 7.x-2.2 and I'm not sure why there is this difference, but thought the clue would help solve the mystery or act as a work around. I set the paths to my private directories using Configuration>Media>File System. The one install that has /private above the drupal root does not have any other files using the /private directory so it works probably because it has no need for the test.txt file.
Comment #10
Rory commented+1 Drupal 7.10, BAM 7.x-2.2
Each time a backup is performed I get three separate logs (as listed below). These occur in both cases whether the backup is manual or scheduled, or if my backup directory is above the root or not.
Warning : Cannot modify header information - headers already sent by (output started at ~/www/drupal_test/includes/common.inc:2575) in drupal_send_headers() (line 1225 of ~/www/drupal_test/includes/bootstrap.inc ).
Warning : session_start() [ function.session-start ]: Cannot send session cookie - headers already sent by (output started at ~/www/drupal_test/includes/common.inc:2575) in drupal_session_start() (line 278 of ~/www/drupal_test/includes/session.inc ).
Warning : session_start() [ function.session-start ]: Cannot send session cache limiter - headers already sent (output started at ~/www/drupal_test/includes/common.inc:2575) in drupal_session_start() (line 278 of ~/www/drupal_test/includes/session.inc ).
Comment #11
twowheeler commentedConfirmed on drupal 7.12, BAM 7.x-2.2.
I notice that this error log:
http://www.example.com/system/files/backup_migrate/manual/test.txt... is wrong from the get-go, considering that there is no such "system" path. It should be:
http://www.example.com/files/backup_migrate/manual/test.txt... so maybe that is part of the problem.
Edit: here is a workaround.
... and there ya go.
Comment #12
twowheeler commentedComment #13
Rory commentedFound some info about Warning: "Headers already sent" or "Cannot modify header information" which might help solve this: http://drupal.org/node/1424
Comment #14
smptebars1 commentedI am having this same issue as well. As per post #11. How much more info does the maintainer need? Mine started having this problem after I changed the cache lifetime to none. but changing it back to 15min. has not fixed it.
EDIT: after changing the cache setting back, now I get this when I try to run Backup and Migrate.... Fatal error: Exception thrown without a stack frame in Unknown on line 0
I'll attach an image in next post of the error log
Comment #15
smptebars1 commentedattached
Comment #16
pixelsweatshop commentedStill seeing this in the latest stable and dev versions 2 years later.
Comment #17
ronan commentedOk, so getting an access denied message is totally normal for B&M. That's the module checking that the backups are indeed safe.
If you are getting an access denied for 'text.txt' in your logs, then all is well.
If you are getting any other more serious errors or if the module isn't functioning in some way please open a new ticket.
Comment #18
pixelsweatshop commentedAs per the issue summary, this issue is not about getting an access denied with the text.txt, this issue is about getting the following along with it.
Comment #19
ronan commentedIs this message showing up in your log or onscreen?
I suspect this is an issue with the built-in poor man's cron in D7. Not sure why B&M would be running during a cached page serve otherwise. The new 3.x branch only checks the destination once and marks it as safe. That should mitigate the issue if it doesn't completely solve it.
Can people with this issue try the 3.x branch and let me know if it's still a problem?
Thanks