#1074 syslog runs over

Reporter bug
Owner Zash
Created
Updated
Stars ★ (1)  
Tags
  • Status-Invalid
  • Type-Defect
  • Priority-Medium
  1. bug on

    What version of the product are you using? On what operating system? Package: prosody-0.10 Version: 1nightly459-1~stretch Architecture: amd64 Debian stretch This loop into the syslog: Jan 29 17:34:59 jabber prosody[141]: jabber.systron.de:mam: Archiving stanza: <message id='44fa7527-85bb-4791-b22d-5dd7be65a7df' type='chat' to='rag@jabber.systron.de' from='rag@jabber.systron.de/Gajim'> Jan 29 17:34:59 jabber prosody[141]: sql: SQL transaction begin [function(mod_storage_sql.lua:228)] Jan 29 17:34:59 jabber prosody[141]: sql: SQL transaction success [function(mod_storage_sql.lua:228)] Jan 29 17:34:59 jabber prosody[141]: sql: SQL transaction begin [function(mod_storage_sql.lua:57)] Jan 29 17:34:59 jabber prosody[141]: sql: SQL transaction success [function(mod_storage_sql.lua:57)] Jan 29 17:34:59 jabber prosody[141]: jabber.systron.de:mam: rag's rule for rag@jabber.systron.de is nil Jan 29 17:34:59 jabber prosody[141]: jabber.systron.de:mam: rag's default rule is true

  2. Zash on

    There is nothing in this log snippet that suggests anything is wrong with the server. All it shows is that the client (Gajim, judging from the resource) is sending a message to their own account, and Prosody receives and archives it. If this is repeating, then I would suggest attempting to debug the client or reporting this issue to the clients issue tracker. If you are concerned about log files growing too large, look into logrotate. Since nothing here suggests a problem in Prosody, I'm closing this issue. If you find evidence of a problem in Prosody, feel free to re-open this or report a new issue.

    Changes
    • owner Zash
    • tags Status-Invalid

New comment

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