atmos:software:chords:home
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
atmos:software:chords:home [2022/03/04 12:47] – delene | atmos:software:chords:home [2023/04/26 14:17] (current) – [CHORDS Server Reset] delene | ||
---|---|---|---|
Line 24: | Line 24: | ||
* Password: Standard + ??? | * Password: Standard + ??? | ||
- | ===== CHORDS/ | + | ===== CHORDS Server Reset ===== |
+ | * cd chords | ||
+ | * sudo python chords_control −−stop | ||
+ | * sudo python chords_control −−run | ||
+ | |||
+ | ===== CHORDS/ | ||
+ | |||
+ | ==== 2022/03/26 - Added Swap Memory to AWS Server ==== | ||
+ | * Added Dashboard that summaries all available site Dashboards. | ||
+ | * Can not make public dashboards in Grafana because it opens up add data to the public. There is a workaround described at [[https:// | ||
+ | |||
+ | ==== 2022/03/24 - Added Swap Memory to AWS Server ==== | ||
+ | * Added 1 Gbyte of Swap to increase memory from 2 Gbytes to 3 Gbytes to try to prevent server crashes. | ||
+ | |||
+ | ==== 2022/02/26 - Sever Goes Down (Crashes) Routinely ==== | ||
+ | * Issue - The sever does down so that nothing accessible and do uploaded data is saved. | ||
+ | * Cause - Has happen several times. Not sure why but will track times of resets. | ||
+ | * Reset at 2022/02/26 13:35 UTC. | ||
+ | * Reset at 2022/02/26 14:51 UTC. Ran for awhile; however, stopped before having CHORDS work. | ||
+ | * Down at 4:11:40 UTC on 2022/ | ||
+ | * sudo docker exec -it chords_app tail -f log/ | ||
+ | * sudo docker container ls gives that chords_nginx chords_grafana chords_influxdb and chords_mysql is running. | ||
+ | * sudo docker ps -a gives | ||
+ | * 0607e0d72783 | ||
+ | * The above 7 hours is when the server clashed. | ||
+ | * sudo docker events --since 2022-02-25 gives | ||
+ | * 2022-03-04T04: | ||
+ | * Indicates the container died but not why. | ||
+ | * sudo docker logs 0607e0d727835ea59127e1c9afb4a18dcba61ad581db724ef2065cfbfbe35456 | ||
+ | * Gives E, [2022-03-04T04: | ||
+ | * This is at the time of the crash. | ||
+ | * Hence, the cause seems to be AWS instance that does not have enough memory. | ||
+ | * Short Term Solution - Reset server using: | ||
+ | * cd chorsds | ||
+ | * sudo python chords_control --stop | ||
+ | * sudo python chords_control --run | ||
+ | * Long Term Solution - Upgrade to larger AWS instance, with more memory. | ||
+ | * See [[https:// | ||
+ | * Note | ||
+ | * Sometimes get a "502 Bad Gateway" | ||
+ | * May be best not to try to access CHORDS right after restarting server. | ||
+ | * After reset, had to clear the browser cache and cookie to be able to access the CHORDS site again. | ||
+ | |||
+ | ==== 2022/01/12 - Sever Data Acceptance Issues (AWS Server 3.89.34.59) ==== | ||
+ | * Issue - At ~00:08, the AWS server stopped accepting data. Error via "sudo docker logs chords_mysql" | ||
+ | * Cause - Seems to be related to uploading CCN counter data, as have warnings about invalid strings. | ||
+ | * Solution - Added check to ensure that ' | ||
+ | |||
+ | ==== UND Docker1 2022 Setup ==== | ||
+ | * Had to get network port (80, 300, 8086) open on local network in addition to via VPN access. | ||
+ | * Kept getting " | ||
+ | |||
+ | ==== AWS 2021 Setup ==== | ||
* Setup Issues (Comments incorporated from Charles Martin at UCAR) | * Setup Issues (Comments incorporated from Charles Martin at UCAR) | ||
* AWS Setup - The configuration on AWS using a template to setup a system did not work. Error that could start CHORDS. | * AWS Setup - The configuration on AWS using a template to setup a system did not work. Error that could start CHORDS. | ||
Line 51: | Line 103: | ||
* Need to open Firewall to allow access to IP. To find the public IP address on Linux, last line. | * Need to open Firewall to allow access to IP. To find the public IP address on Linux, last line. | ||
* host myip.opendns.com resolver1.opendns.com | * host myip.opendns.com resolver1.opendns.com | ||
- | |||
- | ===== CHORDS/ | ||
- | * Had to get network port (80, 300, 8086) open on local network in addition to via VPN access. | ||
- | * Kept getting " | ||
- | |||
- | ===== 2022/01/12 - CHORDS/ | ||
- | * Issue - At ~00:08, the AWS server stopped accepting data. Error via "sudo docker logs chords_mysql" | ||
- | * Cause - Seems to be related to uploading CCN counter data, as have warnings about invalid strings. | ||
- | * Solution - Added check to ensure that ' | ||
- | |||
- | ===== 2022/02/26 - CHORDS/ | ||
- | * Issue - The sever does down so that nothing accessible and do uploaded data is saved. | ||
- | * Cause - Has happen several times. Not sure why but will track times of resets. | ||
- | * Reset at 2022/02/26 13:35 UTC. | ||
- | * Reset at 2022/02/26 14:51 UTC. Ran for awhile; however, stopped before having CHORDS work. | ||
- | * Down at 4:11:40 UTC on 2022/03/04. | ||
- | * sudo docker exec -it chords_app tail -f log/ | ||
- | * sudo docker container ls gives that chords_nginx chords_grafana chords_influxdb and chords_mysql is running. | ||
- | * sudo docker ps -a gives | ||
- | * 0607e0d72783 | ||
- | * The above 7 hours is when the server clashed. | ||
- | * sudo docker events --since 2022-02-25 gives | ||
- | * 2022-03-04T04: | ||
- | * Indicates the container died but not why. | ||
- | * sudo docker logs 0607e0d727835ea59127e1c9afb4a18dcba61ad581db724ef2065cfbfbe35456 | ||
- | * Gives E, [2022-03-04T04: | ||
- | * This is at the time of the crash. | ||
- | * Hence, the cause seems to be AWS instance that does not have enough memory. | ||
- | * Short Term Solution - Reset server using: | ||
- | * cd chorsds | ||
- | * sudo python chords_control --stop | ||
- | * sudo python chords_control --run | ||
- | * Long Term Solution - Upgrade to larger AWS instance, with more memory. | ||
- | * See [[https:// | ||
- | * Note | ||
- | * Sometimes get a "502 Bad Gateway" | ||
- | * May be best not to try to access CHORDS right after restarting server. | ||
- | * After reset, had to clear the browser cache and cookie to be able to access the CHORDS site again. |
atmos/software/chords/home.1646398020.txt.gz · Last modified: 2022/03/04 12:47 by delene