- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-18-2024 11:33 AM
I cannot get this lab to validate. The error is below when I try to run the command that I copied and pasted directly from the lab material. I am using http://198.51.7.33:8080/ticket-monster but is says it doesn't work. I passed the rest of the course and completed the quiz but I'm not getting verification that I passed the course and I think it's this one thing.
If anyone has some advice, please help.
Thank you!
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-19-2024 07:39 PM
@chrisj2 Please raise a case with Now Learning support team. Only they will be able to help you in this case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-06-2024 02:08 PM
also the same issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-07-2024 12:18 AM
There is no hints, which data to use for debugging this task. Is it : http://198.51.7.33:5432/ticket-monster ? also should we provide Directory and host name?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-27-2025 01:45 AM
I'm facing the same issue, the last step cannot be finished.
I analyzed the situation. The find command we are asked to issue will fail, because the temp directory we are using is a symlink. The find command does not by default follow symlinks. The failure can be remediated by using the "find -L" option. This will return the correct file name for the config file. But changing the command will in the end cause the lab validation to fail.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-27-2025 02:08 AM
After trying to reproduce, the find command suddenly works, even without the -L option. Don't know what happened.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-11-2025 06:14 AM
Here is the solution:
Configure Debug Mode as follows:
Entry point for JBoss WildFly
- Select Entry Point Type: HTTP(S) Endpoint
- URL: http://192.168.7.31:8080/ticket-monster
Entry point for Identification for JBoss WildFly Module
- Select Entry Point Type: JBoss WildFly Module Entry Point
- Directory: /opt/wildfly/standalone/tmp/vfs
- Port or Host: <empty>
- Name: ticket-monster