joewalker / prosody-modules Goto Github PK

How to reproduce:

1. Fresh install of prosody 0.9 (deb repository) with prosody-modules provided 
by hg
2. Setup a simple vhost with mod_admin_http => should works
3. Enable authentication = "internal_hashed" => unable to login

What steps will reproduce the problem?
1. Have a conversation with someone
2. Look in /var/lib/prosody/*/archive/user.list

What is the expected output? What do you see instead?

I expect to see both the messages I sent them, and the messages they sent me.

I only see the messages they sent me.

What version of the product are you using? On what operating system?

I am using prosody 0.7.0-1
Linux singpolyma 2.6.18-164.11.1.el5.028stab068.3 #1 SMP Wed Feb 17 15:22:30 
MSK 2010 x86_64 GNU/Linux
Debian GNU/Linux 5.0
Latest mod_archive from hg

Please provide any additional information below.

This existed on the last version of mod_archive I tried, and persists on the 
latest version.

What steps will reproduce the problem?
1. Install Debian Squeeze, apt-get update && apt-get install prosody.
2. Install latest mod_muc_log && mod_muc_http to 
/usr/share/lua/5.1/prosody/modules/
3. Make sure logs are populated in 
/var/lib/prosody/%conference_name%/muc_log/%yymmdd%/%room_name%.dat
4. Visit the page 
http://%server_name%:5290/muc_log/%conference_name%/%room_name%/

What is the expected output? What do you see instead?
Expected to see the list of dates for this room. Got endless "loading" process.

What version of the product are you using? On what operating system?
Debian Squeese, Prosody 0.7.0-1squeeze1, lastest muc_log and muc_log_http.

Please provide any additional information below.

Debug log:
Feb 06 13:37:53 socket  debug   server.lua: accepted new client connection from 
*:53910 to 5290
Feb 06 13:37:53 httpserver  debug   Reading request line...
Feb 06 13:37:53 httpserver  debug   GET request for 
/muc_log/%conference_name%/%room_name%/ on port 5290
Feb 06 13:37:53 httpserver  debug   Reading headers...
[END]

Reactions:
http://%server_name%:5290/muc_log/ - OK: list of servers
http://%server_name%:5290/muc_log/%server_name%/ - OK: list of rooms
http://%server_name%:5290/muc_log/blahblahblah/ - OK: No such MUC component
http://%server_name%:5290/muc_log/%server_name%/%room_name%/ - HUNGS
http://%server_name%:5290/muc_log/%server_name%/blahblahblah/ - HUNGS
http://%server_name%:5290/muc_log/%server_name%/%room_name%/YYYY-mm-dd/ - HUNGS

What steps will reproduce the problem?
1. Use XMPP Framework module on Drupal
2. Have account provisioning enabled
3. Whenever an account operation takes place

What is the expected output? What do you see instead?
I think the account creation/deletion/password change should take place
instead whenever drupal connects to the server i get this error:

Nov 17 00:07:19 c2s22e1650  info    Client connected
Nov 17 00:07:20 c2s22e1650  info    TLS negotiation started...
Nov 17 00:07:20 c2s22e1650  info    Authenticated as adminaccount@domain
Nov 17 00:07:20 xmppclient_listener error   Traceback[c2s]:
/usr/lib/prosody/util/dataforms.lua:56: bad argument #1 to 'ipairs' (table
expected, got nil): stack traceback:
    /usr/lib/prosody/net/xmppclient_listener.lua:44: in function
</usr/lib/prosody/net/xmppclient_listener.lua:44>
    [C]: in function 'ipairs'
    /usr/lib/prosody/util/dataforms.lua:56: in function 'form'
    mod_adhoc_cmd_admin.lua:149: in function <mod_adhoc_cmd_admin.lua:119>
    (tail call): ?
    /usr/lib/prosody/util/events.lua:79: in function 'fire_event'
    /usr/lib/prosody/core/stanza_router.lua:151: in function 'core_post_stanza'
    /usr/lib/prosody/core/stanza_router.lua:101: in function 'core_process_stanza'
    /usr/lib/prosody/net/xmppclient_listener.lua:46: in function
</usr/lib/prosody/net/xmppclient_listener.lua:46>
    [C]: in function 'xpcall'
    /usr/lib/prosody/net/xmppclient_listener.lua:46: in function 'cb_handlestanza'
    /usr/lib/prosody/core/xmlhandlers.lua:132: in function
</usr/lib/prosody/core/xmlhandlers.lua:107>
    [C]: in function 'parse'
    /usr/lib/prosody/net/xmppclient_listener.lua:62: in function 'data'
    /usr/lib/prosody/net/xmppclient_listener.lua:132: in function
</usr/lib/prosody/net/xmppclient_listener.lua:111>
    (tail call): ?
    /usr/lib/prosody/net/server.lua:818: in function
</usr/lib/prosody/net/server.lua:803>
    [C]: in function 'xpcall'
    /usr/bin/prosody:298: in function 'loop'
    /usr/bin/prosody:358: in main chunk
    [C]: ?
Nov 17 00:07:22 c2s22e1650  info    Client disconnected: closed
Nov 17 00:07:22 c2s22e1650  info    Destroying session for
adminaccount@domain/drupal-server (adminaccount@domain)

What version of the product are you using? On what operating system?
Latest module revision on Ubuntu 9.10

Please provide any additional information below.
None.

What steps will reproduce the problem?
1. Load the muc_log and muc_log_http modules.
2. Access http://localhost:5290/muc_log/
3. Select the component and room

What is the expected output? What do you see instead?

Expected is a list of dates and links to the actual log.  Instead there is no 
output.  The error log shows the following:

  Apr 06 16:17:51 general   warn    Attempt to read a non-existent global 'rooms'
stack traceback:
    mod_muc_log_http.lua:658: in function 'callback'
    /usr/share/lua/5.1/prosody/net/httpserver.lua:98: in function 'call_callback'
    /usr/share/lua/5.1/prosody/net/httpserver.lua:168: in function </usr/share/lua/5.1/prosody/net/httpserver.lua:116>
    (tail call): ?
    ...sr/share/lua/5.1/prosody/net/httpserver_listener.lua:33: in function <...sr/share/lua/5.1/prosody/net/httpserver_listener.lua:19>
    (tail call): ?
    /usr/share/lua/5.1/prosody/net/server_select.lua:823: in function </usr/share/lua/5.1/prosody/net/server_select.lua:808>
    [C]: in function 'xpcall'
    /usr/bin/prosody:395: in function 'loop'
    /usr/bin/prosody:462: in main chunk
    [C]: ?
  Apr 06 16:17:51 general   error   Top-level error, please report:
mod_muc_log_http.lua:658: attempt to index field 'rooms' (a nil value)

What version of the product are you using? On what operating system?

I am using Debian Squeeze with prosody 0.7.0 and the most current muc_log_http 
(changeset 633:0d3174d5a1cc).

Thanks for the Mongodb storage. It looks like we need to json encode and json 
decode in mongodb storage setter and getter functions.

I found error when adding a user to the roster, since the data type is table 
and it needs to be json encode before insert into mongodb or else db insert 
fails and server crash's.

Thanks

if i eneable offline_email when the user go online not have the instant 
messages because this are shipped on e-mail.
But in e-mail must be only an alert and when user go online must had all message

I use mod_register_web and "watchregistrations".

Can you give the clients IP address to prosody to show them in the 
notification? Right know it looks like this:

"User tester2 just registered on jabber.example.org from $ip"

What version of the product are you using? On what operating system?
Prosody 0.9.2 on Debian wheezy

Since mod_pastebin counts bytes instead of utf-8 characters,
on other languages, for example Russian, the character threshold limit would 
practically be twice smaller.

Changing the length count with the following patch fixes this problem.

What steps will reproduce the problem?
1. Install Prosody
2. Install mod_archive
3. Install a Spectrum2 transport (in gateway mode).
4. Try to chat with anyone through that transport

What is the expected output?
Messages should get through.

What do you see instead?
All incoming and outgoing messages to users via a transport vanish.

What version of the product are you using? On what operating system?
Last version of mod_archive (bb938db35434)
with prosody 0.8.2
on Ubuntu 12.10
And Spectrum2 beta2

Please provide any additional information below.

From the log:
     xmppclient_listener     error   Traceback[c2s]: /usr/lib/prosody/core/usermanager.lua:79: attempt to index field 'users' (a nil value): stack traceback:
            /usr/lib/prosody/net/xmppclient_listener.lua:62: in function </usr/lib/prosody/net/xmppclient_listener.lua:62>
            /usr/lib/prosody/core/usermanager.lua:79: in function 'user_exists'
            /usr/lib/prosody/modules/mod_archive.lua:775: in function '?'
            /usr/lib/prosody/util/events.lua:67: in function 'fire_event'
            /usr/lib/prosody/core/stanza_router.lua:169: in function 'core_post_stanza'
            /usr/lib/prosody/core/stanza_router.lua:121: in function </usr/lib/prosody/core/stanza_router.lua:44>
            (tail call): ?
            [C]: in function 'xpcall'
            /usr/lib/prosody/net/xmppclient_listener.lua:66: in function 'cb_handlestanza'
            /usr/lib/prosody/util/xmppstream.lua:139: in function </usr/lib/prosody/util/xmppstream.lua:125>
            [C]: in function 'parse'
            /usr/lib/prosody/util/xmppstream.lua:200: in function 'feed'
            /usr/lib/prosody/net/xmppclient_listener.lua:145: in function 'data'
            /usr/lib/prosody/net/xmppclient_listener.lua:161: in function </usr/lib/prosody/net/xmppclient_listener.lua:158>
            (tail call): ?
            /usr/lib/prosody/net/server_select.lua:820: in function </usr/lib/prosody/net/server_select.lua:802>
            [C]: in function 'xpcall'
            /usr/bin/prosody:427: in function 'loop'
            /usr/bin/prosody:494: in main chunk
            [C]: ?

What steps will reproduce the problem?
1. Enable mod_archive_muc
2. Connect to Jabber server using OneTeam client for Windows/iPhone (maybe 
others as well)
3. The messages sent/received are causing error in Prosody logs.

What is the expected output? What do you see instead?
The messages should be working fine

What version of the product are you using? On what operating system?
0.8.2 on Ubuntu 12.04 LTS

Please provide any additional information below.
Traceback:
Dec 26 11:34:10 xmppclient_listener     error   Traceback[c2s]: 
/usr/lib/prosody/core/usermanager.lua:79: attempt to index field '?' (a nil 
value): stack traceback:
        /usr/lib/prosody/net/xmppclient_listener.lua:62: in function </usr/lib/prosody/net/xmppclient_listener.lua:62>
        /usr/lib/prosody/core/usermanager.lua:79: in function 'user_exists'
        /usr/lib/prosody/modules/mod_archive_muc.lua:177: in function '?'
        /usr/lib/prosody/util/events.lua:67: in function 'fire_event'
        /usr/lib/prosody/core/stanza_router.lua:173: in function 'core_post_stanza'
        /usr/lib/prosody/core/stanza_router.lua:121: in function </usr/lib/prosody/core/stanza_router.lua:44>
        (tail call): ?
        [C]: in function 'xpcall'
        /usr/lib/prosody/net/xmppclient_listener.lua:66: in function 'cb_handlestanza'
        /usr/lib/prosody/util/xmppstream.lua:139: in function </usr/lib/prosody/util/xmppstream.lua:125>
        [C]: in function 'parse'
        /usr/lib/prosody/util/xmppstream.lua:200: in function 'feed'
        /usr/lib/prosody/net/xmppclient_listener.lua:145: in function 'data'
        /usr/lib/prosody/net/xmppclient_listener.lua:161: in function 'onincoming'
        /usr/lib/prosody/net/server_event.lua:625: in function </usr/lib/prosody/net/server_event.lua:590>
        [C]: in function 'loop'
        /usr/lib/prosody/net/server_event.lua:804: in function </usr/lib/prosody/net/server_event.lua:803>
        [C]: in function 'xpcall'
        /usr/bin/prosody:427: in function 'loop'
        /usr/bin/prosody:494: in main chunk
        [C]: ?

What steps will reproduce the problem?
I don't know what exactly caused this error.

Aug 09 19:04:37 general error   Top-level error, please report:
/usr/lib/prosody/modules/mod_smacks/mod_smacks.lua:227: attempt to index a nil 
value
Aug 09 19:04:37 general error   
stack traceback:
    /usr/lib/prosody/modules/mod_smacks/mod_smacks.lua:227: in function 'callback'
    /usr/lib64/prosody/util/timer.lua:70: in function </usr/lib64/prosody/util/timer.lua:69>
    [C]: in function 'loop'
    /usr/lib64/prosody/net/server_event.lua:788: in function </usr/lib64/prosody/net/server_event.lua:787>
    [C]: in function 'xpcall'
    /usr/bin/prosody:364: in function 'loop'
    /usr/bin/prosody:431: in main chunk
    [C]: ?

I am running 0.8.x edition of this plugin (without shared connections), rev 
[f58a2c5ae6ef], together with Prosody 0.8.2, Lua 5.1 (Debian Wheezy).
(So I cannot decide whether this bug is still valid in 9.0 version)

Plugin is not able to handle accidental DB disconnect (e.g. Mysql server 
restart) - the rest of Prosody seems to be able to do so. Furthermore, it 
causes no messages are even delivered, because calling error() on line 101: 
function drops everything.

To reproduce
1. Run prosody
2. Send some message - sent & logged
3. Restart mysql server
4. Send another message - raises an error and does not deliver the message at 
all

Just tried to get http page.

<iq type="set" id="newconn1" to="tcp.ut.onego.ru">
    <open xmlns='http://jabber.org/protocol/ibb'
        sid='connection1'
        stanza='message'
        xmlns:tcp='http://prosody.im/protocol/tcpproxy'
        tcp:host='dersd.games.onego.ru'
        tcp:port='80' />
</iq>

<iq from="tcp.ut.onego.ru" type="result" to="[email protected]/rawr"
id="newconn1"/>

<iq id='kr91n475'
    to='tcp.ut.onego.ru'
    type='set'>
  <data xmlns='http://jabber.org/protocol/ibb' seq='0' sid='connection1'>
GET /time.php
Host: dersd.games.onego.ru
  </data>
</iq>


May 13 09:13:18 xmppserver_listener error   Traceback[s2s]:
/usr/lib/prosody/net/server_select.lua:362: bad argument #1 to 'string_len'
(string expected, got nil): stack traceback:
    /usr/lib/prosody/net/xmppserver_listener.lua:51: in function
</usr/lib/prosody/net/xmppserver_listener.lua:51>
    [C]: in function 'string_len'
    /usr/lib/prosody/net/server_select.lua:362: in function 'write'
    mod_tcpproxy.lua:87: in function 'component'
    /usr/lib/prosody/core/componentmanager.lua:70: in function
'component_handle_stanza'
    /usr/lib/prosody/core/stanza_router.lua:156: in function 'core_post_stanza'
    /usr/lib/prosody/core/stanza_router.lua:100: in function 'core_process_stanza'
    /usr/lib/prosody/net/xmppserver_listener.lua:56: in function
</usr/lib/prosody/net/xmppserver_listener.lua:56>
    [C]: in function 'xpcall'
    /usr/lib/prosody/net/xmppserver_listener.lua:56: in function 'cb_handlestanza'
    /usr/lib/prosody/core/xmlhandlers.lua:119: in function
</usr/lib/prosody/core/xmlhandlers.lua:109>
    [C]: in function 'parse'
    /usr/lib/prosody/net/xmppserver_listener.lua:83: in function 'data'
    /usr/lib/prosody/net/xmppserver_listener.lua:157: in function
</usr/lib/prosody/net/xmppserver_listener.lua:135>
    (tail call): ?
    /usr/lib/prosody/net/server_select.lua:823: in function
</usr/lib/prosody/net/server_select.lua:808>
    [C]: in function 'xpcall'
    /usr/lib/prosody/../../bin/prosody:387: in function 'loop'
    /usr/lib/prosody/../../bin/prosody:453: in main chunk
    [C]: ?

1. Install mod_auth_pam with Prosody 0.9 (specifying "pam" for authentication)
2. Set up xmpp file in /etc/pam.d per wiki
3. Try to login as valid system user

The valid system user can't login to Prosody and these errors appear in 
auth.log:

localhost prosody[19726]: pam_unix(xmpp:auth): conversation failed

localhost prosody[19726]: pam_unix(xmpp:auth): auth could not identify password 
for [<username>]


I've tried several variations on the xmpp file in /etc/pam.d - even including a 
stub to allow all logins. I thought this might be related to the changes in 
recent Ubuntu versions that locked down PAM functionality a great deal, so I 
tried temporarily adding the prosody user to a privileged group, but that had 
no effect either.

mod_auth_pam with Prosody 0.9.1 on Ubuntu 13.10

What steps will reproduce the problem?
1. Setup ldap with a wrong bind_password

What is the expected output? What do you see instead?
I would like to see: "LDAP bind failed - server result: ..."
But I get instead:
mod_c2s: Traceback[c2s]: /usr/lib/prosody/modules/ldap.lib.lua:217: attempt to 
index local 'ld' (a nil value)_stack trac
eback:__/usr/lib/prosody/modules/ldap.lib.lua:217: in function 
'singlematch'__/usr/lib/prosody/modules/mod_storage_ldap.lua:154: in function 
'get'
__/usr/lib/prosody/modules/mod_vcard.lua:25: in function 
'?'__/usr/lib/prosody/util/events.lua:67: in function 
</usr/lib/prosody/util/events.lua:6
3>__(tail call): ?__/usr/lib/prosody/modules/mod_iq.lua:38: in function 
'?'__/usr/lib/prosody/util/events.lua:67: in function 'fire_event'__/usr/l
ib/prosody/core/stanza_router.lua:184: in function 
'core_post_stanza'__/usr/lib/prosody/core/stanza_router.lua:132: in function 
</usr/lib/prosody/
core/stanza_router.lua:55>__(tail call): 
?__...__/usr/lib/prosody/util/xmppstream.lua:185: in function 
'feed'__/usr/lib/prosody/modules/mod_c2s.lu
a:230: in function 'data'__/usr/lib/prosody/modules/mod_c2s.lua:252: in 
function 'onincoming'__/usr/lib/prosody/net/server_event.lua:625: in funct
ion </usr/lib/prosody/net/server_event.lua:571>__[C]: in function 
'loop'__/usr/lib/prosody/net/server_event.lua:786: in function </usr/lib/prosody
/net/server_event.lua:785>__[C]: in function 
'xpcall'__/usr/lib/prosody/../../bin/prosody:372: in function 
'loop'__/usr/lib/prosody/../../bin/pros
ody:402: in main chunk__[C]: ?

What steps will reproduce the problem?
1. install mod_auth_dovecot to auth against Dovecot 2.0
2. login using Jitsi XMPP client with any email address matching a virtualhost 
setting in Prosody and any password
3. watch login succeeding

What is the expected output? What do you see instead?
- I only want login to succeed when Dovecot returns an "OK"

What version of the product are you using? On what operating system?
- Ubuntu 12.04.2, Dovecot 2.0.19, Prosody 0.8.2, mod_auth_dovecot + lib from 
the 0.8 branch

Please provide any additional information below.
- Logfile (with debug enabled):

Aug 11 00:24:18 c2s24c9170  info    Client connected
Aug 11 00:24:18 c2s24c9170  debug   Client sent opening <stream:stream> to 
domain.com
Aug 11 00:24:18 c2s24c9170  debug   Sent reply <stream:stream> to client
Aug 11 00:24:18 c2s24c9170  debug   Received[c2s_unauthed]: <starttls 
xmlns='urn:ietf:params:xml:ns:xmpp-tls'>
Aug 11 00:24:18 socket  debug   server.lua: we need to do tls, but delaying until 
send buffer empty
Aug 11 00:24:18 c2s24c9170  debug   TLS negotiation started for c2s_unauthed...
Aug 11 00:24:18 socket  debug   server.lua: attempting to start tls on 
tcp{client}: 0x24adb68
Aug 11 00:24:19 socket  debug   server.lua: ssl handshake done
Aug 11 00:24:19 c2s24c9170  debug   Client sent opening <stream:stream> to 
domain.com
Aug 11 00:24:19 c2s24c9170  debug   Sent reply <stream:stream> to client
Aug 11 00:24:19 c2s24c9170  debug   Received[c2s_unauthed]: <auth 
mechanism='PLAIN' xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
Aug 11 00:24:19 domain.com:auth_dovecot debug   sending 
"AUTH   3   PLAIN   service=xmpp    resp=AHhtcH.....="
Aug 11 00:24:21 domain.com:auth_dovecot debug   received 
"FAIL   3   [email protected]"
Aug 11 00:24:21 c2s24c9170  info    Authenticated as [email protected]
Aug 11 00:24:21 domain.com:saslauth debug   sasl reply: <success 
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'></success>

As you can see, Dovecot returns "FAIL" but the authentication succeeds anyway.

Here are my relevant settings:

anonymous_login = false
authentication = "dovecot"
dovecot_auth_socket = "/var/run/prosody/auth"    # this is created by Doveceot
auth_append_host = true

What steps will reproduce the problem?
1. load the muc_log_http module
2. load the muc_log module

What is the expected output? What do you see instead?
Visiting http://ip:port/muc_log returns an empty page (containing no data 
whatsoever), while the prosody log doesn't contain any load errors for the 
muc_log_http order. 

Reversing the order of the modules fixes the issue.

What version of the product are you using? On what operating system?
Prosody 0.7.0, the latest muc_log and muc_log_http modules

https://code.google.com/p/prosody-modules/source/browse/mod_smacks/mod_smacks.lu
a#62 will only send enable in the case the s2sout session is authenticated, but 
upon receiving features that won't be the case also to note that there will be 
callbacks which hook for features at higher priority in the order tls, sasl, db 
and at least both sasl and db drop execution of other callbacks iirc. So in the 
end, on s2sout, stream management or stanza acks will never be enabled.

1.install mod_pastebin
2. enable it as described in 
https://code.google.com/p/prosody-modules/wiki/mod_pastebin
3. restart prosody


The module isn't loaded and the error log gives this : 

"/usr/lib/prosody/modules/mod_pastebin.lua:3: attempt to call method 'depends' 
(a nil value)"

This corresponds to the line "module:depends("http");"

My version of prosody is 0.8.2-3.

What steps will reproduce the problem?
1. Enable mod_offline_email with following options:
queue_offline_emails = "86400";
smtp_server = "relay.domain.com";
smtp_from = "[email protected]";
2. Wait for 86400 seconds

What is the expected output? What do you see instead?
Prosody should be sending offline emails to users.

What version of the product are you using? On what operating system?
0.8.2 on Ubuntu 12.04 LTS

Please provide any additional information below.
Dec 27 08:47:00 general error   Top-level error, please report:
/usr/lib/prosody/modules/mod_offline_email.lua:101: attempt to compare string 
with number
Dec 27 08:47:00 general error   
stack traceback:
        /usr/lib/prosody/modules/mod_offline_email.lua:101: in function 'func'
        /usr/lib/prosody/util/timer.lua:69: in function </usr/lib/prosody/util/timer.lua:68>
        [C]: in function 'loop'
        /usr/lib/prosody/net/server_event.lua:804: in function </usr/lib/prosody/net/server_event.lua:803>
        [C]: in function 'xpcall'
        /usr/bin/prosody:427: in function 'loop'
        /usr/bin/prosody:494: in main chunk
        [C]: ?

Using prosody 0.9 under linux and mod_c2s_conn_throttle, the number of used fd 
by prosody grows constantly. Without mod_c2s_conn_throttle all is fine.

So mod_c2s_conn_throttle probably leaks some sockets.

What steps will reproduce the problem?
1. setup prosody with mod_admin_web and storage_sql
2. start prosody and load /admin interface
3. enter JID and PW and click login

What is the expected output? What do you see instead?
Expected Output: the login works
Instead: no movement, login screen for 2 hours now

What version of the product are you using? On what operating system?
prosody 0.9.1 with clone from here of the modules, OS funtoo

Please provide any additional information below.

Using mod_onions is not possible with prosody 0.9.2-1~wheezy10 from the debian 
repository and libevent enabled. It results in errors such as

  mod_onions.lua:149: calling 'send' on bad self (tcp{client} expected, got table)

and

  mod_onions.lua:95: bad argument #1 to 'w' (tcp{client} expected, got table)                                       

With help from the prosody-muc I made the changes in the attached patch which 
seem to have resolved the problems.

What steps will reproduce the problem?
1. Load the muc_log module
2. Join a MUC
3. Say something
4. Leave the MUC
5. Join the MUC again
6. Say Something

What is the expected output? What do you see instead?
Expected: that the log contains joins, parts and messages
Actual: the log contains parts and messages, but no joins

What version of the product are you using? On what operating system?
Prosody 0.7.0, latest muc_log

Please provide any additional information below.

Hi,

i search a plugin like jdisk ( http://dev.jabbim.cz/jdisk ), for prosody, do 
you know if a plugin like that exist ?

Jan 29 17:00:40 general error   Top-level error, please report:
...sody/prosody-modules/mod_manifesto/mod_manifesto.lua:97: table index is nil
Jan 29 17:00:40 general error
stack traceback:
        /usr/bin/prosody: in function 'loop'
        /usr/lib/prosody/net/server_event.lua:786: in function </usr/lib/prosody/net/server_event.lua:785>
        [C]: in function 'xpcall'
        /usr/bin/prosody:372: in function 'loop'
        /usr/bin/prosody:402: in main chunk
        [C]: ?

mod_auth_pam requires 
(http://code.google.com/p/prosody-modules/source/browse/mod_auth_pam/mod_auth_pa
m.lua#4) the lua-pam library. After several attempts to compile that library, I 
found that it requires Lua 5.2 (while Prosody requires 5.1). I'm unable to find 
a way to both run Prosody and set up the lua-pam library.

1. Specify 'pam' for authentication after installing mod_auth_pam
2. Attempt to compile lua-pam from https://github.com/devurandom/lua-pam
3. lua-pam requires Lua 5.2. Attempting to compiled under 5.1 fails badly.
4. PAM authentication isn't possible


Prosody .9, Lua 5.1 and default branch of prosody-modules on Ubuntu 13.10

What steps will reproduce the problem?
1. Try to authenticate against Windows active directory server
2. It does not work, because neither the "userPassword" attribute is exposed 
nor can I bind() with the username and password

ActiveDirectory only supports binding via a generic user, then fetch the user 
via a search and the compare() the user's password against a given string. The 
server will return true/false.

So, please support the auth method "compare" in mod_auth_ldap.

What steps will reproduce the problem?

1. Install prosody and the newest mod_remote_roster module.
2. Connect spectrum2 in gateway mode

What is the expected output? What do you see instead?

 Revision 295ae44b8a01 - continuously produces the error shown below in the prosody log. In addition to outputting the error, prosody consumed high cpu and responded very slowly when connecting up a transport.

 I downloaded and reverted back to c86fc337d56f, and this corrected the issue.

 Oct 04 13:11:08 general    error   
stack traceback:
    /usr/lib/prosody/modules/mod_remote_roster.lua:152: in function 'component_roster_push'
    /usr/lib/prosody/modules/mod_remote_roster.lua:166: in function 'func'
    /usr/lib/prosody/util/timer.lua:53: in function '?'
    /usr/lib/prosody/net/server_select.lua:835: in function </usr/lib/prosody/net/server_select.lua:802>
    [C]: in function 'xpcall'
    /usr/lib/prosody/../../bin/prosody:427: in function 'loop'
    /usr/lib/prosody/../../bin/prosody:494: in main chunk


What version of the product are you using? On what operating system?
prosody 0.8.2-1 (from ubuntu repository) on Ubuntu 12.04.1 LTS 

Also using  1:2.0.0~beta2-416-g4100b4c-1 of spectrum2-git (from spectrum 
repository)

Please provide any additional information below.


http://code.google.com/p/prosody-modules/source/list?path=/mod_remote_roster/mod
_remote_roster.lua&r=295ae44b8a010f1974e4ead122de6b4883dfd09b

edit mod_offline_email for read from vcard and check also why send only one 
e-mail from jid from day?

What steps will reproduce the problem?
1. Connect
2. Before binding, send "<enable/>"
3. Stream management is now enabled, before the client bound a resource. This 
should generate an error (http://xmpp.org/extensions/xep-0198.html Example 5)

What steps will reproduce the problem?
1. Connect
2. Send "<enable/>"
3. Send "<enable/>"
4. All stanzas are now counted twice.

What steps will reproduce the problem?
1. Connect
2. Enable stream management and resumption
3. Disconnect
4. Reconnect, without resuming
5. The new session will be destroyed after the timeout

I've attached a patch which fixes all these issues.

mod_smacks in current prosody hg supports protocol version 2, but XEP-0198 has 
advanced to protocol version 3 (XEP version 1.2 and newer).

What steps will reproduce the problem?
1. enable mod_muc_log and mod_muc_log_http
2. from a client, create a new room with a jid containing a HTTP URL special 
character such '#' or '?'
3. connect to http://192.168.1.72:5290/muc_log and follow the links in order to 
display the content of the room create before

What is the expected output? What do you see instead?
The room content is not displayed (as it should). The browser is stucked on the 
"Available rooms on conference.xxxxx:" page (the room'm name has a  "#" in my 
case). Basically the hyperlink is missunderstood by the browser...


What version of the product are you using? On what operating system?
last from prosody-modules

Please provide any additional information below.

What steps will reproduce the problem?
1. Visit http://ip:port/muc_log
2. Click any of the links
3.

What is the expected output? What do you see instead?
Links on http://ip:port/muc_log don't point to /muc_log/<muc>/ but to /<muc> 
instead. Visiting http://ip:port/muc_log/ (note the trailing slash) fixes the 
issue

What version of the product are you using? On what operating system?
Prosody 0.7.0, latest muc_log_http 

I'd like an option for muc_log_http that allows binding to a specific address 
(e.g. 127.0.0.1).

My concrete use case:

I don't want the module to listen on a public interface but instead use a 
reverse http proxy to forward requests to the module, to implement custom 
access control.

1 - load module
2 - send im from jid A to jid B offline
3 - jid B have the e-mail in inbox
4 - send again from jid A to jid B offline
5 - jib B not have anything in the e-mail
6 - jib B not have any e-mail from jid A from server restart for have other 
e-mail alert must send from other jid but not again from jid A also if jid B go 
online and after offline again.

When I connect to prosody (c2s) with a socket stream features includes an xmlns 
as follows:

However when using the websocket implementation the xmlns isn't present:

Is this expected behaviour or should the 'stream:xmlns' be present?

Also a typo on line 180 - c*l*osed :)

------------------- Prosody modules (latest update)

changeset:   1256:ab80da799edf
tag:         tip
user:        Florian Zeitz <[email protected]>
date:        Sat Dec 21 19:28:34 2013 +0100
summary:     mod_admin_web: Bump strophejs version

------------------- Prosody information

Prosody trunk nightly build 452 (2013-12-18, b3d5aa57c454)

# Prosody directories
Data directory:     /var/lib/prosody
Plugin directory:   /usr/lib/prosody/modules/
Config directory:   /etc/prosody
Source directory:   /usr/lib/prosody

# Lua environment
Lua version:                Lua 5.1

Lua module search paths:
  /usr/lib/prosody/?.lua
  /usr/local/share/lua/5.1/?.lua
  /usr/local/share/lua/5.1/?/init.lua
  /usr/local/lib/lua/5.1/?.lua
  /usr/local/lib/lua/5.1/?/init.lua
  /usr/share/lua/5.1/?.lua
  /usr/share/lua/5.1/?/init.lua

Lua C module search paths:
  /usr/lib/prosody/?.so
  /usr/local/lib/lua/5.1/?.so
  /usr/lib/x86_64-linux-gnu/lua/5.1/?.so
  /usr/lib/lua/5.1/?.so
  /usr/local/lib/lua/5.1/loadall.so

LuaRocks:           Not installed

# Lua module versions
lfs:        LuaFileSystem 1.5.0
lxp:        LuaExpat 1.2.0
pposix:     0.3.6
socket:     LuaSocket 3.0-rc1
ssl:        0.4.1

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
}}}

This patch allows specifying IP address in mod_srvinjection configuration as 
follows:

srvinjection = { ["talkr.im"] = {"174.129.226.140", 5269}; };

Useful for bypassing DNS lookups if they are failing sometimes.

mod_mam crashes without any useful information in when it's trying to archive a 
message:

Aug 02 19:16:48 mod_c2s error   Traceback[c2s]: 
/usr/lib/prosody/modules/mod_mam.lua:235: attempt to call method 'append' (a 
nil value)
stack traceback:
        /usr/lib/prosody/modules/mod_mam.lua:235: in function </usr/lib/prosody/modules/mod_mam.lua:208>
        (tail call): ?
        /usr/lib/prosody/util/events.lua:67: in function 'fire_event'
        /usr/lib/prosody/core/stanza_router.lua:180: in function 'core_post_stanza'
        /usr/lib/prosody/core/stanza_router.lua:132: in function </usr/lib/prosody/core/stanza_router.lua:55>
        (tail call): ?
        [C]: in function 'xpcall'
        /usr/lib/prosody/modules/mod_c2s.lua:121: in function 'cb_handlestanza'
        /usr/lib/prosody/util/xmppstream.lua:133: in function </usr/lib/prosody/util/xmppstream.lua:120>
        [C]: in function 'parse'
        /usr/lib/prosody/util/xmppstream.lua:185: in function 'feed'
        /usr/lib/prosody/modules/mod_c2s.lua:228: in function 'data'
        /usr/lib/prosody/modules/mod_c2s.lua:250: in function </usr/lib/prosody/modules/mod_c2s.lua:247>
        (tail call): ?
        /usr/lib/prosody/net/server_select.lua:847: in function </usr/lib/prosody/net/server_select.lua:829>
        [C]: in function 'xpcall'
        /usr/bin/prosody:366: in function 'loop'
        /usr/bin/prosody:396: in main chunk
        [C]: ?


What version of the product are you using? On what operating system?
prosody: trunk nightly build 406 (2013-07-27, 785da1854eb9)
mod_mam: changeset:   1116:2345a30dd8b4  Jul 13 17:43:30 2013 +0200

Please provide any additional information below.

I'm trying to use it without sql2 storage. Probably this is a reason, but it 
would be nice to be able to use it without sql or get proper error message.

Fixes #34/35 for the most part.

I'm using an updated lualdap from https://github.com/mwild1/lualdap - the 
iterator returned from search seemed to fail unless given a table.

hi have prosody 0.9.2 and lib event enabled and offline_email work for first 
but after crash with 

Jan 23 06:59:18 general error   Top-level error, please report:
...sody-modules/mod_offline_email/mod_offline_email.lua:68: attempt to 
concatenate a nil value
Jan 23 06:59:18 general error
stack traceback:
        /usr/bin/prosody:1: in function 'loop'
        /usr/lib/prosody/net/server_event.lua:786: in function </usr/lib/prosody/net/server_event.lua:785>
        [C]: in function 'xpcall'
        /usr/bin/prosody:372: in function 'loop'
        /usr/bin/prosody:402: in main chunk
        [C]: ?

I was not receiving s2s messages from my friend's server.  Turned off 
mod_archive and it started working.  This was in the log file:

Oct 07 16:35:11 xmppserver_listener error   Traceback[s2s]: mod_archive.lua:415: 
attempt to call field 'compare' (a nil value): stack traceback:
    /usr/lib/prosody/net/xmppserver_listener.lua:51: in function 'compare'
    mod_archive.lua:415: in function 'match_jid'
    mod_archive.lua:715: in function 'find_pref'
    mod_archive.lua:744: in function 'apply_pref'
    mod_archive.lua:766: in function '?'
    /usr/lib/prosody/util/events.lua:79: in function 'fire_event'
    /usr/lib/prosody/core/stanza_router.lua:152: in function 'core_post_stanza'
    /usr/lib/prosody/core/stanza_router.lua:100: in function 'core_process_stanza'
    /usr/lib/prosody/net/xmppserver_listener.lua:56: in function </usr/lib/prosody/net/xmppserver_listener.lua:56>
    [C]: in function 'xpcall'
    /usr/lib/prosody/net/xmppserver_listener.lua:56: in function 'cb_handlestanza'
    /usr/lib/prosody/core/xmlhandlers.lua:119: in function </usr/lib/prosody/core/xmlhandlers.lua:109>
    [C]: in function 'parse'
    /usr/lib/prosody/net/xmppserver_listener.lua:83: in function 'data'
    /usr/lib/prosody/net/xmppserver_listener.lua:157: in function 'onincoming'
    /usr/lib/prosody/net/server_event.lua:623: in function </usr/lib/prosody/net/server_event.lua:588>
    [C]: in function 'loop'
    /usr/lib/prosody/net/server_event.lua:802: in function </usr/lib/prosody/net/server_event.lua:801>
    [C]: in function 'xpcall'
    /usr/bin/prosody:394: in function 'loop'
    /usr/bin/prosody:461: in main chunk
    [C]: ?

What steps will reproduce the problem?
1. block a user
2. XEP says "When the user blocks communications with the contact, the user's 
server MUST send unavailable presence information to the contact"
3. prosody does not send the unavailable presence

What version of the product are you using? On what operating system?

prosody 0.9 (quite old nightly) and latest mod_blocking

1. IRC users don't see other participants
2. Prosody doesn't handle sudden disconnects
3. In addition to 2:
May 13 09:04:32 general error   Top-level error, please report:
mod_ircd.lua:159: attempt to concatenate a nil value
May 13 09:04:32 general error   
stack traceback:
    mod_ircd.lua:159: in function 'component'
    /usr/lib/prosody/core/componentmanager.lua:70: in function
'component_handle_stanza'
    /usr/lib/prosody/core/stanza_router.lua:156: in function 'core_post_stanza'
    muc/mod_muc.lua:38: in function 'route_stanza'
    muc/muc.lib.lua:844: in function '_route_stanza'
    muc/muc.lib.lua:198: in function 'send_history'
    muc/muc.lib.lua:360: in function 'handle_to_occupant'
    muc/muc.lib.lua:714: in function 'handle_stanza'
    muc/mod_muc.lua:123: in function 'component'
    /usr/lib/prosody/core/componentmanager.lua:70: in function
'component_handle_stanza'
    /usr/lib/prosody/core/stanza_router.lua:156: in function 'core_post_stanza'
    /usr/lib/prosody/core/stanza_router.lua:100: in function 'core_process_stanza'
    mod_ircd.lua:75: in function '?'
    mod_ircd.lua:33: in function 'data'
    mod_ircd.lua:45: in function <mod_ircd.lua:16>
    (tail call): ?
    /usr/lib/prosody/net/server_select.lua:823: in function
</usr/lib/prosody/net/server_select.lua:808>
    [C]: in function 'xpcall'
    /usr/lib/prosody/../../bin/prosody:387: in function 'loop'
    /usr/lib/prosody/../../bin/prosody:453: in main chunk
    [C]: ?

What steps will reproduce the problem?
1. Use lua-pam from repository
2. Realize auth is not working

What is the expected output? What do you see instead?
Auth working

What version of the product are you using? On what operating system?
0.9.1 on Debian Linux

Please provide any additional information below.
lua-pam changed the constant names. Therefore ``pam.PAM_PROMPT_ECHO_OFF`` 
should become ``pam.PROMPT_ECHO_OFF`` and ``pam.PAM_SUCCESS`` should become 
``pam.SUCCESS``. Applying these changes fixes the issue and auth works again.

If interested, I can provide a pull request or something.

Please provide a user list or a list where you list users filtered by search 
criteria.

I think this would be very useful for admin tasks to perform.

What steps will reproduce the problem?

1. Assume that default save mode is 'body'.

<iq type='result' id='pref1' to='[email protected]/chamber'>
  <pref xmlns='urn:xmpp:archive'>
    <default otr='concede' save='body'/>
    ...
  </pref>
</iq>

2. Create session settings with 'false' save mode.

<iq type='set' id='pref2'>
  <pref xmlns='urn:xmpp:archive'>
    <session thread='ffd707' save='false'/>
  </pref>
</iq>

3. Send message with thread specified:

<message to='[email protected]/chamber'>
 <thread>ffd707</thread>
 <body>Hi!</body>
</message>

What is the expected output?

Message must not be saved.

What do you see instead?

msg_handler searches for the rule for the "<thread>ffd70</thread>" session.
So message will be saved.

What version of the product are you using? On what operating system?

Last from prosody-modules.

Please provide any additional information below.