When the disk is full, gitlab cannot be accessed because gitlab cannot be accessed.
My colleague said that gitlab could not be accessed and 502 of the access was found. I checked nginx error. log on the server.
15:01:50 [alert] 16867 #0: * 67473 write () to "/usr/local/nginx/logs/access. log "failed (28: No space left on device) while logging request, client: 180.169.120.218, server: gitlab.imacco.com, request:" GET/favicon. ico HTTP/1.1 ", upstream:" https: // 127.0.0.1: 8080/favicon. ico ", host:" gitlab.imacco.com ", referrer:" https://gitlab.imacco.com/?## # write () to "/usr/local/nginx/logs/access. log "failed (28: No space left on device
Prompt: access. log write failed, and the disk has no space. View disk space, search for large files, delete, and solve the problem.
# View disk capacity and usage df-lh [root @ iZbp178t84wkep4cvir0zsZ logs] $ df-lhFilesystem Size Used Avail Use % Mounted on/dev/vda1 40G 38G 0 100%/devtmpfs 3.9G 0 3.9G 0%/devtmpfs 3.9G 0 3.9G 0%/dev/shmtmpfs 3.9G 67 M 3.8G 2%/runtmpfs 3.9G 0 3.9G 0%/sys/fs/cgrouptmpfs 783 M 0 783 M 0%/run/user/0 overlay 40G 38G 0 100%/var/lib/docker/overlay/f3eaa0fb4aa3596ad7debc5fed48ddd7edc8a9095bc4b48e70f856a73002a406/mergeds Hm 64 M 0 64 M 0%/var/lib/docker/containers/logs/shm # Find the big file du-sh in the current directory * [root @ iZbp178t84wkep4cvir0zsZ/] $ du-sh * 6.4G Release bin145M boot4.0K deployment0 dev37M etc14G gitlabnew4.0K home0 lib0 lib6416K lost + found352M mail4.0K media4.0K mnt4.0K opt44K postfix. sqldu: cannot access 'proc/3171/task/100': No such file o R directorydu: cannot access 'proc/7746/task/7746/fd/4': No such file or directorydu: cannot access 'proc/7746/task/7746/fdinfo/4': No such file or directorydu: cannot access 'proc/7746/fd/4': No such file or directorydu: cannot access 'proc/7746/fdinfo/4': No such file or directory0 proc1.4G root67M run0 sbin4.0K srv0 sys72K tmp1.6G usr # deleted the 6.4G backup file. Restore normal access