Bug 1007732
Summary: | zarafa on PPC64 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | alessandro.canovi | ||||||||
Component: | zarafa | Assignee: | Robert Scheck <redhat-bugzilla> | ||||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 18 | CC: | karsten, redhat-bugzilla, vanmeeuwen+fedora | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | ppc64 | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2014-02-05 22:22:55 UTC | Type: | Bug | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
alessandro.canovi
2013-09-13 08:52:39 UTC
Set SELinux to permissive as first try. Ensure that /etc/zarafa/server.cfg is contains "local_admin_users = root zarafa" and restart zarafa-server if you had to change that. If this still does not solve the issue, please provide me more logs (if they are sensitive you can also sent them encrypted to my e-mail address directly), log level 6 would be appreciated. Additionally, I would like to see then the whole Zarafa configuration. I can not exclude that this is a PPC64 specific issue, but I can try to reproduce the whole thing on "supported" architectures for you to track it down. Additionally, please bug the PPC guys to build zarafa-7.1.5-1 (as well as the latest libvmime before!) also for PPC, because it's available meanwhile for primary architectures. Created attachment 797316 [details]
zarafa-server log
Created attachment 797317 [details]
zarafa-server configuration
SELinux is disabled and local_admin_users is correctly configured. I've attached level 6 log and server configuration. I've already tested same configuration on Fedora 18 x86_64 and issue isn't reproduced. zarafa-7.1.5 picked up a build requirement on kyotocabinet. That fails to build on PPC with the result that we don't have the latest zarafa on PPC. See http://ppc.koji.fedoraproject.org/kojifiles/work/tasks/1196/1411196/build.log for the latest build attempt. I've successfully built zarafa-7.1.5 from source RPM but issue persists, using zarafa-admin -s I get: Fri Sep 13 18:52:30 2013: Accepted incoming connection from file:///var/run/zarafa Fri Sep 13 18:52:35 2013: Object not found unknown user '匀夀匀吀䔀': 匀夀匀吀䔀 Fri Sep 13 18:52:35 2013: Authentication by plugin failed for user 匀夀匀吀䔀: Trying to authenticate failed: wrong username or password Fri Sep 13 18:52:35 2013: Failed to authenticate user 匀夀匀吀䔀 from file:///var/run/zarafa using program zarafa-admin Can you please try with normal ASCII user names? In theory, unicode usernames are supported, but I would not bet on it... I am using an ASCII user name, I run "zarafa-admin -s" as root There is something wrong even if I just run zarafa-admin without parameters, this is part of the output, full output attached: Usage: zarafa-admin [action] [options] �������������������������������������������� �������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������� Created attachment 797578 [details]
zarafa-admin.log
Even this doesn't solve the Zarafa issue itself, there will be a working RPM for kyotocabinet for PowerPC in the future. Just waiting for shadow builds... This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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. Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |