WCS 6.0.132.0 Database

Hello,
I've been having some problems with the linux version of WCS. Sometimes, and I still don't know why the Database server stops. To activate it again I need to restart the service using the WCSStart script. Is anyone having similar problems? The service can work for two weeks or a month... then it just stops.
Best regards

Hello,
my database stoped working again... It happened last night.
I got this output from the WCSStatus script.
"Health Monitor is running.
WCS is initialized, but is not serving web pages.
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.
Database server is stopped
Apache server is running"
So I think the DBAdmin didn't solve the problem. Any next steps?
Thanks for your help.
Tiago

Similar Messages

Can't add Controller over VPN in WCS v6.0.132.0

Hi
I use WCS v6.0.132.0 to manage my 4402 and 2106 controller both running version 6.0.182.0
When I try to add another 2106 over DM-VPN it fails with the following errors:
”No response from device, check SNMP communities, version or network for issues”
If I move the new 2106 controller to LAN with same config there is no problem.
I found this note in the in “Cisco Wireless Control System Configuration Guide, Release 6.0”
“Note If you are adding a controller into WCS across a GRE link using IPsec or a lower MTU link with multiple fragments, you may need to adjust the MaxVar Binds PerPDU. If it is set too high, the controller may fail to be added into WCS. To adjust the MaxVarBindsPerPDU setting, do the following:
1) Stop WCS.
2) Go to the location of the Open SnmpParameters.properties file on the server that is running WCS.
3) Edit MaxVarBindsPerPDU to 50 or lower.
4) Restart WCS.”
On my system I have the “SnmpParameters.properties” file is located //WCS6.0.132.0\webnms\classes\com\cisco\server\resources
But I don’t have “MaxVarBindsPerPDU” settings in the file.
Beside some # explanations text, the only settings I have in the “SnmpParameters.properties” file is:
DebugEnabled                         false
SerializeRequests                    true
MaxRepetitions                       10
MaxRetryTimeout                      60
WlanTimeoutMsecsPerAP                 50
I have tried to add “MaxVarBindsPerPDU” settings, but it have no effect.
Anyone have an idea what to do?
TIA

Thank you so much!
Step 1 solved the issue.
I changed “Maximum VarBinds per Get PDU” from 30 to 20 and “Maximum VarBinds per Set PDU” from 50 to 20.
Thanks

WLC 5.2.193.0 with WCS 6.0.132.0 a supported config?

I know of a large site (not one of mine) that is running WLC 5.2.193.0 code paired up with WCS 6.0.132.0. The release notes for each product make no mention of support for this configuration.
Is this is supported configuration?

Thanks to both of you who replied. I just need to ensure that Cisco will support this scenario. The larger site is actually a "parent" site, and we try to keep our configs in parallel, but I'm not going to put the smaller site into an unsupported configuration.
I found this document, updated September 1st, which still doesn't list WLC 5.2.193.0 and WCS 6.0.132.0 as a supported config:
http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a0080af7140.shtml

WCS 6.0.132.0 Error

Hi,
I have a problem with WCS 6.0.132.0.
I get every time I press a link a popup with error: "System Error: Wrong Alarm Type rogueUnclassifiedMinor"
Is this a bug?
Any idea to solve this?
Thanks in advance

Hi Juan,
This bug was supposed to be fixed, but it looks like it may have crept back in 6.x;
CSCsr02317 Bug Details
Getting error message for alarm dashboard after upgrade from D3MR2 to F
Symptom:
Receive error popup constantly that states the following:
System Error: Wrong Alarm Type rogueUnclassifiedMinor
Conditions:
After upgrading the WCS this happens
Workaround:
Clear the browser cache and cookies. Then restart browser and the error message should go away. Status
Fixed
Severity
4 - minor
Last Modified
In Last Year
Product
Cisco Wireless Control System
Technology
1st Found-In
5.1(63.0)
5.1(65.4)
Fixed-In
5.2(44.0)
Hope this helps!
Rob

Issue while installing WCS using omii.ini: Database ping failed

Hi,
I am trying to install WCS on local linux VM. I am following the document 'Oracle WebCenter Sites: Installing on Oracle WebLogic Application Server".
Following are the things I have been able to do successfully:
Install Oracle DB, create a database and then create a user for this database
Install WebLogic server, create domain, create admin server, managed server, and finally create a datasource. THe datasource connection to the DB created in step 1 above is successfull.
I downloaded the WCS installer from Oracle Website 'WebCenterSites_11.1.1.6_bp1'. I am installing using silent installer using omii.ini file.
During installation, on receiving the prompt to install CS and CAS applications, I installed them successfully via WebLogic console.
I tested the URL 'http://localhost:7001/cs/HelloCS' and it showed me the Oracle WCS 11g page.
Now, when I go back to the wcs installation terminal and hit Enter, it gives following error:
[2013-07-11 01:32:21.861][CS.INSTALL][INFO] 1. If your platform requires you to manually deploy the Sites application, deploy Sites now. Otherwise, continue with step 2 2. Restart your application server. 3. Test the URL http:////HelloCS to see if application is deployed successfully 4. If the test is successful, press ENTER. URL http://localhost:7001/cs/HelloCS [2013-07-11 01:41:16.841][CS.INSTALL][INFO] CSSetupEngine.testConnectionAction: Testing user configuration and database connectivity. [2013-07-11 01:41:17.118][CS.INSTALL][INFO] CSSetupEngine.postURL: PostURL success for http://localhost:7001/cs/HelloCS [2013-07-11 01:41:17.118][CS.INSTALL][INFO] CSSetupEngine.testConnectionAction: Web Server and Application Server Configuration test finished successfully. [2013-07-11 01:41:17.118][CS.INSTALL][INFO] CSSetupEngine.testConnectionAction: Attempting to Ping the Database. [2013-07-11 01:41:17.459][CS.INSTALL][ERROR] CSSetupEngine.doPing: Database Ping Failed. Make sure your application server and web server are running. Response received = HTTP/1.1 200 OK HOST_SERVICE: FutureTenseContentServer:11.1.1.6.1 Transfer-Encoding: chunked Date: Wed, 10 Jul 2013 20:11:17 GMT Set-Cookie: JSESSIONID=vpMNRd1Fwb1NJyb5NH1pXx5dfmPhzzyJL2S3yYry3FwQqL8hFVJ6!1994306862; path=/; HttpOnly Content-Type: text/html; charset=UTF-8 X-Powered-By: Servlet/2.5 JSP/2.1 [2013-07-11 01:41:17.459][CS.INSTALL][ERROR] CSSetupEngine.doPing: Database Ping Failed. Make sure your application server and web server are running. Response received = HTTP/1.1 200 OK HOST_SERVICE: FutureTenseContentServer:11.1.1.6.1 Transfer-Encoding: chunked Date: Wed, 10 Jul 2013 20:11:17 GMT Set-Cookie: JSESSIONID=vpMNRd1Fwb1NJyb5NH1pXx5dfmPhzzyJL2S3yYry3FwQqL8hFVJ6!1994306862; path=/; HttpOnly Content-Type: text/html; charset=UTF-8 X-Powered-By: Servlet/2.5 JSP/2.1 [2013-07-11 01:41:17.460][CS.INSTALL][ERROR] CSSetupEngine.testConnectionAction: Database Ping was attempted with WCSDataSource as the DSN. The URL that was passed in = http://localhost:7001/cs/CatalogManager. Please Check your connection and property files settings. [2013-07-11 01:41:17.460][CS.INSTALL][ERROR] CSSetupEngine.testConnectionAction: Install was unable to ping the database. Installation has halted. [2013-07-11 01:41:17.461][CS.INSTALL][ERROR] Worker.run. Install failed. Please check log file. Click Yes to modify your install choices and re-try install. Click No to terminate application.
It looks like DB ping is getting failed.
But I am not sure how to resolve this error.
Please help. I am pasting the content of my bea_omii.ini file that I have used. (Please view as HTML, as formatting is getting lost on this page.)
Do let me know if any other information is required from my end.
bea_omii.ini:
#ContentServer install properties #Thu Apr 17 12:03:27 IST 2008 # Content Server Information # Specify the directory where you want to install Content Server i.e on windows C\:/csinstall on unix /opt/csinstall CSInstallDirectory=/home/oracle/WCS # Path to the Shared Directory i.e on windows C\:/csinstall/Shared on unix /opt/csinstall/Shared CSInstallSharedDirectory=/home/oracle/WCS/Shared # For delivery installation set Development to false Development=true # CSInstallType single/upgrade/cluster default is single only needed for upgrade or cluster #CSInstallType=single # This is to select APPSERVER Note: PORTALSERVER is not supported CSInstallPlatformType=APPSERVER # Set the application/portal server you want to install # Possible options are: wls92 for ( weblogic server), websphere60 (for webshpere), tomcat5 (for tomcat) CSInstallAppServerType=wls92 # Set the path to the server directory ex. For weblogic, on windows CSInstallAppServerPath=C\:\\bea\\wlserver_10.3 # on unix CSInstallAppServerPath=/u01/software/bea/wlserver_10.3 CSInstallAppServerPath=/home/oracle/Oracle/Middleware/wlserver_10.3 # [WEBLOGIC ONLY] Set the path to the weblogic domain i.e. on windows CSInstallWLDomainPath=C\:/bea/user_projects/domains/base_domain # on unix CSInstallWLDomainPath=/u01/software/bea/user_projects/domains/base_domain CSInstallWLDomainPath=/home/oracle/Oracle/Middleware/user_projects/domains/WCSDomain # [WEBLOGIC ONLY] Set the weblogic domain name i.e. base_domain name from path C\:/bea/user_projects/domains/base_domain CSInstallAdminDomainName=WCSDomain # Option for manual deployment (Should always be set to true) CSInstallbManual=true #Manual deployment needs to set the path where installer has to explode the war CSManualDeployPath=/home/oracle/WCS/deployment # Set the context path for your web application for example /cs/ sCgiPath=/cs/ # Set the database type Possible options #CSInstallDatabaseType= [SQL Server, DB2, Oracle10] CSInstallDatabaseType=Oracle10 # Set the data source name CSInstallDBDSN=WCSDataSource # By default it is installed as a primary cluster member. To install as cluster member make CSInstallType=cluster. CSInstallType=single #WEM installation IsWEMInstall=TRUE #hostname where cs is installed CASHostName=localhost # port number of cs installation CASPortNumber=7003 #Server HostName of internally accessible CAS CASHostNameLocal=localhost #Server PortNumber of internally accessible CAS CASPortNumberLocal=7003 #Server HostName where CAS is actually deployed CASHostNameActual=localhost # Select the default logger name (possible values com.fatwire.cs.core.logging.StandardLog, com.fatwire.cs.core.logging.TraditionalLog # com.fatwire.cs.core.logging.StandardTraditionalLog , org.apache.commons.logging.impl.Log4JLogger LoggerName=org.apache.commons.logging.impl.Log4JLogger # Set the host name where the application will be running CSInstallWebServerAddress=localhost # Set the port number where the application will be running CSInstallWebServerPort=7001 # Set this property to true if you are installing Spark CSInstallSpark=false # Sample Sites Information # Set this true if you want to install Avisports sample site. Avisports=true # CS-Direct and CS-Direct Advantage properties. Please don't touch them ContentCentre=true CatalogCentre=true # Set this true if you want to install CS Engage otherwise false MarketingStudio=true # Set this to true if you want to install Commerce Connectors CommerceConnector=true # Set this to true to install Structure and Navigation for FS2 this is only installed if this is development mode FSCore=true # Set this to true to install Engage Extensions for Structure and Navigation. This depends on Development and FSCore FSEngageCore=true # Set this to true to install Store Schema. This depends on Development and FSCore FSStoreSchema=true # Set this to true to install Engage Extensions for Store Schema. This depends on Development, CommereceConnector and FSEngageCore FSEngageStoreSchema=true # Set this to true to install Document Schema. This depends on Development and FSCore FSDocSchema=true # Set this to true to install Sample Visitors. This depends on Development and FSCore FSLocalUser=true # Set this to true to install Pretty URL Package. This depends on Development and FSCore FSPrettyURL=true # Set this to true to install Store Demo Data. This depends on Development and FSStoreSchema FSStoreDemoData=true # Set this to true to install Document Demo Data. This depends on Development and FSDocSchema FSDocDemoData=true # Set this to true to install Engage Store Data. This depends on Development,FSStoreDemoData,FSEngageStoreSchema and FSStoreSchema FSEngageStoreDemoData=true # If you want to install First Site II Site View set it true otherwise false. This depends on Development and FSStoreSchema FSSiteView=true # Set this to true to install Analytics. This depends on Development,FSCore,FSEngageCore,FSStoreSchema,CommerceConnector and CatalogCentre FSAnalytics=true # Set this to true to install Legacy (core) asset types (Article, Linkset). This depends on Development and ContentCentre CCSampleAssets=true # Set this to true to install Burlington Financial asset types. This depends on Development and ContentCentre CCSampleAssetsBF=true # Set this to true to install Engage and Analytics extensions for Burlington Financial. This depends on Development,MarketingStudio and ContentCentre MSSampleAssetsBF=true # Set this to true to install HelloAssetWorld asset types. This depends on Development and ContentCentre CCSampleAssetsHW=true # Set this to true to install GE Lighting asset types. This depends on Development and ContentCentre CatCSampleAssets=true # Set this to true to install Hello World sample site. This depends on Development and ContentCentre CCSampleSiteHW=true # Set this to true to install Burlington Financial sample site. This depends on CCSampleAssets and CCSampleAssetsBF CCSampleSiteBF=true # Set this to true to install Burlington Financial Extensions sample site. MSSampleSiteBF=true # Set this to true to install GE Lighting sample site. MSSampleSiteGE=true # Spark sample site components # Set this to true to install Document Management sample asset types DMSampleAssets=false # Set this to true to install Content Management sample asset types WCMSampleAssets=false # Set this to true to install Base Components SparkSampleSite=false # Set this to true to install Sample Data SparkSampleData=false # Set this to true to install Sample Portlets. Set this true if this is a portal server SparkSamplePortlets=false

Thanks for your reply Yct.
I got the ping issue resolved today, there was an issue in the data source. Finally I was able to complete the installation successfully.
But there is one more issue now. After completing the installation, I am trying to access the URL to get to the WCS login page, but with no success.
Below, I am mentioning few URLs that I tried, and the outcome:
http://localhost:7001/cs/HelloCS , This URL gives me a page with some static content messages like 'Welcome to Oracle WebCenter Sites 11gR1'. Then there are some text lines in blue color. I think this page is working as expected.
http://localhost:7001/cs/login , this URL automatically gets redirected to the URL 'http://localhost:7003/cas/login?service=http%3A%2F%2Flocalhost%3A7001%2Fcs%2Fwem%2Ffatwire%2Fwem%2FWelcome' and I get an error message 'Firefox can't establish a connection to the server at localhost:7003.'
http://localhost:7001/cas/login, this takes me to login page, where when I enter fwadmin@xceladmin credentials, I am taken to JASIG Central Authentication Service page, which is again static, and I can't do anything on this page
http://localhost:7001/cs/Satellite?c=Page&cid=1327351719456&pagename=avisports%2FPage%2FHomeLayout1 , this takes me to the Avisports site, which is functional
http://localhost:7001/cs/Satellite?c=Page&childpagename=FirstSiteII%2FFSIILayout&cid=1124747609916&pagename=FSIIWrapper, this takes me to he FirstSit page, which is again functional
Issue: I am not getting the main login page, where I would get 3 sites(Avisports/FirstsiteII) in the dropdown.
Looks like there is something wrong going on.
Following I am pasting my omii.ini file, if it helps:
#ContentServer install properties
#Thu Apr 17 12:03:27 IST 2008
# Content Server Information
# Specify the directory where you want to install Content Server i.e on windows C\:/csinstall on unix /opt/csinstall
CSInstallDirectory=/home/oracle/WCS
# Path to the Shared Directory i.e on windows C\:/csinstall/Shared on unix /opt/csinstall/Shared
CSInstallSharedDirectory=/home/oracle/WCS/Shared
# For delivery installation set Development to false
Development=true
# CSInstallType single/upgrade/cluster default is single only needed for upgrade or cluster
#CSInstallType=single
# This is to select APPSERVER Note: PORTALSERVER is not supported
CSInstallPlatformType=APPSERVER
# Set the application/portal server you want to install
# Possible options are: wls92 for ( weblogic server), websphere60 (for webshpere), tomcat5 (for tomcat)
CSInstallAppServerType=wls92
# Set the path to the server directory ex. For weblogic, on windows CSInstallAppServerPath=C\:\\bea\\wlserver_10.3
# on unix CSInstallAppServerPath=/u01/software/bea/wlserver_10.3
CSInstallAppServerPath=/home/oracle/Oracle/Middleware/wlserver_10.3
# [WEBLOGIC ONLY] Set the path to the weblogic domain i.e. on windows CSInstallWLDomainPath=C\:/bea/user_projects/domains/base_domain
# on unix CSInstallWLDomainPath=/u01/software/bea/user_projects/domains/base_domain
CSInstallWLDomainPath=/home/oracle/Oracle/Middleware/user_projects/domains/WCSDomain
# [WEBLOGIC ONLY] Set the weblogic domain name i.e. base_domain name from path C\:/bea/user_projects/domains/base_domain
CSInstallAdminDomainName=WCSDomain
# Option for manual deployment (Should always be set to true)
CSInstallbManual=true
#Manual deployment needs to set the path where installer has to explode the war
CSManualDeployPath=/home/oracle/WCS/deployment
# Set the context path for your web application for example /cs/
sCgiPath=/cs/
# Set the database type Possible options
#CSInstallDatabaseType= [SQL Server, DB2, Oracle10]
CSInstallDatabaseType=Oracle10
# Set the data source name
CSInstallDBDSN=WCSDataSource
# By default it is installed as a primary cluster member. To install as cluster member make CSInstallType=cluster.
CSInstallType=single
#WEM installation
IsWEMInstall=TRUE
#hostname where cs is installed
CASHostName=localhost
# port number of cs installation
CASPortNumber=7003
#Server HostName of internally accessible CAS
CASHostNameLocal=localhost
#Server PortNumber of internally accessible CAS
CASPortNumberLocal=7003
#Server HostName where CAS is actually deployed
CASHostNameActual=localhost
# Select the default logger name (possible values com.fatwire.cs.core.logging.StandardLog, com.fatwire.cs.core.logging.TraditionalLog
# com.fatwire.cs.core.logging.StandardTraditionalLog , org.apache.commons.logging.impl.Log4JLogger
LoggerName=org.apache.commons.logging.impl.Log4JLogger
# Set the host name where the application will be running
CSInstallWebServerAddress=localhost
# Set the port number where the application will be running
CSInstallWebServerPort=7001
# Set this property to true if you are installing Spark
CSInstallSpark=false
# Sample Sites Information
# Set this true if you want to install Avisports sample site.
Avisports=true
# CS-Direct and CS-Direct Advantage properties. Please don't touch them
ContentCentre=true
CatalogCentre=true
# Set this true if you want to install CS Engage otherwise false
MarketingStudio=true
# Set this to true if you want to install Commerce Connectors
CommerceConnector=true
# Set this to true to install Structure and Navigation for FS2 this is only installed if this is development mode
FSCore=true
# Set this to true to install Engage Extensions for Structure and Navigation. This depends on Development and FSCore
FSEngageCore=true
# Set this to true to install Store Schema. This depends on Development and FSCore
FSStoreSchema=true
# Set this to true to install Engage Extensions for Store Schema. This depends on Development, CommereceConnector and FSEngageCore
FSEngageStoreSchema=true
# Set this to true to install Document Schema. This depends on Development and FSCore
FSDocSchema=true
# Set this to true to install Sample Visitors. This depends on Development and FSCore
FSLocalUser=true
# Set this to true to install Pretty URL Package. This depends on Development and FSCore
FSPrettyURL=true
# Set this to true to install Store Demo Data. This depends on Development and FSStoreSchema
FSStoreDemoData=true
# Set this to true to install Document Demo Data. This depends on Development and FSDocSchema
FSDocDemoData=true
# Set this to true to install Engage Store Data. This depends on Development,FSStoreDemoData,FSEngageStoreSchema and FSStoreSchema
FSEngageStoreDemoData=true
# If you want to install First Site II Site View set it true otherwise false. This depends on Development and FSStoreSchema
FSSiteView=true
# Set this to true to install Analytics. This depends on Development,FSCore,FSEngageCore,FSStoreSchema,CommerceConnector and CatalogCentre
FSAnalytics=true
# Set this to true to install Legacy (core) asset types (Article, Linkset). This depends on Development and ContentCentre
CCSampleAssets=true
# Set this to true to install Burlington Financial asset types. This depends on Development and ContentCentre
CCSampleAssetsBF=true
# Set this to true to install Engage and Analytics extensions for Burlington Financial. This depends on Development,MarketingStudio and ContentCentre
MSSampleAssetsBF=true
# Set this to true to install HelloAssetWorld asset types. This depends on Development and ContentCentre
CCSampleAssetsHW=true
# Set this to true to install GE Lighting asset types. This depends on Development and ContentCentre
CatCSampleAssets=true
# Set this to true to install Hello World sample site. This depends on Development and ContentCentre
CCSampleSiteHW=true
# Set this to true to install Burlington Financial sample site. This depends on CCSampleAssets and CCSampleAssetsBF
CCSampleSiteBF=true
# Set this to true to install Burlington Financial Extensions sample site.
MSSampleSiteBF=true
# Set this to true to install GE Lighting sample site.
MSSampleSiteGE=true
# Spark sample site components
# Set this to true to install Document Management sample asset types
DMSampleAssets=false
# Set this to true to install Content Management sample asset types
WCMSampleAssets=false
# Set this to true to install Base Components
SparkSampleSite=false
# Set this to true to install Sample Data
SparkSampleData=false
# Set this to true to install Sample Portlets. Set this true if this is a portal server
SparkSamplePortlets=false

Reporting in WCS 6.0.132

I recently upgraded from WCS 5.2 to 6.0. I have a number of Client Count reports set up, which are run weekly to generate PDF graphs of usage on all APs in each building. Since the conversion, all of them fail with the message "Failed to run report". I've tried deleting and re-defining them, but get the same result. Running them manually makes no difference. Has anyone seen anything similar? Is there anything I can do, or is reporting just broken in 6.0? The message is singularly unhelpful
Regards
Max Caines
University of Wolverhampton

Have you used a beta version or earlier pre release version?
You have an issue that is related some how to entries that were in beta codes of WCS.
A few things to try, first make a backup of your db.
Then, go on the CLI, bin folder of WCS and after run:
1.StopWCS
2.dbamin checkschema
3.StartWCS
See if this helps.
I dont want to push you for opening a TAC case and would like to avoid it, but if you are concerned about keeping the same db and not loose any data, we need a TAC case to be opened. That will involve that you upload me your database so we can try to fix this manually.
If you dont care about the DB and you are ok to rebuild it then from the CLI
1. StopWCS
2. dbadmin reinitdb
3. StartWCS
Reconfigure your WCS, the issue will be gone.
If you decide that you can not loose the db and the previous steps did not help, open a TAC SR between now and the next couple of hours and ask for lavramov, I can help you out.

WCS 6.0.132 compatibility

Is this version of WCS compatible with a Controller using 5.2.193? I've checked the released notes and for Controller 5.2.193 it says it needs WCS 5.2.130, but is 6.0.132 WCS also compatible?
Thanks in advance!

Yes 6.0.132.0 is compatible with controller 5.2.193.0

Anyone running WCS 6 on CentOS 5?

I ran into an issue when trying to install and run WCS 6.0.132.0 on a clean install of CentOS 5 (2.6.18-194.3.1.el5.centos.plus)
After successfully installing WCS using the option "-DCHECK_OS=false" I tried to start the WCS service with the startupscript as root, but got the following error:
[root@wcs WCS6.0.132.0]# ./StartWCS
Starting WCS
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.
failed to start WCS on startup Health Monitor
Failed to start WCS. Check hm_launchout.txt for details.
Log files are located under webnms/logs in the WCS install directory.
[root@wcs WCS6.0.132.0]# cat webnms/logs/hm_launchout.txt
JAVA_HOME=./../jre
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.
[root@wcs WCS6.0.132.0]#[root@wcs logs]# cat launchout.txt
Invalid OS version detected, can not start Xvfb.
JAVA_HOME=./../jre
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...
the only error I can interpret is the "can not start Xvfb", but my google foo does not yield any results for this issue, so:
Anyone here successfully running this configuration?
Best regards
-LA
PS: I do realize this is not a Cisco supported OS, but I would like to try it before falling back to RHEL

Editing /etc/redhat-release should allow WCS to start. I run ours on CentOS 5 and I had to make this change.
Just comment out the CentOS line and add the Red Hat line below. You will probably need to be root to do this and
it may require a restart. Also after running updates for CentOS I have notice that the file usually changes back
and WCS does not start again. I keep a copy of the file on the server desktop and copy it over after the updates.
I have not notice any issue with running it on CentOS, just thought I would throw that out there.
Cheers!
Eli
Red Hat Enterprise Linux Server release 5 (Tikanga)
#CentOS release 5.4 (Final)

Custom DB password in WCS 7.0.220.0

Hi there,
we are desperately trying to set a custom password of our WCS database in order to use it for direct SQL queries (Cumbersome over Web surface).
To my knowledge there is a way to reset it however this password would be randomly generated and not available in plain text.
Until version 6 there was a feature to directly set a password via the dbadmin command.
Anyone know a way? Thanks!
Regards,
Patrick

Hi all,
I hope not too many have followed my approach yet as it comprises a problem. That is leaving the dbopts.db
file (that contains the encrypted password for the 'dba' user) in the directory /WCS7.0.230.0/webnms/db/eval_kit/standalone unmodified which will no longer allow to start the database server if the WCS service is re-started due to invalid credentials or mismatch between database user record and the password in dbopts.db file.
You would find similar messages as shown below in the logfile solmsg.out
[root@WCS standalone]$ more solmsg.out
23.07 14:36:52 User 'DBA' was disconnected abnormally, user id 39, machine id WCS.
23.07 14:36:52 User 'DBA' was disconnected abnormally, user id 53, machine id WCS.
23.07 14:36:52 Memory allocation size has fallen below 1483MB. Current size: 1483647331 bytes. Number of allocations: 12465.
23.07 14:36:56 User 'DBA' tried to connect from WCS with an illegal username or password.
23.07 14:38:04 User 'DBA' tried to connect from WCS with an illegal username or password.
23.07 14:46:17 User 'DBA' tried to connect from WCS with an illegal username or password.
23.07 14:49:52 User 'DBA' tried to connect from WCS with an illegal username or password.
23.07 15:03:56 Server shut down by either ALT+F4 or kill command
Mon Jul 23 15:09:36 2012
Version: 04.50.0184
Operating system: Linux 2.6.18 ix86 MT
Solid BoostEngine - v.04.50.0184 (Linux 2.6.18 ix86 MT)
(C) Copyright Solid Information Technology Ltd 1993-2010
Using license file /data/WCS/WCS7.0.220.0/webnms/db/eval_kit/standalone/solid.lic
License for Solid BoostEngine 4.x, Standard Edition
Development license
Serial number: 416000266
     4 processors
     100 concurrent connections
     25 threads
     SmartFlow option
     HotStandBy option
     1 master databases
     5 replica databases
     Accelerator option
     Diskless replica option
Licensed to:
     Cisco Systems
     WCS WNBU
Current working directory changed to /data/WCS/WCS7.0.220.0/webnms/db/eval_kit/standalone
Using configuration file /data/WCS/WCS7.0.220.0/webnms/db/eval_kit/standalone/solid.ini
Starting roll-forward recovery, please wait ...
Recovery of 2242 transactions successfully completed
23.07 15:09:57 Listening of 'TCP/IP localhost 1315' started.
23.07 15:09:58 Solid BoostEngine started at Mon Jul 23 15:09:58 2012
23.07 15:09:58 Database started.
23.07 15:09:58 Memory allocation size has exceeded 1102MB. Current size: 1102911836 bytes. Number of allocations: 738.
23.07 15:09:58 User 'DBA' tried to connect from WCS with an illegal username or password.
23.07 15:14:58 User 'DBA' tried to connect from WCS with an illegal username or password.
23.07 15:19:58 User 'DBA' tried to connect from WCS with an illegal username or password.
23.07 15:24:58 User 'DBA' tried to connect from WCS with an illegal username or password.
23.07 15:29:58 User 'DBA' tried to connect from WCS with an illegal username or password.
23.07 15:34:58 User 'DBA' tried to connect from WCS with an illegal username or password.
In order to avoid that problem please follow the steps below:
Please note, that the first two steps are only necessary if you did already change the 'dba' user password with the SQL statement ''ALTER USER dba IDENTIFIED BY ") and only replacing the dbopts.db file does not resolve the issue of mismatching credentials.
1)
Uninstall the WCS 7.0.220.0 installation
2)
Conduct a fresh installation of WCS 7.0.220.0 (or successor version 7.0.230.0).
Restore from an existing database backup (http://www.cisco.com/en/US/docs/wireless/wcs/7.0/configuration/guide/7_0main.html#wp1077207).
3)
Stop the WCS 7.0.220.0 (or 7.0.230.0) service
Update (2012/07/25, 08:18 UTC):
If the database server cannot be stopped by using the /opt/WCS7.0.30.0/StopWCS script, navigate to the /WCS7.0.230.0/webnms/db/bin directory and connect to the database server with the command "./solcon 'tcp localhost 1315' dba ". Issue the command "shutdown" in order to stop the database service. You will be automatically disconnected from the database server. Stopping the WCS service by using the /opt/WCS7.0.30.0/StopWCS script will now work and you can proceed with the next step.
4)
Conduct a fresh installation of WCS 6.0.202.0.
Start the WCS 6.0.202.0 service.
Run the dbadmin.sh utility and change the database password for the user 'dba' (./dbadmin.sh password ).
This will update both the corresponding user record in the database itself as well as the dbopts.db file.
5)
Stop the WCS 6.0.202.0 service.
Start the WCS 7.0.220.0 (or 7.0.230.0) service.
6)
Run the SQL statement as described in my previous post.
7)
Make a backup of the dbopts.db file of the v7 installation and replace it with the one of the v6 installation.
[root@WCSstandalone]# pwd
/data/WCS/WCS7.0.230.0/webnms/db/eval_kit/standalone
[root@WCS standalone]# cp dbopts.db dbopts.db.backup-v7
[root@WCS standalone]# rm -rf dbopts.db
[root@WCS standalone]# cp /data/WCS/WCS6.0.202.0/webnms/db/eval_kit/standalone/dbopts.db .
8)
Restart (Stop and start) the WCS 7.0.220.0 (or 7.0.230.0) service.
By doing so, the WCS will continue working without any problems and direct database access is possible.
[root@WCS bin]# /opt/WCS7.0.230.0/WCSStatus
Health Monitor is running.
WCS is running.
Database server is running
Apache server is running
[root@WCS bin]# ./solsql -e "select * from SYS_USERS" 'tcp localhost 1315' dba
Solid SQL Editor (teletype) v.04.50.0188
(C) Copyright Solid Information Technology Ltd 1993-2010
Connected to 'tcp localhost 1315'.
       ID NAME               TYPE                    PRIV PASSW           PRIORITY   PRIVATE LOGIN_CATALOG
        1 DBA                USER                       1       NULL         0 WEBNMSDB
1 rows fetched.
SOLID SQL Editor exiting.
Please apologize my delayed update to this post!
HTH
Stephan

Can't Modify WCS Report File Destination

Once I upgraded to WCS 6.0.132.0 I can no longer change the destination file location when I run reports. The reports seem to run on schedule but they end up in the default location of C:\WCSFTP\reports\. I would like to change that to my E: where I have more space to save reports. Before version 6.0.132.0 I was able to do this.

Oops, I sent the wrong screenshot.
Go to administration -> settings and you can change the folder there.
You can not customize the file name but surely you can change the location to save the files.
See file attached.

Wcs not starting up after upgrade

I recently upgraded the cisco wcs software from 5.0.56.2 to 5.2.148 in order to eventually upgrade it to the latest version 7.0, after installing the software it fails to start WCS, i rebooted the server already and restarted the services i ran dbadmin checkschema and it completed fine but when it just hangs when starting wcs
here is what i get
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.
Starting WCS Server
Port 69 is in use. DatagramSocket binding gave exception java.net.BindException: Address already in use: Cannot bind
Port 69 needed by the server is being used by some other application.
Please free the port and restart the Server.
Failed to start WCS server. Check launchout.txt for details.
Log files are located under webnms\logs in the WCS install directory.
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...
anyone have any idea whats going on

just a thought i see that it doesn't actually remove verison 5.0.56.2 when i installed version 5.2.148 and im wondering if this isn't causing some issues with WCS not starting
here is my wcs status window
Health Monitor is running with an error.
WCS is stopped.
Database server is running
Apache server is running
but if i start wcs from programs it tells me health monitor is already running.
i created a backup of wcs using the backup feature and saved it so im not sure if i should just uninstall and reinstall at this point and see what happens or not

Upgrading WCS from 4.2.62.11 to ?

Hello All,
I recently purchased 6 1142 AP's and added them to my controller, well since these are not LWAP but instead CAPWAP AP's they were not supported by my WLC with code version 4.2 (not the end of the world) so I upgraded the WLC to code 6.0.182 but had to sacrifice managing it from my WCS.
Now I would like to upgrade my WCS to support managing this WLC again and potentially upgrading my remaining WLC's, the thing is I would like to upgrade to the latest WCS version 6.0.132 but need some input as to the ease of upgading, and/or any potential problems that might surface, or if anyone is currently experiencing any issues using this WCS code. Will 6.0 be the best bet or is it sufficient to step up to 5.2? Are you satisfied with this upgrade? How many WLC and AP's are you managing? Is there anything I need to consider that isnt written in the Cisco documentation?
Any input would be greatly appreciated.

You do need WCS 6.0.132.0 to manage your 6.0.182.0 WLC.
To upgrade, its easy, just make a backup of your db, run the installer of 6.0.132.0 and you will be all set. There are not really issues in the upgrade and this should go smooth.
WCS 5.2 will not support your WLC running 6.0
WCS 6.0.132.0 release note:
http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCS_RN6_0.html

WCS 7.0.172.0 is stopped.

I rebooted the WCS server yesterday and now it is not working anymore.
Here is WCS Status :
Health Monitor is running with an error.
WCS is stopped.
Database server is running
Apache server is running
Logs from hm_launchout.txt
Starting Health Monitor as a primary
Checking for Port 8082 availability... OK
Key entry exists; Update Apache config from Keystore
Configuring Apache server for key
Starting Health Montior Web Server...
Health Monitor Web Server Started.
Starting Health Monitor Server...
Health Monitor Server Started.
Starting WCS Server
Could not create the Java virtual machine.
Unrecognized VM option ''
Failed to start WCS server. Check launchout.txt for details.
Log files are located under webnms\logs in the WCS install directory.
launchout.txt - it is empty
How can I proceed Now.
Regards

Here are collections of the Cisco WCS fails to start up.
Case 1: Apache server is not running.
Case 2: If the WCS were installed as a service, try to rebooted the machine.
Case 3: Check if the scripts are manually run from the bin directory. You must not manually run scripts from the bin directory. You must use the links from the Windows WCS programs menu or the scripts from Linux <Install Dir> (that is, /usr/local/bin/WCS22/StartWCSServer).
Case 4: Make sure the following ports are available to WCS.
*Checking for Port 1299 availability... OK
*Checking for Port 80 availability... OK
*Checking for Port 443 availability... OK
*Checking for Port 8009 availability... OK
*Checking for Port 8456 availability... OK
*Checking for Port 8457 availability... OK
*Checking for Port 8005 availability... OK
*Checking for UDP Port 69 availability... OK
*Checking for Port 21 availability... OK
Case 5: WCS does not start if the database is corrupt. If you reinitialize or restore the database, it fixes the issue. Navigate to the WCS installation directory and issue the dbadmin.bat reinitdb command from the command prompt to reinitialize the database.
case 6: Collect the log files from the <WCS Installation Dir>\webnms\logs. These log files can be used to identify the root cause of the issue.
Case 7: Check if the Windows SNMP trap service is active on the server. Disable the service because it uses Port 162 that is required by WCS. For more information on list of ports used by WCS, refer to the

WCS stops working about once a week

When we attempt to reach the WCS we receive this message occassionally,
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 143.120.12.30 Port 443
The quick fix has been to reboot the server. This is starting to happen at least once a week now, and seems to be getting worse. No changes were made to the server. This problem just started happening all of the sudden. Help!
Health Monitor is running.
WCS is stopped.
Database server is running
Apache server is running
WCS Version 7.0.220.0

Kristen,
A known issue with WCS - 7.0.220.0 is because of a crash due to native memory which has been identified as the following bug
CSCtu49966 - WCS crashes due to native memory error in 7.0.220.0
The workaround for this issue is to enable Escape Analysis in the JVM. How to do this is
outlined in the WCS 7.0.220.0 Release Notes at http://tools.cisco.com/squish/3202f .
Essentially, Stop WCS, edit the startServer.bat/startServer.sh file (Windows/Linux)
appending "-XX:-DoEscapeAnalysis" (no quotes) to the set JAVA_OPTS line, then restart WCS.
Thanks,
Ram.

WCS Enterprise Deployment

Dear All,
i have some Questions about Deploying WCS Enterprise in
a Global Environment.
- How is the Licensing Done, as usual with the Hostname(s) and splitted AP Count per Host til the amount of AP Licenses is full?
- There is no Navigator License purchased, what is the Best Practice to Deploy the WCS; one per Theatre with one dedicated HA Backup Server? This means 2 Machines in every Theatre?
- in an WCS HA Environment, how is the Database Replication done?
- Is there a Scenario supported with one Central WCS and Satellite WCS per Theatre? Again, Navigator is not an Option...
Thanks in Advance, Michael

My 2 cents :
The HA WCS can serve as "secondary" for many other WCS servers. How it works is that the active/primary WCS servers send constantly their database to the HA WCS. Once the HA WCS detects that one of the primary is down, it loads that database and goes active. So the HA WCS can contain several databases.
Nicolas

WCS 6.0.132.0 Database

Similar Messages

Maybe you are looking for