use ngx.timer.at function in init_worker_by_lua_file seems does not work

seuzyx · 2017-11-06T14:50:53+00:00

Resolved the issue. The value in session_info.team_id contained an entire response body due to a bug, causing the headers to be to big. ...

use ngx.timer.at function in init_worker_by_lua_file seems does not work

seuzyx

HI all,

I want to use ngx.timer.at module to start another thread besides the "main" thread for lua worker process. From the documentation, it turned out the ngx.timer.at module make this pretty easy to achieve. However, when I have this simple code, it seems I did not really run in the backend. I tried log to log file when it starts, but the log information did not appear.

local function _hello(premature)
    ngx.log(ngx.ERR, "Hello world")
    if premature then
        return
    end

end
ngx.timer.at(0, _hello)

"Hello world" did not appear in the log file and I have no idea the new thread was ever been created successfully.

Any ideas?

Thanks

zchao1995

Hi!

I think you should always check the result by calling ngx.timer.at i.e. the flag and the error string.

seuzyx

Hi Tokers,

Thanks for the reply. Although this did not solve my issue, but gives me another glance and found out the problem reside in another issue.

init_worker_by_lua_file error: .../.lua: API disabled in the current context

stack traceback:

(Strangely this error log is not in the log file I configured, and hence I did not really found the problem)

On Monday, November 6, 2017 at 4:54:51 PM UTC+8, tokers wrote:

Hi!

I think you should always check the result by calling ngx.timer.at i.e. the flag and the error string.

zchao1995

Hi!

You can found the corresponding API by this traceback information, and it cannot be used at the init_worker phase.

agentzh

Hello!

On Mon, Nov 6, 2017 at 1:26 AM, Yongxin Zhang wrote:
> Thanks for the reply. Although this did not solve my issue, but gives me
> another glance and found out the problem reside in another issue.
>
> init_worker_by_lua_file error: .../.lua: API disabled in the current context
> stack traceback:
>

Too bad you omitted the backtrace. You could clearly see from the
stack traceback exactly which Lua API function is being used
incorrectly in the init_worker_by_lua*. It must not be ngx.timer.at()
since it is supported in that context (unless you are using an ancient
version of OpenResty).

Regards,
Yichun