Luckydonalds Bots: Development/Status
@luckydonaldsbots · Post #186 · 23.02.2019 г., 23:32
Will be updating software of the server, expect #downtime the next hour
Hashtags
TGTGInsighttelegram intelligenceLIVE / telegram public index
TGINSIGHT SIMILAR POSTS
Најди сличен содржај
Изворен канал @pythonotes · Post #303 · 27 дек.
Наверняка вы замечали, что в Python есть удобная функция для получения переменной окружения os.getenv(NAME) И её "сестра" для создания или изменения переменных окружения os.putenv(NAME, VALUE) Но почему-то putenv() не работает как должно. Энвайромент не обновляется! os.putenv('MYVAR', '1') print(os.getenv('MYVAR')) ... и ничего 😴 Почему так? На самом деле энвайромент обновляется, но это значение не добавляется в словарь os.environ. Откройте исходник функции os.getenv(). Это просто шорткат для os.environ.get() В то время как putenv() это built-in С-функция. Словарь os.environ (или точней класс из MutableMapping) создаётся из энвайромента в момент инициализации. Функция putenv() самостоятельно его не изменяет. В тоже время, когда вы создаёте или изменяете ключ в os.environ, автоматически вызывается putenv() в методе __setitem__(). То есть, технически putenv() всё делает верно, но в os.environ это не отражается. Можно проверить так: >>> os.putenv('MYVAR', '123') >>> os.system('python -c "import os;print(os.getenv(\'MYVAR\'))"') 123 Я объявил переменную в текущем процессе и вызвал дочерний процесс, который её унаследовал и получил в составе os.environ. Аналогично при удалении переменной вызывается еще одна built-in функция unsetenv(), удаляющая переменную из системы. Итого ▫️ Удобней всего явно обновлять переменные через os.environ ▫️ Есть способ неявно создать/удалить переменную через putenv/unsetenv, что не повлияет на os.environ но изменит энвайромент и передаст изменения сабпроцессам. Но так лучше не делать! ▫️os.environ это просто обертка для built-in функций putenv() и unsetenv(). #basic
Hashtags
Резултати
Пронајдени 14 слични објави
Пребарај: #downtime
当前筛选 #downtime清除筛选
Luckydonalds Bots: Development/Status
@luckydonaldsbots · Post #124 · 01.02.2018 г., 15:18
Downtime in about one hour, as an now old docker version spammed my /run/ directory making any upgrades impossible. #downtime
Hashtags
Luckydonalds Bots: Development/Status
@luckydonaldsbots · Post #193 · 24.02.2019 г., 02:39
#downtime#resolved
Luckydonalds Bots: Development/Status
@luckydonaldsbots · Post #191 · 24.02.2019 г., 02:11
I'm still experiencing instabilities, still on it. #downtime#in_progress
Hashtags
Luckydonalds Bots: Development/Status
@luckydonaldsbots · Post #290 · 11.12.2021 г., 22:33
Also there will be a scheduled downtime for two remaining bots tomorrow, in about 16h 20h from now : - @BanWarnBot - @RulesRulesBot Those have a database, and therefore they need to be take down to not loose any changes happining while the data is moved over. #scheduled#downtime
Hashtags
Luckydonalds Bots: Development/Status
@luckydonaldsbots · Post #279 · 05.12.2021 г., 14:33
Unexpected downtime: Due to an failed software update, the server is now unreachable. Working hard on resolving the issue. #downtime#unexpected
Hashtags
Luckydonalds Bots: Development/Status
@luckydonaldsbots · Post #162 · 21.10.2018 г., 13:20
Apperently also @anonymize_bot is affected. Currently looking into the issue. Update: It should now be back and running, but telegram reports about two thousand updates being still unprocessed, but that is decreasing. It will recover soon, bear with me, it works as fast as telegram allows it to. Update: @anonymize_bot It is now back to normal. #Anonymize#downtime'
Hashtags
Luckydonalds Bots: Development/Status
@luckydonaldsbots · Post #111 · 06.12.2017 г., 10:53
Need another downtime today, in the same timeframe (13:00 UTC), as the main server is undergoing a hardware check. The backup server however should be online as soon as the database are copied. #scheduled_downtime#downtime
Hashtags
Luckydonalds Bots: Development/Status
@luckydonaldsbots · Post #108 · 29.11.2017 г., 11:39
Expected downtime: Today, 13:00 UTC. Duration 1h. Delayed, see post below. Because my current server isn't powerful enough, especially regarding Disk IO speed, I will move part of the infrastructure to a new server with SSD storage. This means I have to take down the databases, and copy them over. I'll try to keep the bots running which doesn't need a database, like @ponbot, @anonymize_bot, @HeyAdminBot, @moustache_bot, etc. #expected_downtime#downtime
Hashtags
Luckydonalds Bots: Development/Status
@luckydonaldsbots · Post #251 · 04.07.2020 г., 14:51
Maintenance: Moving @BanWarnBot to the new server. Okey going through the same procedure for @BanWarnBot now, hopefully without the database breaking this time. Turning the bot off for moving the database, so any /warns send in the meantime shouldn't get lost. As soon as it's on the new server it should pick up those, and carry out the needed actions. I'll take @BanWarnBot down in 10 minutes. Other bots should not be affected. #maintenance#downtime#BanWarnBot
Hashtags
Luckydonalds Bots: Development/Status
@luckydonaldsbots · Post #188 · 24.02.2019 г., 01:05
If you docker refuses to start and sudo service docker status is showing logs like this: Feb 24 01:30:06 hostname dockerd[19544]: time="2019-02-24T01:30:06.718823877+01:00" level=error msg="stream copy error: reading from a closed fifo" It might be that /var/run/docker.sock is a mount in one of your containers. Therefore if that doesn't exist - and only shortly - it will be created as a folder, thus making it impossible for docker to start. Fix it with sudo rmdir /var/run/docker.sock, and sudo service docker start. #TechnicalDetails#downtime#in_progress
Luckydonalds Bots: Development/Status
@luckydonaldsbots · Post #232 · 24.03.2020 г., 10:45
I will soon migrage some services onto a new server. Therefore those services will be unavailable for the next two hours: @JoinCaptchaBot@BanWarnBot@RulesRulesBot and @ForwardWhitelistBot. #downtime #JoinCaptchaBot#BanWarnBot#RulesRulesBot#ForwardWhitelistBot