ID | Estimate | Status | Description |
---|---|---|---|
917 | 2016-08-10 | FIXED | Order NW Digital board |
981 | 2016-09-11 | WONTFIX | KC8ARJ as repeater |
983 | 2016-09-11 | FIXED | Order quality SD cards |
986 | 2016-09-11 | FIXED | Validate LTE |
982 | 2016-09-12 | FIXED | WiFi startup |
994 | 2016-09-12 | WONTFIX | Investigate hang time control |
978 | 2016-09-13 | FIXED | Select UDRC/Pi Case |
984 | 2016-09-15 | FIXED | SD card receive |
995 | 2016-09-15 | WONTFIX | Investigate hang time in source |
979 | 2016-09-16 | FIXED | Receive UDRC/Pi Case |
987 | 2016-09-19 | FIXED | Select LTE provider |
980 | 2016-09-20 | FIXED | Modify/Install UDRC/Pi Case |
988 | 2016-09-20 | FIXED | Order LTE Device |
989 | 2016-10-04 | FIXED | Receive LTE device |
990 | 2016-10-08 | ASSIGNED | Configure/Test LTE Device |
991 | 2016-10-11 | ASSIGNED | Log file strategy |
985 | 2016-10-17 | ASSIGNED | Schedule 2030 install |
992 | 2016-10-23 | ASSIGNED | Make backup SD |
993 | 2016-11-07 | ASSIGNED | Move to 2030 |
996 | 2016-11-30 | ASSIGNED | Test 100 watt amp |
ID | Estimate | Status | Description |
---|---|---|---|
990 | 2016-10-08 | Configure/Test LTE Device |
2016-09-12 10:30:32:
Configure the Pi to use the hotspot network, adjust the backup scheme for the external address, test repeater using LTE hotspot.
2016-09-30 17:52:38:
Date adjusted based on FedEx delivery projection
2016-10-05 09:09:30:
Initial investigation very discouraging. Device requires a browser. On the website it indicated browser-less devices were usable. However, a month later the website is very different, and it appears that a browser-less device costs $15 a month in addition to the $15 a gig. Will investigate spoofing the browser login.
ID | Estimate | Status | Description |
---|---|---|---|
991 | 2016-10-11 | Log file strategy |
2016-09-11 09:46:43:
Develop a strategy to be sure that log files don't get excessive
2016-09-20 15:26:20:
Looks like we can simply delete all the gzipped log files after the backup has run. Probably should decide about backing up the system logs as well as the openDV logs,
2016-09-25 11:40:11:
Backup logs to cimbaoth #!/bin/sh -x FILENAME=`date +'%Y%m%d-opendv.tar.gz'` FILENAME2=`date +'%Y%m%d-log.tar.gz'` NODE="71.10.153.139" # ***************************************************************** # REMOVE THIS LINE WHEN ON ANOTHER NETWORK # ***************************************************************** NODE="cimbaoth" TARGET="/backup03/backup/kc8arj/" tar -czf ${FILENAME} /etc/opendv/* tar -czf ${FILENAME2} /var/log/opendv/* scp ${FILENAME} backup@${NODE}:${TARGET} scp ${FILENAME2} backup@${NODE}:${TARGET} rm -f ${FILENAME} ${FILENAME2} Clear out old logs on Mondays #!/bin/sh rm /var/log/opendv/*log.?.gz And finally the crontab: MAILTO=root@localhost.localdomain # Edit this file to introduce tasks to be run by cron. # # Each task to run has to be defined through a single line # indicating with different fields when the task will be run # and what command to run for the task # # To define the time you can provide concrete values for # minute (m), hour (h), day of month (dom), month (mon), # and day of week (dow) or use '*' in these fields (for 'any').# # Notice that tasks will be started based on the cron's system # daemon's notion of time and timezones. # # Output of the crontab jobs (including errors) is sent through # email to the user the crontab file belongs to (unless redirected). # # For example, you can run a backup of all your user accounts # at 5 a.m every week with: # 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/ # # For more information see the manual pages of crontab(5) and cron(8) # # m h dom mon dow command # # Backup logs each night 3 minutes before midnight zulu # 57 23 * * * /root/backitup # # Clear out gzipped logs each Monday right after backup # 59 23 * * 1 /root/cleanLogs
2016-10-02 09:43:06:
Doesn't look like cleanLogs is running, or at least not doing what is expected. Unfortunately, with no MTA, any messages are lost. cleanLogs and backitup modified to save messages from the last run as follows: ======================== backitup ================================ #!/bin/sh -x FILENAME=`date +'%Y%m%d-opendv.tar.gz'` FILENAME2=`date +'%Y%m%d-log.tar.gz'` NODE="71.10.153.139" # ***************************************************************** # REMOVE THIS LINE WHEN ON ANOTHER NETWORK # ***************************************************************** NODE="cimbaoth" TARGET="/backup03/backup/kc8arj/" date >backitup.log tar -czf ${FILENAME} /etc/opendv/* >>backitup.log 2>>backitup.log tar -czf ${FILENAME2} /var/log/opendv/* >>backitup.log 2>>backitup.log scp ${FILENAME} backup@${NODE}:${TARGET} >>backitup.log 2>>backitup.log scp ${FILENAME2} backup@${NODE}:${TARGET} >>backitup.log 2>>backitup.log rm -f ${FILENAME} ${FILENAME2} >>backitup.log 2>>backitup.log ===================cleanLogs======================================= #!/bin/sh date >/root/cleanLogs.log rm /var/log/opendv/*log.?.gz >>/root/cleanLogs.log 2>>/root/cleanLogs.log
2016-10-04 13:38:07:
Job didn't run first Monday because script wasn't marked executable. Next schedule is October 10.
ID | Estimate | Status | Description |
---|---|---|---|
985 | 2016-10-17 | Schedule 2030 install |
2016-09-12 10:30:56:
Schedule a time to move the repeater to 2030
ID | Estimate | Status | Description |
---|---|---|---|
992 | 2016-10-23 | Make backup SD |
2016-09-11 09:49:16:
Need to create a backup SD card immediately before taking repeater to site
2016-09-12 10:32:15:
Create a backup of the SD card. Moved date to the day before install since this wants to be the LAST thing we do.
ID | Estimate | Status | Description |
---|---|---|---|
993 | 2016-11-07 | Move to 2030 |
2016-09-12 10:54:35:
Install the repeater at the permanent site at 2030 building.
ID | Estimate | Status | Description |
---|---|---|---|
996 | 2016-11-30 | Test 100 watt amp |
2016-09-12 10:49:37:
Repeater will initially be set for 20 watts. It is unknown at this time whether the addition of an external amplifier will result in excess desense. After the repeater is at the site, an amp will be tested for coverage.
No comments:
Post a Comment