WCS Version 7.0.164.0 won't start

[rwilletts]

WCS fails to start with a Tomcat error , see below ;

See launchout below - any ideas - without re-installing WCS

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

Starting NMS Server...

NMS Server Started.

Starting up TFTP server...

TFTP Server started.

Starting up FTP server

Started FTP

FTP Server started

Apache server is already started

Starting Tomcat server ...

Tomcat server failed to start.

Failed to start the Tomcat web server.

Shutting down Apache server ...

Stopping FTP server...

Exception during ServerEngine::run java.net.SocketException: socket closed

java.net.SocketException: socket closed

at java.net.PlainSocketImpl.socketAccept(Native Method)

at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:390)

Stopping TFTP server...

at java.net.ServerSocket.implAccept(ServerSocket.java:453)

at java.net.ServerSocket.accept(ServerSocket.java:421)

at ranab.server.ServerEngine.run(Unknown Source)

at java.lang.Thread.run(Thread.java:619)

Stopped TFTP server.

Stopped FTP server.

Failed to shutdown Apache server.

Leaving database server running.

[mscherting]

Just curious, when did this problem start?  Did it coincide with any recent Microsoft patches/updates?

[rwilletts]

unsure but i'll check

[Nael Mohammad]

Have you rebooted the server? Ensure that other web applications running from third party such as IIS is disabled as this will cause a port conflict.

What OS is this installed on?

Post the logs from WCS7.0.164.0/webnms/logs in zip format.

WCS 7.0.172 is available for download which is recommended to upgrade to.

[tittonandras2]

Hello!

I have exactly the same problem with WCS 7.0.172.

Fresh install, so I am open to any solution!

Rebooted the server - didn't help.

Re-installed WCS - didn't help.

Disabled McAfee security software - didn't help.

Create a new virtual machine (Win2k3) from template - I think this wouldn't help either.

Any other ideas?

Logs and systeminfo attached.

Best regards,

Andras

[rwilletts]

All I've resolved my issue - which is also in a VM environment - It was related to the available memory provided by VMware

[dennischolmes]

Make sure you always have available memory and disk resources. There is a minimum systems requirement list for the size of deployment you own. See below.

Cisco WCS High-End Server • 3000 lightweight access points, 1250 standalone access points, 750 wireless LAN controllers • Intel® Xeon Quad Core CPUs; 3.16 GHz, 8-GB RAM, 200-GB HDD (free space)

Cisco WCS Standard Server • 2000 lightweight access points, 1000 standalone access points, 450 wireless LAN controllers • Intel® Dual Core CPU; 3.2 GHz, 4-GB RAM, 80-GB HDD (free space)

Cisco WCS Low-End Server • 500 lightweight access points, 200 standalone access points, 125 wireless LAN controllers • Intel® CPU; 3.06 GHz, 2-GB RAM, 50-GB HDD (free space)

Next, check the services running on the server to verify that the database and WCS have started on the machine. If this doesn't solve your problem then there are some database tools to check the integrity of the WCS Solid database. They are in the WCS directory of your server. These will allow you to know if you have a database issue. After these solutions have been exhausted I would open a TAC case.

[ksprague]

Is you IIS service running at startup?  If so try disabling that.

[maldehne]

Netstat -a

Check if there is any other application using WCS ports, stop it and try again.