Today I have startet some release upgrades for some Ubuntu 16.04 VM machines. Sometimes I am strungling with this error.
error processing archive /var/cache/apt/archives/lxd_1%3a0.9_all.deb (--unpack):apt purge lxd lxd-client
Attention if you need snap you should reinstall it
Found here
https://askubuntu.com/questions/1280499/upgrade-from-18-04-lts-to-20-04-lts-fails
Today I had a request from our user for add a PCIe SSD card to a server. One option is you walk to this server and open it. This not the best option to check if it a PCIe slot available.
Another option is use your Linux commandline.
You need your server mainboard manual to see which slot is labeled.
You have only to check under current usage is in use or available.
Current Usage: Available
dmidecode -t 9
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 3.2.1 present.
# SMBIOS implementations newer than version 3.2.0 are not
# fully supported by this version of dmidecode.
Handle 0x000B, DMI type 9, 17 bytes
System Slot Information
Designation: CPU1 SLOT2 PCI-E 3.0 X16
Type: x16 PCI Express 3 x16
Current Usage: In Use
Length: Long
ID: 2
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:18:00.0
Handle 0x000C, DMI type 9, 17 bytes
System Slot Information
Designation: CPU1 SLOT4 PCI-E 3.0 X16
Type: x16 PCI Express 3 x16
Current Usage: In Use
Length: Short
ID: 4
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:3b:00.0
Handle 0x000D, DMI type 9, 17 bytes
System Slot Information
Designation: CPU2 SLOT6 PCI-E 3.0 X16
Type: x16 PCI Express 3 x16
Current Usage: In Use
Length: Short
ID: 6
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:86:00.0
Handle 0x000E, DMI type 9, 17 bytes
System Slot Information
Designation: CPU2 SLOT8 PCI-E 3.0 X16
Type: x16 PCI Express 3 x16
Current Usage: In Use
Length: Short
ID: 8
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:af:00.0
Handle 0x000F, DMI type 9, 17 bytes
System Slot Information
Designation: CPU1 SLOT9 PCI-E 3.0 X16
Type: x16 PCI Express 3 x16
Current Usage: Available
Length: Short
ID: 9
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:ff:00.0
Handle 0x0010, DMI type 9, 17 bytes
System Slot Information
Designation: CPU2 SLOT10 PCI-E 3.0 X16
Type: x16 PCI Express 3 x16
Current Usage: Available
Length: Short
ID: 10
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:ff:00.0
Handle 0x0011, DMI type 9, 17 bytes
System Slot Information
Designation: CPU2 SLOT11 PCI-E 3.0 X4(IN X8)
Type: x4 PCI Express 3 x8
Current Usage: Available
Length: Short
ID: 11
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:ff:00.0
Handle 0x0012, DMI type 9, 17 bytes
System Slot Information
Designation: M.2 CONNECTOR
Type: x4 M.2 Socket 2
Current Usage: In Use
Length: Short
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:02:00.0A very long time I used ha-proxy for lb to publish Exchange OWA/Active-Sync in to the WWW. After the installation with NSX-T. I have the opportunity to replace my old ha-proxy configuration with the integrated LB from NSX-T. I would like to replace the ha-proxy for internal MAPI namespace. Normally that will be used often KEMP LB or ha-proxy. With NSX-T you can also replace this product. To Replace MAPI Namespace lb is very simple that will be used only TCP for lb.
I will not write how to deploy the LB that can you read here.
https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-D39660D9-278B-4D08-89DF-B42C5400FEB2.html
I will show you some configuration where not included in the knowledge base.
To protect your Administrator interface from external access. In my old ha-proxy configuration I had a ACL to protect ecp from external.
For the OWA rule you must add a forwarding rule with this options.
For your SSL configuration you need your domain certificate and intermediate certificates also.
You need Client SSL and Server SSL. You can use twice the same certificate,.
Before you can assign the certificates you have to import the certificates for your domain and the intermediate certificates under System = >Certificates
After importing the certificates you can assign this to your Virtual Servers HTTP 7 rule.
Trusted CA Certificates means your intermediate certificate.
VM wil not power-on and throws the following error:
Object type requires hosted I/O
SSH into the ESX-host that’s hosting the VM.
Browse to the VM-folder containing the disk files.
Run the following command:
vmkfstools -x check “disk.vmdk”
Disk needs repaired
vmkfstools -x repair “disk.vmdk”
Disk was successfully repaired.
Start VM from vCenter
found here
https://tklaassens.wordpress.com/2019/05/13/object-type-requires-hosted-i-o/
What a incredible e-mail from Atlassian, cloud first. Not everyone wants to use the cloud. I worked with Confluence and Jira over ten years now. Time for alternative Wikis. I am a little bit sad about the cloud first strategy. Confluence and Jira are pretty cool tools.
Time for alternative Wiki´s
This Wiki very close to Confluence. But one feature is missing
https://wiki.js.org/feedback/p/multi-sites
Multi Sites
BlueSpice based on MediaWiki but it have a lot more features and a good Editor.
bluespice.com
Multi Sites only available in the enterprise version.
Also look at tiki.org but is more than a wiki
For Jira alternative
I found
I had a heck of a time figuring out how to set this up. Cisco’s documentation related to LDAP authentication is all over the place and there isn’t one article that describes just this. If you want to use Microsoft Active Directory to authenticate users locally logging in to the ASA and give them privileged exec access based on a Group, here are the steps.
These steps assume you are using ASDM, but I have attached the CLI equivalents as well.
1. Log in to the ASA with ASDM (CLI steps below)
2. Go to Device…
View original post 1,113 more words
On Ubuntu you need the cifs-utils
apt-get install cifs-utils
Add the share to the /etc/fstab
//10.10.100.10/blob /mount/share cifs username=john,domain=contoso,noauto,rw,users 0 0
set the correct rights for the local user to the mount share.
sudo mkdir /mount/share sudo chown -R john:john contoso sudo chmod -R 774 contoso
Mount the share with mount.cifs
mount.cifs //10.10.100.10/blob /mount/share
Don´t use mount -t cifs
read more here
https://www.strika.co/ubuntu-14-04-how-to-properly-mount-a-cifs-share-as-a-normal-user/
you must change something on the Active Sync policy for your Exchange Server.
Look her
https://docs.microsoft.com/en-us/exchange/mail-flow/message-size-limits?view=exchserver-2019
%windir%\system32\inetsrv\appcmd.exe set config “Default Web Site/Microsoft-Server-ActiveSync/” -section:system.webServer/serverRuntime /uploadReadAheadSize:31457280
Restart iis and all is fine
Issue:
ActiveSync devices are not able to send e-mails sporadically. E-mails with attachment and long conversation history.
IPhone Error “Message cannot be sent” , “The message was rejected from the server”
Solution:
Browsed to configuration editor of IIS ->Microsoft-Server-ActiveSync Virtual Directory -> select ConfigurationEditor -> system.webServer -> serverRuntime -> uploadReadAheadSize.
Change value to 15728640
Recycle MSExchange ActiveSync AppPool.
Additional Info:
https://www.iis.net/configreference/system.webserver/serverruntime
MDADM hots pare will not working
check your sync_action
cat /sys/block/md0/md/sync_action frozen
enable it with
echo idle > /sys/block/md0/md/sync_action
that´s it
