Differences

This shows you the differences between two versions of the page.

--- haas:status [2015/10/26 04:40] – [cron unhappiness] wedge
+++ haas:status [2022/08/28 16:15] (current) – [August 28th, 2022] wedge
@@ Line 5: / Line 5: @@
   * update grade not-z scripts to handle/be aware of winter terms
   * update system page for (new)www
-    * include information on db server
-  * upgrade mail VM to jessie/opensmtpd
-  * upgrade LDAP VMs to jessie
-  * create new router, using OpenBSD 5.7
   * scripts to write:
     * user homedir backup pruning script
@@ Line 82: / Line 78: @@
     * https://github.com/zeoeng/zeo-android-api
     * http://eric-blue.com/2013/06/09/life-beyond-zeo/
+  * rxvt / .Xresources
+    * http://www.askapache.com/linux/rxvt-xresources.html
 ======Other Days======
-======October 26th, 2015======
-A lot of time has passed since my last update... not that it hasn't been without activity. The LAIR moving, the LAIR getting set back up... merely just a lapse in my documenting habits.
-=====disk space=====
+======August 28th, 2022======
-I am currently on an automation kick, to try and reduce the amount of information that gets pushed into my sphere of attention. Specifically non-actionable information (like normally running systems with adequate amounts of free diskspace). I only want to be notified if a normally running system is no longer normally running, and in this specific context, if its free diskspace reaches at least 80% utilization.
+=====updated dokuwiki=====
+After enduring constant nags of available updates that I could never resolve, and despite an active semester underway, I committed to updating to the recent major release of dokuwiki (igor), and after wrestling with various file permission issues, was seemingly successful in performing the upgrade AND eliminating the annoying nag messages.
+=====dokuwiki included pages no edit button (fixed)=====
+I wanted a read-only base project page, with notes namespace-included content that users could edit.
+Unfortunately, that particular combination did not work, at least, not until I did some searching and found: https://github.com/dokufreaks/plugin-include/issues/132
+<code php>
+function html_secedit($text,$show=true){
+    global $INFO;
+    if((isset($INFO) && !$INFO['writable']) || !$show || (isset($INFO) && $INFO['rev'])){
+        $include_SEC_EDIT_PATTERN = '#<!-- EDIT{(?!.*PLUGIN_INCLUDE).*?} -->#';
+        return preg_replace($include_SEC_EDIT_PATTERN,'',$text);
+    }
+    return preg_replace_callback(SEC_EDIT_PATTERN,
+                'html_secedit_button', $text);
+}
+</code>
+======March 12th, 2020======
+=====borked journal, maybe fix=====
+<code>
+tune2sf -O ^has_journal /dev/<dev>
+e2fsck -f /dev/<dev>
+tune2sf -j /dev/<dev>
+</code>
+Obtained from:
+  * https://www.linuxquestions.org/questions/linux-newbie-8/aborted-journal-and-volume-remounted-read-only-812216/
+======November 21st, 2019======
+=====pi4b dual head=====
+Apparently I was missing something when building up from the lite version of raspbian. For when I popped in a new raspbian (the full desktop version) everything came up just fine.
+Oh well. At least things are now working as they should.
+======November 19th, 2019======
+=====pi4b dual head issues=====
+Attempting to set up a fresh raspbian install on the pi4b. Strangely, getting issues with dual head: it is only coming up in mirrored mode (or when I play with it, not at all).
+The only major variables that have changed:
+  * new raspbian release (I could test my old setup.. that is easy enough to verify)
+  * no longer using HDMI monitors, but the DVI connections on the LAIR monitors.
+    * further investigation suggests the pi may be seeing identical EDIDs and other monitor ID things, so it is defaulting to a mirroring mode.
+    * **tvservice -l** consistently identifies two displays, so the hardware sees it, the software is not.
+Interestingly: my old raspbian setup IS working properly. So what is different between the two?
+======March 15th, 2018======
+Setting up the raspberry pi 3 for use in the comporg class. Named it **pi3b**, and will get the IP of 10.80.2.48; running the latest stable release of rasbian.
+Looking to get LDAP and autofs going, then installing packages to make it minimally functional for our purposes.
+======March 6th, 2018======
+Aside from an attempt at restarting my status-reporting habits in January of 2017, I totally neglected it for the remainder of the year.
+So here we go, attempting another go. Will we be successful?
+=====pods configured for better SSD operation=====
+In other recent projects, I encountered some useful configuration options to improve performance, and avoid some anti-longevity side-effects of default settings.
+I ended up taking a Debian USB installer, booting each pod in rescue mode, getting to a prompt, and running the following on EACH:
+<cli>
+# umount /
+# tune2fs -O ^has_journal /dev/sda1
+# tune2fs -o discard /dev/sda1
+</cli>
+Then on the master nodes, I enhanced both **/etc/fstab** and **/etc/rc.local** as follows:
-Aside from sokraits/halfadder, which still need a new pruning script, only lab46 and log were reaching saturation. log especially so.
+<code>
+# /etc/fstab: static file system information.
+#
+# <file system> <mount point>   <type>  <options>         <dump>  <pass>
+/dev/sda1       /               ext4    noatime,nodiratime,discard,commit=600,errors=remount-ro 0       1
+tmpfs           /tmp            tmpfs   defaults,noatime,mode=1777 0 0
+tmpfs           /var/log        tmpfs   defaults,noatime,mode=1777 0 0
+tmpfs           /var/spool      tmpfs   defaults,noatime,mode=1777 0 0
+tmpfs           /var/tmp        tmpfs   defaults,noatime,mode=1777 0 0
+</code>
-lab46 was simply a matter of clearing out /root of unnecessary files (.cabal, an apparent haskell module repository) and purging a no-longer-used kernel.
+Note how I put the log files in RAM too (on the pods)... this should greatly reduce extraneous writes.
-log I ended up rolling some rather large and long-running log files. Compressing them (-9) really did the trick.
+Then at the bottom of **/etc/rc.local**, I added:
-======October 25th, 2015======
+<code>
-=====cron unhappiness=====
+#!/bin/sh -e
-Seems cron wasn't entirely happy with my new scripts, and wasn't overly happy in general (was having trouble contacting the ldap server). I removed the auth3 entry and restarted it, and fixed various path issues in the troubled scripts... things seem to be okay now.
+#
+# rc.local
+#
+IPADDR=
+while [ -z "${IPADDR}" ]; do
+        IPADDR=`/usr/local/bin/iface | /bin/grep -v 'lo' | /usr/bin/head | /usr/bin/cut -d' ' -f2`
+        sleep 1
+done
+/bin/hostname `/usr/bin/host ${IPADDR} | /usr/bin/cut -d' ' -f5 | /bin/sed s/\.$//`
+/usr/bin/host ${IPADDR} | /usr/bin/cut -d' ' -f5 | /bin/sed s/\.$//  > /etc/hostname
+echo "${IPADDR}    `cat /etc/hostname`"                              > /etc/hosts
+echo "127.0.0.1    localhost"                                       >> /etc/hosts
+echo "10.80.2.46   lab46.g7n.org lab46.corning-cc.edu"              >> /etc/hosts
-=====class metrics=====
+echo deadline > /sys/block/sda/queue/scheduler
-My various class metrics scripts, data, and graphs got some extra love... I now have late submissions reporting, along with class-centric metrics pages allowing for an overall trends graph being (manually) generated.
+echo 1 > /sys/block/sda/queue/iosched/fifo_batch
-I'll have to automate that at some point...
+exit 0
-======October 24th, 2015======
+</code>
-=====idler-ng=====
-Perhaps not quite worthy of 'ng', but I did take some time to polish and comment idler, and attempted a first draft at bringing a (now that I think about it, incomplete) weekly idle time reporting. But at least it has been given some attention, and the logic re-contemplated (even if not immediately changed).
-I actually should pull some data from the 'gn gather' records being studiously kept... or do more of a week-by-week offset sort of thing.
+As the **deadline** scheduler has frequent mention of usage with SSDs.
-=====calcweek module of gn=====
+Useful URLs:
-While investigating a (once again) break week offset bug, I discovered the source of the problem... break week offsets were only being recognized if the span of days was exactly 5. My break weeks were entered including weekend dates, so they were always larger than 5. A '**-ge 5**' seemed to do the trick nicely.
-=====cron stuff and new script: projtasks=====
+  * [[https://github.com/alghanmi/ubuntu-desktop_setup/wiki/SSD-Configuration-on-Linux]]
-I've been wanting to further optimize and automate some things in cron, chief among them **process_attendance**, **opusjournal**, and the various **graphmetrics** scripts being fired off by my neat chain of **at** jobs.
+  * [[https://www.howtogeek.com/62761/how-to-tweak-your-ssd-in-ubuntu-for-better-performance/]]
+  * [[https://wiki.debian.org/SSDOptimization]]
-**projtasks** simplifies the whole **at** job thing, eliminating them and being run once per day. It is aware of not only what projects a class has, but what projects are currently active and in need of seeing metrics page refreshes.
-After various tweaks, I seem to have gotten a number of my other scripts cooperating with cron as well.
-=====holiday themed motd=====
+=====lab46too SSD updates=====
-While I was digging in other stuff, I rediscovered a set of holiday themed motd's I had deployed a number of years ago (say, 2011)... a few **at** jobs and it is now in progress.
+With the pods having seen their SSD updates, I am looking to do the same for lab46too, testing to make sure the similar changes can be applied to that machine before rolling them over to lab46 proper.
+I've updated the /etc/fstab and /etc/rc.local files accordingly on lab46, so those changes have been synced over to lab46too on a recent rsync run.
+I had to remove the commit=600 from the /home partition. For some reason it didn't want to mount with that.
 ======Month Status Page Navigation======
-^  [[haas/status/status_201505|Previous Month]]  ^  [[haas/status|Current Month]]  ^  [[haas/status/status_201511|Next Month]]  |
+^  [[haas/status/status_201701|Previous Month]]  ^  [[haas/status|Current Month]]  ^  [[haas/status/status_201804|Next Month]]  |