manendra1984 / prosody-modules

Automatically exported from code.google.com/p/prosody-modules
0 stars 0 forks source link

mode_roster_command: Attempt to read a non-existent global 'prosodyctl' on startup #14

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
I have installed Prosody 0.8 and mod_roster_command, but can not get it working,

I also installed the hg tip of Prosody, do not work neither, here is the 
traceback.

{{{
certmanager          error  SSL/TLS: Failed to load 
/usr/local/etc/prosody/certs/example.com.key: Check that the path is correct, 
and the file exists. (host: example.com)
certmanager          error  SSL/TLS: Failed to load 
/usr/local/etc/prosody/certs/example.com.key: Previous error (see logs), or 
other system error. (host: example.com)
general              warn   Attempt to read a non-existent global 'prosodyctl'
stack traceback:
    ...usr/local/lib/prosody/modules/mod_roster_command.lua:18: in main chunk
    (tail call): ?
    [C]: in function 'xpcall'
    /usr/local/lib/prosody/core/modulemanager.lua:35: in function 'pcall'
    /usr/local/lib/prosody/core/modulemanager.lua:129: in function 'load'
    /usr/local/lib/prosody/core/modulemanager.lua:88: in function '?'
    /usr/local/lib/prosody/util/events.lua:67: in function 'fire_event'
    /usr/local/lib/prosody/core/hostmanager.lua:84: in function 'activate'
    /usr/local/lib/prosody/core/hostmanager.lua:42: in function '?'
    /usr/local/lib/prosody/util/events.lua:67: in function 'fire_event'
    /usr/local/bin/prosody:376: in function 'prepare_to_start'
    /usr/local/bin/prosody:492: in main chunk
    [C]: ?
modulemanager        error  Error initializing module 'roster_command' on 
'example.com': ...usr/local/lib/prosody/modules/mod_roster_command.lua:18: 
attempt to index global 'prosodyctl' (a nil value)
stack traceback:
    /usr/local/lib/prosody/core/modulemanager.lua:35: in function </usr/local/lib/prosody/core/modulemanager.lua:35>
    ...usr/local/lib/prosody/modules/mod_roster_command.lua:18: in main chunk
    (tail call): ?
    [C]: in function 'xpcall'
    /usr/local/lib/prosody/core/modulemanager.lua:35: in function 'pcall'
    /usr/local/lib/prosody/core/modulemanager.lua:129: in function 'load'
    /usr/local/lib/prosody/core/modulemanager.lua:88: in function '?'
    /usr/local/lib/prosody/util/events.lua:67: in function 'fire_event'
    /usr/local/lib/prosody/core/hostmanager.lua:84: in function 'activate'
    /usr/local/lib/prosody/core/hostmanager.lua:42: in function '?'
    /usr/local/lib/prosody/util/events.lua:67: in function 'fire_event'
    /usr/local/bin/prosody:376: in function 'prepare_to_start'
    /usr/local/bin/prosody:492: in main chunk
    [C]: ?
connlisteners        debug  Registered connection listener xmppclient
}}}

Original issue reported on code.google.com by epau...@gmail.com on 3 Dec 2011 at 2:12

GoogleCodeExporter commented 9 years ago
Ok, this is my error, I added it to modules_enabled.

Original comment by epau...@gmail.com on 3 Dec 2011 at 2:50

GoogleCodeExporter commented 9 years ago
Did you build prosody from source?

Also/and-or What distro/*nix you running prosody on on?
Because the paths in your log snippets looks "anomalous"

Original comment by maranda3...@gmail.com on 3 Dec 2011 at 2:59

GoogleCodeExporter commented 9 years ago
The log path was fine, cause I run the server from cli and log to console, 
anyway, it's my fault, no need add mod_roster_command to prosody.cfg.lua, 
please invalid it.

Original comment by epau...@gmail.com on 3 Dec 2011 at 3:05

GoogleCodeExporter commented 9 years ago
I've fixed the traceback and replaced it with a friendly log message. I've also 
added a note to the wiki page to remind that it doesn't need loading in Prosody.

Even if it was "your mistake" I still consider it a bug every time we show a 
traceback to a normal user, so I consider this a valid report, fixed.

Original comment by MWild1 on 3 Dec 2011 at 3:33