It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How can I change room owner?

Hello,

I am on a team Hipchat server, which is not associated with this account. The instructions on the documentation page for transferring room owner do not work. When I click on the "Rooms" tab, my browser window hangs for a long time on "Services Starting..." Then it brings me to a "Use HipChat in your browser" window, which just launches the web version. The options that follow in the documentation never appear for me.

I am unable to get to the Rooms tab. How can I resolve this?

Thank you for any help!

1 answer

0 votes
AhmadDanial Atlassian Team Aug 06, 2018

Good day, Taylor.

Since you mentioned that clicking on the Rooms tab shows the Services Starting, that indicates that there might be one or more services in HipChat Server that is not starting properly or the server ran out of disk space.

Can you please share the following information to here for so we can confirm on these?

  • Run the df -h command and provide us with the result
  • Obtain root access via sudo dont-blame-hipchat, run the monit status and attach the output here

Let us look at those information first before we dig deeper into the logs to understand the issue better. Thanks.

Hey Ahmad, thanks for responding!

 

How do I run those commands?

Actually, clicking "rooms" worked for the first time in over a year today! That's great. Thank you for your help.

AhmadDanial Atlassian Team Aug 07, 2018

Hi, Taylor!

While I am glad to know that the functionality works now, please apologize me for missing out on the details on where the commands should be executed. For future reference, please access your Hipchat Server instance's backend via SSH and run this through the terminal. For example:

admin@hipchat:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/xvda1 59G 4.0G 53G 7% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
udev 1.9G 12K 1.9G 1% /dev
tmpfs 377M 432K 377M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 1.9G 0 1.9G 0% /run/shm
none 100M 0 100M 0% /run/user
admin@hipchat:~$ sudo dont-blame-hipchat
root@hipchat:/home/admin# monit status
The Monit daemon 5.16 uptime: 34d 21h 5m

Process 'tetra-proxy-1'
status Running
monitoring status Monitored
pid 8464
parent pid 1
uid 9000
effective uid 9000
gid 9000
uptime 34d 21h 5m
threads 4
children 0
memory 87.5 MB
memory total 87.5 MB
memory percent 2.3%
memory percent total 2.3%
cpu percent 0.2%
cpu percent total 0.2%
port response time 1.691 ms to [localhost]:5221/healthcheck type TCP/IP protocol HTTP
data collected Tue, 07 Aug 2018 23:13:26

Process 'tetra-proxy-0'
status Running
monitoring status Monitored
pid 8450
parent pid 1
uid 9000
effective uid 9000
gid 9000
uptime 34d 21h 5m
threads 4
children 0
memory 87.7 MB
memory total 87.7 MB
memory percent 2.3%
memory percent total 2.3%
cpu percent 0.2%
cpu percent total 0.2%
port response time 1.541 ms to [localhost]:5211/healthcheck type TCP/IP protocol HTTP
data collected Tue, 07 Aug 2018 23:13:26

Process 'tetra-app-1'
status Running
monitoring status Monitored
pid 8868
parent pid 1
uid 9000
effective uid 9000
gid 9000
uptime 34d 21h 5m
threads 7
children 0
memory 87.9 MB
memory total 87.9 MB
memory percent 2.3%
memory percent total 2.3%
cpu percent 0.1%
cpu percent total 0.1%
port response time 1.608 ms to [localhost]:5302/healthcheck type TCP/IP protocol HTTP
data collected Tue, 07 Aug 2018 23:13:26

Process 'tetra-app-0'
status Running
monitoring status Monitored
pid 8860
parent pid 1
uid 9000
effective uid 9000
gid 9000
uptime 34d 21h 5m
threads 7
children 0
memory 88.8 MB
memory total 88.8 MB
memory percent 2.4%
memory percent total 2.4%
cpu percent 0.1%
cpu percent total 0.1%
port response time 1.648 ms to [localhost]:5301/healthcheck type TCP/IP protocol HTTP
data collected Tue, 07 Aug 2018 23:13:26

Process 'sshd'
status Running
monitoring status Monitored
pid 1928
parent pid 1
uid 0
effective uid 0
gid 0
uptime 34d 21h 19m
threads 1
children 0
memory 3 MB
memory total 3 MB
memory percent 0.1%
memory percent total 0.1%
cpu percent 0.0%
cpu percent total 0.0%
port response time 4.952 ms to [localhost]:22 type TCP/IP protocol SSH
data collected Tue, 07 Aug 2018 23:13:26

Process 'scissortail-worker-0'
status Running
monitoring status Monitored
pid 8913
parent pid 1
uid 9000
effective uid 9000
gid 9000
uptime 34d 21h 5m
threads 1
children 0
memory 30.0 MB
memory total 30.0 MB
memory percent 0.8%
memory percent total 0.8%
cpu percent 0.0%
cpu percent total 0.0%
data collected Tue, 07 Aug 2018 23:13:26

Process 'scissortail-web-0'
status Running
monitoring status Monitored
pid 8932
parent pid 1
uid 9000
effective uid 9000
gid 9000
uptime 34d 21h 5m
threads 1
children 2
memory 18.5 MB
memory total 79.6 MB
memory percent 0.5%
memory percent total 2.1%
cpu percent 0.0%
cpu percent total 0.0%
data collected Tue, 07 Aug 2018 23:13:26

Process 'rsyslog'
status Running
monitoring status Monitored
pid 1001
parent pid 1
uid 0
effective uid 0
gid 0
uptime 34d 21h 20m
threads 11
children 0
memory 19.4 MB
memory total 19.4 MB
memory percent 0.5%
memory percent total 0.5%
cpu percent 0.0%
cpu percent total 0.0%
port response time 0.116 ms to [localhost]:514 type TCP/IP protocol DEFAULT
data collected Tue, 07 Aug 2018 23:13:26

Process 'redisstats'
status Running
monitoring status Monitored
pid 1620
parent pid 1
uid 109
effective uid 109
gid 113
uptime 34d 21h 20m
threads 3
children 0
memory 9.3 MB
memory total 9.3 MB
memory percent 0.2%
memory percent total 0.2%
cpu percent 0.1%
cpu percent total 0.1%
port response time 200.758 ms to [localhost]:6380 type TCP/IP protocol generic
data collected Tue, 07 Aug 2018 23:13:26

Process 'redisserver'
status Running
monitoring status Monitored
pid 1611
parent pid 1
uid 109
effective uid 109
gid 113
uptime 34d 21h 20m
threads 3
children 0
memory 7.9 MB
memory total 7.9 MB
memory percent 0.2%
memory percent total 0.2%
cpu percent 0.0%
cpu percent total 0.0%
port response time 200.565 ms to [localhost]:6379 type TCP/IP protocol generic
data collected Tue, 07 Aug 2018 23:13:26

Process 'punjab'
status Running
monitoring status Monitored
pid 8493
parent pid 1
uid 9000
effective uid 9000
gid 9000
uptime 34d 21h 5m
threads 2
children 0
memory 45.4 MB
memory total 45.4 MB
memory percent 1.2%
memory percent total 1.2%
cpu percent 0.0%
cpu percent total 0.0%
port response time 0.130 ms to [localhost]:5280 type TCP/IP protocol DEFAULT
data collected Tue, 07 Aug 2018 23:13:26

Process 'php5-fpm'
status Running
monitoring status Monitored
pid 8538
parent pid 1
uid 0
effective uid 0
gid 0
uptime 34d 21h 5m
threads 1
children 11
memory 8.0 MB
memory total 197 MB
memory percent 0.2%
memory percent total 5.2%
cpu percent 0.0%
cpu percent total 0.0%
port response time 0.201 ms to [localhost]:9003 type TCP/IP protocol generic
port response time 0.201 ms to [localhost]:9002 type TCP/IP protocol generic
port response time 0.204 ms to [localhost]:9000 type TCP/IP protocol generic
data collected Tue, 07 Aug 2018 23:13:26

Process 'nginx'
status Running
monitoring status Monitored
pid 8513
parent pid 1
uid 0
effective uid 0
gid 0
uptime 34d 21h 5m
threads 1
children 2
memory 2.0 MB
memory total 14.6 MB
memory percent 0.1%
memory percent total 0.4%
cpu percent 0.0%
cpu percent total 0.0%
port response time 6.664 ms to [localhost]:8080/ type TCP/IP protocol HTTP
port response time 3.092 ms to [localhost]:443/favicon.ico type TCP/IP using SSL/TLS protocol HTTP
port response time 0.199 ms to [localhost]:80/ type TCP/IP protocol HTTP
data collected Tue, 07 Aug 2018 23:13:26

Process 'mysqld'
status Running
monitoring status Monitored
pid 3041
parent pid 2826
uid 106
effective uid 106
gid 111
uptime 34d 21h 17m
threads 59
children 0
memory 188.2 MB
memory total 188.2 MB
memory percent 5.0%
memory percent total 5.0%
cpu percent 0.0%
cpu percent total 0.0%
port response time 0.311 ms to [localhost]:3306 type TCP/IP protocol MYSQL
data collected Tue, 07 Aug 2018 23:13:26

Process 'integrations-0'
status Running
monitoring status Monitored
pid 8875
parent pid 1
uid 9000
effective uid 9000
gid 9000
uptime 34d 21h 5m
threads 8
children 0
memory 84.3 MB
memory total 84.3 MB
memory percent 2.2%
memory percent total 2.2%
cpu percent 0.1%
cpu percent total 0.1%
port response time 1.519 ms to [localhost]:6101/healthcheck type TCP/IP protocol HTTP
data collected Tue, 07 Aug 2018 23:13:26

System 'hipchat.example.com'
status Running
monitoring status Monitored
load average [0.00] [0.01] [0.05]
cpu 0.8%us 0.2%sy 0.0%wa
memory usage 1.9 GB [52.7%]
swap usage 0 B [0.0%]
data collected Tue, 07 Aug 2018 23:13:26

Process 'gearmand'
status Running
monitoring status Monitored
pid 8653
parent pid 1
uid 111
effective uid 111
gid 115
uptime 34d 21h 5m
threads 7
children 0
memory 5.1 MB
memory total 5.1 MB
memory percent 0.1%
memory percent total 0.1%
cpu percent 0.0%
cpu percent total 0.0%
port response time 200.380 ms to [localhost]:4730 type TCP/IP protocol generic
data collected Tue, 07 Aug 2018 23:13:27

Process 'elasticsearch'
status Running
monitoring status Monitored
pid 5166
parent pid 1
uid 9002
effective uid 9002
gid 9001
uptime 34d 21h 16m
threads 42
children 0
memory 308.5 MB
memory total 308.5 MB
memory percent 8.2%
memory percent total 8.2%
cpu percent 0.1%
cpu percent total 0.1%
port response time 0.422 ms to [localhost]:9200/_cat/health type TCP/IP protocol HTTP
data collected Tue, 07 Aug 2018 23:13:27

Filesystem 'xvda1'
status Accessible
monitoring status Monitored
permission 755
uid 0
gid 0
filesystem flags 0x1000
block size 4 kB
space total 58.9 GB (of which 4.2% is reserved for root user)
space free for non superuser 52.5 GB [89.1%]
space free total 55.0 GB [93.3%]
inodes total 3932160
inodes free 3793902 [96.5%]
data collected Tue, 07 Aug 2018 23:13:27

Filesystem '333411ff-71fc-42c0-a7bc-1e61068a5985'
status Accessible
monitoring status Monitored
permission 755
uid 0
gid 0
filesystem flags 0x1000
block size 4 kB
space total 58.9 GB (of which 4.2% is reserved for root user)
space free for non superuser 52.5 GB [89.1%]
space free total 55.0 GB [93.3%]
inodes total 3932160
inodes free 3793902 [96.5%]
data collected Tue, 07 Aug 2018 23:13:27

Process 'curler'
status Running
monitoring status Monitored
pid 8674
parent pid 1
uid 9000
effective uid 9000
gid 9000
uptime 34d 21h 5m
threads 2
children 0
memory 15.7 MB
memory total 15.7 MB
memory percent 0.4%
memory percent total 0.4%
cpu percent 0.0%
cpu percent total 0.0%
data collected Tue, 07 Aug 2018 23:13:27

Process 'crowd'
status Running
monitoring status Monitored
pid 8273
parent pid 1
uid 0
effective uid 0
gid 0
uptime 34d 21h 5m
threads 111
children 0
memory 536.1 MB
memory total 536.1 MB
memory percent 14.2%
memory percent total 14.2%
cpu percent 0.1%
cpu percent total 0.1%
port response time 0.567 ms to [localhost]:8095/ type TCP/IP protocol HTTP
data collected Tue, 07 Aug 2018 23:13:27

Process 'coral-1'
status Running
monitoring status Monitored
pid 8893
parent pid 1
uid 9000
effective uid 9000
gid 9000
uptime 34d 21h 5m
threads 9
children 0
memory 90.6 MB
memory total 90.6 MB
memory percent 2.4%
memory percent total 2.4%
cpu percent 0.1%
cpu percent total 0.1%
port response time 1.605 ms to [localhost]:5402/healthcheck type TCP/IP protocol HTTP
data collected Tue, 07 Aug 2018 23:13:27

Process 'coral-0'
status Running
monitoring status Monitored
pid 8884
parent pid 1
uid 9000
effective uid 9000
gid 9000
uptime 34d 21h 5m
threads 10
children 0
memory 88.3 MB
memory total 88.3 MB
memory percent 2.3%
memory percent total 2.3%
cpu percent 0.1%
cpu percent total 0.1%
port response time 1.605 ms to [localhost]:5401/healthcheck type TCP/IP protocol HTTP
data collected Tue, 07 Aug 2018 23:13:27

Process 'barb-0'
status Running
monitoring status Monitored
pid 32472
parent pid 1
uid 9000
effective uid 9000
gid 9000
uptime 12d 20h 55m
threads 7
children 0
memory 83.1 MB
memory total 83.1 MB
memory percent 2.2%
memory percent total 2.2%
cpu percent 0.1%
cpu percent total 0.1%
port response time 1.487 ms to [localhost]:12000/healthcheck type TCP/IP protocol HTTP
data collected Tue, 07 Aug 2018 23:13:27

Feel free to let me know if it surfaces again and we can continue troubleshooting the issue further. Thanks!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Hipchat

Hipchat Cloud and Stride have reached End of Life (updated)

All good things come to an end - thanks to all our customers and partners who have been along the Hipchat and Stride journey with us.  As of Feb 15th 2019, Hipchat Cloud and Stride have reached ...

35,184 views 9 8
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you