#1049 mod_pep_plus: failure to write to activity and mood storage
Reporter
kartoffelsalat.ddns.net
Owner
Zash
Created
Updated
Stars
★ (1)
Tags
Priority-Medium
Type-Defect
Status-WontFix
kartoffelsalat.ddns.net
on
It seems that gajim is aksing for pep storages that mod_pep_plus does not offer?
What do you see instead?
```
Dec 02 11:58:12 datamanager error Unable to write to pep_http://jabber.org/protocol/activity storage ('/var/lib/prosody/server%2etld/pep_http://jabber.org/protocol/activity/user.list~: No such file or directory' in <nil>) for user: user@server.tld
Dec 02 11:58:12 server.tld:pep_plus error Unable to set item: /var/lib/prosody/server%2etld/pep_http://jabber.org/protocol/activity/user.list~: No such file or directory
Dec 02 11:58:12 mod_c2s error Traceback[c2s]: /home/pi/prosody-modules/mod_pep_plus/pubsub.lib.lua:31: bad argument #1 to 't_unpack' (table expected, got nil)
stack traceback:
[C]: in function 't_unpack'
/home/pi/prosody-modules/mod_pep_plus/pubsub.lib.lua:31: in function 'pubsub_error_reply'
/home/pi/prosody-modules/mod_pep_plus/pubsub.lib.lua:305: in function 'handler'
/home/pi/prosody-modules/mod_pep_plus/pubsub.lib.lua:118: in function </home/pi/prosody-modules/mod_pep_plus/pubsub.lib.lua:105>
(tail call): ?
/usr/lib/prosody/util/events.lua:78: in function </usr/lib/prosody/util/events.lua:74>
(tail call): ?
(tail call): ?
/usr/lib/prosody/modules/mod_iq.lua:38: in function '?'
/usr/lib/prosody/util/events.lua:78: in function </usr/lib/prosody/util/events.lua:74>
...
[C]: in function 'parse'
/usr/lib/prosody/util/xmppstream.lua:271: in function 'feed'
/usr/lib/prosody/modules/mod_c2s.lua:258: in function 'data'
/usr/lib/prosody/modules/mod_c2s.lua:281: in function </usr/lib/prosody/modules/mod_c2s.lua:278>
(tail call): ?
/usr/lib/prosody/net/server_select.lua:879: in function </usr/lib/prosody/net/server_select.lua:861>
[C]: in function 'xpcall'
/usr/bin/prosody:400: in function 'loop'
/usr/bin/prosody:431: in main chunk
[C]: ?
Dec 02 11:58:15 datamanager error Unable to write to pep_http://jabber.org/protocol/mood storage ('/var/lib/prosody/server%2etld/pep_http://jabber.org/protocol/mood/user.list~: No such file or directory' in <nil>) for user: user@server.tld
Dec 02 11:58:15 server.tld:pep_plus error Unable to set item: /var/lib/prosody/server%2etld/pep_http://jabber.org/protocol/mood/user.list~: No such file or directory
Dec 02 11:58:15 mod_c2s error Traceback[c2s]: /home/pi/prosody-modules/mod_pep_plus/pubsub.lib.lua:31: bad argument #1 to 't_unpack' (table expected, got nil)
stack traceback:
[C]: in function 't_unpack'
/home/pi/prosody-modules/mod_pep_plus/pubsub.lib.lua:31: in function 'pubsub_error_reply'
/home/pi/prosody-modules/mod_pep_plus/pubsub.lib.lua:305: in function 'handler'
/home/pi/prosody-modules/mod_pep_plus/pubsub.lib.lua:118: in function </home/pi/prosody-modules/mod_pep_plus/pubsub.lib.lua:105>
(tail call): ?
/usr/lib/prosody/util/events.lua:78: in function </usr/lib/prosody/util/events.lua:74>
(tail call): ?
(tail call): ?
/usr/lib/prosody/modules/mod_iq.lua:38: in function '?'
/usr/lib/prosody/util/events.lua:78: in function </usr/lib/prosody/util/events.lua:74>
...
[C]: in function 'parse'
/usr/lib/prosody/util/xmppstream.lua:271: in function 'feed'
/usr/lib/prosody/modules/mod_c2s.lua:258: in function 'data'
/usr/lib/prosody/modules/mod_c2s.lua:281: in function </usr/lib/prosody/modules/mod_c2s.lua:278>
(tail call): ?
/usr/lib/prosody/net/server_select.lua:879: in function </usr/lib/prosody/net/server_select.lua:861>
[C]: in function 'xpcall'
/usr/bin/prosody:400: in function 'loop'
/usr/bin/prosody:431: in main chunk
[C]: ?
```
I'm running prosody on a raspberry, raspbian.
```
> prosodyctl about
Prosody 0.10 nightly build 450 (2017-11-22, 7ea3311ca632)
# Prosody directories
Data directory: /var/lib/prosody
Config directory: /etc/prosody
Source directory: /usr/lib/prosody
Plugin directories:
/home/pi/prosody-modules - prosody-modules rev: 3ba8fd1a297e
/usr/lib/prosody/modules/
# 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/arm-linux-gnueabihf/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.6.2
lxp: LuaExpat 1.3.0
socket: LuaSocket 3.0-rc1
ssl: 0.5.PR
```
Zash
on
Turns out it depends on more changes that are only available in trunk. Since the module is included with trunk already, and that keeping an outdated version in prosody-modules is only going to cause confusion and problems, I'm going to remove it.
So, the way to test bleeding edge trunk-only features will be to run trunk.
It seems that gajim is aksing for pep storages that mod_pep_plus does not offer? What do you see instead? ``` Dec 02 11:58:12 datamanager error Unable to write to pep_http://jabber.org/protocol/activity storage ('/var/lib/prosody/server%2etld/pep_http://jabber.org/protocol/activity/user.list~: No such file or directory' in <nil>) for user: user@server.tld Dec 02 11:58:12 server.tld:pep_plus error Unable to set item: /var/lib/prosody/server%2etld/pep_http://jabber.org/protocol/activity/user.list~: No such file or directory Dec 02 11:58:12 mod_c2s error Traceback[c2s]: /home/pi/prosody-modules/mod_pep_plus/pubsub.lib.lua:31: bad argument #1 to 't_unpack' (table expected, got nil) stack traceback: [C]: in function 't_unpack' /home/pi/prosody-modules/mod_pep_plus/pubsub.lib.lua:31: in function 'pubsub_error_reply' /home/pi/prosody-modules/mod_pep_plus/pubsub.lib.lua:305: in function 'handler' /home/pi/prosody-modules/mod_pep_plus/pubsub.lib.lua:118: in function </home/pi/prosody-modules/mod_pep_plus/pubsub.lib.lua:105> (tail call): ? /usr/lib/prosody/util/events.lua:78: in function </usr/lib/prosody/util/events.lua:74> (tail call): ? (tail call): ? /usr/lib/prosody/modules/mod_iq.lua:38: in function '?' /usr/lib/prosody/util/events.lua:78: in function </usr/lib/prosody/util/events.lua:74> ... [C]: in function 'parse' /usr/lib/prosody/util/xmppstream.lua:271: in function 'feed' /usr/lib/prosody/modules/mod_c2s.lua:258: in function 'data' /usr/lib/prosody/modules/mod_c2s.lua:281: in function </usr/lib/prosody/modules/mod_c2s.lua:278> (tail call): ? /usr/lib/prosody/net/server_select.lua:879: in function </usr/lib/prosody/net/server_select.lua:861> [C]: in function 'xpcall' /usr/bin/prosody:400: in function 'loop' /usr/bin/prosody:431: in main chunk [C]: ? Dec 02 11:58:15 datamanager error Unable to write to pep_http://jabber.org/protocol/mood storage ('/var/lib/prosody/server%2etld/pep_http://jabber.org/protocol/mood/user.list~: No such file or directory' in <nil>) for user: user@server.tld Dec 02 11:58:15 server.tld:pep_plus error Unable to set item: /var/lib/prosody/server%2etld/pep_http://jabber.org/protocol/mood/user.list~: No such file or directory Dec 02 11:58:15 mod_c2s error Traceback[c2s]: /home/pi/prosody-modules/mod_pep_plus/pubsub.lib.lua:31: bad argument #1 to 't_unpack' (table expected, got nil) stack traceback: [C]: in function 't_unpack' /home/pi/prosody-modules/mod_pep_plus/pubsub.lib.lua:31: in function 'pubsub_error_reply' /home/pi/prosody-modules/mod_pep_plus/pubsub.lib.lua:305: in function 'handler' /home/pi/prosody-modules/mod_pep_plus/pubsub.lib.lua:118: in function </home/pi/prosody-modules/mod_pep_plus/pubsub.lib.lua:105> (tail call): ? /usr/lib/prosody/util/events.lua:78: in function </usr/lib/prosody/util/events.lua:74> (tail call): ? (tail call): ? /usr/lib/prosody/modules/mod_iq.lua:38: in function '?' /usr/lib/prosody/util/events.lua:78: in function </usr/lib/prosody/util/events.lua:74> ... [C]: in function 'parse' /usr/lib/prosody/util/xmppstream.lua:271: in function 'feed' /usr/lib/prosody/modules/mod_c2s.lua:258: in function 'data' /usr/lib/prosody/modules/mod_c2s.lua:281: in function </usr/lib/prosody/modules/mod_c2s.lua:278> (tail call): ? /usr/lib/prosody/net/server_select.lua:879: in function </usr/lib/prosody/net/server_select.lua:861> [C]: in function 'xpcall' /usr/bin/prosody:400: in function 'loop' /usr/bin/prosody:431: in main chunk [C]: ? ``` I'm running prosody on a raspberry, raspbian. ``` > prosodyctl about Prosody 0.10 nightly build 450 (2017-11-22, 7ea3311ca632) # Prosody directories Data directory: /var/lib/prosody Config directory: /etc/prosody Source directory: /usr/lib/prosody Plugin directories: /home/pi/prosody-modules - prosody-modules rev: 3ba8fd1a297e /usr/lib/prosody/modules/ # 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/arm-linux-gnueabihf/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.6.2 lxp: LuaExpat 1.3.0 socket: LuaSocket 3.0-rc1 ssl: 0.5.PR ```
Turns out it depends on more changes that are only available in trunk. Since the module is included with trunk already, and that keeping an outdated version in prosody-modules is only going to cause confusion and problems, I'm going to remove it. So, the way to test bleeding edge trunk-only features will be to run trunk.
Changes