Problem: One of the docker nodes does not start up after restart. Error in the log is

Reason: Docker swarm and network stack sucks.
Fix:
Problem: One of the docker nodes does not start up after restart. Error in the log is
Reason: Docker swarm and network stack sucks.
Fix:
The bit rates for the most common audio formats –
ALAW | 8 BITS |
ULAW | 8 BITS |
PCM | 16 BITS SIGNED/UNSIGNED |
ADPCM | 8 BITS |
The endian-ness for more than one byte systems:
Motorola Processors | Big Endian |
Intel Processors | Small Endian |
Error : Few docker containers don’t start up. In the /var/log/syslog they give the error “Cannot start container Subnet sandbox join failed…”
Fix: Restart the machine !
Optionally you can try the steps mentioned here, and see that they don’t work, and restart the machine anyway 🙂
Problem : On page refreshes, the ajax calls in the componentDidMount functions throws the error : “Error: Should not already be working.”
Reason : Probably the ajax request is called before the react’s async calls framework is initialized.
Fix: Run within a timeout function
Eg –
componentDidMount() {
setTimeout(() => {
$.ajax(...);
}, 400);
}
Issue : When doing an apt update, we get the this error.
The repository ‘http://archive.ubuntu.com/ubuntu disco-backports Release’ no longer has a Release file. N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
fix :
[bash] vi /etc/apt/sources.list replace all occurrences of archive.ubuntu.com to old-releases.ubuntu.com [/bash]I had recently hit a blocker to production deployment, when my processes just won’t connect to my Cassandra DB from within their containers.
This is how I could fix it –
Else, as it happens mosltly, you are on your own 🙂
Best of luck for your resolution, and please comment if you have have a different solution to the problem.
On the terminal, do the following to open port 80
Persisting the rule changes across boot cycles –
iptables-persistent will look for the file “/etc/iptables/rules.v4” after boot up, to restore the rules for IPV4, thus automating the restore for each boot.
To make a new disk you just added to the Ubuntu device, please go through the following steps –
Check whats the /dev path of the disk. On terminal, run-
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 97M 1 loop /snap/core/9289
loop1 7:1 0 18M 1 loop /snap/amazon-ssm-agent/1566
nvme0n1 259:0 0 1T 0 disk
nvme1n1 259:1 0 10G 0 disk
You would have got a result as above.
In this case, the disk I wanted add is the 1 TB disk, which is /dev/nvme0n1
Format the disk with a new compatible filesystem (XFS).
sudo mkfs -t xfs /dev/nvme0n1
Wait for the file-system creation to finish.
sudo mkdir /data
sudo mount /dev/nvme0n1 /data
sudo cp /etc/fstab /etc/fstab.orig
sudo blkid
From the output of the last command, find the UUID of your disk
sudo vim /etc/fstab
Append the line –
UUID=[your disk's UUID] /data xfs defaults,nofail 0 2
Note that in the above replace your disk’s UUID without the square brackets, and save the file.
sudo umount /data
sudo mount -a
df -h
Verify that /data is listed as a disk in the last command. If not, please check the /etc/fstab file, apply correction of UUID, spaces etc, and repeat the above test block again.
Problem:
The newly set hostname reverts back to older one after reboot
Reason :
Hostname is reset by cloud-init
Solution :
Inactivate cloud-init.
On terminal, key in –
[bash] hostnamectl set-hostname YourNewHostName sudo touch /etc/cloud/cloud-init.disabled sudo reboot [/bash]
Hey there !
So you are a programmer, wanting to master machine learning ?
You are at the right place.
Lets get started.
We as programmers, have been programming some pretty complex algorithms, which made our computers really smart. So how do we understand machine learning from the perspective of programmers ?
Machine learning and programming achieves the same purpose – as in both makes the computers do some useful work for us. The approaches are in exact opposition to each other.
While programming is about setting the rules to reach a particular output from inputs, machine learning is about finding these rules from existing output and work inwards.
While programming is intrinsic logic directly added by a programmer, machine learning is extrinsic – existing output data massaging a malleable function into shape, so that this function is the “new program” which can be put to use to find outputs from new previously unseen inputs.
Its very tempting to help a function (which works backwards from output data) with what we know about the domain of the problem.
For example, when predicting the prices of houses in a city, we naturally would make use of our knowledge that it’s location in the city, the area of the house etc have a direct bearing on its price. These are called features of our function, which has to find the importance of each feature in predicting the output by working backwards.
Machine learning is what we call the data driven shaping of solution function (or program) when the features or the broader input variables are set by us.
When we have enough historical data (of inputs vs outputs) we have the luxury of the letting the function decide for itself which inputs are actually features (have a say in the output). This is more like larger program which makes use of sub routines to filter input signals to allow only relevant ones to enter the main routine. Only that the main routine and sub routines – all are shaped up by many iterations of massaging inwards by the historical data. Such a system which does automated feature selection and predicts output from the features so found, is know as a Deep learning system.
Deep learning systems obviously have more stacks of variables layered between input to output, to facilitate filtration or amplification of input signals as the need be, in preceding layers.