Talk:Systems
There is an SD card reader that fits in a 3.5" floppy bay, which is intended to be installed in a system that is connected to the Lulzbot or Replicator.
The SD card reader is sitting next to the Replicator as of 9/23/2013.
Useful commands
This need to be properly docuemnted, but for now:
samba-tool dns query vm ad.pumpingstationone.org @ ALL samba-tool dns add vm ad.pumpingstationone.org vm A 96.127.153.34 -k yes
Dead link
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!
- https://unifi.ad.pumpingstationone.org:8443
- In Systems on 2014-07-21 05:02:07, Socket Error: '_ssl.c:510: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error'
- In Systems on 2014-07-22 05:02:17, Socket Error: '_ssl.c:510: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error'
- In Systems on 2014-07-23 05:02:05, Socket Error: '_ssl.c:510: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error'
- In Systems on 2014-07-24 05:02:48, Socket Error: '_ssl.c:510: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error'
- In Systems on 2014-07-25 05:02:41, Socket Error: '_ssl.c:510: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error'
- In Systems on 2014-07-26 05:02:08, Socket Error: '_ssl.c:510: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error'
- In Systems on 2014-07-27 05:01:44, Socket Error: '_ssl.c:510: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error'
- In Systems on 2014-07-30 05:03:26, Socket Error: '_ssl.c:510: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error'
- In Systems on 2014-08-01 05:02:11, Socket Error: '_ssl.c:510: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error'
--Wikibot (talk) 05:02, 1 August 2014 (UTC)
Dead link 2
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!
- https://10.100.0.1
- In Systems on 2014-12-15 06:02:24, Socket Error: u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)'
- In Systems on 2014-12-16 06:02:22, Socket Error: u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)'
- In Systems on 2014-12-17 06:02:27, Socket Error: u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)'
- In Systems on 2014-12-18 06:02:47, Socket Error: u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)'
- In Systems on 2014-12-19 06:03:24, Socket Error: u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)'
- In Systems on 2014-12-20 06:02:44, Socket Error: u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)'
- In Systems on 2014-12-21 06:02:09, Socket Error: u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)'
- In Systems on 2014-12-22 06:03:50, Socket Error: u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)'
--Wikibot (talk) 00:03, 22 December 2014 (CST)
Dead link 3
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!
- https://10.100.200.51:8006/
- In LAN on 2014-12-15 06:01:21, Socket Error: u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)'
- In LAN on 2014-12-16 06:01:40, Socket Error: u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)'
- In LAN on 2014-12-17 06:01:24, Socket Error: u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)'
- In LAN on 2014-12-18 06:01:33, Socket Error: u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)'
- In LAN on 2014-12-19 06:02:04, Socket Error: u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)'
- In LAN on 2014-12-20 06:01:43, Socket Error: u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)'
- In LAN on 2014-12-21 06:01:26, Socket Error: u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)'
- In LAN on 2014-12-22 06:02:22, Socket Error: u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)'
Updating
From IRC:
4/30/2015 hef1: https://wiki.pumpingstationone.org/Systems is probably the best list there is carl: so all others are obsolete and should be expunged.
Carl had originally put this in the content page, I'm moving it to the discussion page --Hef (talk) 09:31, 1 May 2015 (CDT)
members site incidents
Someone unplugged a thing 2016/02/??
Someone literally unplugged a thing, from what I hear. Skm (talk) 15:29, 2 February 2016 (CST)
Gateway timeout 2015/10/25
here is a discussion from the systems list and irc back when this incident happened. Skm (talk) 15:28, 2 February 2016 (CST)
initial email
the members site is timing out (502) and I notice the backup status on proxmox is still going. It started at midnight.
What's the SOP for this? kill it with fire?
later email (after I played around with the proxmox ui)
I don't know how to kill it with fire, and I couldn't reboot it since the UI blocks it while a bootup is happening.
later email, after some discussion on irc
On bob, Hef did:
`qm unlock 123; qm stop 123; qm start 123`
The nfs server woke up after doing that.
I didn't realize bob was doing hte http stuff to members, I thought nginx was on the members box. For later reference, the 502 is coming from bob, not the ps1auth vm.
If no one gets around to it before I do, add a SOP section to one of the wiki pages (members? proxmox?).
later clarification from hef
small clarification, the nfs server woke up after the 05 crash, not after running the qm commands
123 is the vmid of ps1auth
bob is the http gateway for all http/https services in the space. ps1auth is also running an nginx server for dealing with static files.
