Too many files open. passman.cnf error..unable to login to admin IS console

Varalakshmi_Nanduru · September 11, 2015, 11:43am

Hi,

I am unable to login to IS .getting below error
EDT [ISS.0014.0054C] Error occurred while initializing server: com.wm.passman.PasswordManagerException: java.io.FileNotFoundException: /opt/webMethods-dev1/wm95/IntegrationServer/config/passman.cnf (Too many open files)

Holger_von_Thomsen · September 11, 2015, 11:54am

Hi Varalakshmi,

please check with “uname -a” how many file handler are allowed.

You can try to increase this with “uname -n ”.

Restart IS afterwards.

Regards,
Holger

Mahesh_K_Sreenivas · September 11, 2015, 12:19pm

This should do it:

ulimit -n 65535

Varalakshmi_Nanduru · September 11, 2015, 12:35pm

I am getting below error in logs.
Iam unable to login IS console using Administrator

Unable to initialize JAAS login context. JASS Configuration file in use:config/is_jaas.cnf. Error msg: No Login modules configured for IS_Transport

Mahesh_K_Sreenivas · September 11, 2015, 12:54pm

Hey There,

Do you see the directory /opt/WmData/tmp, check the access permission please?

MR_as173d · September 13, 2015, 8:50pm

Nanduru – Did you fix this issue, if yes what steps did you follow to fix, if not what error message you are getting ?

Thanks,

Sanket_Pandey3 · June 29, 2019, 3:01am

Hi All,

We are also facing the similar issue in one of our environment which was working all these days

Any help to troubleshoot this would be much appreciated, the error snippet from server log can be found below:

2019-06-28 12:03:35 CDT [ISS.0053.0002C] Access denied for user Administrator on port 80 → ‘WmRoot/index.dsp’ from 10.147.212.177.
2019-06-28 12:03:44 CDT [ISS.0012.0014C] Unable to initialize JAAS login context. JAAS configuration file in use: config\is_jaas.cnf. Error message: No LoginModules configured for IS_Transport. Stack trace:
javax.security.auth.login.LoginException: No LoginModules configured for IS_Transport

Regards,

Sanket

Mahesh_K_Sreenivas · June 30, 2019, 7:33am

What is your wM version? And when did you encounter this issue initially?

Can you verify the below property from other IS nodes and see if it is same in the affected node, the location is

SAG/profiles/instance_name/configuration/config.ini

com.softwareag.platform.jaas.enabled=false

Also, verify if this file is changed is_jaas.cnf due to some reason present in \IntegrationServer\instances\default\config