Issue #3 new

Confluence not running

Matt Doar (ServiceRocket)
created an issue

OSX 10.7.5, vagrant 1.2.5, everything looks good. The 'up' command has one warning but exits successfully I think. The VBoxHeadless process is running. But connecting to

http://localhost:1990/confluence

returns nothing. Telnet to that port and netstat -a both confirm that there is nothing listening there.

Where can I look for the Confluence logs? How can I see what processes are running in my VM?

[mdoar@mdoar2 atlassian-connect-confluence-vagrant]$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Importing base box 'base'...
[default] Matching MAC address for NAT networking...
[default] Setting the name of the VM...
[default] Clearing any previously set forwarded ports...
[default] Creating shared folders metadata...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] -- 1990 => 1990 (adapter 1)
[default] Running 'pre-boot' VM customizations...
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
[default] VM booted and ready for use!
[default] Configuring and enabling network interfaces...
[default] Mounting shared folders...
[default] -- /vagrant
[default] -- /tmp/vagrant-puppet/manifests
[default] -- /tmp/vagrant-puppet/modules-0
[default] Running provisioner: puppet...
Running Puppet with default.pp...
stdin: is not a tty
warning: Could not retrieve fact fqdn
notice: /Stage[main]/Sudo/File[/etc/sudoers.d/]/mode: mode changed '0755' to '0550'
notice: /Stage[main]/Sudo/File[/etc/sudoers]/content: content changed '{md5}683eca72967d971ee3be5cd581069b9a' to '{md5}ebd77e09715c4da6be84d56233139fff'
notice: /Stage[main]//Exec[apt-get-update]/returns: executed successfully
notice: /Stage[main]//Package[curl]/ensure: ensure changed 'purged' to 'present'
notice: /Stage[main]//Package[git-core]/ensure: ensure changed 'purged' to 'present'
notice: /Stage[main]/Java7/Apt::Ppa[ppa:webupd8team/java]/Package[python-software-properties]/ensure: ensure changed 'purged' to 'present'
notice: /Stage[main]/Java7/File[/tmp/java.preseed]/ensure: defined content as '{md5}7e39d91ad5e8514ea8627ba773f0d840'
notice: /Stage[main]/Java7/Apt::Ppa[ppa:webupd8team/java]/Exec[add-apt-repository-ppa:webupd8team/java]/returns: executed successfully
notice: /Stage[main]/Apt::Update/Exec[apt_update]: Triggered 'refresh' from 1 events
notice: /Stage[main]/Java7/Package[oracle-java7-installer]/ensure: ensure changed 'purged' to 'present'
notice: /File[/etc/sudoers.d/README]/ensure: removed
notice: /Stage[main]//Sudo::Conf[vagrant]/File[10_vagrant]/ensure: created
notice: /Stage[main]//Exec[install_ap3]/returns: executed successfully
notice: /Stage[main]//Exec[start_confluence_in_background]/returns: executed successfully
notice: 
    ***************************************************************************************************

      Congratulations! Your Atlassian Connect Development Box has been provisioned. In a few more minutes,
      you'll be able to access Confluence at:

          http://localhost:1990/confluence (user: admin, password: admin)

      It might take 2-5 minutes to start up Confluence depending on how fast your machine is. In order to
      install your Connect add-on, you can issue the following command from your terminal:

          curl -v -u admin -X POST -d url={url_where_your_atlassian-plugin.xml_resides}
          > http://localhost:1990/confluence/rest/remotable-plugins/latest/installer

      That command relies the availability of the `curl` command on your machine.

    ***************************************************************************************************
notice: /Stage[main]//Notify[done]/message: defined 'message' as '
    ***************************************************************************************************

      Congratulations! Your Atlassian Connect Development Box has been provisioned. In a few more minutes,
      you'll be able to access Confluence at:

          http://localhost:1990/confluence (user: admin, password: admin)

      It might take 2-5 minutes to start up Confluence depending on how fast your machine is. In order to
      install your Connect add-on, you can issue the following command from your terminal:

          curl -v -u admin -X POST -d url={url_where_your_atlassian-plugin.xml_resides}
          > http://localhost:1990/confluence/rest/remotable-plugins/latest/installer

      That command relies the availability of the `curl` command on your machine.

    ***************************************************************************************************'
notice: Finished catalog run in 115.64 seconds
[mdoar@mdoar2 atlassian-connect-confluence-vagrant]$ ls
README.md*   Vagrantfile* manifests/   modules/

Comments (5)

  1. Matt Doar (ServiceRocket) reporter

    Listing the running processes with: vagrant ss -c "ps auxww" I see the Confluence processes

    vagrant 5077 2.6 4.9 392428 51124 ? Sl 21:06 0:20 /usr/lib/jvm/java-7-oracle/bin/java -DAP3_HOME=/home/vagrant/.ap3-sdk -Dlog4j.configuration=file:////home/vagrant/.ap3-sdk/log4j.properties -Dap3.javacmd=/usr/lib/jvm/java-7-oracle/bin/java -jar /home/vagrant/.ap3-sdk/bin/ap3-bootstrap-0.6.jar start confluence --jvmargs -Datlassian.upm.on.demand=true

    vagrant 6291 41.0 10.5 863828 107896 ? Sl 21:22 0:05 /usr/lib/jvm/java-7-oracle/jre/bin/java -Datlassian.upm.on.demand=true -XX:MaxPermSize=256m -Xmx512m -Xms128m -XX:PermSize=48m -Datlassian.dev.mode=true -Djava.awt.headless=true -Dbaseurl=http://localhost:1990/confluence -Dconfluence.home=/home/vagrant/.ap3/container/confluence-home-1990 -Dcatalina.home=/home/vagrant/.ap3/container/confluence-5.2-sidebar-m1/apache-tomcat-6.0.32/apache-tomcat-6.0.32 -Dcatalina.base=/home/vagrant/.ap3/container/confluence-5.2-sidebar-m1/cargo-confluence-home -Djava.io.tmpdir=/home/vagrant/.ap3/container/confluence-5.2-sidebar-m1/cargo-confluence-home/temp -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=/home/vagrant/.ap3/container/confluence-5.2-sidebar-m1/cargo-confluence-home/conf/logging.properties -classpath /home/vagrant/.ap3/container/confluence-5.2-sidebar-m1/apache-tomcat-6.0.32/apache-tomcat-6.0.32/bin/bootstrap.jar:/usr/lib/jvm/java-7-oracle/lib/tools.jar org.apache.catalina.startup.Bootstrap start

    but I still can't seem to find the active logs directory:

    [mdoar@mdoar2 atlassian-connect-confluence-vagrant]$ vagrant ssh -c "find /home/vagrant/.ap3 -name logs" /home/vagrant/.ap3/container/confluence-5.2-sidebar-m1/cargo-confluence-home/logs /home/vagrant/.ap3/container/confluence-5.2-sidebar-m1/apache-tomcat-6.0.32/apache-tomcat-6.0.32/logs /home/vagrant/.ap3/templates/.git/logs

  2. Rich Manalang [Atlassian] repo owner

    Odd... did it finally fail? Sorry, I haven't had time to look into this. If it did work, please comment. Re: the confluence log, I noticed that it wasn't getting generated as well... on my list to look at.

  3. Log in to comment