Plan is to reprovision a baremetal server and redirect the Ysul IP there: T1268
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Oct 20 2017
Oct 19 2017
Equatower has been provisionned as a CentOS Atomic, with git, salt-client and docker-compose added to the base system.
Actually, we're going to create an 'ops' group instead of fighting the OS.
The hypervisor machine is broken, we received a new replacement machine.
Oct 18 2017
Hypervisor currently unreachable by ping.
Oct 17 2017
That means the Let's encrypt unit has to be moved to a shared role folder.
Oct 15 2017
[ Decreasing priority as it's up for 60 hours. ]
I don't see what we can do about this one.
By the way, as shown at P263, there are still some DNS records too for mail. and lists.nasqueron.org
@amj you wanted CLI tools automating this like ./new-jail-dns-record awesome-software or just a plain BIND/djbdns/whatever instance?
Closing former Ysul issues before server decom/migration.
Not interest among Nasqueron dwellers those last two years.
DNS entry should be removed per T536 close as WONTFIX.
Matrix experience at HSBXL seems this software lacks of traction, and can create issues with IRC users with the current state of the gateways.
Blocked by Ysul strategy to determine.
Oct 14 2017
00:05:29 < philectro> [philectro@ysul ~]$ dd bs=1m count=200 if=/dev/zero of=test
00:05:29 < philectro> 200+0 records in
00:05:29 < philectro> 200+0 records out
00:05:29 < philectro> 209715200 bytes transferred in 13.754970 secs (15246503 bytes/sec)
Oct 13 2017
Hard drive is fine according @ledesillusionniste:
Not needed, @ledesillusionniste found it at http://www.virten.net/2016/05/determine-tbw-from-ssds-with-s-m-a-r-t-values-in-esxi-smartctl/
Build process
Meanwhile, at 10:30 UTC, Ysul froze, hypervisor performance graphs simply showed a stop of activity.
@ledesillusionniste finds https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2146233 about the temperature issue: if we upgrade EXSi, we can get a correct reading.
Oct 12 2017
$ esxcli storage core device smart get -d t10.ATA_____HGST_HTS721010A9E630__________________________JR10006PH7JXKE Parameter Value Threshold Worst ---------------------------- ----- --------- ----- Health Status OK N/A N/A Media Wearout Indicator N/A N/A N/A Write Error Count N/A N/A N/A Read Error Count 100 62 100 Power-on Hours 32 0 32 Power Cycle Count 100 0 100 Reallocated Sector Count 100 5 100 Raw Read Error Rate 100 62 100 Drive Temperature 206 0 206 Driver Rated Max Temperature N/A N/A N/A Write Sectors TOT Count 200 0 200 Read Sectors TOT Count N/A N/A N/A Initial Bad Block Count N/A N/A N/A
@ledesillusionniste is checking SMART status, and a dd test to measure I/O.
Works now, probably a bug fixed during an upgrade :)
So the current IP block is reserved like this:
Dwellers have been moved here, with our dev infrastructure and Mastodon, but not Jenkins :
We've ordered a new hypervisor this 2017-10-12 during the night at OVH, the OP-SAT-1-32, with a first block of 4 IPs, 51.255.124.11/30.
Oct 11 2017
I've added varnish to startup sequence in /etc/rc.conf, so agora will be responsive on IPv6 too on boot :)
Oct 10 2017
This configuration is currently live for agora.nasqueron.org on 2001:470:1f13:9e1:0:cac:7e:1.
Oct 9 2017
Done, submitted at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222846.