Bug 564135
| Summary: | SQL Failed: SESSION variable 'max_allowed_packet' is read-only | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Robert Scheck <redhat-bugzilla> |
| Component: | zarafa | Assignee: | Robert Scheck <redhat-bugzilla> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | bob, redhat-bugzilla, vanmeeuwen+fedora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | zarafa-6.40.0-2.fc13 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-06-10 22:56:56 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 600993 | ||
| Bug Blocks: | |||
|
Description
Robert Scheck
2010-02-11 22:11:07 UTC
The installation manual (which I don't think we ship as part of the packages) describes the max_allowed_packet MySQL server configuration variable needs to change to 32M, I believe. I think this is more of a documentation issue then it is a Zarafa issue, what say you? I'm wondering why they use SET SESSION max_allowed_packet = 16777216; rather SET GLOBAL max_allowed_packet = 16777216; as the error message suggests. Or did I misunderstand the error message. This is upstream ticket #5033. This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Still affects Rawhide. Seems to be fixed in Zarafa 6.40.0. zarafa-6.40.0-2.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/zarafa-6.40.0-2.fc13 zarafa-6.40.0-2.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/zarafa-6.40.0-2.fc12 zarafa-6.40.0-2.el5 has been submitted as an update for Fedora EPEL 5. http://admin.fedoraproject.org/updates/zarafa-6.40.0-2.el5 zarafa-6.40.0-2.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report. zarafa-6.40.0-2.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. zarafa-6.40.0-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. |