maranda / metronome Goto Github PK

This will be useful.

Self explanative let room owners decide either to enable limiting or not in a room, and limit ratio also.

This allows full Stream Management for Client-to-Server Streams and Stanza Acknowledgement for Server-to-Server ones.

See this.

Recommended Order of Stream Feature Negotiation.

Put on par with mod_c2s for this.

As the pubsub nodes 'emselved may be persisted to disk but the list may not.

This deeply interferes with SASL External c2s wise,
It was a counter, compatibility measure to help s2s interoperability with servers which had invalid certificates without assigned purpose or client purpose instead of server purpose.

hi
i'm trying to intall with
./configure --prefix=/usr
after make make install i do metronome start
and i got few messages on /usr/local/lib/metronome/util/events.lua that cannot be started
so i think that there's a hardlink to this util lib and maybe should be somehow changed
after i've put whole /usr/lib/metronome into /usr/local/lib i got it working, but it's not a real deal

This should help conserve some memory, and also fix the annoying issue with ghosts when remote servers for any reason fail to broadcast the (unavailable) presence states of the user.

Rework the cipher list and ssl default options if the OpenSSL version is suitable for the task and leaves a wide enough ciphers' suite.

It should effectively return the last x messages with the specified jid but currently will just subset the last 50 messages in the archive and return entries with jid if they're in the said subset.

Not doing this could cause unwanted layovers to stay for what regards node recipients.

Rework the executable to allow specifying through configuration which libraries to pre-load before the global state is initialized.

Self explanative, let server owners eventually set a max size in bytes to vCards submitted by users.

In accordance with Section 3.2.2.1 of XML Schema Part 2: Datatypes, the form must support false and true lexical forms.

Implement SASL mechanism (c2s wise) to perform passwordless certificate authentication for clients which support that.

Improve by merging in mod_discoitems functionality and also by performing items' caching.

This will improve user experience a lot.

I think this is desiderable when a service supports items and nodes' persistence.

• Fix logging statements
• Fix logic to determine wheter there're more results or not
• Various code fixes

So an event handler isn't required, and it doesn't depend on events.

This will allow to let users limit access to a node only to 'emselves without implementing affiliations nor the whitelist access model.

Implement XEP-309 and consequentially XEP-267.

Fixes a leak of old session archives within the memory cache.

Old, discouraged and deprecated in the new XMPP rfc set.

This allows to query a node for extended service discovery informations.

See MattJ's comment.

This will prove useful and a first actual use of mod_server_presence outside listing scopes.

This affects both mod_disco and hostmanager.

Problem : when my ISP box isn't sycnhronized, my internet connexion doesn't work.
Then, my box resynchronized after 4 seconds of waiting.

But metronome disconnect… and doesn't reconnect automatically ; I must restart my xmpp server…

To my experience, I know that Prosody automatically reconnect, and apache too.
So can you correct it please

Thanks,
Kcchouette

metronomectl start

general error The version of LuaExpat on your system leaves Metronome vulnerable to denial-of-service attacks. You should upgrade to LuaExpat 1.1.1 or higher as soon as possible. See http://prosody.im/doc/depends#luaexpat for more information.
lua: /usr/share/lua/5.1/ssl.lua:29: bad argument #3 to 'func' (string expected, got boolean)
stack traceback:
[C]: in function 'func'
/usr/share/lua/5.1/ssl.lua:29: in function 'optexec'
/usr/share/lua/5.1/ssl.lua:78: in function 'ssl_newcontext'
/usr/lib/metronome/core/certmanager.lua:80: in function 'create_context'
/usr/lib/metronome/../../bin/metronome:247: in function 'init_global_state'
/usr/lib/metronome/../../bin/metronome:385: in main chunk
[C]: ?
Still waiting...
Metronome is still not running. Please give it some time or check your log files for errors.

Optimize GC'ing further to reduce allocated memory by the server process.

Add a proper iterator to not have a configuration form with a scrambled ugly order, at the very least.

Very useful for WSAPI Apps, where those are already appended.

I've installed metronome by cloning with git:
git clone https://github.com/maranda/metronome.git

Here is the result:

$ make upgrade

• This target calls hg pull -u, make clean, make all and sudo make install.
• Please remember that you may have to reload the changed modules and / or
• restart Metronome after.

hg pull -u

make: hg: Command not found

make: *** [upgrade] Error 127

Perform some auto-detection.

This is very useful to prevent users to use sensible node names for the JID address they want to register (e.g. support, admin and such).

The prototype doesn't work, rectify using the new API/structure changes.

Passed a boolean instead of the jid.

Add logic in both usermanager and mod_roster to correctly broadcast presence of type unsubscribe/d to the deleted user roster's contacts before the account is actually discarded.

• Have usermanager fire pre-user deletion event
• Have mod_roster hook to the above event and broadcast unsubscribe
• Completely remove code dealing with this task from mod_register

Sort out a few errors in the code which were ulimately uncaught and are ultimately very nasty.
This was caught after release, reopening milestone... le sigh

I recently speak with you of a problem with a pop-up window when my account is loading.
I use a JID providing by a metronome server (@devosi.org) and join one chat : [email protected] (so a metronome chatroom)

The problem isn't a unique case : mario_26, and checkpoint have this bug too.

So I join two screenshot of the windows.

Thank you to fix this bug or tell me how to disable the pop-up…

Kcchouette

Screenshot of the 04/11/2013

Screenshot of the 06/11/2013

EDIT : Some information → metronome version is a hg version, according to my host ;
Checkpoint has an other pop-up windows :

sorry for bothering
just tried to implement sql auth as it is described in prosody
i got new tables in my database after that (it makes it from template), but no users created and no activity in debug logs
i've set storage = "sql" and no difference
is it disabled?
also it would be nice to have hashing for user\pass in sql but there's no such option
and i'm running in daemon now and see
'cannot open /var/lib/metronome/realm/roster/user.dat: No such file or directory')
for privacy, offline and private , so it's not using sql at all

and looks like i found some more

host 'realm' now set to use user provider 'internal_plain'
datamanager debug Assuming empty server_presence storage ('cannot open /var/lib/metronome/realm/server_presence/outbound.dat: No such file or directory') for user: outbound@realm
datamanager debug Assuming empty server_presence storage ('cannot open /var/lib/metronome/realm/server_presence/pending.dat: No such file or directory') for user: pending@realm
datamanager debug Assuming empty server_presence storage ('cannot open /var/lib/metronome/realm/server_presence/subscribed.dat: No such file or directory') for user: subscribed@realm
hostmanager debug Activated host: room.realm
datamanager debug Assuming empty directory storage ('cannot open /var/lib/metronome/room.realm/directory/store.dat: No such file or directory') for user: [email protected]

datamanager debug Assuming empty pubsub storage ('cannot open /var/lib/metronome/pub.realm/pubsub.dat: No such file or directory') for user: [email protected]
hostmanager debug Activated host: status.realm
hostmanager debug Activated host: chat.realm
datamanager debug Assuming empty persistent storage ('cannot open /var/lib/metronome/chat.realm/persistent.dat: No such file or directory') for user: [email protected]

looks like it should be created somehow not sure when
those setting mostly from config file.
in my realm name i got . realm.name and it is changed to ' %2e' for directories that's the only odd thing and it is stored in /var/lib/metronome/realm%2ename

i've added "storage_sql" in module load, looks like it's not taking sql settings from main part and actually something
i've changed name from localhost to 127.0.0.1 with no luck - no connection to the server
/usr/lib/metronome/core/modulemanager.lua:30: in function </usr/lib/metronome/core/modulemanager.lua:30>
[C]: in function 'assert'
/usr/lib/metronome/modules/mod_storage_sql.lua:158: in main chunk
(tail call): ?
[C]: in function 'xpcall'
/usr/lib/metronome/core/modulemanager.lua:30: in function 'pcall'
/usr/lib/metronome/core/modulemanager.lua:159: in function 'do_load_module'
/usr/lib/metronome/core/modulemanager.lua:232: in function 'load'

it is the same connection settings that i got for jabberd2 on this machine
the problem was in md5 auth method and it not recognizes localhost only 127.0.0.1.

now when user is registering i got failed to write data to disk in client
and [c2s_unauthed]: on server debug
looks like there's no table "metronome" to where this should be written
and in mod_auth_sql they are using authreg table, so maybe this is somehow related.

This will prevent stale s2s connections and "Luasocket" ghosts, saving a further bit of system resources from being consumed.

Old, not up to date, very partial, buggy...
and also I do not wish to work on it.

This was a longtime outstanding bug... which I didn't manage to caught until now.

The new session object is not supposed to be indexed to get that value.

not sure if this is a real issue maybe just a wrong behaviour for my installation

i'm starting under metronome:metronome and i've tried to register account with plain
it tries to create realm/accounts/user file but for /var/lib/metronome user is set to root:root

This is a long standing change, currently the code for both mod_muc_log and mod_muc_log_http is highly inefficent.

Expecially in mod_muc_log_http where the use of Luaexpat LOM parsing increases RES usage abominously (to generate a page from a 800 kilobytes log requires 50 MiBs!!!).

SM pre-resource-unbind hook returns in case the session is hibernating, this prevents the MAM store to be properly saved and could cause new messages to be garbage collected on resumption.