Push failed. Can't delete temp index file. Warning on service stop #18691
Comments
|
I'm having difficulty understanding what it is you're reporting. I think you might be reporting a possible db deadlock. In which case it would be helpful to give us more logs. |
|
I posted all the log that I have. I try to set a more verbouse log level |
|
I set the log level to info, restarted the service, do a fetch from a client, stopped the service. Here the log |
LogsWhen you are reporting bugs or issues it is helpful to give us DEBUG logs. In fact the issue proforma expressly asks you to do that and links to a helpful section of the documentation that to do that: https://docs.gitea.io/en-us/logging-configuration/#debugging-problems I will copy that below: Debugging problemsWhen submitting logs in Gitea issues it is often helpful to submit [database]
LOG_SQL = false ; SQL logs are rarely helpful unless we specifically ask for them
...
[log]
MODE = console
LEVEL = debug ; please set the level to debug when we are debugging a problem
ROUTER = console
COLORIZE = false ; this can be true if you can strip out the ansi coloringSometimes it will be helpful get some specific [log.traceconsole] ; traceconsole here is just a name
MODE = console ; this is the output that the traceconsole writes to
LEVEL = trace
EXPRESSION = ; putting a string here will restrict this logger to logging only those messages that match this expression(It's worth noting that log messages that match the expression at or above debug
|
|
From the small amount of logs you've given me it appears that Gitea is being shutdown externally. This is likely by the windows service. There was an older issue regarding this: #15762 but I'm not sure what's going on here. |
|
Yup. Gitea is being shutdown by your windows service. |
|
I know that, I start and then stop the windows service. |
|
Here the push client side, as you can see it fail after 2 minutes. And the related gitea log |
|
Hi tried the same push again without doing nothing client or server side and this time worked. gitea log |
|
|
There is a package for the latest 1.16 head? In the mean time I got the failed to remove tmp index file again. Here the log |
|
Here the log with the router entry, got the failed to remove tmp index file again |
|
If can be usefull the client that cause this info message is windows 11, with windows 10 this dosen't appear |
|
So I need to see the router.log file too. (This is why the documentation says use Anyway... I think that's telling you what the problem is... https://docs.gitea.io/en-us/config-cheat-sheet/#server-server Take a look at It would be useful to know if you've set a LOCAL_ROOT_URL and to know what the rest of your app.ini looks like. At present I don't know if the problem is that Gitea can't talk to itself or if it's git that can't talk to Gitea. The Router logs would help a little with that. |
|
Sorry, I didn't know that router log go in a different file. Router.log |
zeripath
added
the
issue/needs-feedback
|
@zeripath I have some logs for you. After that I restarted the service and tried to push again, this time the server respond but after 2 minutes I got a timeout, I retried again and in 3 seconds the push succeded. Here the client git output, here the gitea log |
|
Today the service was stuck again. Here the logs |
|
hmm... I wonder if this is related to #18734 would it be possible to try the latest 1.16 head https://dl.gitea.io/gitea/1.16? |
|
ok I installed the latest 1.16 head, let see how it go. Complete logs here |
|
Unfortunately even with the latest version the server sometime is unresponding. |
Looks like it's still related with #18754 . |
|
Hi @lunny, |
|
Got again the open checker error and then the push timeouts |
|
Many different issues are mixed here. I would like to guess:
ps: 1.16 is out dated. As a suggestion, running Gitea on Windows doesn't seem to be a good idea. If you can use docker, you wouldn't have so many troubles. If you can try 1.17 and provide reproducible steps from scratch (a fresh installation, all configs, all operations), it would be easier for others to help. |
|
Hi @wxiaoguang, |
|
Thanks for understanding. Windows server 2012 seems quite old nowadays 😂 , while Git is a POSIX-based system, I have seen many issues of running Gitea on old Windows for large scale use (git compatibility problem, performance problem). And another challenge is that nowadays few Gitea contributors use Windows for production, so if Windows users can not provide details about bugs, it's really difficult to improve. |
|
Just moved the setup to another server with windows server 2019, let's see if there works without problems 🤞 |
|
haven't had any problem on the last week since the server migration, seems fixed! 🥳 Thank's wxiaoguang |
|
Lol so is this some kind of Windows 7 era specific bug, I can't afford newer hardware is there no way to fix the |
Gitea Version
1.16.1
Git Version
2.35.1.windows.2
Operating System
Windows server 2012
How are you running Gitea?
Gitea is running as a windows service, it's installed with the package gitea-1.16.1-windows-4.0-amd64.exe
Database
SQLite
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Description
Often the push from a client to the gitea remote get stuck for a lot of time.
Looking at the log I found this
This temp index folders are empty, I've tried to remove that but I can't until I stop the gitea service. This take a lot of time and sometime even fail and I have to terminate the gitea process from the task manager.
During the stop of the service this lines are added to the log, even after a restart without any remote push
Screenshots
No response
The text was updated successfully, but these errors were encountered: