Jun Omae wrote on 06.02.2019 at 12:35:
On Wed, Feb 6, 2019 at 7:58 PM Clemens Feige <[email protected]> wrote:

Please find the full trac.log in the attachment.

Still the new SVN revisions [180] [181] (and some others) are not
visible in the ticket "BackLink" section. For illustration I also made
two screenshots.

What can we do?

Thanks for the sharing of the trac.log. I noticed your have a problem
in /data/trac/plugins.

1. The post-commit invoked trac-admin command at 2019-02-06 11:28:34.
    * TracKeywordsPlugin, TracBackLinkPlugin, WikiAutoComplete are NOT loaded.
2. Timeline page is viewed at 2019-02-06 11:28:59.
    * TracKeywordsPlugin, TracBackLinkPlugin, WikiAutoComplete are loaded.

Then, the svnserve user over ssh tunnels cannot read
/data/trac/plugins directory. I suggest to use the same user of web
server for svnserve user.

Work around:
    $ sudo chmod -R go=u-w /data/trac/plugins


Hello Jun

You are right. Thanks a lot!
Now it works.

It had been a two-fold permission problem on my TRAC installation.
 1. permission problem with trac.ini
 2. permission problem with plugins directory

My conclusion is that one needs to be extra extra careful with permissions if multiple Linux users need to access the TRAC and SVN repos. This is an issue especially for SSH tunnelling setup. Things are much easier of SVN and TRAC are operated only by one single user, that would be the Apache webserver. Unfortunately this is not an option for me.

Here is the full problem story:
1.
It happened that the conf/ini/trac.ini file was not readable for the SVN user (tunnelled over SSH) in scope of the SVN hook. Of course I gave correct permissions. But I did not consider, that TRAC (apache webserver user) itself would not only read/write this file, instead TRAC creates a completely new ini-file. My mistake was that this new ini-file did not inherit the correct permission (missing default ACL). This issue happened if someone changed things in the the TRAC-admin panel.
2.
As pointed out by Jun, some of the files in my plugins-directory were not fully readable in scope of the SVN-hook (other user!). Once again an issue of missing default ACLs. Especially those pre-compiled pyc-files were affected. One need to consider that Python may decide create those pyc-file (not always, but sometimes).


Once again many thanks for your help
Clemens



--
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to