search

yduchesne / sapia

Automatically exported from code.google.com/p/sapia
0 stars 0 forks source link

Corus web UI: On first staging of corus does not work #25

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. install corus
  a. cd ~/
  b. wget http://<server>/<path>/corus_installer-4.2.7.tar.gz
  c. sudo mv corus_installer-4.2.7.tar.gz /opt/app
  d. cd /opt/app
  e. sudo tar zxvf corus_installer-4.2.7.tar.gz
  f. cd corus_installer-4.2.7
  g. sudo chmod 700 installer.sh
  h. sudo sh ./installer.sh
  i. /opt/app/corus
  j. sudo ln -sfn /opt/app/corus/sapia_corus_server_package-4.2.7 current
2. Update /opt/app/corus/current/config/corus.properties
  a. update corus.server.domain=<domain>
  b. ubik.rmi.naming.broadcast.provider=ubik.rmi.naming.boardcast.avis
  c. ubik.rmi.naming.broadcast.avis.url=elvin://<server>
  d. corus.server.repository.mode.type=client
3. Start avis
  a. sudo chkconfig avisd on
  b. sudo service avisd start
4. Start corus
  a. sudo service corus start
5. start coruscli
6. test corus is running using web ui
  a. http://<server>:30000

What is the expected output? What do you see instead?
Expected: See corus web UI
Actual: No UI

What version of the product are you using? On what operating system?
Corus v4.2.7 on Linux (CentOS 6.3 Final)

Please provide any additional information below.
If you exit coruscli, restart the ssh session and start coruscli again ... now 
the web UI page works fine

Original issue reported on code.google.com by sundeep....@gmail.com on 21 Oct 2014 at 8:55

GoogleCodeExporter commented 9 years ago 
How long have you waited between the moment you started corus and when you 
opened a browser? It can take a few seconds for corus to boot the different 
module and start the http server. Of course in the step 6a. I guess you meant 
http://{server}:33000 as corus runs by default on port 33000 (and not 30000).

On an other note, the fact that you exist the CLI and restart you ssh 
connection is not related at all with the internals of the corus server. The 
coruscli command starts a client (command-line based) that goes through the 
same path as the web interface. So reconnecting your client does not impact how 
the server behaves intenally...

Original comment by jcdesroc...@gmail.com on 12 Nov 2014 at 8:25

GoogleCodeExporter commented 9 years ago 
I did mean 33000 (that was indeed a typo).

This does not make sense but it happened on 12 out of 12 virtual servers I 
provisioned using OpenStack on our intranet.

Original comment by sundeep....@gmail.com on 8 Dec 2014 at 10:40