Roundtable August 2017

roundtable@muug.ca

8 participants
6 discussions

Neat bitcoin tracker
by Adam Thompson 25 Aug '17

25 Aug '17

I know we have a number of Bitcoin enthusiasts on the list, so I forward without further ado: http://www.bitlisten.com/ -Adam

2 1

HPC sysadmin job at UVic
by Grigory Shamov 23 Aug '17

23 Aug '17

Hi, Not sure if it is the appropriate list. A sysadmin job, University of Victoria. https://uvic.mua.hrdepartment.com/hr/ats/Posting/view/3034 -- Grigory Shamov WestGrid Site Lead / HPC Specialist University of Manitoba E2-588 EITC Building, (204) 474-9625

1 0

Best update problem ever
by Glen Ditchfield 18 Aug '17

18 Aug '17

"When I run apt-get upgrade on my Ubuntu 17.04 machine, sometimes it starts Dwarf Fortress by itself." -- https://askubuntu.com/questions/938606/dwarf-fortress-starting-during-apt-g…

3 2

mail server help
by Trevor Cordes 18 Aug '17

18 Aug '17

I just started getting some weirdness with some email sent to my mail servers. Greylisting "come back later" (451) messages are being interpreted (it appears) by remote MTAs as a 5xx level error, meaning they immediately abort send attempts and bounce the email! I have never seen this before. I've seen it from two separate remote MTAs so far, but from reports I'm getting in, it's happening on more. Here's what I get from umce3cip03.ad.umanitoba.ca: Remote Server returned '554 5.0.0 <[50.71.247.87] #5.0.0 smtp; 5.1.0 - Unknown address error 550-'<foobar(a)tecnopolis.ca>... 451 4.7.1 Greylisting in action, please come back later' (delivery attempts: 0)>' On my server sendmail log I see: Aug 16 08:43:15 pog sendmail[14379]: v7GDhFav014379: Milter: to=<foobar(a)tecnopolis.ca>, reject=451 4.7.1 Greylisting in action, please come back later So umce3cip03.ad.umanitoba.ca appears to be taking my 451 and turning it into a 500/554/510 permanent error. I also see this from yahoomail, but that's a different situation because yahoo is always considered "broken mta" in milter-greylist and we must whitelist all of their servers... but, the usual/previous symptom was yahoo would keep retrying as normal, just with a different IP each time, thus never passing greylisting. And now yahoo is doing the same thing as umce3cip03.ad.umanitoba.ca above (when I haven't yet whitelisted the particular IP that day, grrr): Sorry, we were unable to deliver your message to the following address. <foo(a)tecnopolis.ca>: 550: <foo(a)tecnopolis.ca>... 451 4.7.1 Greylisting in action, please come back later So at least 2 MTAs, probably more, are changing 451 greylist into 5xx. Is there some new massive change out there to basically take greylist MTAs as broken? Is there a way to find out what MTA (or outsourced service provider) umce3cip03.ad.umanitoba.ca is using? Perhaps there is just one brand that unilaterally decided on this action? I can find no google hits on any of this. :-( There is an easy workaround/gotcha: if people wait the greylist timeout (usually 2 to 20 minutes) and then resend the same to-from-ip tuple email, it will go through as their server will have been whitelisted in the interim! But that makes it harder to troubleshoot this problem because it then becomes transient. If any MUUGers have problems with MUUG mailing lists bouncing, please resend your email after 1 hr if it hasn't showed up yet (you can check the website mail list archives section) and/or please email me directly with your bounce email message (twice, wait 20 mins!) so I can solve this for both MUUG servers and my own. If this problem is a) permanent/deliberate, and b) widespread, I think that spells the death of greylisting (grrrrr...) and the nearing of "spf strict" enabling.

3 5

git subtree pull error
by Trevor Cordes 17 Aug '17

17 Aug '17

Hi to all gitters who helped me a couple of years back. I'm implementing a subtree using git subtree (better fits my model than submodules), but I'm trying to do my 1st merge/pull (after the initial subtree import) and I'm getting a weird error: git subtree pull -P Nub nub master * branch master -> FETCH_HEAD fatal: refusing to merge unrelated histories I'm conceptually confused as to why it's saying this. The whole subtree command is basically the same as when I setup the remote and did the initial bits. So why aren't the subtree histories related? Or is it confusing the entire project with the subtree? The google hits I get aren't really helping me since they aren't really specific to subtree. If I add a squash: git subtree pull --squash -P Nub nub master Then it works and I can commit. If I take out squash and add --allow-unrelated-histories it barfs because subtree doesn't understand --allow-unrelated-histories, though I guess I could do the separate parts manually and merge with --allow-unrelated-histories. However, in my understanding, I don't want squash nor feel I should require allow-unrelated-histories? Am I wrong? The reason I don't want squash is that I want all the subtree history mixed into my main project because I want to be able to bisect on the entire project+subtree if I ever need to (they are extremely tightly coupled). Plus, I don't understand why squash solves the "unrelated histories" error! That makes me nervous as to what is going on under the hood, and I'd like to ensure I am doing this correctly before I commit my entire project to a specific course of action. Anyone understand this git subtree stuff better than me who can take a mo to explain? Thanks!!!

1 0

Intel watchdog in linux?
by Trevor Cordes 06 Aug '17

06 Aug '17

I have an Intel S1200BT-family server board which I'm pretty sure has a "watchdog" option in the BIOS. I find myself wanting this feature while working through a kernel hang bug (64-bit this time!). The board is considered an entry-level (E3) server board so while it does have many server bells, it's missing some of the higher-end whistles. Does anyone know if Linux has support for this watchdog? Where do I start looking in terms of packages/programs to support this? I'm hoping this is old hat to someone here... Thanks!

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

Roundtable August 2017