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

Key: CIB-999
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Trivial Trivial
Assignee: jason
Reporter: Stephen Ng
Votes: 0
Watchers: 0
Operations

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

"System Starting" screen never goes away on a new instance

Created: 10/Mar/07 02:46 PM   Updated: 04/Dec/07 07:04 AM
Component/s: None
Affects Version/s: 1.2.18
Fix Version/s: 2.0.5, 1.2.42

Environment: linux


 Description  « Hide
Here's how I ran into this problem:

- I migrated an old Pulse instance to a new Pulse instance
- I started Pulse. The web page redirected me to http://pulsebox:8080/startup/starting.action
- I decided I really wanted a brand new install.
- I killed Pulse, removed .pulse and the database, and restarted pulse
- I refreshed my web page, which was still on "starting.action"
- Starting never seems to finish
- Navigating to http://pulsebox:8080 leads to setup/setupWizard.action page--apparently it needs an admin user.

starting.action (and all other pages) should have redirected me to setupWizard.

 All   Comments   Change History      Sort Order:
James French - 27/Sep/07 07:45 PM
I also got something like this recently. I installed Pulse 2.02 locally (we are running 1.2.35 on the build machine), which went completely cleanly. I then uninstalled it and tried to install 1.2.37 for some local testinhg. I got a hang on the starting up. I restarted the service and managed to get to putting my license key in, but then it just hung again. In the end I had to uininstall it. Actually, if memory serves it may have just ended up with the 'page not available' notification.

jason - 03/Oct/07 02:49 PM
Hi James,

Thanks for the details. There are a few problems around this startup redirect which we need to look at in one hit.

jason - 04/Dec/07 03:14 AM
Fixed in change 4013.

jason - 04/Dec/07 07:04 AM
Merged to trunk in change 4018.