Pushlog are unavailable in gitea 1.3.x @ docker #1344

New Issue

GiteaMirror · 2025-11-02T03:57:13-06:00

GiteaMirror commented

2025-11-02 03:57:13 -06:00

Originally created by @davydov-vyacheslav on GitHub (Dec 11, 2017).

Prerequisites:

Gitea Version: 2cb6c51
docker container image (latest as of 2017/11/22)

Hi,
previously I used Gitea project on raspberry pi, where I installed the product directly into the system.
Recently I have upgraded environment and now I switched to docker containers on NAS system. Transition was almost without issues.
Unfortunately I experience only one issue: when I make push to master, I expected the system's dashboard shows me something like this:

davs pushed to master at davs/pushlog-issue
    ca8771a1be commit 3
    abed6bb441 commit 2
    e952de7309 initial commit

But after transition these new push logs are not available so far.
I hope that I have configuration issue and need your assist, please.

Attached app.ini:
app.ini.txt

Thanks,
Slava

Originally created by @davydov-vyacheslav on GitHub (Dec 11, 2017). Prerequisites: * Gitea Version: 2cb6c51 * docker container image (latest as of 2017/11/22) Hi, previously I used Gitea project on raspberry pi, where I installed the product directly into the system. Recently I have upgraded environment and now I switched to docker containers on NAS system. Transition was almost without issues. Unfortunately I experience only one issue: when I make push to master, I expected the system's dashboard shows me something like this: ``` davs pushed to master at davs/pushlog-issue ca8771a1be commit 3 abed6bb441 commit 2 e952de7309 initial commit ``` But after transition these new push logs are not available so far. I hope that I have configuration issue and need your assist, please. Attached app.ini: [app.ini.txt](https://github.com/go-gitea/gitea/files/1547512/app.ini.txt) Thanks, Slava

GiteaMirror closed this issue

2025-11-02 03:57:13 -06:00

GiteaMirror commented

2025-11-02 03:57:14 -06:00

@lunny commented on GitHub (Dec 11, 2017):

@davydov-vyacheslav maybe the version should be v1.3.x ?

@lunny commented on GitHub (Dec 11, 2017): @davydov-vyacheslav maybe the version should be v1.3.x ?

GiteaMirror commented

2025-11-02 03:57:14 -06:00

@lunny commented on GitHub (Dec 11, 2017):

How did you migrate to new system and what's the error displayed when you push?

@lunny commented on GitHub (Dec 11, 2017): How did you migrate to new system and what's the error displayed when you push?

GiteaMirror commented

2025-11-02 03:57:14 -06:00

@davydov-vyacheslav commented on GitHub (Dec 11, 2017):

@lunny , yes, sorry, 1.3.x
migrate processs was like a charm:

make database backup on source system (RPi)
restored database on target system (NAS)
started up the gitea on target system (NAS) . Migration process during first start was without issues

Attached logs during push
push.log

@davydov-vyacheslav commented on GitHub (Dec 11, 2017): @lunny , yes, sorry, 1.3.x migrate processs was like a charm: - make database backup on source system (RPi) - restored database on target system (NAS) - started up the gitea on target system (NAS) . Migration process during first start was without issues Attached logs during push [push.log](https://github.com/go-gitea/gitea/files/1547750/push.log)

GiteaMirror commented

2025-11-02 03:57:14 -06:00

@lunny commented on GitHub (Dec 11, 2017):

have you rewrite all public keys on admin panel?

@lunny commented on GitHub (Dec 11, 2017): have you rewrite all public keys on admin panel?

GiteaMirror commented

2025-11-02 03:57:15 -06:00

@davydov-vyacheslav commented on GitHub (Dec 11, 2017):

@lunny , sorry, where and what should I rewrite?

@davydov-vyacheslav commented on GitHub (Dec 11, 2017): @lunny , sorry, where and what should I rewrite?

GiteaMirror commented

2025-11-02 03:57:15 -06:00

@programmeroftheeve commented on GitHub (Dec 11, 2017):

I was having a similar issue with my repos, have you checked the permissions on the githooks to make sure that they are executable?

Example path: </path/to/gitea/data>/git/<owner>/<repo>/hooks.

@programmeroftheeve commented on GitHub (Dec 11, 2017): I was having a similar issue with my repos, have you checked the permissions on the githooks to make sure that they are executable? Example path: `</path/to/gitea/data>/git/<owner>/<repo>/hooks`.

GiteaMirror commented

2025-11-02 03:57:15 -06:00

@lafriks commented on GitHub (Dec 11, 2017):

@davydov-vyacheslav go to admin panel and click "Rewrite all authorized keys" link

@lafriks commented on GitHub (Dec 11, 2017): @davydov-vyacheslav go to admin panel and click "Rewrite all authorized keys" link

GiteaMirror commented

2025-11-02 03:57:15 -06:00

@davydov-vyacheslav commented on GitHub (Dec 11, 2017):

@lafriks , thank for your reply. But, is it what you mean:

Rewrite '.ssh/authorized_keys' file (for Gitea SSH keys). There is no need to do this if you are using the built-in SSH server.

(I really don't think that it is necessary as I don't use ssh for gitea)

I did that and

Resync pre-receive, update and post-receive hooks of all repositories.
as well

but still nothing after push ...
Updated logs are:

gitea.log2.txt

@davydov-vyacheslav commented on GitHub (Dec 11, 2017): @lafriks , thank for your reply. But, is it what you mean: >> Rewrite '.ssh/authorized_keys' file (for Gitea SSH keys). There is no need to do this if you are using the built-in SSH server. (I really don't think that it is necessary as I don't use ssh for gitea) I did that and >> Resync pre-receive, update and post-receive hooks of all repositories. as well but still nothing after push ... Updated logs are: [gitea.log2.txt](https://github.com/go-gitea/gitea/files/1549419/gitea.log2.txt)

GiteaMirror commented

2025-11-02 03:57:16 -06:00

@davydov-vyacheslav commented on GitHub (Dec 11, 2017):

@btaidm , thank you for your reply as well !

I checked following path:

/data/git/repositories/[user]/[project].git/hooks

it has rights for 'git' user as well as Gitea RUN_USER in app.ini.
actually, everything under /data/git/repositories/ belongs to git:git user

@davydov-vyacheslav commented on GitHub (Dec 11, 2017): @btaidm , thank you for your reply as well ! I checked following path: > /data/git/repositories/[user]/[project].git/hooks it has rights for 'git' user as well as Gitea RUN_USER in app.ini. actually, everything under /data/git/repositories/ belongs to git:git user

GiteaMirror commented

2025-11-02 03:57:16 -06:00

@programmeroftheeve commented on GitHub (Dec 12, 2017):

@davydov-vyacheslav As they should. However, I was talking about the permissions on the hooks files, not just the owner and group.

run ls -l in one of the hooks directory, you should get something similar to this:

-rwxr-xr-x    1 1000     1000           478 Sep 14 15:33 applypatch-msg.sample
 ^^^

with the executable bit set. I pointed out the bits that need to be set for gitea. chmod u+rwx will give you the proper permissions for the hooks file. That will need to run on each of the files and
in the *.d directories.

@programmeroftheeve commented on GitHub (Dec 12, 2017): @davydov-vyacheslav As they should. However, I was talking about the permissions on the hooks files, not just the owner and group. run ```ls -l``` in one of the hooks directory, you should get something similar to this: ``` -rwxr-xr-x 1 1000 1000 478 Sep 14 15:33 applypatch-msg.sample ^^^ ``` with the executable bit set. I pointed out the bits that need to be set for gitea. ```chmod u+rwx``` will give you the proper permissions for the hooks file. That will need to run on each of the files and in the ```*.d``` directories.

GiteaMirror commented

2025-11-02 03:57:16 -06:00

@davydov-vyacheslav commented on GitHub (Dec 12, 2017):

@ btaidm , thank you so much! that really helped!

Many thanks :)

@davydov-vyacheslav commented on GitHub (Dec 12, 2017): @ btaidm , thank you so much! that really helped! Many thanks :)

GiteaMirror referenced this issue

2025-11-02 11:56:33 -06:00

[PR #1344] [MERGED] Fix broken table layout #15871

Sign in to join this conversation.