"Disk Quota Exceeded" when chown-ing


#1

I have been trying to install Discourse on my VPS (1GB RAM), I have a swapfile and all, however when I get to the part where you have to run ./loader bootstrap app, it errors out, the error looks something like this:

chown: changing ownership of ‘/var/www/discourse/.bundle’: Disk quota exceeded
I, [2015-12-09T20:14:48.373258 #36]  INFO -- :
I, [2015-12-09T20:14:48.400951 #36]  INFO -- : Terminating async processes
I, [2015-12-09T20:14:48.401066 #36]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/9.3/bin/postmaster -D /etc/postgresql/9.3/main pid: 65
I, [2015-12-09T20:14:48.409038 #36]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 193
2015-12-09 20:14:48 UTC [65-2] LOG:  received fast shutdown request
2015-12-09 20:14:48 UTC [65-3] LOG:  aborting any active transactions
2015-12-09 20:14:48 UTC [72-2] LOG:  autovacuum launcher shutting down
193:signal-handler (1449692088) Received SIGTERM scheduling shutdown...
193:M 09 Dec 20:14:48.454 # User requested shutdown...
193:M 09 Dec 20:14:48.454 * Saving the final RDB snapshot before exiting.
193:M 09 Dec 20:14:48.469 * DB saved on disk
193:M 09 Dec 20:14:48.469 # Redis is now ready to exit, bye bye...
2015-12-09 20:14:48 UTC [69-1] LOG:  shutting down
2015-12-09 20:14:48 UTC [69-2] LOG:  database system is shut down


FAILED
--------------------
RuntimeError: cd /var/www/discourse && chown -R discourse /var/www/discourse failed with return #<Process::Status: pid 292 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:105:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"web", "cmd"=>["gem update bundler", "chown -R discourse $home"]}
97c624fd7ac6347cf9c58dc184729f7071786f0519be673108ca568b43f37b4f
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

Can you guys please help with this?

Thanks :smiley:

EDIT: There are NO disk quotas in place. The server is also NOT out of disk space (see below).


(Jeff Atwood) #2

Is it out if disk space?


#3

I would have already checked that but…
df -h

Filesystem      Size  Used Avail Use% Mounted on
/dev/vda1        39G  5.7G   31G  16% /
none            4.0K     0  4.0K   0% /sys/fs/cgroup
udev            487M  4.0K  487M   1% /dev
tmpfs           100M  400K   99M   1% /run
none            5.0M     0  5.0M   0% /run/lock
none            497M     0  497M   0% /run/shm
none            100M     0  100M   0% /run/user

(Jeff Atwood) #4

What does docker --info and docker --version report?


#5
docker --info
flag provided but not defined: --info
See 'docker --help'.

docker --version
Docker version 1.9.1, build a34a1d5

(Jeff Atwood) #6

Sorry minor mistake on my part we need the output of docker info


#7
docker info
Containers: 0
Images: 6
Server Version: 1.9.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 6
 Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.13.0-71-generic
Operating System: Ubuntu 14.04.3 LTS
CPUs: 4
Total Memory: 993.7 MiB
Name: -Removed for Security Reasons-
ID: US2B:MB6U:NFDR:J5OH:7KWH:V4QC:CGTO:IKCK:POZH:2EVW:7ITI:BKGT
WARNING: No swap limit support

(Jeff Atwood) #8

And what does free -m return?


(Sam Saffron) #9

This is an indicator that the quota of the user running the docker service is full… what does sudo quota return?


#10
free -m
             total       used       free     shared    buffers     cached
Mem:           993        812        181        183          3        361
-/+ buffers/cache:        446        547
Swap:         1023        202        821

sudo quota
Disk quotas for user root (uid 0): none

#11

Bump! I need this to get fixed soon please!


(Sam Saffron) #12

Discourse is uid 1000 I bet it has a quota set


#13

root@1dev:~# quota -u discourse Disk quotas for user discourse (uid 1003): none


#14

So

  1. discourse has NO quotas.
  2. It’s not UID 1000, it’s UID 1003.

#15

Support here is HORRIBLE…can anyone help please?


(Sam Saffron) #16

We tried, we just have no idea what your problem is, sorry.


(Jeff Atwood) #17

Would you like to purchase a $99 install? https://discourse.org/buy – we do guarantee those setups are stable. Or you could purchase a hosting plan.


#18

I’m extremely tempted to buy that however I do not have the money to do so.

Also, I highly doubt that paying for that install will be any more successful than what I have done; because if the creators of Discourse can’t figure it out, who can?


(cpradio) #19

Their $99 install happens on Digital Ocean, so they are very certain they won’t see that error. What host are you with? And what happens when you run quota -v?


#20

Oh, OK! That makes more sense!
But that makes matters worse since DigitalOcean’s prices are INSANE compared to the servers I have with HostSailor.

quota-v
iDisk quotas for user root (uid 0): Filesystem blocks quota limit grace files quota limit grace /dev/disk/by-uuid/1c4b4b7b-5e73-4c87-85b8-cba6e526ede9 4949740 0 0 213235 0 0