cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
853
Views
0
Helpful
7
Replies

WCS won't start after Linux Upgrade

scottwilliamson
Level 2
Level 2

Hi,

I've just upgrade RH to v5.0 and it all seemed to go fine except WCS won't start. I was running v5.0.56.0 on RH v4.0 (I know it's not supported) on a WLSE appliance, which ironically seemed to be fine. Now I get this....

Database server is running

Apache server is stopped

WCS is registered, but not initialized.

*********************************

The Server seems to be unavailable. The possible reasons are

1. The server is not running yet.

2. The server is hanging.

3 The server has crashed.

If the server has crashed or is hanging

Please report the issue and follow the instructions to restart it.

1. Run StopWCS to stop all WCS processes.

2. Run StartWCS to start the WCS server.

3. If the server still fails to start, or you still get this

message, then reboot the machine.

*********************************

Any suggestions will be most welcome.

Thanks

Scott

1 Accepted Solution

Accepted Solutions

From the bin directory, to execute dbadmin you were missing the ./ :

./dbadmin checkschema

./dbadmin defrag

./dbadmin reinitdb (that will clear all the DB)

The reinitdb would clear a db issue (worst case scenario for db).

If it's a tomcat issue, then a re-install will fix it.

The message you posted does not necessary mean that the root cause is the webserver apache.

View solution in original post

7 Replies 7

scottwilliamson
Level 2
Level 2

additional....

I get the above output from the WCSStatus command and I tried the suggestions.

Thanks

Scott

A few ideas:

1. Run a dbadmin checkschema from the bin directory.

2. Make a backup of the db, reinit the db (dbadmin reinitdb). and see if then the WCS starts. If it does, restore the previous db.

Im not sure at this point if it's a tomcat issue or db issue, this can help to narrow it down.

Hi Lucien,

Thanks for the suggestions - unfortunately I can't get dbadmin to do anything;

[root@nlcwcs1 bin]# dbadmin ?

-bash: dbadmin: command not found

[root@nlcwcs1 bin]# DBAdmin ?

-bash: DBAdmin: command not found

[root@nlcwcs1 bin]# dbadmin.sh

-bash: dbadmin.sh: command not found

[root@nlcwcs1 bin]#

Am I in the right directory?

[root@nlcwcs1 WCS5.0.56.0]# cd bin

[root@nlcwcs1 bin]# dir

aclProtocol.sql upgrade_2.2_b.sql

Backup upgrade_2.2_c.sql

Backup.lax upgrade_3.0-3.1.sql

CVS upgrade_3.0_Beta1_Beta2.sql

DBAdmin upgrade_3.0_Beta2_Beta3.sql

DBAdmin.lax upgrade_3.1-3.2.sql

dbadmin.sh upgrade_3.2_Beta1_Beta2.sql

EULA.html upgrade_4.0_Beta1_Fcs.sql

If I am, can you tell me how to use these commands please?

Many Thanks

Scott

Also...

I'm not desperate to keep WCS5.0.56.0 - would an upgrade to the next version be worth trying or how about an uninstall and reinstall of WCS?

Thanks Again

Scott

Hi Lucien,

I've not been able to try your suggestions yet but I found this in /opt/WCS5.0.56.0/webnms/logs/mod_jk.log

[Tue Aug 04 15:33:31.197 2009] [1584:3083486912] [error] ajp_service::jk_ajp_common.c (2097): (ajp13) Connecting to tomcat failed. Tomcat is probably not star

ted or is listening on the wrong port

Does this help with the diagnosis?

Thanks

Scott

From the bin directory, to execute dbadmin you were missing the ./ :

./dbadmin checkschema

./dbadmin defrag

./dbadmin reinitdb (that will clear all the DB)

The reinitdb would clear a db issue (worst case scenario for db).

If it's a tomcat issue, then a re-install will fix it.

The message you posted does not necessary mean that the root cause is the webserver apache.

Hi Lucien

I tried the checkschema option first and then tried starting WCS - no joy. I then decided to Uninstall and reinstall and WCS now works - I restored the database and I'm fully up and running.

This whole process was fraught with worry due to my lack of experience with Linux.

Many Thanks for your Guidance

Scott

Review Cisco Networking products for a $25 gift card