Mopidy fails to connect to Icecast server

This issue affects both Ubuntu and Debian.
For example Mopidy 3.0.2 on Ubuntu 20.04 (Focal Fossa) using the apt.mopidy.com method.
Also mopidy 3.3  on Debian 11 (bullseye).

All attempts to connect to a known working Icecast2 server would not work and the Icecast server would not log any errors. However the Mopidy log would record the following error:
[MainThread] mopidy.audio.gst GStreamer error: Could not connect to server
The root cause is a bug in the version of the libshout3 library that is included in the repository has a bug.

For example on Ubuntu 20.04 (source: https://bugs.launchpad.net/mixxx/+bug/1833225).

A workaround is to downgrade libshout3 library to a working version. In this example we will use the library in Ubuntu 19.10 (Eoan): 2.4.3 (2.4.3-1) –> 2.4.1 (2.4.1-2build1)
https://packages.ubuntu.com/eoan/libshout3

Steps for Ubuntu (see Notes for Debian)

  1. cd /tmp
  2. wget http://mirrors.kernel.org/ubuntu/pool/main/libs/libshout/libshout3_2.4.1-2build1_amd64.deb
  3. sudo dpkg -i libshout3_2.4.1-2build1_amd64.deb
  4. Restart Mopidy

To prevent the library from being replaced with every apt-get upgrade  you can hold it:

sudo apt-mark hold libshout3

Once the libshout3 package is fixed in 20.04 we will be able to undo it:

sudo apt-mark unhold libshout3

Then upgrade libshout3 using apt-get.

Notes:
Modify steps 2 and 3 for Debian to use the version in the buster repository. This will downgrade libshout3 from version 2.4.5
https://packages.debian.org/buster/amd64/libshout3/download
http://ftp.us.debian.org/debian/pool/main/libs/libshout/libshout3_2.4.1-2_amd64.deb

Steps to Reset Windows Server 2003 R2 Standard using Linux

These are the steps taken from my notes to reset/change an administrator password on a Windows Server 2003 R2 Standard install. I used Ubuntu and chntpw and the Windows partition was not encrypted.

  1. Boot from Ubuntu live disk
  2. Switch to root
    sudo -i
  3. Add the repository that has chntpw
    apt-add-repository universe
  4. Install chntpw
    apt-get install chntpw
  5. Make a folder to mount the Windows partition drive
    mkdir /winmount
  6. Mount the partition (search available partitions using Gparted)
    mount /dev/xxx /winmount
  7. List all users
    chntpw -l /winmount/WINDOWS/system32/config/SAM
  8. Modify the desired user
    chntpw -u username /winmount/WINDOWS/system32/config/SAM
  9. Clear (blank) the password of the user, option 1.  Then unlock if necessary, option 2.
  10. Quit and write the changes
  11. Unmount and reboot
    unmount /winmount

Adjusting RAID Speed in OpenMediaVault

This affects the minimum and maximum speeds allowed for throttling of reshaping and checking activities of mdadm.

To monitor the current speed
sudo cat /proc/mdstat

To temporarily adjust the speed use the commands below. They will reset to defaults on the next reboot. The speed, x, is a number in kbytes/seconds.
echo x > /proc/sys/dev/raid/speed_limit_min
echo x > /proc/sys/dev/raid/speed_limit_max

To make the change permanent and persist after a reboot modify this file:
/etc/sysctl.d/99-openmediavault-mdadm.conf
Add these lines where the speed, x, is a number in kbytes/seconds.
dev.raid.speed_limit_min = x
dev.raid.speed_limit_max = x

Note: the default setting for a fresh install of OMV version 6.0 is only a minimum speed with a value of 10000 (contrary to the comment in the config file with a value of 1000).

Office 365 Install Hangs and Errors with Office Deployment Tool

First error We’re sorry, we can’t continue because we weren’t able to download a required file. Please make sure you’re connected to the internet or connect to a different network, then try again. Error Code: 30182-1011

Removing

I was getting a repeating error in the log file when trying to download using the ODT (setup.exe /download rather than /configure):

Nexus Transport xxxxx Monitorable MsoGetRemoteHostNetworkStatusWithUrlType failed {“RemoteHost”: “https://nexus.officeapps.live.com”}

Ultimately it would fail with the message: We’re sorry, we  had a problem installing your Office program(s). Error Code: 30015-1007

Folder size of Office/Data would increase to about 300-400MB.

Root cause was an old version of the tool’s setup.exe (I was running 16.0.7614.3602). I downloaded the latest ODT and then the O365 download would complete without error. At the time of this post the latest version was 16.0.12624.20290.