WCS not working

Unanswered Question
Mar 8th, 2010

After having some server issue (firmware update needed for the chassis it was sitting in) I'm now having a problem starting the WCS (version 6.0.132.0) When I run it, it just says:

Starting WCS
DbMonitor.sendAdminCommand: shutdown force - [Solid JDBC 04.50.0150] Invalid authorization specification
Failed to start WCS.  Check hm_launchout.txt for details.
Log files are located under webnms\logs in the WCS install directory.

I looked at the lhm_launchout.txt log and that just says:

Starting Health Monitor as a primary
Checking for Port 8082 availability... OK
Starting Health Montior Web Server...
Health Monitor Web Server Started.
Starting Health Monitor Server...
Health Monitor Server Started.

I can ping the ip address from another pc and able to ping out from the WCS server.

The Cisco Wireless Control System and Nms_Apache services appear to be working, the only error in the event viewer seems to be for apache:

The Apache service named  reported the following error:
>>> [Mon Mar 08 10:07:57 2010] [notice] Disabled use of AcceptEx() WinSock2 API

At the moment, whenever I try to get to the WCS site I'm getting

Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.


--------------------------------------------------------------------------------

Apache Server at 10.4.20.10 Port 80

Has anyone else had this problem or has any ideas?

Steve

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
sschmidt Wed, 03/10/2010 - 11:15

Try to restart it again and add the launchout.txt output to the post.

The winsock error can be ignored.

sgilfrin1 Thu, 03/11/2010 - 02:38

The launchout.txt doesn't give much away:

Starting Health Monitor as a primary
Checking for Port 8082 availability... OK
Starting Health Montior Web Server...
Health Monitor Web Server Started.
Starting Health Monitor Server...
Health Monitor Server Started.

Steve

sschmidt Thu, 03/11/2010 - 06:24

Steve,

That looks like the "hm_launchout.txt" file.  Can you attach the "launchout.txt" file?

sgilfrin1 Thu, 03/11/2010 - 06:32

Your right I did post the hm_launchout.txt file.  Here's the "launchout.txt" file

Checking for Port 21 availability... OK
Checking for Port 8456 availability... OK
Checking for Port 8457 availability... OK
Checking for Port 1299 availability... OK
Checking for local Port 1299 availability... OK
Checking for Port 6789 availability... OK
Checking for local Port 6789 availability... OK
Checking for UDP Port 69 availability... OK
Checking for Port 8005 availability... OK
Checking for UDP Port 162 availability... OK
Checking for Port 8009 availability... OK
Starting RMI registry on port 1299
Registry started.
DB is already started
Shutting down Apache server ...
Leaving database server running.

Steve

sschmidt Thu, 03/11/2010 - 06:38

Please go to Administration > Logging and uncheck Status Polling, Object
Manager, Configuration, SNMP Mediation, MSE/Location Servers, XML
Mediation, Navigator, Reports and Database Administration and change the
message level to TRACE and click submit.  Restart WCS and then go back to

the logging area and download and attach the wcs-0-0.log and wcs-1-0.log.

sgilfrin1 Thu, 03/11/2010 - 07:15

I don't have any programs related to the WCS in my start - all programs. Where else can I find them?

Steve

sschmidt Thu, 03/11/2010 - 07:18

The path provided is within WCS after you are logged in.  From there you can adjust the logging and download the logs.

Is there not an install directory for WCS where you found these logs originally?

sgilfrin1 Thu, 03/11/2010 - 07:28

Your very fast at replying.

I'm unable to login to the WCS, thats the problem. The program was installed to c:\program files\wcs6.0.132.0 logs are available within the webnms\logs but I'm not sure which logs are going to be of use.

Steve

sschmidt Thu, 03/11/2010 - 07:41

Sorry I forgot that

Ok attach those 2 logs wcs-0-0.log and wcs-1-0.log after a restart and we will at least see what they have.

sgilfrin1 Thu, 03/11/2010 - 07:55

The wcs-0.0 log:

3/08/10 09:09:37.756 INFO[general] [10] Checking for Port 21 availability... OK
3/08/10 09:09:37.771 INFO[general] [10] Checking for Port 8456 availability... OK
3/08/10 09:09:37.771 INFO[general] [10] Checking for Port 8457 availability... OK
3/08/10 09:09:37.771 INFO[general] [10] Checking for Port 1299 availability... OK
3/08/10 09:09:37.771 INFO[general] [10] Checking for local Port 1299 availability... OK
3/08/10 09:09:37.771 INFO[general] [10] Checking for Port 6789 availability... OK
3/08/10 09:09:37.771 INFO[general] [10] Checking for local Port 6789 availability... OK
3/08/10 09:09:37.771 INFO[general] [10] Checking for UDP Port 69 availability... OK
3/08/10 09:09:37.771 INFO[general] [10] Checking for Port 8005 availability... OK
3/08/10 09:09:37.771 INFO[general] [10] Checking for UDP Port 162 availability... OK
3/08/10 09:09:37.771 INFO[general] [10] Checking for Port 8009 availability... OK
3/08/10 09:09:37.771 INFO[general] [10] Starting RMI registry on port 1299
3/08/10 09:09:37.849 INFO[general] [10] Registry started.
3/08/10 09:09:37.943 INFO[general] [10] DB is already started
3/08/10 09:09:38.412 ERROR[general] [10] Cannot check database schema because java.sql.SQLException: [Solid JDBC 04.50.0150] Invalid authorization specification

wcs-1.0.log:

3/08/10 09:09:29.84 INFO[general] [10] Checking for Port 21 availability... OK
3/08/10 09:09:29.100 INFO[general] [10] Checking for Port 8456 availability... OK
3/08/10 09:09:29.100 INFO[general] [10] Checking for Port 8457 availability... OK
3/08/10 09:09:29.100 INFO[general] [10] Checking for Port 1299 availability... OK
3/08/10 09:09:29.100 INFO[general] [10] Checking for local Port 1299 availability... OK
3/08/10 09:09:29.100 INFO[general] [10] Checking for Port 6789 availability... OK
3/08/10 09:09:29.100 INFO[general] [10] Checking for local Port 6789 availability... OK
3/08/10 09:09:29.100 INFO[general] [10] Checking for UDP Port 69 availability... OK
3/08/10 09:09:29.100 INFO[general] [10] Checking for Port 8005 availability... OK
3/08/10 09:09:29.100 INFO[general] [10] Checking for UDP Port 162 availability... OK
3/08/10 09:09:29.100 INFO[general] [10] Checking for Port 8009 availability... OK
3/08/10 09:09:29.100 INFO[general] [10] Starting RMI registry on port 1299
3/08/10 09:09:29.178 INFO[general] [10] Registry started.
3/08/10 09:09:29.303 INFO[general] [10] DB is already started
3/08/10 09:09:29.756 ERROR[general] [10] Cannot check database schema because java.sql.SQLException: [Solid JDBC 04.50.0150] Invalid authorization specification

Steve

sschmidt Thu, 03/11/2010 - 08:12

Ok we have one thing to try before I recommend a reinstall and restore from a backup that I hope you have.

Make sure the server is completely stopped especially the DB.

Go into the install dir/bin and run the command "dbadmin checkschema" it will tell you it may modify the db say yes.  Allow this to finish.

If it does not finish or after it finishes you can not start WCS you should at least try a restore of a backup or uninstall/reinstall WCS and restore a backup.

One last question.  Is this a VM install? If so you might try increasing the memory available as I have seen this in relation to this error but have not seen it help much but it is worth a try.

sgilfrin1 Thu, 03/11/2010 - 08:39

running the dbamin checkschema comes up with error message:

Updating schema.  This may take a while.
java.sql.SQLException: [Solid JDBC 04.50.0150] Invalid authorization specification
Failed to export Hibernate schema

Where do I go to stop the database? There seems to be a few messages regarding [Solid JDBC 04.50.0150] Invalid authorization specification.

I don't remember ever doing a backup of the wcs. Its not a vm install, but the server has plenty of memory.

Steve

sgilfrin1 Fri, 03/12/2010 - 02:50

If I go to c:\program files\wcs6.0.132.0\bin and

run sqlgui.bin it launches solidconsole. However I don't have a username or password to get into it. I'm wondering if this is the problem. Is there a default username and password or anyway to reset it. Wish my collegue left notes on this before he did a runner!

Steve

Actions

This Discussion