History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-1885
Type: Bug Bug
Status: Closed Closed
Resolution: Won't Fix
Priority: Critical Critical
Assignee: Robin Shen
Reporter: productivity
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
QuickBuild

Cannot access server after restoring backup that had its system paused

Created: 13/Dec/13 06:48 PM   Updated: 16/Dec/13 11:31 PM
Component/s: None
Affects Version/s: 5.1.2
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment: Windows Server 2008


 Description  « Hide
Context:
I've tried updating from the 5.1.2 update (December 11th edition) to the 5.1.2 update (December 13th edition) but I couldn't access the server after.

Steps to reproduce:
1. Ensure that no builds are running on the server.
2. Pause the system through the "Administration tab" > "System setting" > "Pause system?" option.
3. Take a manual database backup through the " "Administration tab" > "Database backup" screen.
4. Shutdown the server (server.bat stop)
5. Uninstall the server (server.bat remove)
6. Delete the current installation folder of quickbuild-5.1.2 (which dates from December 11th).
7. Download and extract the new 5.1.2 version of QB (which dates from December 13th).
8. Restore the backup from step 3 (with restore.bat).
9. Install and start the server.
10. Open a browser and access the server's dashboard.

Observed results:
The server's dashboard page will fail to load (no connection could be established to the server).

Also note that when booting the server in console mode, I get the following exception repeated a few times:

jvm 1 | 2013-12-13 12:39:29,341 INFO - QuickBuild server started.
jvm 1 | 2013-12-13 12:39:29,343 INFO - You can now point browser to 'http://wn-qb-master-01:80' to access the server.
jvm 1 | Exception in thread "pool-1-thread-2" com.pmease.quickbuild.QuickbuildException: System is now paused and new builds are not allowed to run.
jvm 1 | at com.pmease.quickbuild.DefaultBuildEngine.requestBuild(DefaultBuildEngine.java:1389)
jvm 1 | at com.pmease.quickbuild.DefaultBuildEngine$5$1.run(DefaultBuildEngine.java:1672)
jvm 1 | at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
jvm 1 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
jvm 1 | at java.lang.Thread.run(Unknown Source)


 All   Comments   Work Log   Change History      Sort Order:
productivity [13/Dec/13 07:09 PM]
I tried restoring a previous database backup that was done this morning (i.e. it was created without having paused the system beforehand) and this problem still persists, although I got another exception now (it also gets repeated):

jvm 1 | 2013-12-13 13:56:09,354 ERROR - Error allocating node for step 'master'.
jvm 1 | com.pmease.quickbuild.QuickbuildException: Can not find any node matching specified criteria.
jvm 1 | at com.pmease.quickbuild.DefaultBuildEngine.run(DefaultBuildEngine.java:1124)
jvm 1 | at java.lang.Thread.run(Unknown Source)

In conclusion, the problem *might* have nothing to do with whether or not the system was paused or not, although I'm not 100% sure.

Robin Shen [14/Dec/13 04:47 AM]
I tried the same and can access dashboard without any issues. The exception message you posted here should not cause this. Can you please check the server log to see if there is any other error messages?

productivity [16/Dec/13 07:53 PM]
Ok, I found the issue.

The real problem was that we recently modified the http port of the server (from 8810 to 80, which makes it easier to remember QB's URL). However, when I did step 6 & 7, I lost the configuration information of the new port number, which meant that I had to access the server with its default port (8810) for the connection to work.

The fact that the URL printed in server console is wrong (http://wn-qb-master-01:80, which I guess is read from the "URL to Access QuickBuild" administration setting) did not make this error easy to find, though. Should I create another issue so that the server console prints out the real server URL instead of the one that is read from the "URL to Access QuickBuild" setting?

Robin Shen [16/Dec/13 11:31 PM]
Yes, please.