Greetings all. Checking to see if there's a quick...
# lucee
m
Greetings all. Checking to see if there's a quick fix for this... have attempted to run both
lucee/lucee:5.4.3.2-light-nginx-tomcat9.0-jdk8-temurin-focal
and
5.3.12.1-light-nginx-tomcat9.0-jdk8-temurin-focal
including both admin 1.0.0.3 or 1.0.0.5 lex and am getting this after attempting to log in: "requested action doesn't exist"
does not matter what I click, it returns me to the login screen, and after logging in this is all i get
the app we have in this container works fine and passes all tests, but the admin appears hopelessly broken. All I could find is: https://luceeserver.atlassian.net/jira/software/c/projects/LDEV/issues/?filter=doneissues
b
@Marc Funaro Have you searched the bug tracker for this error? 😉
m
i've searched everywhere i know to, hence the above.
b
Oh, look! A ticket perfectly matching that error withi details and a fix version! 😁 https://luceeserver.atlassian.net/browse/LDEV-4675
Took me about half a second to find that ☝️
I literally just pasted the error from your post into the JIRA search
It was the first result
m
okay, #1 stop with the condescension - i literally linked to that exact page.
#2 it's marked as deployed. But it is not "deployed" for me, since, you know, I'm still having the problem.
b
So, if you know about the ticket, what exactly is the question?
Deployed just means released in a version. It's not necessarily a final version
The details on the ticket say it's in version 5.4.3.4
m
i've tried all versions it's supposedly deployed into. Yes, i tried that one. still broken.
Even with latest admin lex.
tried 5.4.3.4-SNAPSHOT as well.
b
Interesting-- comments on the ticket indicate it worked for others. Maybe Zac has some ideas.
FWIW, the actual code for the admin is in Lucee proper, not the extension
m
okay, so THAT makes little sense to me. what is the LEX for, then?
b
Version 1.0.0.5 of the admin extension is from 4 months ago-- long before this bug and fix
The lex just adds a CF mapping that makes the admin visible
It's unexpected yes, but that's how it works
m
that's kinda absurd.
b
So updating the admin lex will basically never change the actual admin code
My guess is the Lucee core needed access to parts of the admin, but that's just a guess
m
so it's likely that the lex version won't matter either way. at least that's one less thing to f#$K around with.
b
Yep, I'd ignore that
Maybe try 5.4.3 on a fresh server in case the upgrade didn't work?
m
this is a docker container. the serverr is always fresh. 😉
✅ 1
minimum i can do is 5.4.3.2, as this has the security update that started this whole thing. This should have been a 2 minute job that's now consumed over an hour.
😞 1
i can also do these... 5.3.12.1 5.3.9.173 5.3.8.237 5.3.7.59 But 5.3.12.1 didn't work either.
b
yep, I'm familiar with it
m
our apps work, just not the admin. may sacrifice admin in favor of security for now, but would be nice to know WTF is going on with it.
b
If it's any help, I have a 5.4.2.17 server I just updated for a client yesterday and the admin seems to work just fine
have you tried clearing any admin cookies?
m
yes. cookies, browser cache, etc.
👍 1
b
Can you directly visit any pages inside the admin like
/lucee/admin/server.cfm?action=resources.mappings
m
gotta switch gears, but may start over later just to make sure I am not losing my marbles.
none of the pages work (as i described in my OP)
b
Ok. And sorry the way I came across at first. I thought you were saying you couldn't find any info on the error (which has come up several times in Slack recently) and I failed at being a bit funny 🙂
m
no worries. I know we all have to deal with people that show up and say "this doesn't work, what's wrong?" without any other details or homework done. I'm just not one of 'em LOL
👍 1
b
I'm out of ideas for (and since it seems to be working for me ATM)
m
i'll post back if i figure it out. i wish the ticket showed what/how it was "fixed" - that's probably out there somewhere in a commit, no time to find it RN
b
Yeah, no linked commits that I can see
d
So I think this is only fixed in the 5.4.3.3+ snapshot. The problem appears to be related to Lucee's template caching strategy and the way that the admin pages get compiled. I think you can either turn off template temporarily turn of caching to fix it (which I haven't tested), but I know usually restarting the Lucee servlet (i.e. Tomcat) fixes it. If it doesn't restart again. It should then be good for as long as the servlet is running.
m
i have tried starting lucee/tomcat inside the runnning container, it's still completely broken. disappointing.