@luckydonaldsbots · Post #186 · 2019/02/23 23:32
Will be updating software of the server, expect #downtime the next hour
Hashtags
DN42 access 本服务为那些无法轻松访问自身网络的用户以及希望体验 dn42 但又不想承担维护自有网络成本的用户提供 dn42 连接 默认情况下,地址从/96地址块中分配,如果您希望租用独立的/96前缀或更大的地址空间,请按照联系方式联系我 所有公开的PoP均已屏蔽来自中国境内的 IP 地址。如果您确实需要dn42 access,请与我联系并提供合理的理由 该服务由AS4242423377提供 - - - - - - - The service provides DN42 connectivity to members who cannot easily access their own networks, as well as to those who would like to explore DN42 without the overhead of maintaining their own network. By default, addresses are allocated from a /96 block. If you wish to lease a dedicated /96 prefix or a larger address space, please contact me using the methods provided in the contact information. All publicly accessible PoP are blocked for IPs originating from within China. DN42 access from within China is not publicly available. If you genuinely require access, please contact me and provide a valid justification. Hosted by AS4242423377. Policy 本服务需要花费时间和金钱才能运行,但为了您的利益,我们免费提供。使用本服务是一种特权,而非权利。您必须合理使用本服务,以确保其他用户也能继续享受同样的便利。任何滥用、误用或干扰服务或其他用户的行为都可能导致您的访问权限立即被暂停或终止。 滥用行为包括但不限于: - 过度使用资源 - 黑客攻击、病毒、木马等,或任何其他可能损害服务或对服务及其用户造成风险的干扰行为 - 传播可能导致民事或刑事责任的不良内容 - - - - - - - This service require real time and financial resources to operate, yet are provided free of charge for your benefit. Access to the services is a privilege, not a right. You must use the services responsibly and considerately to ensure that other users can continue to enjoy the same opportunities. Any misuse, abuse, or activities that disrupt the service or other users may result in immediate suspension or termination of access. Abuse could include, but is not limited to: - Excessive use of resources - Hacking, viruses, trojans etc or any other disruption that could harm or create risk to the services or its users - Distribution of objectional content that could create a civil or criminal liability PoP ## Toronto, Canada Prefix: fdb6:fc6a:e66c:724f:fad1:d2cf::/96 Zerotier: 4753cf475f65b0fb ## Los Angeles, USA coming soon #announcement#service
Hashtags
搜索 #downtime
@luckydonaldsbots · Post #186 · 2019/02/23 23:32
Will be updating software of the server, expect #downtime the next hour
Hashtags
@luckydonaldsbots · Post #124 · 2018/02/01 15:18
Downtime in about one hour, as an now old docker version spammed my /run/ directory making any upgrades impossible. #downtime
Hashtags
@luckydonaldsbots · Post #193 · 2019/02/24 02:39
#downtime#resolved
@luckydonaldsbots · Post #191 · 2019/02/24 02:11
I'm still experiencing instabilities, still on it. #downtime#in_progress
Hashtags
@luckydonaldsbots · Post #290 · 2021/12/11 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
@luckydonaldsbots · Post #279 · 2021/12/05 14:33
Unexpected downtime: Due to an failed software update, the server is now unreachable. Working hard on resolving the issue. #downtime#unexpected
Hashtags
@luckydonaldsbots · Post #162 · 2018/10/21 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
@luckydonaldsbots · Post #111 · 2017/12/06 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
@luckydonaldsbots · Post #108 · 2017/11/29 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
@luckydonaldsbots · Post #251 · 2020/07/04 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
@luckydonaldsbots · Post #188 · 2019/02/24 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
@luckydonaldsbots · Post #232 · 2020/03/24 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