Mitigating Pi-hole ISE 500 Error on the "Long term data - Query Log"
When selecting a large date range on the long term data Query Log, say
last 30 or even last 7 days, I’d be greeted with the following error
message and some more information in Lighttpd’s logs.
And the relevant line in /var/log/lighttpd/error.log:
2020-06-07 19:40:24: (mod_fastcgi.c.421) FastCGI-stderr: PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 10489856 bytes) in /var/www/html/admin/api_db.php on line 422
Request Tracker: Automatically Set Ticket Owner to Specific User
Request Tracker is an insanely powerful ticketing system. I started using RT about 6 months ago, and I’ve been absolutely enjoying every hour of it. About 2 months ago, I used a guide on the RT Wiki titled AutoSetOwner to automatically set every new ticket’s owner to myself, on my personal hosted instance of RT. It works great!
Now, since I’m more or less the only IT person at this company, it’s safe to assume that any ticket in the IT Projects, or certain other queues should belong to me. So I adapted the AutoSetOwner scrip to automatically set the owner of a new ticket to myself, on certain queues. I have to admit, since I don’t know Perl hardly at all, it took a little trial and error to get this right, fortunately RT’s logs came in useful and I now have a working scrip!
VeganMSP.com
Late one evening, I was having dinner with some vegan friends of mine at Comet Cafe in Milwaukee, Wisconsin. The Comet is a relatively punky-style small diner in the Lower East Side. We stopped in Milwaukee for dinner after spending about 16 hours on the road. The three of us had all rode together to a small vegan get-together in Knoxville, Tennessee.
This article was originally published on the old blog on 2018-09-03. It was republished here on the new blog on 2019-10-28, since I hadn’t mentioned VeganMSP.com before and I feel it’s one of my more important projects.
Remove and Prevent Access to Shut Down Commands Except on my VMs
I would do anything in my power to prevent the accidental shutdown of a critical server. Unfortunately, Windows makes it really easy to accidentally shut down a computer.
One slip of the wrist would cause you to “Shut down” a machine instead of “Sign out” of it. I’m not perfect, I’ve made that mistake before.
Originally we created a Group Policy Object to control this behavior. It’s pretty easy to set up.
Pleroma: admin-fe
I recently switched from Mastodon to Pleroma, for no real reason in specific other than: Pleroma is far less resource intensive. Setting up Pleroma was a breeze compared to setting up Mastodon–I remember having a great deal of trouble. I enjoy the simpler interface as well. While Pleroma doesn’t have all of the flashy features1 mastodon does, I don’t need or use them anyway.
Tonight I came across admin-fe for Pleroma, and thought I’d give it a shot even though I’m the only use on my instance. Installation documentation is lacking for the project, so I thought I’d offer my notes in case they could be useful to anyone else.