Difference between revisions of "Computers"

From IARC 207 Wiki
Jump to navigation Jump to search
 
(7 intermediate revisions by 4 users not shown)
Line 11: Line 11:
 
[[Several Important Network Devices]] (Covers much of the same ground)<br>
 
[[Several Important Network Devices]] (Covers much of the same ground)<br>
 
* [https://docs.google.com/a/alaska.edu/document/d/1rRO1Ess8hwZkxBgZB5HRP-FZ8u2NcKENp2TvAYmtYTE/edit?usp=sharing Fairbanks IARC Base Station server (Ralph) Configuration]<br>
 
* [https://docs.google.com/a/alaska.edu/document/d/1rRO1Ess8hwZkxBgZB5HRP-FZ8u2NcKENp2TvAYmtYTE/edit?usp=sharing Fairbanks IARC Base Station server (Ralph) Configuration]<br>
 +
** follow that link for data radio setup, too.
  
 
* [https://docs.google.com/a/alaska.edu/document/d/1cvtqjE0w6MpFALUuruchsc71XF1WgvOJFbtLxnAWBQo/edit?usp=sharing Barrow Base Station server (Trout) Configuration]<br>
 
* [https://docs.google.com/a/alaska.edu/document/d/1cvtqjE0w6MpFALUuruchsc71XF1WgvOJFbtLxnAWBQo/edit?usp=sharing Barrow Base Station server (Trout) Configuration]<br>
Line 18: Line 19:
 
* [[Ser2Net Config Reference]] (Hopefully this reflects all of them)
 
* [[Ser2Net Config Reference]] (Hopefully this reflects all of them)
  
−
* Barrow Raspberry Pi 1 ''Lost in the mail *Sad Emoji*''<br>
 
−
* Barrow Raspberry Pi 2 ''Lost in the mail *Sad Emoji*''<br>
 
 
* '''Barrow Dreamplug''' -- Kind of decommissioned at this point.   
 
* '''Barrow Dreamplug''' -- Kind of decommissioned at this point.   
 
** Related though is [https://docs.google.com/document/d/1YK5Bt3QrWyU5LtWgWrdJ9skdwRxcxilH--8yFzSlQJ4/edit# Network Information on Barrow]
 
** Related though is [https://docs.google.com/document/d/1YK5Bt3QrWyU5LtWgWrdJ9skdwRxcxilH--8yFzSlQJ4/edit# Network Information on Barrow]
 
** It is old and still up in Barrow in the control shed.  Still works but I sent the raspberry pis up to replace it.  My plan is to replace it with a small server with a different computer architecture this winter.  The reason for that over these small ARM processors is that I'm still trying to work around this weak telemetry problem.  Thinking that if it is an x86 (well 64 bit but that style of CPU) that we can leave a copy of loggernet running up there so that when the network goes down as long as the unit is on we are still in business.  I am working to put all of its configs in one location though.  What was unique to it that hasn't been documented yet is that it used its second ethernet port as a DHCP server in support of a PTZ web cam.  That required an additional package, special iptables rules, and some scripts in /usr/local/bin.  On the to do list to get going at some point.
 
** It is old and still up in Barrow in the control shed.  Still works but I sent the raspberry pis up to replace it.  My plan is to replace it with a small server with a different computer architecture this winter.  The reason for that over these small ARM processors is that I'm still trying to work around this weak telemetry problem.  Thinking that if it is an x86 (well 64 bit but that style of CPU) that we can leave a copy of loggernet running up there so that when the network goes down as long as the unit is on we are still in business.  I am working to put all of its configs in one location though.  What was unique to it that hasn't been documented yet is that it used its second ethernet port as a DHCP server in support of a PTZ web cam.  That required an additional package, special iptables rules, and some scripts in /usr/local/bin.  On the to do list to get going at some point.
 +
* [[Decommisioned Serial Server Config and notes]]
  
 
===Virtual Machines===
 
===Virtual Machines===
Line 44: Line 44:
 
** Python Utilities: https://github.alaska.edu/rcbusey/python_utilities
 
** Python Utilities: https://github.alaska.edu/rcbusey/python_utilities
 
** DataPro V3 & other python utilities from Ross: https://github.com/rwspicer/csv_utilities
 
** DataPro V3 & other python utilities from Ross: https://github.com/rwspicer/csv_utilities
−
 
+
====WERC====
 +
Similar to NGEEDATA
 +
* Debian VM
 +
* Function is ''main data processing server'' and ''web server'' for sharing data with 3rd parties
 +
* [[werc.uaf]]
 
===Other===
 
===Other===
 
* [[High precision computer logger]]
 
* [[High precision computer logger]]
 
* [[Airplane Computer 2016]]
 
* [[Airplane Computer 2016]]
 +
* http://www.jubilinux.org/ (for edison installations rather than raspberry pi.
  
 
===Other Important Information===
 
===Other Important Information===
Line 54: Line 59:
 
* [[Automated System Work Flow]]
 
* [[Automated System Work Flow]]
 
* [[IP Tables Firewall Example]]
 
* [[IP Tables Firewall Example]]
 +
* Disable Autoreboot in windows 10 update: http://www.tenforums.com/windows-updates-activation/17530-disable-automatic-reboot-updates.html
 +
* Side note: If you do any buliding of these low power linux systems, start with an industrial microSD card.  Have had intermittent issues with memory corruption on consumer grade cards.  Search digikey etc for extended temperature industrial models.  SLC or MLC and temperature range to -25C or -40C is easy to find there.  Similar deal for the Compact Flash cards for the CSI cmf100.
 +
* Related... I've kind of standardized on 16 or 32GB industrial cards.  to back them up I use the command line tool dd:
 +
dd if=/dev/sdb of=backupofsystem.img bs=4096
 +
* that creates a pretty large file that is mostly empty.  So, follow this page to shrink things:
 +
** https://softwarebakery.com/shrinking-images-on-linux
 +
** I guess the alternative is to just gzip the large file... then use dd to copy the file onto new media:
 +
dd if=backpuofsystem.img of=/dev/sdb bs=4096
 +
** if say the image is 32gb but the media is a 16gb card the file system will extend beyond the length of the card.  That caused a boot error (of course) but I was able to use gparted the tool mentioned on the softwarebakery link to resize the file system on the new card.
 +
* https://serverfault.com/questions/363922/how-to-move-files-with-scp

Latest revision as of 18:49, 30 July 2018

Stub here to act as a table of contents sorts to our important computers / servers / related information.

Loggernet Systems

Serial Server Systems

What is a Serial Server?
Several Important Network Devices (Covers much of the same ground)

  • Barrow Dreamplug -- Kind of decommissioned at this point.
    • Related though is Network Information on Barrow
    • It is old and still up in Barrow in the control shed. Still works but I sent the raspberry pis up to replace it. My plan is to replace it with a small server with a different computer architecture this winter. The reason for that over these small ARM processors is that I'm still trying to work around this weak telemetry problem. Thinking that if it is an x86 (well 64 bit but that style of CPU) that we can leave a copy of loggernet running up there so that when the network goes down as long as the unit is on we are still in business. I am working to put all of its configs in one location though. What was unique to it that hasn't been documented yet is that it used its second ethernet port as a DHCP server in support of a PTZ web cam. That required an additional package, special iptables rules, and some scripts in /usr/local/bin. On the to do list to get going at some point.
  • Decommisioned Serial Server Config and notes

Virtual Machines

What is a Virtual Machine?

LogNet

Primary LoggerNet server

  • CentOS Linux virtual machine
  • Located in IARC server room
  • Function is main LoggerNet server for related projects.
  • This computer pushes data to ngeedata after automated retrievals.
  • LoggerNet configuration (Partial GIPL & IARC)

NGEEDATA

Primary Data processing server & data sharing web server

WERC

Similar to NGEEDATA

  • Debian VM
  • Function is main data processing server and web server for sharing data with 3rd parties
  • werc.uaf

Other

Other Important Information

dd if=/dev/sdb of=backupofsystem.img bs=4096

dd if=backpuofsystem.img of=/dev/sdb bs=4096
    • if say the image is 32gb but the media is a 16gb card the file system will extend beyond the length of the card. That caused a boot error (of course) but I was able to use gparted the tool mentioned on the softwarebakery link to resize the file system on the new card.
  • https://serverfault.com/questions/363922/how-to-move-files-with-scp
Retrieved from "http://ocotal.iarc.uaf.edu/index.php?title=Computers&oldid=2503"