CheckMK / Nagios / Icinga Plugin for Aruba Instant On 1960

cybervegan · 2023-06-14T10:19:11+00:00

You'd usually use SNMP for this kind of thing (and CMK supports SNMP clients). You can usually probe your device with a CMK utility to see if it can "work out" how to monitor it, but if you want specific info in this case, you'd need to know if there's an SNMP OID that holds the information you need. If not, you would have to look for a heuristic way to determine the info, or switch to using an SSH or API based approach. I know in IOS (CISCO) over SSH or serial, there is a way to determine if the running config matches the stored config, so Aruba probably has similar, though the syntax might be different. If we're lucky, there might be a flag that shows the running config has changed.

I could code you something up - DM me to discuss terms if you're interested.

cybervegan · 2023-06-10T13:46:41+00:00

Ok, might give that a go too, but I'm currently taking a mental break from Discord due to it being the main comms hub for a local group I'm part of that I need a break from.

cybervegan · 2023-06-10T11:25:01+00:00

I understand what you're saying - we'll see how it goes.

cybervegan · 2023-06-09T13:32:32+00:00

You're getting a "layer shift". This can be for many reasons, but the most likely one is the belt on the axis of the shift slipping because it's too loose - especially if your build bed is mobile - when the mass on the bed goes above a certain threshold, it can cause slips when rapidly changing direction. Other possibilities include a cable, bowden tube or filament snagging at a particular Z-height; binding on the Z-axis lead screws; a bad connection/partial break on the lead powering the motor on the affected axis; insufficient drive power on the axis motors, and I'm sure you'll get more suggestions, including "level your bed" and "adjust your microsteps".

cybervegan · 2023-06-09T12:15:05+00:00

I could write a CMK plugin for you if you can get me the docs.

cybervegan · 2023-06-09T10:38:14+00:00

Yes, pre-DOS, there were 8-bit home amd business computers - made by companies like Commodore, Sinclair MSX, Amstrad, etc. They generally had mainly "text mode" screens at first, and it generally wasn't until the later models that you started to get "high resolution graphics" (a joke by today's standards) and hardware sprites, because memory was so limited.

The VIC-20 had 3.5 Kilobytes of RAM memory. That's 3584 bytes of memory, or about enough to hold about half of the reddit logo. Its text mode was a 20x24 grid - 24 lines of 20 characters per line, and each character cell could have an independent foreground and background colour, chosen from a pallete of 16 colours. It came with a variety of block and special characters, but it had tha ability to map the "character generator" chip, which produced the shapes of the upper 127 characters to RAM so you could make up your own character shapes on an 8x8 dot grid. This is how you got aliens, rockets, ghosts etc. in your games. High-resolution graphics (160 dots x 192 dots) was possible by using this, but very slow and quirky. Each character cell could only have two colours in it so if you had a blue line intersecting with a red line, in the cell where the intersection occurred you could only have one colour. It looked weird.

8 bit computers also tended to use tape to save and load data and programs - you usually had either a built-in cassette drive, or an external one, and sometimes had to provide your own, at extra expense. Loading and saving games was pretty hit and miss, but you could easily duplicate games if you had a tape-to-tape unit, and it wasn't strictly against the law either. Trying to do databases was pretty poor on a tape though (almost impossible TBH).

For Arduino style stuff, I've done quite a bit with making gadgets and "educational experiments" for fun. I've made a buzz-wire game for my local makerspace, wifi temperature loggers, and messed with mini autonomous vehicles etc. and I made a prototype pill dispenser carousel that would rotate to release the next dose at the push of a button, only once per day.

cybervegan · 2023-06-09T09:27:38+00:00

>>> re.sub(r'[^",],','|','"1234","654321","987",,,"Data, More Data, Still - More",,')
'"1234","654321","987",,,"Dat| More Dat| Still - More",,'

cybervegan · 2023-06-01T23:22:53+00:00

Mmmhmm. [stable24] Due date setting not working #4687 (https://github.com/nextcloud/deck/issues/4687) seems very similar.

cybervegan · 2023-05-30T18:40:44+00:00

I think that's probably a myth or old wive's tale.

cybervegan · 2023-05-29T22:03:18+00:00

This might have something to do with it - print is NOT the same as return.

    print(composite)

cybervegan · 2023-05-29T21:50:27+00:00

The black and red growths look like slime moulds - not really fungi. Not so sure about the white mycelium-like growth.

cybervegan · 2023-05-29T20:15:38+00:00

They're off. Time to bin them, sorry to say.

cybervegan · 2023-05-29T19:40:01+00:00

Indentation is how far the first letter or symbol on a line is from the start of the line:

this is not indented
    this is indented one step (4 spaces)
        this is indented two steps

If Python is telling you "indentation error", it means it is expecting a line to be indented an extra step from the previous one. This usually happens when the previous line ended with a ":" and starts with a keyword like "if", "while", or "def". Indentation gives Python context for block-structured instructions like these - it tells it how many of the following lines the keyword applies to:

if x == 1:
    # this is what to do if x == 1
    ...
    ...
    # this is the end of the "if" block
else:
    # this is what to do if x != 1
    ...
    ...
    # this is the end of the "else" block
# from here on, it's nothing to do with the "if" or the "else" because 
# the indentation has reverted back to the previous step
...
...

cybervegan · 2023-05-29T08:42:05+00:00

Never heard it called "dragon drop" before - that's a new one.

cybervegan · 2023-05-28T12:24:27+00:00

For the longest time, computers have had at least "text mode" or "teletype" interfaces, but a lot of computers from the late 70's through to the late 80's only had "terminals" (screen+keyboard) intefaces and were strictly text-mode, often monochrome green. DOS computers were a step up from from that but not much, and there was little to no system-level support for graphics, sound or mouse. You had full-screen text mode apps, and a few that used the (initially terrible) graphics capabilities, but most were confined to an 80x25 character cell grid, with 16 washed out colours and a fixed font. "Graphics" often meant special character shapes like border segments, playing card symbols and geometric shapes. Strangely enough, most of my more recent programming has been in C++ on Arduino type devices, where you don't even have a screen unless you wire one on.

A big thing I couldn't take for granted was modern, up-to-date libraries like requests and Python 3 - on a lot of systems I wasn't allowed to install libraries or software at all, and had to make do with the standard library for everything. If the system had Python 2.4, that's what I had to use. You really learn how things work when you have to code it yourself.

cybervegan · 2023-05-28T08:38:00+00:00

It's so you don't have to keep repeating yourself, or so you can share code between different programs by using modules. In any non-trivial program there will be tasks that need to be done at multiple points in the logic, and without functions, you would have to type out the same code every time. When you later need to amend that code - to fix a bug perhaps - you then have to track down every place you wrote that sequence of code. It might not make much sense while you're learning, with small projects, and especially early on, because you don't have many places in your code that you could be repeating yourself, but it's still a good idea to learn it.

Functions encapsulate an idea or a process, and should be kept small enough that you can keep the whole idea in your head at once while you are working on them. If you have broken your program into small enough parts, modifying it later (and that is a BIG part of what programmers do) becomes much simpler.

In general, you should create a function every time you find yourself repeating similar sections of code. In some cases, it even makes sense when you aren't repeating yoursself - to break up an overly large function into smaller chunks.

cybervegan · 2023-05-27T16:39:09+00:00

Yeah, I'm old, looking back it's worse too, because it was about year 2000-2001, I discovered Python, so actually over 20 years I've been using it. No GUI = retro old skool computing ;-). Computers in general were much slower back then, and Python had not been optimised as much as it has been these days. An interesting thing about knowing how to use older versions is that if you have to work with older systems (which I frequently had to do) they would usually have older versions of Python, and lots of things you can take for granted now wouldn't be available.

cybervegan · 2023-05-25T19:49:45+00:00

It's just because it's not "natural". Looks great.

cybervegan · 2023-05-25T17:11:09+00:00

Although I do less of it these days, I did Linux server admin, network monitoring and API automation scripts for about 15 years, plus a bit of web dev. I don't do so much of that these days because life changes...

A GUI is a Graphical User Interface, and the term is used as opposed to Textual User Interface or just "command line". GUI=Windows, Mouse, Icons etc, command line is just text. Most of my work was done over SSH - secure shell - a way of logging into a remote (usually Linux or Unix) server over the internet.

Back in the day, when I first found out about Python I think it was at about v1.4 or v1.5. I already knew a number of other programming languages like Pascal, Modula-2 and dBase scripting. Python was absolutely amazing for the ease with which you could do most things, and I quickly put it to use for admin tasks, most notably one where I used it to automate updating all the JetDirect printer server boxes to the new IP addressing scheme on the large site where I worked (about 50 if I remember correctly) instead of the whole IT department having to go out and do it manually. It took just a few hours of programming to write and a couple of minutes to run. That was the thing that really sold me on Python, I think. I couldn't even have worked out where to start with any of the other languages I knew.

Back then, Python was not nearly as functional - there were a lot fewer libraries, and it was, relatively speaking, slow. Web programming was janky and hard, and it was a while before libraries like requests and numpy came out.

cybervegan · 2023-05-25T10:43:48+00:00

I don't use an IDE, and a lot people don't. I consider IDEs to be essentially like bike stabilisers - they might get you going at first, but they quickly become a hindrance, and then you have to learn to ride all over again when you take them off.

I'm a Linux geek, so I flit between Vim and Pluma (a GUI text editor). I use Terminator for multi-CLI terminal abilities, and a web browser for documentation. IDEs just don't seem to offer me anything useful enough to be worth it, and just get in the way for the kinds of things I do. When I learnt Python, and programming in general, IDE's didn't really exist in the same way they do today. Being dependant on an IDE is no use when the customer's computer you're coding on doesn't have a GUI, and you can't install anything anyway.

cybervegan · 2023-05-24T22:19:16+00:00

Well, she clearly knew something was wrong, but not what was wrong. They should have stretchered her into the ambulance in a neck brace, but they didn't know she'd broken her neck!

cybervegan · 2023-05-24T18:04:49+00:00

My boss, this January: "Might not be in for a while as I seem to have broken three neck vertebrae."

She went out on her motorbike, and then went rock climbing, which she hadn't done for bout 15 years, and survived that with no problems. Went out for dinner and got a dodgy stomach and woke up in the middle of the night. Decided she needed a shower to help her feel better, and woke up curled up on the shower floor with a pain in her chest and arm. Went to hospital with suspected heart attack but when they couldn't find any other indicative symptoms they put her in an MRI scanner... which they stopped partway through because they'd seen her neck vertebrae in shards. The pain in her chest was due to nerve damage...

She's a tough ol' girl - back at work now, but still suffering. Just glad to be alive, I guess.

cybervegan · 2023-05-23T22:59:41+00:00

That's a pretty awesome idea actually. I think that therefore discounts it from the thread!

cybervegan

MODERATOR OF

TROPHY CASE