Setup wizard fail on CentOS with RC1

Toony · September 20, 2012, 7:58am

[quote=kurt998]Hi everybody

I also tried to install BM on centos 6.2 x86-64bit from official installation manual

I finish installed BM system by yum, but I couldn’t start to config the system from beginning. I got error apache 403 when I tried to access https://hostname/setup

Is there anybody can help me?

Thanks in advance[/quote]

It seems that your Tomcat isn’t started.
You can try to start it with command:

service bm-tomcat restart

How much memory does your system have ? I update prerequisites pages, because since RC1, 4Go is the minimum even for test.

kurt998 · September 20, 2012, 8:18am

Thanks for your feedback

Now,the server total has 2GB memory for test, do you mean I need to upgrade to 4GB to try again?

Thanks

kurt998 · September 20, 2012, 8:20am

[quote=Toony][quote=kurt998]Hi everybody

I also tried to install BM on centos 6.2 x86-64bit from official installation manual

I finish installed BM system by yum, but I couldn’t start to config the system from beginning. I got error apache 403 when I tried to access https://hostname/setup

Is there anybody can help me?

Thanks in advance[/quote]

It seems that your Tomcat isn’t started.
You can try to start it with command:

service bm-tomcat restart

How much memory does your system have ? I update prerequisites pages, because since RC1, 4Go is the minimum even for test.[/quote]


# rpm -qa|grep tomcat
bm-tomcat-0.19.6314-0.x86_64
apache-tomcat-apis-0.1-1.el6.noarch

# service bm-tomcat restart
Waiting for BM Tomcat shutdown...
Using CATALINA_BASE:   /usr/share/tomcat
Using CATALINA_HOME:   /usr/share/tomcat
Using CATALINA_TMPDIR: /tmp
Using JRE_HOME:       /usr/lib/jvm/java-openjdk

# ps -ef|grep tomcat
root      4361     1 19 08:21 pts/2    00:00:03 /usr/lib/jvm/java-openjdk/bin/java -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=/usr/share/tomcat/conf/logging.properties -Dfile.encoding=UTF-8 -Xms256m -Xmx256m -XX:MaxPermSize=128m -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:CMSInitiatingOccupancyFraction=80 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp -Djava.awt.headless=true -Duser.timezone=GMT -Djava.endorsed.dirs=/usr/share/tomcat/endorsed -classpath :/usr/share/tomcat/bin/bootstrap.jar -Dcatalina.base=/usr/share/tomcat -Dcatalina.home=/usr/share/tomcat -Djava.io.tmpdir=/tmp org.apache.catalina.startup.Bootstrap start
root      4564  3776  0 08:21 pts/2    00:00:00 grep tomcat

Toony · September 20, 2012, 8:34am

[quote=kurt998]Thanks for your feedback

Now,the server total has 2GB memory for test, do you mean I need to upgrade to 4GB to try again?

Thanks[/quote]

Yes we recommend to upgrade to 4GB, but you don’t need te reinstall, just reboot.

Toony · September 20, 2012, 8:43am

[quote=kurt998]Hi everybody

[code]

rpm -qa|grep tomcat

bm-tomcat-0.19.6314-0.x86_64
apache-tomcat-apis-0.1-1.el6.noarch

service bm-tomcat restart

Waiting for BM Tomcat shutdown…
Using CATALINA_BASE: /usr/share/tomcat
Using CATALINA_HOME: /usr/share/tomcat
Using CATALINA_TMPDIR: /tmp
Using JRE_HOME: /usr/lib/jvm/java-openjdk

ps -ef|grep tomcat

root 4361 1 19 08:21 pts/2 00:00:03 /usr/lib/jvm/java-openjdk/bin/java -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=/usr/share/tomcat/conf/logging.properties -Dfile.encoding=UTF-8 -Xms256m -Xmx256m -XX:MaxPermSize=128m -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:CMSInitiatingOccupancyFraction=80 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp -Djava.awt.headless=true -Duser.timezone=GMT -Djava.endorsed.dirs=/usr/share/tomcat/endorsed -classpath :/usr/share/tomcat/bin/bootstrap.jar -Dcatalina.base=/usr/share/tomcat -Dcatalina.home=/usr/share/tomcat -Djava.io.tmpdir=/tmp org.apache.catalina.startup.Bootstrap start
root 4564 3776 0 08:21 pts/2 00:00:00 grep tomcat

[/code][/quote]

In fact, if you have less than 4GB, some needed services may fail to start during installation, sometimes it’s Tomcat, sometimes Postgres…
You can try to restart all services:

# bmctl stop
# service postgresql restart
# bmctl start

But we recommend you to upgrade to 4GB.

tcataldo · September 20, 2012, 9:01am

Humm 2gigs should be more than enough for testing.

A problem with tomcat not being up would return a 502 error, not 403.

Anything interesting in your /var/log/bm-tomcat/bm-java.log ?

Toony · September 20, 2012, 10:22am

Another thing, do you disable SELinux and iptables like explain in note section ?

philherbert · September 26, 2012, 2:06pm

I’m in exactly the same situation. Built a VM box running 64-bit CentOS 6.3 with Basic Server install and added own install of OpenLDAP.

I can only see the setup wizard page if I got to https://servername:8080/setup but then the setup fails on the Server Test.

If I run ‘nmap localhost’ I see :-

PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
110/tcp open pop3
111/tcp open rpcbind
143/tcp open imap
389/tcp open ldap
631/tcp open ipp
993/tcp open imaps
995/tcp open pop3s
5432/tcp open postgresql
8022/tcp open oa-system
8080/tcp open http-proxy

SELinux and iptables are disabled.

Toony · September 26, 2012, 2:23pm

Is NGinx service started ?
If you start NGinx and connect to https://servername/setup, which error did you get ?

Can you send us result of commands:

# hostname
# hostname -f

philherbert · September 26, 2012, 4:48pm

Output of both hostname commands is the same ie bluemind.domainname.com

However when starting nginx service I see :-

Starting nginx: nginx: [emerg] invalid number of arguments in “server_name” directive in /etc/nginx/sites-enabled/bm-force-setup:4
[FAILED]

I’ve manually added the server_name values at lines 4 & 14 in /etc/nginx/sites-enabled/bm-force-setup and now nginx starts OK.

However, I do not get the setup wizard, but a screen stating that Blue Mind is uptodate.

Thanks for your assistance!

Phil

Toony · September 26, 2012, 5:05pm

You must restart installation. To do that, you must drop Blue Mind database and try again to connect to https://hostname/setup:

# bmctl stop
# su - postgres
$ dropdb bj
^D
# bmctl start

philherbert · September 27, 2012, 9:03am

OK, step completed.

Now, going to https://hostname/setup and get prompted for username / password.

Toony · September 27, 2012, 9:17am

Ok, this password is set after a successfull installation to prevent access to /setup by anybody. This password is given to administrator after successfull installation and must be used when upgrading.

To reset this password, you can run command:

htpasswd -b /etc/nginx/sw.htpasswd admin newpassword

philherbert · September 27, 2012, 9:51am

Thanks!

I had to use

htpasswd -c -b /etc/nginx/sw.htpasswd admin newpassword

because the file did not exist.

However the installation wizard has now run successfully.

Toony · September 27, 2012, 10:03am

Yes, it may not exist if your installation fail.
I think that we are adding a script to reset an installation… Our goal is that step don’t fail, never… Howerver this script may be usefull on some case, at least in your case, but if you’re testing and want to restart from scratch without re-install all the system