https://bz.apache.org/bugzilla/show_bug.cgi?id=64834
Bug ID: 64834 Summary: Sporadic file truncation or excessive NULL bytes at the end Product: Apache httpd-2 Version: 2.4.41 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P2 Component: Core Assignee: bugs@httpd.apache.org Reporter: mmd....@gmail.com Target Milestone: --- OpenStreetMap publishes a replication status file under https://planet.openstreetmap.org/replication/minute/state.txt, which is served as static content and gets updated atomically on the filesystem every minute. File sizes might vary slightly from minute to minute, e.g. 158 bytes, 168 bytes. Consumers reading from that file have reported sporadic issues, like truncated files, or files with excessive NULL bytes towards the end. Our observations have shown that although the file gets updated atomically on the file system, Apache serves the _new_ state.txt file contents using the _old_ state.txt file length. This way, some response might lack the last 10 Bytes, or there's an additional 10 NULL bytes towards the end. We're suspecting that there might be some race condition, where checking the file size and processing the actual file contents might see different versions of that file. Is is a valid use case to change a minutely changing file as static content? Is this a bug or works-as-designed? Downstream issue: https://github.com/openstreetmap/operations/issues/465 -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org