No space available. I'm unable to login to jira and bitbucket due to storage.

[Vijay]

Tried pushing few files to bitbucket and it was successful but later, it stopped and unable to push any further as the space is full.

Also, unable to login to Jira or the Bitbucket I guess for the same reason. 

How can I increase the storage limit on both?

I'm currently using one database "Postgresql" for Jira, Bitbucket and Confluence.

Thanks

[Nic Brough -Adaptavist-]

There are no limits in the applications, you'll need to give the server or database more storage, or increase the user's limits (if quotas are in use)

[Vijay]

Thank you for the help.

[Vijay]

Hello, 

I'm facing the similar problem again. The disk is full for Jira. I'm hosting atlassian on CentOS. How can I increase the limit for the server or the database? I'm using postgresql for atlassian. 

It was all working fine but suddenly, it stopped working. When I try to access Postgresql in the server, I get the below error: 

psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

And when I try to start the Jira, it throws the below error: 

/opt/atlassian/jira/bin/catalina.sh: line 450: /opt/atlassian/jira/work/catalina.pid: No space left on device
Tomcat started.

How can I get the Jira up and running without loosing any data. 

Please help. 

Thanks, 

Vijay

[Nic Brough -Adaptavist-]

You need to increase the size of the disk (either by adding more storage, or by deleting stuff you don't want), or increase the user's allocation (only applies if you have limited them for some reason)

[Vijay]

The current directory for atlassian is /opt/atlassian where jira, bitbucket and confluence are located and nothing much. And I found out that there is no limit for /opt. 

Also, why is that I'm unable to start the postgresql? It says postgresql not found when trying to start it. 

[Nic Brough -Adaptavist-]

Ok, there's no limit, that means you're out of disk space and/or inodes.  The message "no space left on device" means what it says, there's no space to save files to.  You need to give it more disk space or clear stuff out.

You probably should check whether it is inodes or physical space.  Use "mount" to see what partition /opt is mounted on and then "df -khi" to see what space and inodes are used.

[Vijay]

I have relocated the bitbucket and confluence to /home from /opt and made some room for jira.  Not sure if this really helps. But I still can't start Jira. 

Running mount gives me this: 

sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime,seclabel)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,seclabel,size=3983928k,nr_inodes=995982,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,seclabel)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,seclabel,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,seclabel,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,seclabel,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_prio,net_cls)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
configfs on /sys/kernel/config type configfs (rw,relatime)
/dev/xvda1 on / type xfs (rw,relatime,seclabel,attr2,inode64,noquota)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=27,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=12467)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime,seclabel)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,seclabel)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,seclabel,size=800920k,mode=700,uid=1000,gid=1000)

And df -khi shows this: 

Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/xvda1 111K    111K    465 100%   /
devtmpfs   973K      282    973K   1%    /dev
tmpfs      978K           3      978K   1%    /dev/shm
tmpfs       978K       308     978K   1%    /run
tmpfs      978K      16        978K    1%    /sys/fs/cgroup
tmpfs     978K       1        978K      1%   /run/user/1000

[Vijay]

Never mind!! I could increase the size on the disk and everything is back in normal. 

Thanks!

[Nic Brough -Adaptavist-]

You probably want to investigate - whatever consumed all the inodes is likely to continue chewing up the new ones.

Use the following to find out where the inodes are most heavily used:

du --inodes -d 5 / | sort -n | tail

This will take a while to run, and it might not find the exact culprit if the problem is more than 5 directories below root.