«Bind9 unable to convert errno to isc result: 28: No space left on device» и «Golang - библиотека начинающего»: разница между страницами

Материал из support.qbpro.ru
(Различия между страницами)
imported>Vix
(Новая страница: «==Первое решение проблемы:== if you have enough free Mb on disk and stil get this error message, it may mean that there is no enough free f…»)
 
imported>Vix
(Новая страница: «'''ПОЛЕЗНОЕ:''' <hr> * [https://golangs.org/ Уроки для изучения Golang] * [https://metanit.com/go/tutorial/2.11.php Функции и их...»)
 
Строка 1: Строка 1:
==Первое решение проблемы:==
'''ПОЛЕЗНОЕ:'''
 
<hr>
if you have enough free Mb on disk and stil get this error message,
* [https://golangs.org/ Уроки для изучения Golang]
it may mean that there is no enough free file descriptors,
* [https://metanit.com/go/tutorial/2.11.php Функции и их параметры]
you may check it by this command:
* [https://www.ibm.com/developerworks/ru/library/l-go_01/ Язык программирования go]
 
* [https://tproger.ru/translations/golang-basics/ Golang: основы для начинающих]
[root@fooks ~]# df -ih
* [http://golang-book.ru/ Введение в программирование на Go]
Filesystem Inodes IUsed IFree IUse% Mounted on
* [https://medium.com/golang-notes/%D0%BD%D0%B0%D1%81%D1%82%D1%80%D0%BE%D0%B9%D0%BA%D0%B0-visual-studio-code-%D0%B4%D0%BB%D1%8F-go-647ea94aa795 Настройка Visual Studio Code для Go]
/dev/hda1 3.7M 329K 3.4M 9% /
* [https://serverspace.by/support/help/ustanovka-go-na-windows-server/ Установка GoLang на Windows Server]
/dev/shm 127K 1 127K 1% /dev/shm
* [https://otus.ru/nest/post/1015/ GOPATH и GOROOT больше не нужны?]
/dev/hda2 18M 52K 18M 1% /home
* [https://nuancesprog.ru/p/5966/ Идеальная настройка вашего Golang проекта]
/dev/hda5 7.0M 15K 7.0M 1% /share
* [https://habr.com/ru/post/249449/ Кросс-компиляция в Go]
 
* [https://gobyexample.com/ Go by Example]
in 98% - just delete unused files or move them to another partition
* [https://golang.org/pkg/ Golang Packages]
 
* [http://www.webhostingtalk.com/showthread.php?t=606486 взято тут...]
 
==Второе решение проблемы:==
please check the following parameters at your system of the values are set like follows:
# cat /proc/sys/kernel/sem
1250    256000  100    8192
 
# cat /proc/sys/kernel/msgmni
1024
 
according to the kernel documentation:
/proc/sys/kernel/sem - The maximum number and size of semaphore sets that can be allocated.
/proc/sys/kernel/msgmni - Sets maximum number of message queues
Anyway, your values are far to small. On sles9 the suse-sapinit rpm package should adjust these values by default. I assume that you did not install this package. Please do so, or adjust the values to the ones of my last reply.
 
"i have 30Gb on each server.
 
its 64bit
 
we have changes the parameters like Hannes said, and we are now able to keep both instances on all servers alive.
to make the changes permanent ill have to put this on /etc/sysctl.conf, and the entries would be something like :
kernel.sem="1250 256000 100 8192"
kernel.msgmni=1024
"
 
yes, your sysctl.conf values are correct. After reboot these values are then set by default.

Версия от 09:13, 18 августа 2020