search

gitblit-org / gitblit

pure java git solution
http://gitblit.com
Apache License 2.0
2.27k stars 671 forks source link

reindexing tickets removes them from web GUI resulting in server history lost. #1377

Closed TomaszSzt closed 2 years ago

TomaszSzt commented 2 years ago

Steps to reproduce

1.Stop server , make sure FileTickeService is set as tickets.service, start server. 2.Create some tickets 3.Check if they show in repository tickets. 4.Stop server 5.Run re-indexing script. Observe log listing found tickets. 6.Start server 3.Check if they show in repository tickets.

They DO NOT SHOW in repository tickets tab. All I can see is "create Your first ticket" MyTickets is no longer showing an InternalError if it was previously but the list of tickets is EMPTY. All tickets are effectively lost, even tough I still can find them in bare repository tickets folder.

So I suppose it is a problem with re-indexing them.

This is a SERIOUS issue for me. Tickets functionality is important. I don't mind running some re-indexing procedure if something goes wrong, but I don't like it to make tickets completely lost.

How can I correctly trigger GitBlit to rebuild tickets indexes from tickets data stored in bare repository?

TomaszSzt commented 2 years ago

All right, my wrong.

I am running the server under Linux and I run scripts using root account. This resulted in index files belonging to root while the server runs under a dedicated account. Adding chown and the end of script solved the problem of lost tickets.

This issue may be then closed.