Re: [fossil-users] fossil server gives 403 after upgrade to apache 2.4

2017-02-17 Thread Benedikt Ahrens
Addendum: I probably took the original configuration from [1], which
would need an update for apache2.4.

[1] https://www.fossil-scm.org/xfer/wiki?name=Cookbook#CGI


On 02/17/2017 12:05 PM, Benedikt Ahrens wrote:
> Hi,
> 
> after upgrade from apache2.2 to apache2.4, my fossil cgi server gives a
> 403 error. It worked fine with apache2.2.
> The rest of the website works after the upgrade, both over http and https.
> 
> The apache error log states:
> [Fri Feb 17 12:00:41.004779 2017] [authz_core:error] [pid 1681] [client
> 90.105.173.97:55792] AH01630: client denied by server configuration:
> /home/user/cgi-bin/r.cgi
> 
> The VirtualHost config is posted below.
> 
> Any help for solving this particular problem, or for improving the setup
> more generally, would be appreciated.
> 
> Best,
> Benedikt
> 
> 
> 
> 
> ServerAdmin ***
> ServerName ***
> 
> DirectoryIndex index.html index.php
> DocumentRoot /home/user/public_html
> 
> Options +FollowSymLinks -Indexes
> AllowOverride AuthConfig
> Require all granted
> 
> 
> ScriptAlias /cgi-bin/ /home/user/cgi-bin/
> 
> AllowOverride None
> Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
> # Order allow,deny
> # Allow from all
> Require all granted
> 
> 
> #   SSL Engine Switch
> SSLEngine on
> 
> SSLCertificateFile /etc/ssl/private/cert.ssl
> 
> ErrorLog /home/user/apache-logs/error.log
> 
> # Possible values include: debug, info, notice, warn, error, crit,
> # alert, emerg.
> LogLevel warn
> 
> CustomLog /home/user/apache-logs/access.log combined
> 
> 
> 
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
> 
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] fossil server gives 403 after upgrade to apache 2.4

2017-02-17 Thread Benedikt Ahrens
Hi,

after upgrade from apache2.2 to apache2.4, my fossil cgi server gives a
403 error. It worked fine with apache2.2.
The rest of the website works after the upgrade, both over http and https.

The apache error log states:
[Fri Feb 17 12:00:41.004779 2017] [authz_core:error] [pid 1681] [client
90.105.173.97:55792] AH01630: client denied by server configuration:
/home/user/cgi-bin/r.cgi

The VirtualHost config is posted below.

Any help for solving this particular problem, or for improving the setup
more generally, would be appreciated.

Best,
Benedikt




ServerAdmin ***
ServerName ***

DirectoryIndex index.html index.php
DocumentRoot /home/user/public_html

Options +FollowSymLinks -Indexes
AllowOverride AuthConfig
Require all granted


ScriptAlias /cgi-bin/ /home/user/cgi-bin/

AllowOverride None
Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
# Order allow,deny
# Allow from all
Require all granted


#   SSL Engine Switch
SSLEngine on

SSLCertificateFile /etc/ssl/private/cert.ssl

ErrorLog /home/user/apache-logs/error.log

# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn

CustomLog /home/user/apache-logs/access.log combined



___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] about fossil ignore and clean

2014-03-22 Thread Benedikt Ahrens
Hi,

I am confused by fossil ignore and clean behaviour.
I have a lot of files, recognizable by extension, that I would like to
ignore when calling fossil status (1), but delete when calling fossil
clean (2).

For (1), I had put a pattern in ignore-glob. Realizing that they would
not be cleaned any more, I copied ignore-glob to clean-glob, hoping to
achieve (2).

However, the files are still not deleted when I call fossil clean.

So I basically would like to have git's .gitignore behaviour.

Could you please tell me how to do that? I found some other threads
which showed that I am not the only one confused about fossil's
behaviour, but I could not extract any solution.

I am using fossil 1.26, in case that is of importance.

Thanks a lot for your help in advance.
Best,
Benedikt
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] fossil running out of memory

2013-08-20 Thread Benedikt Ahrens
 On Mon, Aug 5, 2013 at 10:15 PM, Richard Hipp d...@sqlite.org wrote:
 
 On Mon, Aug 5, 2013 at 3:55 PM, Benedikt Ahrens 
 benedikt.ahr...@gmx.netwrote:

 is not feasible in my situation.


 packages or libraries or deal with package managers.  Just copy *one file*
 into your $PATH on each machine where it matters.

 
 @Benedikt: the easiest thing to do is to edit your $PATH to include
 $HOME/bin and drop fossil in $HOME/bin. If you need help with setting the
 PATH, google for ubuntu edit path (bzw. ubuntu path bearbeiten) and
 several useful answers are there.

Thanks. However, my objection to upgrading to newer fossil was not
motivated by a lack of know-how, but rather by the fact that this
solution comes with a complexity of O(number of affected machines).
Also, not all of the affected machines are mine.

My question was intended to be Can I do something to the

 repository---and not to fossil---in order to get things working again,
 with version 1.22?


 We don't know, and that version is old enough for us to justify suggesting
 you try a newer version before we pursue it further.

It works fine with 1.26.

BTW, is there any chance the Debian packaging could happen in a debian
branch of the fossil development repository, i.e. that the Debian fossil
maintainer get write access to that repo?

Thanks for your help and patience.
Benedikt

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718812
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] getting fossil timeline to show time offsets

2013-08-20 Thread Benedikt Ahrens
Hello,

the fossil timeline command shows UTC time rather than observing the
system setting (UTC+02:00, in my case).
Is there anything I can do to change this?

fossil version is 1.26.

Thanks.
Benedikt
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] fossil running out of memory

2013-08-05 Thread Benedikt Ahrens

Hello,

thanks a lot for your answers.

The repository in question is a bit less than 100MB big and carries
around 30 binaries of up to 6MB each.

I am aware that the fossil version I am using is outdated, but as Joseph
said, it is the version packaged in Debian stable, and in Ubuntu 12.04
as well. Installing newer versions manually on all the machines involved
is not feasible in my situation.
My question was intended to be Can I do something to the
repository---and not to fossil---in order to get things working again,
with version 1.22?

In line with what Joseph suggested I have filed a wishlist bug against
fossil in Debian, where I ask the package maintainer to package a recent
version of fossil for inclusion in unstable and testing (not backports,
though).

Best,
Benedikt

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718812



___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] fossil running out of memory

2013-08-02 Thread Benedikt Ahrens

Hello,

I am having trouble with a fossil repository containing many binary files.

Firstly, after cloning I only have the first (empty) commit in the
timeline, even though many commits have been made to the cloned repository:

$ fossil timeline
=== 2013-08-01 ===
13:06:56 [c497b616a3] *CURRENT* initial empty check-in (user: user tags:
trunk)

Then, when trying to update, fossil runs out of memory:

$ fossil update trunk
Autosync:  https://u...@host.com/cgi-bin/r.cgi/repo
Bytes  Cards  Artifacts Deltas
Sent: 177  2  0  0
Received:4679 96  0  1
Total network traffic: 396 bytes sent, 2773 bytes received
fossil: out of memory

During the update try, fossil uses 100% of one of the cores (AMD Athlon
64 X2 Dual Core Processor 4400+).

The fossil version is the one packaged in Debian Wheezy:

$ fossil version
This is fossil version 1.22 [ab461f39af] 2012-03-29 08:48:38 UTC



On a different machine with the same operating system, fossil version
and architecture, cloning and updating works without problems.


Any hints what I could try to better debug the problem, or to even solve it?

Thanks a lot.
Benedikt

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] fossil problem

2012-06-19 Thread Benedikt Ahrens
Dear all,

since today I am experiencing problems with my fossil repositories:
I can clone and update from the fossil repo on my server, but not write
to it:

$ fossil ci -m added test textfile
Autosync:  http://user@server/r.cgi/ba
Bytes  Cards  Artifacts Deltas
Sent: 130  1  0  0
Received:3206 69  0  0
Total network traffic: 336 bytes sent, 992 bytes received
New_Version: 265359316d615b3be18eecaef671f5028962b0b5
Autosync:  http://user@server/r.cgi/ba
Bytes  Cards  Artifacts Deltas
Sent:4250 74  1  2
Error: Database error: unable to open database file
INSERT INTO rcvfrom(uid, mtime, nonce, ipaddr)VALUES(1,
julianday('now'), '36747a7a30d63512b7bcf90f290631c838dbfb43',
'abc.def.hij.klm')
Received: 201  1  0  0
Total network traffic: 2490 bytes sent, 55 bytes received
fossil: Autosync failed

$ fossil version
This is fossil version [6502627a3e] 2011-02-08 12:52:37 UTC

Fossil versions are the same locally and on the server.

The problem concerns all fossil repos on that server.

Do you know how to fix this?

Please put me in CC, since I am not subscribed to the list.
Thanks a lot.
Best,
Benedikt



___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] fossil problem

2012-06-19 Thread Benedikt Ahrens

That was indeed the problem.
Thanks a lot for your help.

All the best,
Benedikt

On 06/19/2012 08:21 PM, Kevin Martin wrote:
 Just an idea, check the permissions of of the database files on the server. 
 Make sure the user accessing them has read and write access. I get a similar 
 error when I've accidentally set it to 640 instead of 660.
 
 Thanks,
 Kevin
 
 Sent from my iPhone
 
 On 19 Jun 2012, at 18:59, Benedikt Ahrens benedikt.ahr...@gmx.net wrote:
 
 Dear all,

 since today I am experiencing problems with my fossil repositories:
 I can clone and update from the fossil repo on my server, but not write
 to it:

 $ fossil ci -m added test textfile
 Autosync:  http://user@server/r.cgi/ba
Bytes  Cards  Artifacts Deltas
 Sent: 130  1  0  0
 Received:3206 69  0  0
 Total network traffic: 336 bytes sent, 992 bytes received
 New_Version: 265359316d615b3be18eecaef671f5028962b0b5
 Autosync:  http://user@server/r.cgi/ba
Bytes  Cards  Artifacts Deltas
 Sent:4250 74  1  2
 Error: Database error: unable to open database file
 INSERT INTO rcvfrom(uid, mtime, nonce, ipaddr)VALUES(1,
 julianday('now'), '36747a7a30d63512b7bcf90f290631c838dbfb43',
 'abc.def.hij.klm')
 Received: 201  1  0  0
 Total network traffic: 2490 bytes sent, 55 bytes received
 fossil: Autosync failed

 $ fossil version
 This is fossil version [6502627a3e] 2011-02-08 12:52:37 UTC

 Fossil versions are the same locally and on the server.

 The problem concerns all fossil repos on that server.

 Do you know how to fix this?

 Please put me in CC, since I am not subscribed to the list.
 Thanks a lot.
 Best,
 Benedikt



 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users