From zanchey at ucc.gu.uwa.edu.au Wed Oct 4 15:32:07 2006 From: zanchey at ucc.gu.uwa.edu.au (David Adam) Date: Wed, 4 Oct 2006 15:32:07 +0800 (WST) Subject: [tech] Arctic's authentication with LDAP Message-ID: I have no idea what's going on here. Arctic refuses to authenticate users via LDAP for some reason. I think it's actually a problem with the OpenLDAP server, but debugging it is proving very difficult at the moment. We had logging turned off, and the only error message on the server side I'm getting is: "Error: unable to open Berkeley db /etc/sasldb2: No such file or directory" I have no idea if this is normal or not, mainly because I don't have any previous logs to look back at. I did upgrade (and briefly break) slapd for a little while a few days ago, but it doesn't appear to have affected any other machines. If it's not fixed in a couple of days, I'll just put Arctic back on NIS for a while. It has been suggested that we try a non-OpenLDAP LDAP server, but I think that might be a mit more long-term. Cheers, David Adam UCC Wheel Member zanchey at ucc.gu.uwa.edu.au From matt at ucc.asn.au Sat Oct 14 18:57:02 2006 From: matt at ucc.asn.au (Matt Johnston) Date: Sat, 14 Oct 2006 18:57:02 +0800 Subject: [tech] Bronze Message-ID: <20061014105702.GX15021@ucc.gu.uwa.edu.au> Hi all. Alwyn, Grahame and I poked the the alloy switch (bronze) this afternoon. At one point I ended up making it unresponsive so had to reset the config (think I put the management on a bad vlan trunk). Its default IP is 192.168.1.1. I've put some config screenshots at http://matt.ucc.asn.au/alloy/new/ , with a description of the setup. Connect to 192.168.1.1 on port 1 (no vlan) for the config interface. Port 1 should probably be left as a straight non-tagged port, so that it's easy to connect a non-vlanning client to fix things without resetting defaults. Port 2 is good for madako's trunk, other trunk ports can be added as required. Interestingly it didn't crash at all today, so maybe it is extraneous traffic that causes it to crash. If we firewall vlan 4 well on madako, hopefully it should be OK... (maybe beware other random LAT traffic etc? dunno). Matt readme.txt: [msh] 2006-10-14 The alloy is configured as per the screenshots. Note that the management vlan is set to 4. In case we eventually might get SFP things, ports 23/24 have been left the same as other ports, and 1/2 have been used for mgmt/trunking. Port 1 - not tagged, vlan 4 by default, 192.168.1.1 is mgmt. Port 2 - tagged, vlan 4 "by default" doesn't seem to work. use this for madako's trunk. If more trunks are required, leave port 1 alone and give some more ports like port 3 perhaps, since then there's always a plain non-trunk working management port (1). Other than that, the upper odd ports are for machineroom, lower even ports are for clubroom. From zanchey at ucc.gu.uwa.edu.au Thu Oct 19 09:32:43 2006 From: zanchey at ucc.gu.uwa.edu.au (David Adam) Date: Thu, 19 Oct 2006 09:32:43 +0800 (WST) Subject: [tech] Martello hung (again) Message-ID: Hi everyone, I managed to hang Martello again this morning while doing some `apt-get install`ing. I'm not sure what causes it, although fsck(8) is reporting that there are some errors on /var - we might need to take it down to single-user and do a full filesystem check at some stage. David Adam UCC Wheel Member zanchey at ucc.gu.uwa.edu.au From nick at ucc.gu.uwa.edu.au Sun Oct 29 22:26:16 2006 From: nick at ucc.gu.uwa.edu.au (Nick Bannon) Date: Sun, 29 Oct 2006 22:26:16 +0800 Subject: [tech] Snack machine (was Re: [ucc] Minutes 2006-10-26) In-Reply-To: <1161831061.13475.101.camel@frobisher.madeley.id.au> References: <1161831061.13475.101.camel@frobisher.madeley.id.au> Message-ID: <20061029142616.GD10186@ucc.gu.uwa.edu.au> On Thu, Oct 26, 2006 at 10:51:01AM +0800, Davyd Madeley wrote: > - snack machine is broken, slots don't rotate > - restocked the machine, not that anyone can get it [...] Probably overstocked for now - we'll have to get sell the perishables. The top half of the redskins have melted, leaving a minor mess. ::-/ The snack machine was acting oddly, now it's not acting at all. It _will_ rip you off - I've put signs on it. The motor on each slot is properly driven at about 24V (I measured 21V), but some slots were driving intermittently. Driving most columns (eg column 9, e.g. slot 91) would make that slot turn, but column 1 (e.g. slot 11) would make a partial turn at about 7V. However, nothing is turning now. Anyone want to help me work through the schematic to make the minimal test to drive a single motor? The original ROM has some diagnostic facilities, however, I don't think it will boot fully when the communication to the coin mechanism fails. ([DAG] and co's ROM has useful PEEK and POKE diagnostics too! (currently enabled) but again, we'll have to dig a bit deeper) Nick. -- Nick Bannon | "I made this letter longer than usual because nick-sig at rcpt.to | I lack the time to make it shorter." - Pascal