Webserver Hangs or will not start
Originally Published: 2010-01-26
Article Number
Applies To
Issue
In versions prior to 4.0, there is a limit to the number of devices that the webserver can load. The exact number can vary, but it was reported at 158. We are reaching the point where the number of devices we support goes over that limit, resulting in the webserver service hanging. There is a temporary workaround, where you disable unused devices to get under the limit:
Resolution
From the GUI:
System Configuration -> Devices -> Manage Device Types, Uncheck the "Enabled" box for unused device types and Apply.
From the filesystem (You may need to do this on each LC)
E:\nic\<version>\<host>\etc\devices\<devicename>\<devicename>.ini
If the .ini file contains:
Enabled=true
change it to
Enabled=false
otherwise add
Enabled=false
There is a fix for 3.7.0 SP 1 only. It can be obtained from technical support.
EBF's for previous versions will not be created.
Related Articles
RSA SecurID Access identity router will not start after reboot on Microsoft Hyper-V Number of Views RSA Via Lifecycle and Governance/Aveksa server will not start after environment customization Number of Views Adding trusted realm in RSA Authentication Manager 8.1 SP1 fails with an error: "The trust is not unique. Either the trust… Number of Views AM8.1-Web tier Bootstrap service will not start after re-install Number of Views Removing a drive mounted as CD-ROM on the RSA AM virtual machine via vCenter console Number of Views
Trending Articles
Unable to login to RSA Authentication Manager Security Console as super admin Authentication Manager Administration Server with operations console service Fails to Start with "No config.xml Was Found"… Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update RSA Authentication Manager Upgrade Process Authentication Manager How to Retrieve the LDAPS Certificate and Configure an External Identity Source to Use LDAPS
Don't see what you're looking for?
