使用mobDebug远程调试OpenResty时Idea无法触发断点

It sounds like you're hitting a common set of quirks when debugging Lua in OpenResty's multi-process, event-driven environment—since it behaves way differently from a plain command-line Lua script. Let's break down the likely causes and fix them step by step:

1. Force mobDebug to Wait for IDEA's Breakpoint Configs #

OpenResty's access_by_lua_block executes extremely quickly, often finishing before IDEA can send breakpoint settings to the debug client. Add explicit connection details and a pause to your client.lua:

local mobdebug = require("mobdebug")
-- Match the address/port in your IDEA debug configuration (default is 127.0.0.1:8172)
mobdebug.start("127.0.0.1", 8172)
-- Pause execution until IDEA sends breakpoint setup commands
mobdebug.wait()

local lfs = require("lfs")
print("Folder: "..lfs.currentdir())

-- Add a test loop to keep the request alive long enough to trigger breakpoints
local counter = 0
while counter < 10 do
    counter = counter + 1
    print("Debug test iteration: " .. counter)
    ngx.sleep(1) -- Use OpenResty's coroutine-safe sleep, not plain Lua's sleep
end

2. Fix OpenResty's Lua Path for mobDebug #

OpenResty uses its own isolated Lua path, which might not include the directory where mobDebug is installed. Update your nginx.conf to make mobDebug visible:

http {
    # Add mobDebug's directory to OpenResty's package search path
    lua_package_path "/path/to/your/mobdebug/?.lua;;";

    server {
        location / {
            access_by_lua_block {
                local client = require("client")
            }
        }
    }
}

Also, confirm the user running OpenResty (usually nginx) has read permissions for the mobDebug files.

3. Avoid OpenResty Master/Worker Process Isolation #

OpenResty runs with master and worker processes—debug code initialized in the master process won't propagate to workers (which handle actual requests). Your current access_by_lua_block setup is correct (it runs in worker processes per request), but double-check you're not accidentally running debug code in init_by_lua_block (which runs in the master process).

4. Disable LuaJIT Optimization (Temporarily) #

LuaJIT's aggressive optimizations can sometimes strip the debug hooks mobDebug relies on. Disable JIT to rule this out:

Add this to your nginx.conf:

http {
    lua_jit off;
    # ... rest of your config
}

Or add this at the top of client.lua:

jit.off()
local mobdebug = require("mobdebug")
-- ... rest of your code

5. Enable mobDebug Logging for Diagnostics #

To see exactly what's going wrong with the connection, turn on mobDebug's internal logging:

local mobdebug = require("mobdebug")
-- Log debug activity to a file you can inspect later
mobdebug.log("/tmp/mobdebug_openresty.log")
mobdebug.start("127.0.0.1", 8172)
mobdebug.wait()
-- ... rest of your code

Check the log file for errors related to connection setup or breakpoint reception.

6. Verify IDEA's Debug Configuration #

• Ensure IDEA's mobDebug listener uses the same port (default 8172) and address (127.0.0.1 for local debugging) you specified in mobdebug.start().
• Make sure IDEA isn't filtering debug sessions to only accept command-line Lua processes (check the debug run configuration settings for any process restrictions).

After trying these steps, you should see IDEA trigger breakpoints as expected when sending requests to your OpenResty server.

内容的提问来源于stack exchange，提问作者Irina