LASE NOT STARTING

Are you starting lase as root? What version of Lawson are you on? I seem to recall having problems like this, but it was a while ago. I think the problem may have been related to file permissions. Sorry, it rings a bell, but only faintly. What error messages are you getting in the logs?

We recently (within the past 2 months) started having this issue as well but we are a Unix shop. Our automated scripts jut stopped working in both our Dev and production environments and we found that it was failing on the startlase step. If I issue the startlase command manually and then start the other services it is fine but we have not been able to find what changed yet. The main suggestion I received so far is that somehow the response time changed because disk space is filling up but because it happened in both environments that doesn't make sense to me. Has anyone else found this/figured out why it is happening?

Thanks for the response. As of now, when I issue a startlase the system will try to start it but will never, therefore a startlaw will not work at all. This is what comes back affter issueing a startlaw lase: security environment 9.0.0.8.174 2009-08-07 04:00:00 (200910) started. Waiting on security connection... Unable to start lase, exiting... at /lawtest1/gen/bin/startlaw line 80

There's a time out setting you need to adjust, but with the KB down I can't remember what it is. These are the values I've got in various config files, if yours are shorter, try increasing them. lajs.cfg:EXECTIMEOUT 180 latm.cfgPENTIMEOUT 240 latm.cfg:LOOPTIMEOUT 13 Other than that, I'm afraid its a LGC ticket. Sorry, just can not remember this one.

Thanks Eric, Let me look

Have you checked to make sure that Tivoli is running? Jeff

Jeff, Yes Tivoli is running, actually I just stopped and started just to make sure

I've experienced this a few times in the past. I know, it's really annoying and may sound 'dumb', but you need to make sure that the permissions of all of the lase*.log files are open enough that the root or lawson user who is running startlase or startlaw has permission to write and read to them. Yes there is a KB article on this.  Try that and let us know if that works, Roger

GSC was leading toward BouncyCastle but we replaced those file and still no go. They are know leading toward the patches changing the CA certifications but I am not sure how that would have effected it

Roger, I will do that now

OK, I did a chmod 777 on lase*.log, I them ran startlase ..... It sill dies. Not sure if there are any other logs but I do not think so.

Try your ssosmoketest? It could be that TDS is timing out?

On ALL of the lase logs... lase.log, lase_server_0_0. log, etc. all of them. Also the lase.cfg 

Are you able to login to the ldap with a directory browser, i.e. JxPlorer? Bart

Eric ,will smoketests run without the envrionment being up?

Roger ... I will change all the logs now ...

Roger, I think I changed everything, but still no dice, same error

I will check JEXPLORER now

Yes, smoketests can run with the enviornment down. It only requires that TDS be up.

I can access LDAP via JEXPLORER

I can access LDAP with JEXPLORER ...

Eric, I will try to run the sometests, any one in particular

If it was AIX patch that you applied, also check your java version and location too. Were you able to confirm the bouncycastle tests too? WHo is actually running the startlaw/startlase?  Is it root or lawson? Can you try to use root?

Do you get any errors in ladb.log? Check that you can login into the RDBMS for GEN and LOGIN using the usernames/passwords stored in the CAPS (e.g. ORACLE) files. If the DBs are on a diff server make sure ports are open :)=