Why recent commits of some repositories are not listed on the index page? #3188

@lunny commented on GitHub (Apr 15, 2019):

Have you changed to the correct organization on top bar left side?

@lunny commented on GitHub (Apr 15, 2019): Have you changed to the correct organization on top bar left side?

GiteaMirror commented

@netjune commented on GitHub (Apr 16, 2019):

I switched to other organizations, then nothing was listed.

The repositories are under one organization. But if I switch to the organization, nothing is listed.

I switch back to the default(my owner account), then some commits are listed as yesterday.

@netjune commented on GitHub (Apr 16, 2019): I switched to other organizations, then nothing was listed. The repositories are under one organization. But if I switch to the organization, nothing is listed. I switch back to the default(my owner account), then some commits are listed as yesterday.

GiteaMirror commented

@qsodev commented on GitHub (Jun 10, 2019):

I have the same issue for all repositories...no update on dashboard for a few months.

@qsodev commented on GitHub (Jun 10, 2019): I have the same issue for all repositories...no update on dashboard for a few months.

GiteaMirror commented

@lunny commented on GitHub (Jun 10, 2019):

@qsodev any error messages on your log files?

@lunny commented on GitHub (Jun 10, 2019): @qsodev any error messages on your log files?

GiteaMirror commented

@qsodev commented on GitHub (Jun 10, 2019):

The only updates that I see on dashboard are created or transfered repositories.
However each repository itself shows the correct commit history.
But also on the user profile page, the last changed timestamp e.g. Updated 2 months ago under each repo in the list is incorrect.
It seems like it just stopped updating somewhere in the past. Furthermore it looks like the last changed timestamp could be the time where I created or migrated the repository in Gitea.

No Errors in log files.
xorm.log shows warnings and infos. I am not sure if this might be related to this issue.
For example, :

2019/01/23 20:15:48 [W] Table protected_branch has column id but struct has not related field
2019/01/23 20:15:48 [W] Table protected_branch has column repo_id but struct has not related field
2019/01/23 20:15:48 [W] Table protected_branch has column branch_name but struct has not related field
2019/01/23 20:15:48 [W] Table protected_branch has column can_push but struct has not related field
2019/01/23 20:15:48 [W] Table protected_branch has column enable_whitelist but struct has not related field
2019/01/23 20:15:48 [W] Table protected_branch has column whitelist_user_i_ds but struct has not related field
2019/01/23 20:15:48 [W] Table protected_branch has column whitelist_team_i_ds but struct has not related field
2019/01/23 20:15:48 [W] Table protected_branch has column enable_merge_whitelist but struct has not related field
2019/01/23 20:15:48 [W] Table protected_branch has column merge_whitelist_user_i_ds but struct has not related field
2019/01/23 20:15:48 [W] Table protected_branch has column merge_whitelist_team_i_ds but struct has not related field
2019/01/23 20:15:48 [W] Table protected_branch has column created_unix but struct has not related field
2019/01/23 20:15:48 [W] Table protected_branch has column updated_unix but struct has not related field

Or very often this:

2019/06/08 15:57:39 [I] PING DATABASE sqlite3
2019/06/08 15:57:40 [W] Table user Column diff_view_style db default is '''', struct default is ''

@qsodev commented on GitHub (Jun 10, 2019): The only updates that I see on dashboard are created or transfered repositories. However each repository itself shows the correct commit history. But also on the user profile page, the _last changed_ timestamp e.g. `Updated 2 months ago` under each repo in the list is incorrect. It seems like it just stopped updating somewhere in the past. Furthermore it looks like the _last changed_ timestamp could be the time where I created or migrated the repository in Gitea. No Errors in log files. `xorm.log` shows warnings and infos. I am not sure if this might be related to this issue. For example, : ``` 2019/01/23 20:15:48 [W] Table protected_branch has column id but struct has not related field 2019/01/23 20:15:48 [W] Table protected_branch has column repo_id but struct has not related field 2019/01/23 20:15:48 [W] Table protected_branch has column branch_name but struct has not related field 2019/01/23 20:15:48 [W] Table protected_branch has column can_push but struct has not related field 2019/01/23 20:15:48 [W] Table protected_branch has column enable_whitelist but struct has not related field 2019/01/23 20:15:48 [W] Table protected_branch has column whitelist_user_i_ds but struct has not related field 2019/01/23 20:15:48 [W] Table protected_branch has column whitelist_team_i_ds but struct has not related field 2019/01/23 20:15:48 [W] Table protected_branch has column enable_merge_whitelist but struct has not related field 2019/01/23 20:15:48 [W] Table protected_branch has column merge_whitelist_user_i_ds but struct has not related field 2019/01/23 20:15:48 [W] Table protected_branch has column merge_whitelist_team_i_ds but struct has not related field 2019/01/23 20:15:48 [W] Table protected_branch has column created_unix but struct has not related field 2019/01/23 20:15:48 [W] Table protected_branch has column updated_unix but struct has not related field ``` Or very often this: ``` 2019/06/08 15:57:39 [I] PING DATABASE sqlite3 2019/06/08 15:57:40 [W] Table user Column diff_view_style db default is '''', struct default is '' ```

GiteaMirror commented

@lunny commented on GitHub (Jun 11, 2019):

Could you try run Resynchronize pre-receive, update and post-receive hooks of all repositories. on admin panel and try again?

@lunny commented on GitHub (Jun 11, 2019): Could you try run `Resynchronize pre-receive, update and post-receive hooks of all repositories.` on admin panel and try again?

GiteaMirror commented

@qsodev commented on GitHub (Jun 11, 2019):

That did not help... Still no update on dashboard.
But when I edit and commit a file in Gitea web editor, the dashboard gets updated.

@qsodev commented on GitHub (Jun 11, 2019): That did not help... Still no update on dashboard. But when I edit and commit a file in Gitea web editor, the dashboard gets updated.

GiteaMirror commented

@qsodev commented on GitHub (Jun 14, 2019):

during investigation I found another issue which might be related:

I create a repository empty without initializing files.
Then I clone create a file, commit and push to this repo.
Gitea still shows the this repository as empty with the default info page, how to clone etc.

It seems that all git actions do no longer trigger the database or ui refreshes.

@qsodev commented on GitHub (Jun 14, 2019): during investigation I found another issue which might be related: - I create a repository empty without initializing files. - Then I clone create a file, commit and push to this repo. - Gitea still shows the this repository as empty with the default info page, how to clone etc. It seems that all git actions do no longer trigger the database or ui refreshes.

GiteaMirror commented

@lunny commented on GitHub (Jun 15, 2019):

Check your app.ini and focus on LOCAL_ROOT_URL on server section.

@lunny commented on GitHub (Jun 15, 2019): Check your `app.ini` and focus on `LOCAL_ROOT_URL` on `server` section.

GiteaMirror commented

@zeripath commented on GitHub (Jun 15, 2019):

Two common causes come to mind:

Is it possible you have your repositories on a noexec mounted filesystems? That would lead to Git not running hooks that are necessary to tell Gitea about pushes.
If you're pushing using SSH you must login in as the Gitea user with a Gitea managed key. If you can SSH to a prompt using your key that's wrong.

@zeripath commented on GitHub (Jun 15, 2019): Two common causes come to mind: * Is it possible you have your repositories on a noexec mounted filesystems? That would lead to Git not running hooks that are necessary to tell Gitea about pushes. * If you're pushing using SSH you must login in as the Gitea user with a Gitea managed key. If you can SSH to a prompt using your key that's wrong.

GiteaMirror commented

@qsodev commented on GitHub (Jun 16, 2019):

I think LOCAL_ROOT_URL is set correctly, because when I change it I get errors during pushes.
The repos are not mounted with noexec and I can run scripts with gitea user in the repo directory.
I tried to push with SSH and HTTPS. Both works fine.
But still no update on dashboard or in the (no longer) "empty" repo.

@qsodev commented on GitHub (Jun 16, 2019): I think `LOCAL_ROOT_URL` is set correctly, because when I change it I get errors during pushes. The repos are not mounted with noexec and I can run scripts with gitea user in the repo directory. I tried to push with SSH and HTTPS. Both works fine. But still no update on dashboard or in the (no longer) "empty" repo.

GiteaMirror commented

@qsodev commented on GitHub (Aug 5, 2019):

I just found out that for me this problem only affects the builtin ssh server.
When I don't use the internal ssh server then my dashboard gets updated.

@qsodev commented on GitHub (Aug 5, 2019): I just found out that for me this problem only affects the builtin ssh server. When I don't use the internal ssh server then my dashboard gets updated.

GiteaMirror commented

@lafriks commented on GitHub (Aug 5, 2019):

what version are you using?

@lafriks commented on GitHub (Aug 5, 2019): what version are you using?

GiteaMirror commented

@qsodev commented on GitHub (Aug 6, 2019):

first it was <= 1.7 and recently I upgraded to 1.8.3

@qsodev commented on GitHub (Aug 6, 2019): first it was <= 1.7 and recently I upgraded to 1.8.3

GiteaMirror commented

@qsodev commented on GitHub (Aug 9, 2019):

I found out that it is related to systemd hardening.
These hardening options are present in gitea.service

CapabilityBoundingSet=
NoNewPrivileges=True
PrivateUsers=true
PrivateDevices=true
PrivateTmp=true
ProtectHome=true
ProtectSystem=strict
ProtectControlGroups=yes
ProtectKernelTunables=true
ProtectKernelModules=yes
ReadWritePaths=/etc/gitea/app.ini
LockPersonality=true
MemoryDenyWriteExecute=true
RestrictRealtime=true
SystemCallArchitectures=native
SystemCallFilter=@system-service

When I comment out SystemCallFilter=@system-service. Dashboard gets updated.
However removing this line is discouraged by package maintainers.
Does anyone have an idea how to fix this?

@qsodev commented on GitHub (Aug 9, 2019): I found out that it is related to systemd hardening. These hardening options are present in gitea.service ``` CapabilityBoundingSet= NoNewPrivileges=True PrivateUsers=true PrivateDevices=true PrivateTmp=true ProtectHome=true ProtectSystem=strict ProtectControlGroups=yes ProtectKernelTunables=true ProtectKernelModules=yes ReadWritePaths=/etc/gitea/app.ini LockPersonality=true MemoryDenyWriteExecute=true RestrictRealtime=true SystemCallArchitectures=native SystemCallFilter=@system-service ``` When I comment out `SystemCallFilter=@system-service`. Dashboard gets updated. However removing this line is discouraged by package maintainers. Does anyone have an idea how to fix this?

GiteaMirror commented

@stale[bot] commented on GitHub (Oct 8, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Oct 8, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

@stale[bot] commented on GitHub (Oct 22, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Oct 22, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror commented