nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

LSCS REST call returns file not found

Rohan_t1

Hi All,

REST calls were working fine for us until today morning. The query which used to work fine earlier returns 404 error as below:

I have verified and looks like deployment is successful. I cannot see anything in lscs.log. I checked the status and lscs is up and running. Nothing seems to be odd in Weblogic logs as well.

IDOL is restarted but still the same issue. Nothing in idol specific logs as well.

Has anyone seen this error before? Any pointers?

Error 404: SRVE0190E: File not found: /cae45c38f81cf24cdba17cfb615e2e59/content/html/abc.html

TS:6.7.2 SP1 with LSCS
OD: 7.1

Find more posts tagged with

Comments

Crsb

did you check the LSCS file system and verified that this file $LSCSHOME.../cae45c38f81cf24cdba17cfb615e2e59/content/html/abc.html actually exists?

Rohan_t1

did you check the LSCS file system and verified that this file $LSCSHOME.../cae45c38f81cf24cdba17cfb615e2e59/content/html/abc.html actually exists?

Yes, the file exists in the LSCS filesystem. Which is what makes it very strange.
Further to this we also tried clearing the projects and redeploy the content. But we still see the same error.

Crsb

is this the only file that is coming back as 404 or every lscs query returns 404?
check if $LSCSHOME/.../webapps/lscs/WEB-INF/classes/lscs-conf.properties was changed and what the content root path is set to: #
content.root=/prod/LSCSRT-Store

Rohan_t1

Thanks for your reply. Sorry i should have mentioned it earlier, the query returns 404 for all the files in all the projects. Nothing was changed in lscs-conf.properties from quite sometime.content.root points to correct location. We are going to open a support case for this. Thankfully it is one of lower environment for us so we can play around a bit but this is something we haven't seen before and in a way stuck.

Rick Poulin

Did permissions change on the content root? Anything of use in your web server logs?

rohit34582

Is LSCS up?

Can you hit:

http://server-name:8080/lscs/v1/admin/status

Check the lscs.log...

Check the DB... >> There is a table for the projects...

These should help you debug...

Rohan_t1

Did permissions change on the content root? Anything of use in your web server logs?

Permissions didn't change on the content root. I compared them to the working instance and they look the same. The logs do not have anything conclusive. We have opened the support case.

Rohan_t1

Ok, so it turned out that someone messed up with the WEB-INF/ibm-web-ext.xmi which had incorrect entry. Corrected that and it works fine now.

Closing the thread.