RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
akonadi server does not start if the home directory is in afs space which does not allow creation of unix sockets (and named pipes). The socket paths in the source are somehow hardcoded to be in ~/.local/share/akonadi/akonadiserver.socket and ~/.local/share/akonadi/db_misc/mysql.socket. Is it possible to move it to /tmp/kde-username or /var/tmp/kdecache-usernameXXXXX?

Version-Release number of selected component (if applicable):
akonadi-1.2.1-2.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. use home dirs on AFS
2.
3.

Actual results:
akonadi server does not start

Expected results:
akonadi server does not start

Additional info:
From https://bugs.kde.org/show_bug.cgi?id=179006#c12 upstream patch available.

~~~
 Use symlink to /tmp as socket directory by default 

This patch is based on the one written by Ansgar Burchardt to use a socket directory linked to /tmp/<username>-akonadi.<random> instead of the hard-coded one from ~/.local/share/akonadi. With this patch Akonadi will start on systems with $HOME on AFS without any further configuration needed.
~~~

Created attachment 889763 [details]
logs

Pushed to rhel-6.6 branch.

Brew build: http://brewweb.devel.redhat.com/brew/taskinfo?taskID=7416522

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0539.html