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; } } }

6.7.1: 404 after running make_toolkit.ipl

Bill Klish

TeamSite 6.7.1
Red Hat Enterprise Linux

When I run make_toolkit.ipl with the defaults, it says Build Successful at the end. If I try to refresh my web browser, or click a new link, I get a 404 error. If I immediately refresh or go back and click a link, it works. Is there some sort of time delay that we have to wait for before the UI will respond again?

Find more posts tagged with

Comments

Migrateduser

The make_toolkit.ipl will stop and start the application server so this will take a couple of minutes before the application server can render the requested pages.

Bill Klish

I am thinking that it shouldn't return from the process until the server has really finished its startup and can accept connections.

nipper

I am thinking that it shouldn't return from the process until the server has really finished its startup and can accept connections.

I think this has been the behavior for a while. Same with iwreset -a

Migrateduser

The make_toolkit.ipl also invokes the iwreset command. I think when the java servlet engine is started it spawns a separate process or thread that initializes the applications, but the Main function that start all other process does not wait still the server can accept requests. I think this is how Tomcat application server works.

Adam Stoller

I am thinking that it shouldn't return from the process until the server has really finished its startup and can accept connections.

This is an old problem (as nipper stated - it's the same with iwreset -ui / iwreset -a) - the commands invoke other commands that run in the background and the initial script doesn't (can't?) wait for them, so it returns immediately even though the background processes haven't (usually) completed.

If the background processes touch a file or log a certain entry somewhere when they're completed - it shouldn't be too difficult to make the calling program poll (loop/sleep) until it sees what its looking for - or has waited some maximum (reasonable) threshold - before returning... However, I've never spent the time to try to figure this out.