[VGLUG] ejabberd chat server issue
1 view
Skip to first unread message
Bhavin Mehta
May 4, 2010, 8:30:18 AM5/4/10
to vglug
Hi All,
We have configure ejabber Chat Server on Ubuntu 9.04 and it was working fine since last six months but now a days some issues are taken place on ejabberd chat server. When all chat users are connected at that time process consumes 100% memory and ejabbered server crashed with attached ejabbered_log file. Please help me with this issue so i can fix this issue on my server.
--
Thanks,
Bhavin Mehta
Complitech Solution Pvt. Ltd.
(www.complitech.net)
--
Please read http://www.catb.org/~esr/faqs/smart-questions.html before posting.
You received this message because you are subscribed to the "Vibrant GNU/Linux User Group".
To stop receiving emails from this group, mail to VGLUG-un...@googlegroups.com
To post to this group, send email to VG...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/VGLUG
ElectroMech :- Vibrant GNU/Linux User Group
May 5, 2010, 1:53:16 AM5/5/10
to VGLUG
Hi,
Bhavin Mehta wrote:
> Hi All,
>
> We have configure ejabber Chat Server on Ubuntu 9.04 and it was working fine
> since last six months but now a days some issues are taken place on ejabberd
> chat server. When all chat users are connected at that time process consumes
> 100% memory and ejabbered server crashed with attached ejabbered_log file.
> Please help me with this issue so i can fix this issue on my server.
I do not see any attachment.
Nilesh J. Vaghela
http://www.electromech.info
Bhavin Mehta wrote:
> Hi All,
>
> We have configure ejabber Chat Server on Ubuntu 9.04 and it was working fine
> since last six months but now a days some issues are taken place on ejabberd
> chat server. When all chat users are connected at that time process consumes
> 100% memory and ejabbered server crashed with attached ejabbered_log file.
> Please help me with this issue so i can fix this issue on my server.
Nilesh J. Vaghela
http://www.electromech.info
Bhavin Mehta
May 5, 2010, 2:01:28 AM5/5/10
to vg...@googlegroups.com
On Wed, May 5, 2010 at 11:23 AM, ElectroMech :- Vibrant GNU/Linux User Group <nileshj...@gmail.com> wrote:
Hi,
Bhavin Mehta wrote:
> Hi All,
>
> We have configure ejabber Chat Server on Ubuntu 9.04 and it was working fine
> since last six months but now a days some issues are taken place on ejabberd
> chat server. When all chat users are connected at that time process consumes
> 100% memory and ejabbered server crashed with attached ejabbered_log file.
> Please help me with this issue so i can fix this issue on my server.
Hi,
I do not see any attachment.
Sorry sir i forgot attched file
below is my erl_crash.dump error log
root@hq:/var/log/ejabberd# head erl_crash.dump -n 200
=erl_crash_dump:0.1
Wed May 5 11:23:03 2010
Slogan: Kernel pid terminated (application_controller) ({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}})
System version: Erlang (BEAM) emulator version 5.6.5 [source] [async-threads:0] [kernel-poll:false]
Compiled: Fri Feb 20 01:40:17 2009
Atoms: 4273
=memory
total: 10365224
processes: 1104044
processes_used: 1096676
system: 9261180
atom: 202517
atom_used: 178885
binary: 117528
code: 1106438
ets: 26900
=hash_table:atom_tab
size: 3203
used: 2353
objs: 4273
depth: 7
=index_table:atom_tab
size: 5120
limit: 1048576
entries: 4273
=hash_table:module_code
size: 47
used: 34
objs: 46
depth: 3
=index_table:module_code
size: 1024
limit: 65536
entries: 46
=hash_table:export_list
size: 1201
used: 958
objs: 1869
depth: 7
=index_table:export_list
size: 2048
limit: 65536
entries: 1869
=hash_table:secondary_export_table
size: 97
used: 0
objs: 0
depth: 0
=hash_table:process_reg
size: 11
used: 3
objs: 3
depth: 1
=hash_table:fun_table
size: 197
used: 135
objs: 234
depth: 4
=hash_table:node_table
size: 11
used: 1
objs: 1
depth: 1
=hash_table:dist_table
size: 11
used: 1
objs: 1
depth: 1
=allocated_areas
sys_misc: 59164
static: 7733248
atom_space: 65544 42080
atom_table: 33373
module_table: 4368
export_table: 13080
register_table: 108
fun_table: 850
module_refs: 1024
loaded_code: 981952
dist_table: 167
node_table: 131
bits_bufs_size: 0
bif_timer: 40028
link_lh: 0
proc: 6108 1244
atom_entry: 103600 103432
export_entry: 90640 90112
module_entry: 2436 1876
reg_proc: 508 100
monitor_sh: 828 28
nlink_sh: 1476 180
proc_list: 24 24
fun_entry: 13512 13176
db_tab: 1788 204
driver_event_data_state: 24 24
driver_select_data_state: 348 44
=allocator:sys_alloc
option e: true
option m: libc
option tt: 131072
option tp: 0
=allocator:temp_alloc
versions: 0.9 2.2
option e: true
option t: false
option ramv: false
option sbct: 524288
option asbcst: 4145152
option rsbcst: 90
option rsbcmt: 80
option rmbcmt: 100
option mmbcs: 131072
option mmsbc: 256
option mmmbc: 10
option lmbcs: 10485760
option smbcs: 1048576
option mbcgs: 10
option as: af
mbcs blocks: 0 150 150
mbcs blocks size: 0 65544 65544
mbcs carriers: 1 1 1
mbcs mseg carriers: 0
mbcs sys_alloc carriers: 1
mbcs carriers size: 131104 131104 131104
mbcs mseg carriers size: 0
mbcs sys_alloc carriers size: 131104
sbcs blocks: 0 0 0
sbcs blocks size: 0 0 0
sbcs carriers: 0 0 0
sbcs mseg carriers: 0
sbcs sys_alloc carriers: 0
sbcs carriers size: 0 0 0
sbcs mseg carriers size: 0
sbcs sys_alloc carriers size: 0
temp_alloc calls: 6198
temp_free calls: 6198
temp_realloc calls: 7
mseg_alloc calls: 0
mseg_dealloc calls: 0
mseg_realloc calls: 0
sys_alloc calls: 1
sys_free calls: 0
sys_realloc calls: 0
=allocator:sl_alloc
versions: 2.1 2.2
option e: true
option t: false
option ramv: false
option sbct: 524288
option asbcst: 4145152
option rsbcst: 80
option rsbcmt: 80
option rmbcmt: 50
option mmbcs: 131072
option mmsbc: 256
option mmmbc: 5
option lmbcs: 10485760
option smbcs: 1048576
option mbcgs: 10
option mbsd: 3
option as: gf
mbcs blocks: 0 1 1
mbcs blocks size: 0 40 40
mbcs carriers: 1 1 1
mbcs mseg carriers: 0
mbcs sys_alloc carriers: 1
mbcs carriers size: 131104 131104 131104
mbcs mseg carriers size: 0
mbcs sys_alloc carriers size: 131104
sbcs blocks: 0 0 0
sbcs blocks size: 0 0 0
sbcs carriers: 0 0 0
sbcs mseg carriers: 0
sbcs sys_alloc carriers: 0
sbcs carriers size: 0 0 0
sbcs mseg carriers size: 0
sbcs sys_alloc carriers size: 0
sl_alloc calls: 97
sl_free calls: 97
sl_realloc calls: 0
mseg_alloc calls: 0
mseg_dealloc calls: 0
mseg_realloc calls: 0
sys_alloc calls: 1
sys_free calls: 0
sys_realloc calls: 0
=allocator:std_alloc
versions: 0.9 2.2
option e: true
option t: false
option ramv: false
option sbct: 524288
option asbcst: 4145152
option rsbcst: 20
option rsbcmt: 80
option rmbcmt: 50
option mmbcs: 131072
option mmsbc: 256
option mmmbc: 5
option lmbcs: 10485760
below is my erl_crash.dump error log
root@hq:/var/log/ejabberd# head erl_crash.dump -n 200
=erl_crash_dump:0.1
Wed May 5 11:23:03 2010
Slogan: Kernel pid terminated (application_controller) ({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}})
System version: Erlang (BEAM) emulator version 5.6.5 [source] [async-threads:0] [kernel-poll:false]
Compiled: Fri Feb 20 01:40:17 2009
Atoms: 4273
=memory
total: 10365224
processes: 1104044
processes_used: 1096676
system: 9261180
atom: 202517
atom_used: 178885
binary: 117528
code: 1106438
ets: 26900
=hash_table:atom_tab
size: 3203
used: 2353
objs: 4273
depth: 7
=index_table:atom_tab
size: 5120
limit: 1048576
entries: 4273
=hash_table:module_code
size: 47
used: 34
objs: 46
depth: 3
=index_table:module_code
size: 1024
limit: 65536
entries: 46
=hash_table:export_list
size: 1201
used: 958
objs: 1869
depth: 7
=index_table:export_list
size: 2048
limit: 65536
entries: 1869
=hash_table:secondary_export_table
size: 97
used: 0
objs: 0
depth: 0
=hash_table:process_reg
size: 11
used: 3
objs: 3
depth: 1
=hash_table:fun_table
size: 197
used: 135
objs: 234
depth: 4
=hash_table:node_table
size: 11
used: 1
objs: 1
depth: 1
=hash_table:dist_table
size: 11
used: 1
objs: 1
depth: 1
=allocated_areas
sys_misc: 59164
static: 7733248
atom_space: 65544 42080
atom_table: 33373
module_table: 4368
export_table: 13080
register_table: 108
fun_table: 850
module_refs: 1024
loaded_code: 981952
dist_table: 167
node_table: 131
bits_bufs_size: 0
bif_timer: 40028
link_lh: 0
proc: 6108 1244
atom_entry: 103600 103432
export_entry: 90640 90112
module_entry: 2436 1876
reg_proc: 508 100
monitor_sh: 828 28
nlink_sh: 1476 180
proc_list: 24 24
fun_entry: 13512 13176
db_tab: 1788 204
driver_event_data_state: 24 24
driver_select_data_state: 348 44
=allocator:sys_alloc
option e: true
option m: libc
option tt: 131072
option tp: 0
=allocator:temp_alloc
versions: 0.9 2.2
option e: true
option t: false
option ramv: false
option sbct: 524288
option asbcst: 4145152
option rsbcst: 90
option rsbcmt: 80
option rmbcmt: 100
option mmbcs: 131072
option mmsbc: 256
option mmmbc: 10
option lmbcs: 10485760
option smbcs: 1048576
option mbcgs: 10
option as: af
mbcs blocks: 0 150 150
mbcs blocks size: 0 65544 65544
mbcs carriers: 1 1 1
mbcs mseg carriers: 0
mbcs sys_alloc carriers: 1
mbcs carriers size: 131104 131104 131104
mbcs mseg carriers size: 0
mbcs sys_alloc carriers size: 131104
sbcs blocks: 0 0 0
sbcs blocks size: 0 0 0
sbcs carriers: 0 0 0
sbcs mseg carriers: 0
sbcs sys_alloc carriers: 0
sbcs carriers size: 0 0 0
sbcs mseg carriers size: 0
sbcs sys_alloc carriers size: 0
temp_alloc calls: 6198
temp_free calls: 6198
temp_realloc calls: 7
mseg_alloc calls: 0
mseg_dealloc calls: 0
mseg_realloc calls: 0
sys_alloc calls: 1
sys_free calls: 0
sys_realloc calls: 0
=allocator:sl_alloc
versions: 2.1 2.2
option e: true
option t: false
option ramv: false
option sbct: 524288
option asbcst: 4145152
option rsbcst: 80
option rsbcmt: 80
option rmbcmt: 50
option mmbcs: 131072
option mmsbc: 256
option mmmbc: 5
option lmbcs: 10485760
option smbcs: 1048576
option mbcgs: 10
option mbsd: 3
option as: gf
mbcs blocks: 0 1 1
mbcs blocks size: 0 40 40
mbcs carriers: 1 1 1
mbcs mseg carriers: 0
mbcs sys_alloc carriers: 1
mbcs carriers size: 131104 131104 131104
mbcs mseg carriers size: 0
mbcs sys_alloc carriers size: 131104
sbcs blocks: 0 0 0
sbcs blocks size: 0 0 0
sbcs carriers: 0 0 0
sbcs mseg carriers: 0
sbcs sys_alloc carriers: 0
sbcs carriers size: 0 0 0
sbcs mseg carriers size: 0
sbcs sys_alloc carriers size: 0
sl_alloc calls: 97
sl_free calls: 97
sl_realloc calls: 0
mseg_alloc calls: 0
mseg_dealloc calls: 0
mseg_realloc calls: 0
sys_alloc calls: 1
sys_free calls: 0
sys_realloc calls: 0
=allocator:std_alloc
versions: 0.9 2.2
option e: true
option t: false
option ramv: false
option sbct: 524288
option asbcst: 4145152
option rsbcst: 20
option rsbcmt: 80
option rmbcmt: 50
option mmbcs: 131072
option mmsbc: 256
option mmmbc: 5
option lmbcs: 10485760
>
>
> --
Nilesh J. Vaghela
http://www.electromech.info
--
Please read http://www.catb.org/~esr/faqs/smart-questions.html before posting.
You received this message because you are subscribed to the "Vibrant GNU/Linux User Group".
To stop receiving emails from this group, mail to VGLUG-un...@googlegroups.com
To post to this group, send email to VG...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/VGLUG
Bhavin Mehta
May 7, 2010, 6:57:23 AM5/7/10
to vg...@googlegroups.com
Hi,
Solved
Reinstall ejabberd package After taking ejabberd users badkup and than remove /var/lib/ejabberd/ data
On Wed, May 5, 2010 at 11:31 AM, Bhavin Mehta <bhavin....@gmail.com> wrote:
On Wed, May 5, 2010 at 11:23 AM, ElectroMech :- Vibrant GNU/Linux User Group <nileshj...@gmail.com> wrote:
Hi,
Bhavin Mehta wrote:
> Hi All,
>
> We have configure ejabber Chat Server on Ubuntu 9.04 and it was working fine
> since last six months but now a days some issues are taken place on ejabberd
> chat server. When all chat users are connected at that time process consumes
> 100% memory and ejabbered server crashed with attached ejabbered_log file.
> Please help me with this issue so i can fix this issue on my server.
Solved
Reinstall ejabberd package After taking ejabberd users badkup and than remove /var/lib/ejabberd/ data
Reply all
Reply to author
Forward
0 new messages