Well, my first interview is Tuesday, even before my final pay check is due

@DustinB3403 said in What Are You Doing Right Now:

@RojoLoco said in What Are You Doing Right Now:

@DustinB3403 said in What Are You Doing Right Now:

@RojoLoco That is a totally different life style to what I was imaging...

So where do they grow their plants if they don't have land to work? Where do they sleep if they don't own or rent? And don't they ever just get an urge to have a big fat juicy steak with a side of shrimp?

The answer to all those queries is "who cares, they're filthy hippies".

hey now, hippies have a use, like human shields.... or fertilizer for feed for beef farms..

Yes, they made my news feeds again today.

https://www.bleepingcomputer.com/news/security/hardcoded-password-found-in-cisco-software/

Since Cisco keeps being so popular with the security breaches and vulnerabilities, I figured it's time they get their very own thread.

Well, looks like I will be able to make it, thanks to @DustinB3403!

Dilbert and one of the big topics around here:

Thought I'd drop one of my current projects here. It started as just wanting a way to see what the temperature in a room is without having to have someone go check. (It's another building in a locked room few people have a key for.)

We already have lots of project cases, and also already had a Raspberry Pi. The new $5 Pi would need a network connection of some sort, so figure $10 for the networked PC ($20 if you need a power supply and memory card as well). I splurged at $13 for a combination temperature and humidity sensor. I went ahead and added a door sensor as well, it was $2. I also got a Cobbler Plus GPIO Breakout for $8 and a Perma-Proto board for $6. Total cost for me was $29. If you need a Pi as well figure ~$50 for everything. Compare that to any of the commercial offerings!

I'll post the code I use for everything here, along with references where possible. After all, that's where the real cost of these little things end up being.

It might be good to add a battery backup to it as well, which is quite easy, but I have no real need for that (if the power is out, the temperature isn't going to be getting out of control.) Adafruit makes it really easy.

@eddiejennings said in What Are You Doing Right Now:

Thing learned today: Domain controller must have SMB v1 enabled for a Server 2003 member to join the domain.

I learned that I only have to get inside your LAN in order to steal all the network data.

This is mostly to make things a matter of public record, in addition to a bit of a rant.

Got a call yesterday morning. They can't process credit cards. That office happens to use Intuit/Quickbooks for everything from inventory tracking, to payment processing and accounting. I've been down the road of getting away from Intuit often. Don't know if this will push them past the edge or not.

Ok, spent 2 hours manually doing updates because the automatic ones broke along the way somewhere. Updates complete. Good, we should be up and running. They try to login, and get asked for a code. Ok, check the email address... nothing.

Now I'm calling Intuit support (bad idea, but we're basically not in business at this point.) That's a 3 hour call where I'm told something is wrong with our email server.

Fine, hang up with one unhelpful peon. Go eat lunch (3:30pm at this point, my blood sugar is about to tank.)

Get back into the office around 4:30. Enough time to find something very interesting in the server logs...

2016-10-05 14:01:56 H=lvmailappout12.intuit.com [199.16.139.22]:30939 sender verify fail for <[email protected]>: response to "RCPT TO:<[email protected]>" from mailin.intuit.com [206.108.40.19] was: 550 #5.1.0 Address rejected.
2016-10-06 11:17:10 H=mailout203.intuit.com [206.108.40.17]:49121 X=TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256 CV=no F=<[email protected]> rejected RCPT <[email protected]>: Sender verify failed

Now, I spent way to much time figuring out how to deal with spam, and have gotten it figured out for the most part. So, they are sending a confirmation code out using an address that their own email server does not acknowledge as being valid. Yet it's somehow my fault that the email is not being delivered.

Spent another 2 hours on the phone this morning going over the same stuff. We're working through alternatives, none of which are something the business would normally find acceptable.

This on top of them having me enable SSL2 in the browser. Uhm, these computers have to remain PCI compliant, and they just purposely made them non-compliant.

Malicious company, let it be known.

Getting noticed is easy!

Getting the right kind of notice is very hard!

http://www.bleepingcomputer.com/news/security/900-000-routers-knocked-offline-in-germany-amid-rumors-of-cyber-attack/

On Facebook, Deutsche Telekom engineers recommended that users unplug their devices, wait for 30 seconds and restart their router. If the equipment fails to connect to the company's network, engineers told users to disconnect their device from the company's network permanently.

To compensate the downtime, Deutsche Telekom is offering free mobile Internet until the technical problem is resolved.

DSL routers all over Germany, and presumably worldwide if anyone else happens to be using the same DSL Modem that got hit by this.

@thwr, hope you're still running!

Next up from the Docker site, how to actually enable the GPU in a Docker Compose file.

Example of a Compose file for running a service with access to 1 GPU device

services:
  test:
    image: nvidia/cuda:12.3.1-base-ubuntu20.04
    command: nvidia-smi
    deploy:
      resources:
        reservations:
          devices:
            - driver: nvidia
              count: 1
              capabilities: [gpu]

I've been working on a bunch of stuff lately, and I'm going to be recording some of the annoyances and fixes in the near future.

For now, it's Docker and getting access to Nvidia cards in containers.

For starters, just use Ubuntu Desktop. I know it sucks running a desktop for servers, but in this case the Desktop installer allows you to install the Nvidia proprietary drivers. I had no luck getting the proprietary drivers working on Ubuntu Server.

Step 1: Install Ubuntu Desktop and make sure to select the proprietary Nvidia driver.
Step 2: Verify nvidia-smi has the correct card(s) listed.
Step 3: Run the script below. Sourced from the Docker and Nvidia sites.

Edit: added nvidia-docker2 to the installed Nvidia software

# Add Docker's official GPG key:
sudo apt-get update
sudo apt-get install ca-certificates curl
sudo install -m 0755 -d /etc/apt/keyrings

sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc
sudo chmod a+r /etc/apt/keyrings/docker.asc

# Add the repository to Apt sources:
echo \
"deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu \
 $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | \
sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

sudo apt-get update

sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

curl -fsSL https://nvidia.github.io/libnvidia-container/gpgkey | sudo gpg --dearmor -o /usr/share/keyrings/nvidia-container-toolkit-keyring.gpg \

  && curl -s -L https://nvidia.github.io/libnvidia-container/stable/deb/nvidia-container-toolkit.list | \

sed 's#deb https://#deb [signed-by=/usr/share/keyrings/nvidia-container-toolkit-keyring.gpg] https://#g' | \
sudo tee /etc/apt/sources.list.d/nvidia-container-toolkit.list

sudo apt-get update
sudo apt-get install -y nvidia-container-toolkit nvidia-docker2

@gjacobse Now that I think about it, you might want to try a bios reset on the iDRAC. I don't know if that will make a difference, but it's corrected issues with them for me in the past.

@gjacobse said in Dell r720 and Hitachi Drive:

iDRAC -

Ended up being short lived excitement when I came in last night to see that I could access the LifeCycle controller and was able to get the iDRAC connected.

Used the reboot option and that was it I suppose... Back to LifeCycle controller being disabled and the iDRAC being inaccessible.

Odd also is that it seems to only allow one of the four main NICs over the iDRAC NIC - Has it been so long since I worked on something at this level that I've misconstrued some information on how the iDRAC NIC is suppose to work/

iDRAC normally has a NIC separate from all the others. Some utilize the same NIC as the main system, but those are the jank version. My R620 iDRAC is a physically separate network port, and all the servers at work are as well.

@gjacobse said in Dell r720 and Hitachi Drive:

Specs:
Dell r720 surplused
Hitachi HUC106060css600 512 drives

I admit - I've realized that the last server I had to physically touch was likely back in 2009. While I have worked with systems, I've not had to build or rebuild an array in a very long time. So I am a tad rusty.

System does see these drives - I have a full complement of sixteen to fully populate the two bays. However I have run into a slight issue with these drives I hadn't had to work with previously as technology has changed.

These drives are per the details above 512/512e and the r720 doesn't want to 'accept' them. While the PERC does see them, they are all marked as BLOCKED.

Now, I understand that sector size is set and cannot be changed - I rather expected to find the correct firmware needed to update the PERC to allow these drives to be used...

I do see that Dell has the driver for this drive - but reading the details about it seems to point at an OS side issue and not the PERC.

I fully expect that I am simply overlooking the solution because I am looking at or for the wrong information.

Are you looking at the PERC bios screen? If it's in standard RAID mode, that's where you need to setup the array.

Hotkeys are always different. If you have access to the iDRAC, you should be able to boot directly into the RAID bios from that. I have an even older R620 still in use as my home lab box, and that's normally how I access the PERC bios when needed.

You're reminding me that I really should see about upgrading my home lab box.