Re: [Savannah-hackers-public] bzr post-commit email hook

2017-02-10 Thread Bob Proulx
Glenn Morris wrote: > Bob Proulx wrote: > > Yes. Looks like bzr is logging to /var/lib/bzr/bzr-anon.log. Which I > > think should be /var/log/bzr/bzr-anon.log instead. I am going to make > > that change. Will copy the logrotate over for the new location. > > It's as you prefer. But you will

Re: [Savannah-hackers-public] bzr post-commit email hook

2017-02-10 Thread Bob Proulx
Glenn Morris wrote: > ChangeLog tells me to update the log on mgt0 instead, but I cannot > log in to mgt0. I just made a big edit, import, cleanup to the authorized keys file. Try it again now. I it should allow you in. You should be able to log in from fencepost to mgt0 now. In other

Re: [Savannah-hackers-public] bzr post-commit email hook

2017-02-10 Thread Assaf Gordon
Hello Bob and Glenn, I'll add one more thing: > On Feb 10, 2017, at 19:38, Bob Proulx wrote: > [...] > > /opt/savannah/savane/backend/accounts/sv_membersh is a checked out > copy of the git source for Savannah's savane source code. That is the > source code copy of the file.

Re: [Savannah-hackers-public] bzr post-commit email hook

2017-02-10 Thread Glenn Morris
I think I've copied all the changes across now, so it might be working. I no longer have any writable bzr repos on Savannah to test with.

Re: [Savannah-hackers-public] bzr post-commit email hook

2017-02-10 Thread Glenn Morris
Bob Proulx wrote: > Yes. Looks like bzr is logging to /var/lib/bzr/bzr-anon.log. Which I > think should be /var/log/bzr/bzr-anon.log instead. I am going to make > that change. Will copy the logrotate over for the new location. It's as you prefer. But you will need to edit

Re: [Savannah-hackers-public] bzr post-commit email hook

2017-02-10 Thread Bob Proulx
Glenn Morris wrote: > PS I would also copy /etc/logrotate.d/bzr across. Yes. Looks like bzr is logging to /var/lib/bzr/bzr-anon.log. Which I think should be /var/log/bzr/bzr-anon.log instead. I am going to make that change. Will copy the logrotate over for the new location. > Other relevant

[Savannah-hackers-public] cvs: timeout: fork system call failed: Resource temporarily unavailable

2017-02-10 Thread Bob Proulx
Today Andrew grabbed me on IRC with complaints from cvs checkouts: timeout: fork system call failed: Resource temporarily unavailable This was intermittent throughout the day. I was able to catch some of them myself when doing test checkouts repeatedly. Nagios noted the service flapping

Re: [Savannah-hackers-public] vcs0 cgi errors ("502 bad gateway")

2017-02-10 Thread Bob Proulx
Hi Assaf, Assaf Gordon wrote: >2017/02/10 10:58:20 [error] 3647#0: *370418 connect() to > unix:/var/run/fcgiwrap.socket failed (11: Resource temporarily unavailable) > while connecting to upstream, client: X.X.X.X, server: git.savannah.gnu.org, > request: "GET

[Savannah-hackers-public] Visible PHP warnings on savannah's webpages

2017-02-10 Thread Assaf Gordon
Hello, Benno Schulenberg reported that some PHP warnings are rendered visible on the html pages: https://savannah.gnu.org/support/?109253 I noticed the same when replying to a ticket just now. I'll see if there's a way to disable them from appearing on the HTML (but keep them in the logs),

[Savannah-hackers-public] vcs0 cgi errors ("502 bad gateway")

2017-02-10 Thread Assaf Gordon
Hello, A user just reported the vcs0 gives "502 Bad Gateway": http://savannah.gnu.org/support/?109254 The immediate cause is nginx failure to connect to fcgiwrap: $ tail -n1 /var/log/nginx/error.log 2017/02/10 10:58:20 [error] 3647#0: *370418 connect() to unix:/var/run/fcgiwrap.socket