A few starts problems and "what's those files"

Welcome,
1)Installing ejabberd-1.1.1.bin on SuSE 10.0
In ejabberd.cfg file I put 2 kind of hosts but no one can connect with this second which wasn't set throw instalation process
(I set it after instalation editing ejabberd.cfg file). What and where shall i do to make visible second host for users?

2)what for are those files: beam, child_setup, epmd, erl, erlexec, inet_gethost,
postinstall.sh, preinstal.sh? how i can use it and what for?

3)what for is file "inetrc" ?

4)I install ejabberd bin file and sometimes during installation i get that message (i tryed to install it on Slackware 10.1):
"ERROR: There was an error registering the RPM file"
after that i can't enter "admin interface".
choosing: ./start it seems it's ok but
choosing: ./status i got:
"/opt/ejabberd-1.1.1/bin/ejabberdctl: line 4: jabber.wassup-l.site (which is my second host): command not found
./status: line 3: 5253 (this number is changing, e.g. 5569) Segmentation fault $ROOTDIR/bin/ejabberdctl status"
oh, and during installation this time i choose (when asking about hostname) wassup-l.site and jabber.wassup-l.site
my computer has got hostname: wassup-l.site

Please help if anybody can. AAnd forgive me if this was in past.

"che"

Re: A few starts problems and "what's those files"

cheeroke wrote:

1)Installing ejabberd-1.1.1.bin on SuSE 10.0
In ejabberd.cfg file I put 2 kind of hosts but no one can connect with this second which wasn't set throw instalation process
(I set it after instalation editing ejabberd.cfg file). What and where shall i do to make visible second host for users?

I do not understand your question.

cheeroke wrote:

2)what for are those files: beam, child_setup, epmd, erl, erlexec, inet_gethost,

Files from Erlang/OTP.

cheeroke wrote:

postinstall.sh, preinstal.sh? how i can use it and what for?

The .sh files are scripts used by the installer to create the icons for instance. In short: you do not need to do anything with these files, but they are needed to install or run ejabberd.

cheeroke wrote:

3)what for is file "inetrc" ?

Read this.

cheeroke wrote:

4)I install ejabberd bin file and sometimes during installation i get that message (i tryed to install it on Slackware 10.1):
"ERROR: There was an error registering the RPM file"

Did the installer had root access to register the RPM file?

cheeroke wrote:

after that i can't enter "admin interface".
choosing: ./start it seems it's ok but
choosing: ./status i got:
"/opt/ejabberd-1.1.1/bin/ejabberdctl: line 4: jabber.wassup-l.site (which is my second host): command not found

Looks like you didn't configured the second host right. How did you tried to add the second host? Did you looked at the documentation?

Re: A few starts problems and "what's those files"

sander wrote:
cheeroke wrote:

1)Installing ejabberd-1.1.1.bin on SuSE 10.0
In ejabberd.cfg file I put 2 kind of hosts but no one can connect with this second which wasn't set throw instalation process
(I set it after instalation editing ejabberd.cfg file). What and where shall i do to make visible second host for users?

I do not understand your question.

The problem is that i set second host after installation proces editing ejabberd.cfg file and after that i cannot connect using it in my name server: in installation i choose: wassup-l.site and after instalation i set jabber.wassup-l.site as second host. but no wcannot connect as an user using user_name@jabber.wassup-l.site

sander wrote:
cheeroke wrote:

2)what for are those files: beam, child_setup, epmd, erl, erlexec, inet_gethost,

Files from Erlang/OTP.

yes i know that but what are they for if i install from *.bin file?

sander wrote:
cheeroke wrote:

postinstall.sh, preinstal.sh? how i can use it and what for?

The .sh files are scripts used by the installer to create the icons for instance. In short: you do not need to do anything with these files, but they are needed to install or run ejabberd.

I run server typing ./start Where they create those icons?

sander wrote:
cheeroke wrote:

4)I install ejabberd bin file and sometimes during installation i get that message (i tryed to install it on Slackware 10.1):
"ERROR: There was an error registering the RPM file"

Did the installer had root access to register the RPM file?

In truth i donot know, i just "click" on *.bin file and that is it. I do not set any permissions to any files. Where should I do it and how?

sander wrote:
cheeroke wrote:

after that i can't enter "admin interface".
choosing: ./start it seems it's ok but
choosing: ./status i got:
"/opt/ejabberd-1.1.1/bin/ejabberdctl: line 4: jabber.wassup-l.site (which is my second host): command not found

Looks like you didn't configured the second host right. How did you tried to add the second host? Did you looked at the documentation?

[/quote]
Well I set it during installation, when installer ask about hostname I write: wassup-l.site, jabber.wassup-l.site

Re: A few starts problems and "what's those files"

cheeroke wrote:

The problem is that i set second host after installation proces editing ejabberd.cfg file and after that i cannot connect using it in my name server: in installation i choose: wassup-l.site and after instalation i set jabber.wassup-l.site as second host. but no wcannot connect as an user using user_name@jabber.wassup-l.site

Did you restarted ejabberd?

cheeroke wrote:

yes i know that but what are they for if i install from *.bin file?

The binary installers for Linux and Mac OS X include a stripped down version of Erlang/OTP, and other libraries, so that it can work out of the box on each system. So they are used to run ejabberd.

cheeroke wrote:

I run server typing ./start Where they create those icons?

These scripts are not executed by the start script, but by the Bitrock installer. These icons should be visible in ~/Desktop/ when you run Linux.

cheeroke wrote:

In truth i donot know, i just "click" on *.bin file and that is it. I do not set any permissions to any files. Where should I do it and how?

It is not that important, but if you install as root, I believe the Bitrock installer can register ejabberd in SUSE's RPM database which means that you can remove it from the package manager of SUSE.

cheeroke wrote:

Well I set it during installation, when installer ask about hostname I write: wassup-l.site, jabber.wassup-l.site

AFAIK you can only specify one hostname in the installer. Try to enter only one host during installation and add the other host afterwards in the configuration file (see documentation).

Re: A few starts problems and "what's those files"

sander wrote:
cheeroke wrote:

The problem is that i set second host after installation proces editing ejabberd.cfg file and after that i cannot connect using it in my name server: in installation i choose: wassup-l.site and after instalation i set jabber.wassup-l.site as second host. but no wcannot connect as an user using user_name@jabber.wassup-l.site

Did you restarted ejabberd?

No, becouse first i set second host and than start it. Second host wasn't visible.

sander wrote:
cheeroke wrote:

In truth i donot know, i just "click" on *.bin file and that is it. I do not set any permissions to any files. Where should I do it and how?

It is not that important, but if you install as root, I believe the Bitrock installer can register ejabberd in SUSE's RPM database which means that you can remove it from the package manager of SUSE.

[/quote]
Yes, but problems with RPM error is when I try to install on Slackware 10

Re: A few starts problems and "what's those files"

cheeroke wrote:
sander wrote:

Did you restarted ejabberd?

No, becouse first i set second host and than start it. Second host wasn't visible.

AFAIK, ejabberd is automatically started by the installer, so you first have to stop it.

Re: A few starts problems and "what's those files"

sander wrote:
cheeroke wrote:
sander wrote:

Did you restarted ejabberd?

No, becouse first i set second host and than start it. Second host wasn't visible.

AFAIK, ejabberd is automatically started by the installer, so you first have to stop it.

Strange... when my os starts and if i write "./status" i got the message simillar to that error from slackware about RPM... and server is not running. If i write :./start" than it runs. Whats wrong? Are U shure that ejabberd shall be started on boot?

And what about RPM on slackware? "Slack" do not use rpm-s so what it means this error which i was written above?

Syndicate content