Trac problems!

[Daniel Marjamäki]

we have some serious issues with the https://trac.cppcheck.net today.

In last 2-3 hours I got 5xx responses when I try to load pages.

when I restart the webserver the CPU usage of the trac process increase to 100%.

I can see many such log messages in the trac.log from today:

2024-08-29 14:32:21,574 Trac[api] ERROR: Failed to sync with repository "(default)"; You may be able to reduce the impact of this issue by configuring the sync_per_r
equest option; see https://trac.edgewall.org/wiki/TracRepositoryAdmin#ExplicitSync for more detail: 
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/trac/versioncontrol/api.py", line 373, in pre_process_request
    repo.sync()
  File "/usr/local/lib/python2.7/dist-packages/tracopt/versioncontrol/git/git_fs.py", line 678, in sync
    if not self.git.sync():
  File "/usr/local/lib/python2.7/dist-packages/tracopt/versioncontrol/git/PyGIT.py", line 924, in sync
    return self._refresh_rev_cache(force=True)
  File "/usr/local/lib/python2.7/dist-packages/tracopt/versioncontrol/git/PyGIT.py", line 459, in _refresh_rev_cache
    refs = self._get_refs()
  File "/usr/local/lib/python2.7/dist-packages/tracopt/versioncontrol/git/PyGIT.py", line 568, in _get_refs
    for line in self.repo.show_ref('--dereference').splitlines():
  File "/usr/local/lib/python2.7/dist-packages/tracopt/versioncontrol/git/PyGIT.py", line 140, in __execute
    with self.__pipe(git_cmd, *cmd_args) as p:
  File "/usr/local/lib/python2.7/dist-packages/tracopt/versioncontrol/git/PyGIT.py", line 133, in __pipe
    close_fds=close_fds, **kw)
  File "/usr/lib/python2.7/subprocess.py", line 386, in __init__
    errread, errwrite), to_close = self._get_handles(stdin, stdout, stderr)
  File "/usr/lib/python2.7/subprocess.py", line 806, in _get_handles
    p2cread, p2cwrite = self.pipe_cloexec()
  File "/usr/lib/python2.7/subprocess.py", line 865, in pipe_cloexec
    r, w = os.pipe()
OSError: [Errno 24] Too many open files

I am experimenting with a move to a new VM.

[Daniel Marjamäki]

You can try on the new VM here if you want:

http://16.170.133.133/timeline

I am not sure if I will execute the move to this VM but right now it seems to me that it works a lot better.

EDIT: consider this to be a "playground" instance more or less. If we can get https://trac.cppcheck.net up again we will not move..

[Daniel Marjamäki]

I removed the cppcheck git repo from the https://trac.cppcheck.net server. Now it works acceptable again for me at least. You should be able to use it now.

It is unfortunate that the changes are not shown in the timeline though.