Please show me the console log of main container of onedev pod

Please follow this guide to get thread dump of the Java process to see where it is stucking at:

https://www.baeldung.com/java-thread-dump

Are there any other process running in the container besides this one?

No. only this one. I was tried to rollback with helm,I'm sorry I hava new problem,here is my log of the onedev pod.

Please follow this guide to enter into maintenance mode: https://code.onedev.io/projects/162/blob/main/pages/maintenance-mode.md

Then run /opt/onedev/bin/restore-db.sh /path/to/db-backup.zip to see if you can restore the database.

Please copy all files from /app/boot to /opt/onedev/boot and try again

When I do this copying.I see this.But I check all files in /opt/onedev/boot ,the files is copied successfully. Then I leave out the maintenance mode.Howerver it's stucking again. LIke this:

When I do this copying.I see this

Anything odd here? From the screenshot I see nothing but the copy command input by you. Is this manual copy command also hangs?

Please switch to maintenance mode again, , copy boot files, and then run restore command against the first backup file as suggested in previous comment.

If restore successfully, exit maintenance mode by specifying version as your original version to avoid the upgrade.

The copy command doesn't hang but restore failed.

Please take a backup of /opt/onedev/site and then copy all files from /app to /opt/onedev manually. Then run same restore again.

I backup /opt/onedev/site, and uninstall onedev with helm, delete pvc I create. Then I install new version with helm again, restore the backup data.all is done.Thank you very much.

No problem. Seems like a PVC issue preventing files to be deleted for some reason.

Please check all files under /opt/onedev including site to make sure they all owned by root and readonly flag is not set.

Also make sure your PV is not shared with other nodes.

I use nfs-client-provisioner,here is my pvc status

Is this error starts with below message?

Can't acquire environment lock after ...

yes

Please check if process with id 29 is running. If yes, is it the same process as OneDev?

Also please enter into maintenance mode to delete all xd.lck recursively under the site directory to see if it works.

Thank you again, that I used new nfs-client to reinstall my onedev. Seems like nothing wrong, and when I get the same problem, I will try to delete all xd.lck.

I found the reason,that I did too much buildwork with nfs, it hanged. May use systemctl restart rpcbind.socket rpcbind.service to resolve this.

Thanks for the update. Definitely helps in case others have same issue.