"shutdown on Windows not supported"

[neunhoef]

Investigation needed: At some stage I got this message on shutdown. I could not easily find out where it was coming from. The servers seem to have been shut down, I do not know whether soft or hard.

[ewoutp]

Is there any more context, logs, anything?

[neunhoef]

I need to investigate to find out.

[kishorel]

@neunhoef, Found any solution to this?

I have started my three node cluster on linux using arangodb utility and one of the server went down due to maintenance, so all the three process (agent,coordniator and dbserver) seem to be stopped. I had to remove everything and re configure the cluster.It is really hampering.

i could see the below processes when server went down.

root      1320  1253  0 11:44 ?        00:00:00 /usr/sbin/arangod --uid arangodb --gid arangodb --log.foreground-tty false --pid-file /var/run/arangodb/arangod.pid --temp.path /var/tmp/arangod --supervisor

root      1321  1320  0 11:44 ?        00:00:00 /usr/sbin/arangod --uid arangodb --gid arangodb --log.foreground-tty false --pid-file /var/run/arangodb/arangod.pid --temp.path /var/tmp/arangod --supervisor

arangodb  1322  1321 11 11:44 ?        00:00:00 /usr/sbin/arangod --uid arangodb --gid arangodb --log.foreground-tty false --pid-file /var/run/arangodb/arangod.pid --temp.path /var/tmp/arangod --supervisor

Please help.We are planning to move on to production.

Thanks and Regards, Kishore.

[kishorel]

I think i should create a new issue. Creating one

[sleto-it]

@neunhoef Max, I always get confusing messages when trying to shutdown the cluster on windows

To reproduce: start a cluster using the starter, then ctr+c to stop it:

2017/11/01 10:16:02 Shutting down services...
2017/11/01 10:16:02 Failed to terminate coordinator: not supported by windows
2017/11/01 10:16:04 coordinator has terminated
2017/11/01 10:16:04 Failed to terminate dbserver: not supported by windows
2017/11/01 10:16:05 agent has terminated
2017/11/01 10:16:09 dbserver has terminated
2017/11/01 10:16:12 Failed to terminate agent: invalid argument

The shutdown is successful - just the above confusing messages are printed

Thanks,

[neunhoef]

I have to investigate this, I do not know by heart what the actual limitations on Windows are round this.

[OmarAyo]

In addition to what Santo said, please also note that for the shutdown to be successful you have to press CTRL + C several times, as one seems not to be enough.

Is this expected?

[Simran-B]

Pressing Ctrl+C once seems to start the shutdown sequence:

Received signal: interrupt
2018/06/19 19:57:45 Shutting down services...
2018/06/19 19:57:45 Failed to terminate coordinator: not supported by windows
2018/06/19 19:57:47 agent has terminated
2018/06/19 19:57:50 coordinator has terminated
2018/06/19 19:57:50 Failed to terminate dbserver: not supported by windows
2018/06/19 19:57:52 dbserver has terminated
2018/06/19 19:57:55 Failed to terminate agent: invalid argument

But then it hangs there. You have to press Ctrl+C again at that point to actually terminate it:

Received signal: interrupt

C:\Demo>

Pressing Ctrl+C more often shouldn't be necessary, unless you want to fake an unexpected shutdown I guess? Although that might just be the arangodb executable that gets killed, not the server process.

[sleto-it]

reporting status with more recent version, 3.4.5, using arangodb stop on windows:

the command hangs, and the arangodb log prints

2019-05-21T05:24:56-07:00 |INFO| Shutting down services... component=arangodb
2019-05-21T05:24:56-07:00 |WARN| Failed to terminate coordinator component=arangodb error="not supported by windows"

and the coordinator, agent and dbserver are still up