OneDev
Dashboards
Projects
Global Views
Code Search
server
Code
Pull Requests
Issues
List
Boards
Iterations
Builds
Packages
Statistics
Child Projects
Audit Log
OneDev 14.1.0
Documentation Support & Bug Report RESTful API Incompatibilities License Agreement Check Update
Projects onedev server Issues OD-209
Upgrade error to 4.0.1 (OD-209)
bufferUnderrun opened 5 years ago

Hi,

first time i see this error so i can't upgrade

image.png

it seems to be located in wrapper-licence.conf of 4.0.1 build.

  • Robin Shen commented 5 years ago

    I tested upgrading from 3.2.9 to 4.0.0, and from 4.0.0 to 4.0.1 and everything works fine. Can you please tell me the exact reproducing steps?

  • bufferUnderrun commented 5 years ago

    The bare metal update needs some manual actions like copying the "conf/" and "site/lib/". I've copied all the "conf/*" and so overwrite the wrapper which i presume i should'nt.

    So i've upgrade successfully but some page are broken :

    Error when accessing to any project/issues, see log

    2020-11-22 11:50:16,187 ERROR [pool-3-thread-4] i.o.s.u.work.DefaultBatchWorkManager Error doing works
jetbrains.exodus.ExodusException: Failed to lock file xd.lck
	at jetbrains.exodus.io.LockingManager.throwFailedToLock(LockingManager.java:156) ~[org.jetbrains.xodus.xodus-environment-1.2.3.jar:1.2.3]
	at jetbrains.exodus.io.LockingManager.lock(LockingManager.java:119) ~[org.jetbrains.xodus.xodus-environment-1.2.3.jar:1.2.3]
	at jetbrains.exodus.io.LockingManager.lock(LockingManager.java:56) ~[org.jetbrains.xodus.xodus-environment-1.2.3.jar:1.2.3]
	at jetbrains.exodus.io.FileDataWriter.lock(FileDataWriter.java:82) ~[org.jetbrains.xodus.xodus-environment-1.2.3.jar:1.2.3]
	at jetbrains.exodus.log.Log.tryLock(Log.java:933) ~[org.jetbrains.xodus.xodus-environment-1.2.3.jar:1.2.3]
	at jetbrains.exodus.log.Log.<init>(Log.java:91) ~[org.jetbrains.xodus.xodus-environment-1.2.3.jar:1.2.3]
	at jetbrains.exodus.env.Environments.newLogInstance(Environments.java:137) ~[org.jetbrains.xodus.xodus-environment-1.2.3.jar:1.2.3]
	at jetbrains.exodus.env.Environments.newLogInstance(Environments.java:115) ~[org.jetbrains.xodus.xodus-environment-1.2.3.jar:1.2.3]
	at jetbrains.exodus.env.Environments.newLogInstance(Environments.java:104) ~[org.jetbrains.xodus.xodus-environment-1.2.3.jar:1.2.3]
	at jetbrains.exodus.env.Environments.newInstance(Environments.java:59) ~[org.jetbrains.xodus.xodus-environment-1.2.3.jar:1.2.3]
	at io.onedev.server.infomanager.AbstractEnvironmentManager.getEnv(AbstractEnvironmentManager.java:82) ~[io.onedev.server-core-4.0.1.jar:na]
	at io.onedev.server.infomanager.DefaultPullRequestInfoManager.collect(DefaultPullRequestInfoManager.java:123) ~[io.onedev.server-core-4.0.1.jar:na]
	at io.onedev.server.infomanager.DefaultPullRequestInfoManager.access$100(DefaultPullRequestInfoManager.java:44) ~[io.onedev.server-core-4.0.1.jar:na]
	at io.onedev.server.infomanager.DefaultPullRequestInfoManager$1$1.call(DefaultPullRequestInfoManager.java:101) ~[io.onedev.server-core-4.0.1.jar:na]
	at io.onedev.server.infomanager.DefaultPullRequestInfoManager$1$1.call(DefaultPullRequestInfoManager.java:97) ~[io.onedev.server-core-4.0.1.jar:na]
	at io.onedev.server.persistence.DefaultSessionManager.call(DefaultSessionManager.java:79) ~[io.onedev.server-core-4.0.1.jar:na]
	at io.onedev.server.infomanager.DefaultPullRequestInfoManager$1.doWorks(DefaultPullRequestInfoManager.java:97) ~[io.onedev.server-core-4.0.1.jar:na]
	at io.onedev.server.util.work.DefaultBatchWorkManager$2.doWorks(DefaultBatchWorkManager.java:112) ~[io.onedev.server-core-4.0.1.jar:na]
	at io.onedev.server.util.work.DefaultBatchWorkManager$1.run(DefaultBatchWorkManager.java:80) ~[io.onedev.server-core-4.0.1.jar:na]
	at io.onedev.server.security.SecurityUtils$2.run(SecurityUtils.java:330) ~[io.onedev.server-core-4.0.1.jar:na]
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[na:na]
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[na:na]
	at java.base/java.lang.Thread.run(Thread.java:830) ~[na:na]
Caused by: java.io.FileNotFoundException: D:\APPLICATIONS\OneDev\server\site\projects\40\info\pullRequest\xd.lck (Acc�s refus�)
	at java.base/java.io.RandomAccessFile.open0(Native Method) ~[na:na]
	at java.base/java.io.RandomAccessFile.open(RandomAccessFile.java:347) ~[na:na]
	at java.base/java.io.RandomAccessFile.<init>(RandomAccessFile.java:261) ~[na:na]
	at java.base/java.io.RandomAccessFile.<init>(RandomAccessFile.java:216) ~[na:na]
	at jetbrains.exodus.io.LockingManager.lock(LockingManager.java:90) ~[org.jetbrains.xodus.xodus-environment-1.2.3.jar:1.2.3]
	... 21 common frames omitted
2020-11-22 11:50:58,014 WARN  [qtp380113286-34] o.a.wicket.RequestListenerInterface behavior not enabled; ignore call. Behavior org.apache.wicket.ajax.markup.html.AjaxLink$1@23b08e61 at component [AjaxLink [Component id = showDetail]]
2020-11-22 11:51:11,553 WARN  [qtp380113286-63] o.a.wicket.RequestListenerInterface behavior not enabled; ignore call. Behavior org.apache.wicket.ajax.markup.html.AjaxLink$1@5a9a6caa at component [AjaxLink [Component id = showDetail]]

    I have another error in the board : the milestone is empty.

    image_2.png

    Others errors when accessing to an issue or issue detail via the modal window...

    i've successfully restored the backup and waiting your help

  • Robin Shen commented 5 years ago

    The upgrade process will copy those files automatically. Please make sure OneDev process is stopped, and also the user running the upgrade process has full permission over the installation folder. As to milestone and issue displaying issue, please make sure you are using Chrome/Firefox/Safari/Edge. IE11 is not supported.

  • bufferUnderrun commented 5 years ago

    I believed i have to copy some files before upgrade ? but no.

    I always run the update.bat with the same user and with administrator privilege. I use only FF/Chrome.

    When i compare the OneDev backup v3 and the new v4, the permissions of the file above "D:\APPLICATIONS\OneDev\server\site\projects\40\info\pullRequest.xd.lck" are differents ? It could explains the error but why theses changes after update ?

  • Robin Shen commented 5 years ago

    Nothing changed at this aspect. Perhaps there is an abnormal shutdown, and that file is left behind. Please delete that file and try again.

  • Robin Shen commented 5 years ago

    For upgrade error, please let me know from which version you are performing the upgrade. And what OS OneDev is running on.

    For milestone/issue displaying issue, please also let me know OS of your browser. The more detail you can provide, the easier for me to solve the issue.

  • bufferUnderrun commented 5 years ago

    Well some good news.

    OK. Windows 2016 server, SQL Server 2008, JDK 13.02 and just upgrading with only update.bat.

    ERROR. When running"server.bat console" i've directory "temp" write error and other xd.lck.

    OK. When running "server.bat start" everything works. The error seems come from the onedev service which is exec by "local system" account and whereas console is exec by my admin account.

    I've found the milestone error : when the deadline is passed, the field has a red border but the font color is white. That's why i don't see anything.

    image_3.png

    You need to change to red

    image_4.png

  • Robin Shen commented 5 years ago

    Thanks for findings. Will get it fixed in the upcoming 4.0.2

    For upgrade error, I guess as long as these two accounts have full permission over OneDev's installation directory, there will be no any issues?

    You also mentioned that there are some problems displaying issue detail in modal window. Can you please show the screenshot? Is this still happening if you are using latest chrome?

  • bufferUnderrun commented 5 years ago

    I use the same procedure for the upgrad since the beginning and i've always running console successfully. This build is the first not working.

    I think the problem with issue detail in modal was due to permission problem in the update. Everything seems to work great, you can close the issue.

    Thanks for your support

  • Robin Shen changed state to 'Closed' 5 years ago
    Previous Value Current Value 
    Open
    		 
    Closed
issue 1/1
Type
Bug
Priority
Critical
Assignee
Robin Shen
Affected Versions
Not Found
Issue Votes (0)
Login to vote
Watchers (2)
Reference
OD-209
Please wait...
Connection lost or session expired, reload to recover
Page is in error, reload to recover