Comment on How to install and configure Jabber Server (Ejabberd) on Debian Lenny GNU / Linux by hip0.
One other Jabber helpful command is the cmd to check all logged in usernames on ejabberd:
This is done with ejabberdctl
ejabberdctl connected-users
georgi.georgiev@jabber.myserver.com/33452567231325714453446703
….
etc.
hip0 Also Commented
How to install and configure Jabber Server (Ejabberd) on Debian Lenny GNU / Linux
For those who want to access it via Mobile Phone be it Android or IOS, here is a list of some clients you might consider with support for ORT encryption.
Xabber, IM+ , AstraChat, Bruno the Jabber Bear, Salut à Toi, Tigase Messenger, Zom
How to install and configure Jabber Server (Ejabberd) on Debian Lenny GNU / Linux
If your jabber init script /etc/init.d/ejabberd start is failing to launch ejabberd, once all is configured as explained in the article, you’ll have to check your firewall rules, you will need to have allowed for connection as a minimum following rules add them to your firewall init script and then try again. Another thing to check whether it is the firewall causing ejabberd to malfunction, just stop the firewall for a short time and relaunch ejabberd:
-A INPUT -s 127.0.0.1/32 -p tcp -m tcp –dport 5222 -j ACCEPT
-A INPUT -s 127.0.0.1/32 -p tcp -m tcp –dport 5223 -j ACCEPT
-A INPUT -s 127.0.0.1/32 -p tcp -m tcp –dport 4369 -j ACCEPT
-A INPUT -s 127.0.0.1/32 -p tcp -m tcp –dport 5269 -j ACCEPT
-A INPUT -s 127.0.0.1/32 -p tcp -m tcp –dport 5280 -j ACCEPT
A INPUT -p tcp -m tcp –dport 5222 -j ACCEPT
-A INPUT -p tcp -m tcp –dport 5223 -j ACCEPT
-A INPUT -p tcp -m tcp –dport 4369 -j ACCEPT
-A INPUT -p tcp -m tcp –dport 5269 -j ACCEPT
-A INPUT -p tcp -m tcp –dport 5280 -j ACCEPT
-A INPUT -p udp -m udp –dport 5222 -j ACCEPT
-A INPUT -p udp -m udp –dport 5223 -j ACCEPT
-A INPUT -p udp -m udp –dport 4369 -j ACCEPT
-A INPUT -p udp -m udp –dport 5269 -j ACCEPT
-A INPUT -p udp -m udp –dport 5280 -j ACCEPT
How to install and configure Jabber Server (Ejabberd) on Debian Lenny GNU / Linux
Actually lately I prefer Gajim much more, because Pidgin is too much interactive for my console soul 🙂
Recent Comments by hip0
Install and configure rkhunter for improved security on a PCI DSS Linux / BSD servers with no access to Internet
–rwo, –report-warnings-only
This option causes only warning messages to be displayed. This can be useful when rkhunter is run via cron. Other options may
be used to force other items of information to be displayed.
–sk, –skip-keypress
When the –check command option is used, after certain sections of tests, the user will be prompted to press the return key
in order to continue. This option disables that feature, and rkhunter will run until all the tests have completed.
Install and configure rkhunter for improved security on a PCI DSS Linux / BSD servers with no access to Internet
As rkhunter check, can be pretty annoying and ask you to press keypresses multiple times and spit you a lot of unnecessery data a very good useful option arguments are:
–rwo and –sk
# rkhunter -c –rwo –sk
Warning: The SSH and rkhunter configuration options should be the same:
SSH configuration option 'PermitRootLogin': yes
Rkhunter configuration option 'ALLOW_SSH_ROOT_USER': no
Sorry for really late reply.
perhaps you have to create it or rename the ifcfg-eno1 to ifcfg-eth1 or you have some old ifcfg-enp1s0f0 or ifcfg-eno still under /etc/sysconfig/network-scripts/ interfering
How to RPM update Hypervisors and Virtual Machines running Haproxy High Availability cluster on KVM, Virtuozzo without a downtime on RHEL / CentOS Linux
if you happen to be missing versionlock plugin and you need to get use of it
yum versionlock capabilities
You will have to install yum-utils package:
For example on CentOS 8 Linux, to enable the yum versionlock plugiun
yum install yum-utils.noarch
In case if by default log is not configured for snoopy,
these are default output locations on various Linux distributions:
Distribution | Snoopy output location | Notes |
---|---|---|
CentOS |
/var/log/secure
|
|
Debian |
/var/log/auth.log
|
|
Ubuntu |
/var/log/auth.log
|
|
(others) |
/var/log/messages
|
(potentially, could be elsewhere) |