CommandBox Service Manager startup looping

Communities CommandBox CLI
1

I suspect that something changed in Microsoft® Windows® in the past few months that affected my running legacy application. Everything worked fine last year, but now when I attempt to start the service by clicking stuff in SERVICES.MSC or with box server service start there are processes starting and stopping in a loop. It’s hard to describe. I recorded the behavior here:

Is this a known problem? I did not find anything when searching the Ortus Community. Is there a way to get the CommandBox Service Manager logs to figure out why its unhappy?

Thank you.

2

The first thing I would try is starting it from the command line and not as a service. You can also follow some of the steps here for debugging.

Once its working standalone then try running as a service.

3

I should have mentioned that box server start works just fine. That is how I’ve been running the legacy application since the Microsoft® Windows® Service™ broke a couple months ago. The problem is only with the Microsoft® Windows® Service™ and CommandBox Service Manager.

I already tried removing the service and recreating it. That did not present any errors, but also didn’t address the problem shown in the video.

I just need to get some output from the service launcher to understand why it is unsatisfied.

4

Next thing I would check is if the service is running as the same user account you are testing it with.

5

Turn on service logs. This will capture the raw console output of the server start command which is running behind the scenes when the service attempts to start. It will show whatever the error is.

See the following:

  • standardOutPath - Path to a file to write the “out” logs. Similar to the server log but also includes the raw output of the server start command itself. Useful for debugging failed starts. (Windows only)

  • errorOutPath - Path to a file to write the “error” logs. Similar to the server log but also includes the raw output of the server start command itself. Useful for debugging failed starts. Can be set to the same path as the “out” log. (Windows only)

here:

6

@bdw429s @MikeR Thank you for the assistance.

I turned on both logs and saw that the error was due to permissions loading JAR files:

C:\Tools\CommandBox\engine\cfml\cli\lucee-server\bundles\org.lucee.commons-email-all-1.6.0.jar (Access is denied)

So, apparently when I updated to the latest CommandBox a while ago, I did it in a way that made the legacy application service user unable to read them. I reapplied the desired permissions from the top of the tree and now everything works fine.

Thank you.

1 Like
7

Great, glad you got it figured out!