Not all users kicked from hub

Bug #263023 reported by E_zombie
2
Affects Status Importance Assigned to Milestone
DSHub
Incomplete
Undecided
Unassigned

Bug Description

[19:51:59] <DSHub> [command:] !kick share>0
and 300+ user kicked from hub.
But 300+ users not kicked.

[19:52:44] <DSHub> Death Squad Hub. Version DSHub Iota.
  Running on SunOS Version 5.10 on Architecture sparc
  Java Runtime Environment 1.6.0_07 from Sun Microsystems Inc.
  Java Virtual Machine 1.0
  Available CPU's to JVM 2
  Available Memory to JVM: 957743104 Bytes, where free: 439190600 Bytes
Hub Statistics:
  Online users: 337
  Connecting users: 0
  Uptime: #1w#20h#47m#45s#669.
  Bytes read per second: 2597.6897689768975
  Bytes written per second: 37357.755775577556

if use again only ONE user kicked

20:05:16] <DSHub> [command:] !kick share>0
[20:05:16] <DSHub> No such user online. Parsing to Extended Kick...
[20:05:16] <DSHub> Done with matching users...
[20:05:16] <DSHub> Kicked user Abbadon with CID MHO33FNUNRAWCRQQHCHAWHIWLL6C4HLKVTFRY7Y out in flames.

___________________________________________

[17:40:17] <DSHub> [command:] !stats
- [17:40:17] <DSHub> Death Squad Hub. Version DSHub Iota.
  Running on SunOS Version 5.10 on Architecture sparc
  Java Runtime Environment 1.6.0_07 from Sun Microsystems Inc.
  Java Virtual Machine 1.0
  Available CPU's to JVM 2
  Available Memory to JVM: 957743104 Bytes, where free: 123861208 Bytes
Hub Statistics:
  Online users: 816
  Connecting users: 0
  Uptime: #1w#18h#35m#7s#928.
  Bytes read per second: 5753.7953795379535
  Bytes written per second: 180138.61386138614

E_zombie (lv77)
description: updated
Revision history for this message
Pietry (pietry) wrote :

Why would all the users had to be kicked ? Only those with a share higher than 0...

Changed in dshub:
status: New → Invalid
Changed in dshub:
status: Invalid → Incomplete
Revision history for this message
Pietry (pietry) wrote :

Tried on 150 user hub and all non null share was kicked. Perhaps you can explain more.. ?

Revision history for this message
E_zombie (lv77) wrote :

In addition more than anything I can not tell. Unless the hub worked continuously almost two weeks and next day a hub has ceased to work with an error described in #254725 was completed.

Revision history for this message
Toast (swetoast-deactivatedaccount) wrote :

it might be caused by the overload on your hubsoft. DSHub has a known issue with alot of users and we are trying to work on getting the performance better so i think we can close this bug

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.