2014-02-23

‎More Resources

← Older revision

Revision as of 14:08, 23 February 2014

(3 intermediate revisions by one user not shown)

Line 159:

Line 159:

 

* '''Check for known issues'''<br>Look at the [http://prosody.im/doc/release release notes] for your Prosody version to see if your issue is listed as a known issue. Also check the [http://code.google.com/p/lxmppd/issues/list issue tracker] to see if your issue has already been reported.

 

* '''Check for known issues'''<br>Look at the [http://prosody.im/doc/release release notes] for your Prosody version to see if your issue is listed as a known issue. Also check the [http://code.google.com/p/lxmppd/issues/list issue tracker] to see if your issue has already been reported.

 

* '''Check configuration syntax'''<br>Run {{Ic|luac -p /etc/prosody/prosody.cfg.lua}} to check for any syntax errors in your configuration file. If there is no output your syntax is fine.

 

* '''Check configuration syntax'''<br>Run {{Ic|luac -p /etc/prosody/prosody.cfg.lua}} to check for any syntax errors in your configuration file. If there is no output your syntax is fine.



* '''Check the log
files
'''<br>
Log files are located in {{ic|/var/log/prosody}}.
Errors are only logged if there is a critical problem so always address those issues. If you think you have a very low level issue (like protocol compatibility between clients and servers with Prosody) then you can enable the very verbose debug level logging
. The default configuration file has commented out lines to log debug messages to {{ic|prosody.debug}}
.

+

* '''Check the log'''<br>Errors are only logged if there is a critical problem so always address those issues. If you think you have a very low level issue (like protocol compatibility between clients and servers with Prosody) then you can enable the very verbose debug level logging.

 

* '''Check permissions'''<br>The Prosody package should add a new {{Ic|prosody}} user and group to your system and set appropriate permissions, but it is always good to double check. Ensure that {{ic|/etc/prosody}} and {{ic|/var/lib/prosody}} are owned by the {{Ic|prosody}} user and that the user has appropriate permissions to read and write to those paths and all contained files.

 

* '''Check permissions'''<br>The Prosody package should add a new {{Ic|prosody}} user and group to your system and set appropriate permissions, but it is always good to double check. Ensure that {{ic|/etc/prosody}} and {{ic|/var/lib/prosody}} are owned by the {{Ic|prosody}} user and that the user has appropriate permissions to read and write to those paths and all contained files.

 

* '''Check listening ports'''<br>When troubleshooting connection issues make sure that Prosody is actually listening for connections. You may do so by running {{Ic|ss -tul}} and making sure that {{Ic|xmpp-client}} (port 5222) and {{Ic|xmpp-server}} (port 5269) are listed.

 

* '''Check listening ports'''<br>When troubleshooting connection issues make sure that Prosody is actually listening for connections. You may do so by running {{Ic|ss -tul}} and making sure that {{Ic|xmpp-client}} (port 5222) and {{Ic|xmpp-server}} (port 5269) are listed.



* '''Restart'''<br>Like most things, it doesn't hurt to restart Prosody ({{Ic|
/etc/rc.d/prosody
restart}}) to see if it resolves an issue.

+

* '''Restart'''<br>Like most things, it doesn't hurt to restart Prosody ({{Ic|
systemctl
restart
prosody
}}) to see if it resolves an issue.

 

 

 

If you're unable to resolve your issue yourself there are a variety of resources you can use to seek help. In order of immediacy with which you'll likely receive help:

 

If you're unable to resolve your issue yourself there are a variety of resources you can use to seek help. In order of immediacy with which you'll likely receive help:

Line 172:

Line 172:

 

==Development==

 

==Development==

 

 



===Change Log===

 



You may view the change log of the Prosody package by issuing the following command:

 



 



{{Ic|$ pacman -Qc prosody}}

 



 



===Packages===

 

 

Two development packages are maintained for Prosody in the AUR, {{AUR|prosody-devel}} and {{AUR|prosody-hg]}}. {{Ic|prosody-devel}} tracks the latest source release of a development version (alpha, beta, release candidate) and will actually be behind the stable version if a final version of the development version is released. {{Ic|prosody-hg}} tracks the [http://www.selenic.com/mercurial/wiki/ Mercurial] repository tip for Prosody and will always contain the latest code as it is checked in. Both packages are built similarly to the stable package.

 

Two development packages are maintained for Prosody in the AUR, {{AUR|prosody-devel}} and {{AUR|prosody-hg]}}. {{Ic|prosody-devel}} tracks the latest source release of a development version (alpha, beta, release candidate) and will actually be behind the stable version if a final version of the development version is released. {{Ic|prosody-hg}} tracks the [http://www.selenic.com/mercurial/wiki/ Mercurial] repository tip for Prosody and will always contain the latest code as it is checked in. Both packages are built similarly to the stable package.

 

 



==More Resources==

+

==Communication==



===Development===

+



* [http://code.google.com/p/lxmppd/issues/list Issue Tracker]

+



* [http://prosody.im/source/browse/ Source Repository]

+



* [http://code.google.com/p/prosody-modules/ Prosody Modules] (Non-Core Modules)

+



 

+



===Documentation===

+



* [http://prosody.im/doc/faq Frequently Asked Questions]

+



* [http://prosody.im/doc/troubleshooting Troubleshooting Guide]

+



* [http://prosody.im/doc/xeplist XEP Support List]

+



* [http://prosody.im/doc/modules Module List]

+



 

+



=
==Communication
=
==

+

 

* Mailing Lists: [http://groups.google.co.uk/group/prosody-dev prosody-dev], [http://groups.google.co.uk/group/prosody-users prosody-users]

 

* Mailing Lists: [http://groups.google.co.uk/group/prosody-dev prosody-dev], [http://groups.google.co.uk/group/prosody-users prosody-users]

 

* Conference: {{Ic|prosody@conference.prosody.im}}

 

* Conference: {{Ic|prosody@conference.prosody.im}}

 

* Blog: [http://blog.prosody.im/ Prosodical Thoughts]

 

* Blog: [http://blog.prosody.im/ Prosodical Thoughts]



 



===Social===

 



* [http://freshmeat.net/projects/prosody Freshmeat]

 



* [http://identi.ca/group/prosody Identi.ca]

 



* [http://www.ohloh.net/p/prosody Ohloh]

 

 

 

 

== See also ==

 

== See also ==

Show more