No, this is very strange. First please make a firmware update (with preselected option load from server) to make sure, that the latest version is installed. In the very first release of V10 the behaviour of consecutive commands was a little different. However, even with that firmware it would not explain the log entrys. It seems that the curl command is going crazy.
When a command comes in and the Light-Manager is busy, the HTTP GET will wait in the queue until the Light-Manager is available again. In the first firmware the HTTP GET was responded immediately even when busy, but the command was discarded. That's not nice, therefore it was changed to the previous method. However, both variants don't explain why the curl command is sent over and over again.
You can try it within the browser, just copy the GET into the adddress field and press return:
Then press F5 to trigger the command several times. You will see that it takes 1-2 seconds until the command is processed and the next command accepted. There are only as many entries in the log as the browser has triggered the command succesfully.