Koozali.org: home of the SME Server

Deployment Internal Chat with SME Server 7.4

Offline magwm

  • *
  • 159
  • +0/-0
  • SmeLover
    • Gadis Tourist Service Italia SRL
Re: Deployment Internal Chat with SME Server 7.4
« Reply #15 on: May 18, 2009, 09:59:41 AM »
Hello Stefano, english is somewhat easier for me but i'll drop by.. with the same question..
And yes I know this is beta, well I hope just the smeserver part is beta, the jabberserver is ok isnt it?  I am trying this on a box that does just do proxying/dansguardian for our company.. just hope it won't interfere.

anyway:  ps aux |egrep jab   gives this

Code: [Select]
root      2425  0.0  0.0    20   20 ?        Ss   May14   3:17 runsv ejabberd
smelog    2463  0.1  0.1  1864  320 ?        S    May14   6:07 /usr/local/bin/multilog t s5000000 /var/log/ejabberd.run
ejabberd  3933  0.0  0.0  2580  160 ?        S    May14   0:00 /usr/lib/erlang/erts-5.5.2/bin/epmd -daemon
ejabberd 10604  0.0  4.3 24940 11060 ?       Sl   09:46   0:00 /usr/lib/erlang/erts-5.5.2/bin/beam -K false -P 250000 -- -root /usr/lib/erlang -progname erl -- -home /var/lib/ejabberd -pa /usr/lib/ejabberd/ebin -noshell -noinput -smp auto -sname ejabberd -mnesia dir "/var/lib/ejabberd/spool" -kernel inetrc "//etc/ejabberd/inetrc" -s ejabberd -ejabberd config "/etc/ejabberd/ejabberd.cfg" log_path "/var/log/ejabberd/ejabberd.log" -sasl sasl_error_logger {file,"/var/log/ejabberd/sasl.log"}
root     10623  0.0  0.2  4876  616 pts/0    R+   09:46   0:00 egrep jab

then the user has been created (I did it with the user manager):
Code: [Select]
ejabberd:x:5046:5046:erling jabberdaemon:/home/e-smith/files/users/ejabberd:/usr/bin/rssh
then netstat gives
Code: [Select]
[root@mailtampone ~]# netstat -napt
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address               Foreign Address             State       PID/Program name
tcp        0      0 0.0.0.0:993                 0.0.0.0:*                   LISTEN      3542/tcpsvd
tcp        0      0 0.0.0.0:515                 0.0.0.0:*                   LISTEN      3618/lpd
tcp        0      0 0.0.0.0:995                 0.0.0.0:*                   LISTEN      3584/tcpsvd
tcp        0      0 0.0.0.0:548                 0.0.0.0:*                   LISTEN      4198/afpd
tcp        0      0 0.0.0.0:389                 0.0.0.0:*                   LISTEN      3694/slapd
tcp        0      0 0.0.0.0:3306                0.0.0.0:*                   LISTEN      4493/mysqld
tcp        0      0 0.0.0.0:139                 0.0.0.0:*                   LISTEN      4013/smbd
tcp        0      0 0.0.0.0:110                 0.0.0.0:*                   LISTEN      3566/tcpsvd
tcp        0      0 0.0.0.0:143                 0.0.0.0:*                   LISTEN      3527/tcpsvd
tcp        0      0 127.0.0.1:783               0.0.0.0:*                   LISTEN      2780/perl
tcp        0      0 0.0.0.0:80                  0.0.0.0:*                   LISTEN      2811/httpd
tcp        0      0 0.0.0.0:4369                0.0.0.0:*                   LISTEN      3933/epmd
tcp        0      0 0.0.0.0:465                 0.0.0.0:*                   LISTEN      3809/tcpsvd
tcp        0      0 127.0.0.1:980               0.0.0.0:*                   LISTEN      3798/httpd-admin
tcp        0      0 0.0.0.0:21                  0.0.0.0:*                   LISTEN      3770/tcpsvd
tcp        0      0 127.0.0.2:53                0.0.0.0:*                   LISTEN      3536/dnscache
tcp        0      0 192.168.0.80:53             0.0.0.0:*                   LISTEN      3508/dnscache
tcp        0      0 192.168.0.80:22             0.0.0.0:*                   LISTEN      3826/sshd
tcp        0      0 127.0.0.1:3128              0.0.0.0:*                   LISTEN      13056/squid
tcp        0      0 192.168.0.80:3128           0.0.0.0:*                   LISTEN      13056/squid
tcp        0      0 0.0.0.0:25                  0.0.0.0:*                   LISTEN      3789/perl
tcp        0      0 127.0.0.1:26                0.0.0.0:*                   LISTEN      2465/perl
tcp        0      0 0.0.0.0:443                 0.0.0.0:*                   LISTEN      2811/httpd
tcp        0      0 127.0.0.1:4700              0.0.0.0:*                   LISTEN      4190/cnid_metad
tcp        0      0 192.168.0.80:3128           192.168.0.49:1196           ESTABLISHED 13056/squid
tcp        0      0 192.168.0.80:37786          216.239.59.104:80           ESTABLISHED 13056/squid
tcp        0      0 192.168.0.80:3128           192.168.0.49:1194           ESTABLISHED 13056/squid
tcp        0      0 127.0.0.1:37336             127.0.0.1:37337             ESTABLISHED 13057/(squidGuard)
tcp        0      0 192.168.0.80:37787          194.183.88.60:80            ESTABLISHED 13056/squid
tcp        0      0 127.0.0.1:37337             127.0.0.1:37336             ESTABLISHED 13056/squid
tcp        0      0 127.0.0.1:37338             127.0.0.1:37339             ESTABLISHED 13058/(squidGuard)
tcp        0      0 192.168.0.80:37784          216.239.59.101:80           ESTABLISHED 13056/squid
tcp        0      0 127.0.0.1:37339             127.0.0.1:37338             ESTABLISHED 13056/squid
tcp        0      0 127.0.0.1:37340             127.0.0.1:37341             ESTABLISHED 13059/(squidGuard)
tcp        0      0 127.0.0.1:37341             127.0.0.1:37340             ESTABLISHED 13056/squid
tcp        0      0 127.0.0.1:37342             127.0.0.1:37343             ESTABLISHED 13060/(squidGuard)
tcp        0      0 127.0.0.1:37343             127.0.0.1:37342             ESTABLISHED 13056/squid
tcp        0      0 127.0.0.1:37344             127.0.0.1:37345             ESTABLISHED 13061/(squidGuard)
tcp        0      0 127.0.0.1:37345             127.0.0.1:37344             ESTABLISHED 13056/squid
tcp        0    200 192.168.0.80:22             192.168.0.246:1314          ESTABLISHED 32715/0
tcp        0      0 192.168.0.80:37785          216.239.59.113:80           ESTABLISHED 13056/squid

in /etc/rc7.d there  is
Code: [Select]
S90ejabberd -> /etc/rc.d/init.d/e-smith-service
Code: [Select]
[root@mailtampone ~]# service ejabberd restart
Restarting ejabberd                                        [  OK  ]

and pidgin continues to say 'connection refused'. (I am trying to register the admin user with pidgin.)

any hint would be most welcome..
ciao ciao, Michel
MagWm

Offline Stefano

  • *
  • 10,894
  • +3/-0
Re: Deployment Internal Chat with SME Server 7.4
« Reply #16 on: May 18, 2009, 01:25:40 PM »
and pidgin continues to say 'connection refused'. (I am trying to register the admin user with pidgin.)

any hint would be most welcome..
ciao ciao, Michel


hi

everything seems ok to me..

I'd check /var/log/ejabberd/* log files

Ciao
Stefano

Offline magwm

  • *
  • 159
  • +0/-0
  • SmeLover
    • Gadis Tourist Service Italia SRL
Re: Deployment Internal Chat with SME Server 7.4
« Reply #17 on: May 18, 2009, 01:50:23 PM »
Quote
I'd check /var/log/ejabberd/* log files

yeah, i did..
there are no log files there..
MagWm

Offline Stefano

  • *
  • 10,894
  • +3/-0
Re: Deployment Internal Chat with SME Server 7.4
« Reply #18 on: May 18, 2009, 02:07:10 PM »
yeah, i did..
there are no log files there..

so, please raise a bug as they should be there...

Ciao
Stefano

p.s. once done, please report here the number for future reference, thank you

Offline magwm

  • *
  • 159
  • +0/-0
  • SmeLover
    • Gadis Tourist Service Italia SRL
Re: Deployment Internal Chat with SME Server 7.4
« Reply #19 on: May 18, 2009, 02:56:05 PM »
MagWm

Offline magwm

  • *
  • 159
  • +0/-0
  • SmeLover
    • Gadis Tourist Service Italia SRL
Re: Deployment Internal Chat with SME Server 7.4
« Reply #20 on: May 21, 2009, 03:54:31 PM »
I have made some progressions:

according to the log in /var/log/ejabberd.run , ejabberd was crashing continuously. probably because of permission problems?

I have made a user ejabberd with the user panel
I have made /var/log/ejabberd/* writable by all (chmod -r 775)

I have REMOVED the ejabberd package (yum remove ejabberd )
I have ADDED the smeserver-ejabberd package ( yum --enablerepo=smetest --enablerepo=smecontribs install smeserver-ejabberd )

Still, I could not connect to the server with pidgin, so I have made the first user by hand ( ejabberdctl register admin@server password)

then I could log in to the user page

I have created a new user with the user page.

now, the server seems to be running, but I still cannot connect to it..

M
MagWm

Offline magwm

  • *
  • 159
  • +0/-0
  • SmeLover
    • Gadis Tourist Service Italia SRL
Re: Deployment Internal Chat with SME Server 7.4
« Reply #21 on: May 21, 2009, 04:23:14 PM »
now that was quite stupid.
When compiling a new account in pidgin,
you must insert the hostname of the ejabber server in the secont tab in the field "connection server" (between port and proxy)

IT WORKS!!
MagWm