#896 prosodyctl, things other than modules don't normalize types of config options

Reporter Martin
Owner Nobody
Created
Updated
Stars ★ (1)  
Tags
  • Priority-Medium
  • Type-Defect
  • Status-Accepted
  1. Martin on

    prosodyctl check Checking config... Done. Checking DNS for host mdosch.de... lua: /home/md85/bin/prosodyctl:1146: bad argument #1 to 'to_ascii' (string expected, got table) stack traceback: [C]: in function 'to_ascii' /home/md85/bin/prosodyctl:1146: in function '?' /home/md85/bin/prosodyctl:1388: in main chunk [C]: ? According to ZASH in prosody MUC this is caused by a different parsing method from prosodyctl. Informations about my installation: prosodyctl about Prosody 0.10 nightly build 385 (2017-04-19, 1773559b03a8) # Prosody directories Data directory: /home/md85/var/lib/prosody Config directory: /home/md85/etc/prosody Source directory: /home/md85/lib/prosody Plugin directories: /home/md85/opt/prosody-modules/ - prosody-modules rev: dae655657a92 /home/md85/lib/prosody/modules/ # Lua environment Lua version: Lua 5.1 Lua module search paths: /home/md85/lib/prosody/?.lua /home/md85/.luarocks/share/lua/5.1/?.lua /home/md85/.luarocks/share/lua/5.1/?/init.lua /usr/share/lua/5.1/?.lua /usr/share/lua/5.1/?/init.lua /home/md85/.luarocks/share/lua/5.1/?.lua /home/md85/.luarocks/share/lua/5.1/?/init.lua /usr/lib64/lua/5.1/?.lua /usr/lib64/lua/5.1/?/init.lua /home/md85/.luarocks/share/lua/5.1/?.lua /home/md85/.luarocks/share/lua/5.1/?/init.lua Lua C module search paths: /home/md85/lib/prosody/?.so /home/md85/.luarocks/lib/lua/5.1/?.so /usr/lib/lua/5.1/?.so /home/md85/.luarocks/lib/lua/5.1/?.so /usr/lib64/lua/5.1/?.so /usr/lib64/lua/5.1/loadall.so /home/md85/.luarocks/lib/lua/5.1/?.so LuaRocks: Installed (2.1.2) # Lua module versions lfs: LuaFileSystem 1.6.3 libevent: 2.1.5-beta luaevent: 0.4.4 lxp: LuaExpat 1.3.0 socket: LuaSocket 3.0-rc1 ssl: 0.6

  2. Zash on

    It would have been helpful to mention that you set inproxy65_address to a table, which is wrong. Modules access the config via an API that knows how to deal with this, but other things that access the config directly don't.

    Changes
    • title 0.10: prosodyctl is parsing the config different then prosody Things other than modules don't normalize types of config options
  3. Zash on

    Changes
    • tags Status-Accepted
    • title Things other than modules don't normalize types of config options prosodyctl, things other than modules don't normalize types of config options
  4. Zash on

    Also affects port options if they are not wrapped in { }

New comment

Not published. Used for spam prevention and optional update notifications.