2022-08-28 08:14:34 UTC - Alessandro Parrino: Good morning, I have an OpenWhisk 
installed in Kubernetes, and I was trying to use the alarms package (tag 
2.3.0). Unfortunately the trigger feed creation fails, I tried to check the 
logs but I can't figure out the problem.

This is the output :
```$ wsk trigger create periodic --feed /whisk.system/alarms/alarm -p cron '* * 
* * * *' -i
ok: invoked /whisk.system/alarms/alarm, but the request has not yet finished, 
with id 1952302661204df392302661206df3a4
ok: invoked /whisk.system/alarms/alarm, but the request has not yet finished, 
with id 13db0d81866b43f29b0d81866bc3f2c2
ok: deleted trigger periodic```
Once the `wsk trigger create` command is launched the CLI freezes until the 
trigger is automatically deleted, not allowing me to create the rule to connect 
it to the function.

Activation:
```$ wsk activation get 13db0d81866b43f29b0d81866bc3f2c2 -i
ok: got activation 13db0d81866b43f29b0d81866bc3f2c2
{
    "namespace": "whisk.system",
    "name": "alarm",
    "version": "0.0.1",
    "subject": "whisk.system",
    "activationId": "13db0d81866b43f29b0d81866bc3f2c2",
    "start": 1661638981538,
    "end": 1661639041678,
    "duration": 60140,
    "statusCode": 2,
    "response": {
        "status": "action developer error",
        "statusCode": 0,
        "success": false,
        "result": {
            "error": "The action exceeded its time limits of 60000 
milliseconds."
        }
    },
    "logs": [
        "2022-08-27T22:24:01.693526796Z stdout: alarm: Error invoking whisk 
action: 202 {",
        "2022-08-27T22:24:01.693594328Z stdout:   code: 
'igPMMGrGNTruq2me3h31Lf45Gt4KRooe',",
        "2022-08-27T22:24:01.693606409Z stdout:   error: 'Response not yet 
ready.'",
        "2022-08-27T22:24:01.693615741Z stdout: }",
        "2022-08-27T22:24:01.680535872Z stderr: The action did not initialize 
or run as expected. Log data might be missing."
    ],
    "annotations": [
        {
            "key": "path",
            "value": "whisk.system/alarms/alarm"
        },
        {
            "key": "waitTime",
            "value": 2170
        },
        {
            "key": "kind",
            "value": "nodejs:14"
        },
        {
            "key": "timeout",
            "value": true
        },
        {
            "key": "limits",
            "value": {
                "concurrency": 1,
                "logs": 10,
                "memory": 256,
                "timeout": 60000
            }
        },
        {
            "key": "initTime",
            "value": 80
        }
    ],
    "publish": false
}```
Logs of action pods created:
```$ kubectl logs -n openwhisk wskowdev-invoker-01-17-whisksystem-alarm -f
alarm: Error invoking whisk action: 202 {
  code: 'Sm1ZDhHo7CL3eY9lmcqBzSCP12hK1gqr',
  error: 'Response not yet ready.'
}
XXX_THE_END_OF_A_WHISK_ACTIVATION_XXX
XXX_THE_END_OF_A_WHISK_ACTIVATION_XXX```
```$ kubectl logs -n openwhisk 
wskowdev-invoker-01-18-whisksystem-alarmwebaction -f
trigger will be assigned to worker worker0```
Logs of Alarm provider:
```$ kubectl logs -n openwhisk owdev-alarmprovider-5b7dcf569d-d8xb9
[2022-08-27T22:00:34.268Z] [INFO] [??] [alarmsTrigger] [createDatabase] 
creating the trigger database
[2022-08-27T22:00:34.282Z] [INFO] [??] [alarmsTrigger] [server.listen] Express 
server listening on port 8080
[2022-08-27T22:00:34.372Z] [INFO] [??] [alarmsTrigger] [createDatabase] created 
trigger database: almalarmservice
[2022-08-27T22:00:34.443Z] [INFO] [??] [alarmsTrigger] [initAllTriggers] 
resetting system from last state```

https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1661674474538859?thread_ts=1661674474.538859&cid=C3TPCAQG1
----

Reply via email to