sometimes you got an error with ssh-agent mykey
Could not open a connection to your authentication agent.
then try this
exec ssh-agent bash
found here
sometimes you got an error with ssh-agent mykey
Could not open a connection to your authentication agent.
then try this
exec ssh-agent bash
found here
What a heck. Installed a fresh Suse tumbleweed and Twitch is not running. All Browsers have an error 4000.
You must install some codecs. How it works?
openSUSE Tumbleweed:
sudo zypper addrepo -cfp 90 'https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/' packman
openSUSE Leap:
sudo zypper addrepo -cfp 90 'https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_$releasever/' packman
for all systems the same command
sudo zypper refresh
sudo zypper dist-upgrade --from packman --allow-vendor-change
sudo zypper install --from packman ffmpeg gstreamer-plugins-{good,bad,ugly,libav} libavcodec-full vlc-codecs
thats it
found here
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.0
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
Hello,
good news. You are using Linux with Kernel 4.13 so that can happend that you get a mount error by mounting a smb share. Why happend this?
You are mounting a SMB 1 share.
Since Kernel 4.13 it will be tried to mount with version 3.
See git commit
You should use SMB in Version 2.1 or higher
SMB 1.0 is broken, see blog post from Microsoft
https://blogs.technet.microsoft.com/filecab/2016/09/16/stop-using-smb1/
http://www.cyberciti.biz/faq/how-to-mount-remote-directory-filesystems-with-sshfs-on-linux/
da gibt es das praktische Tool sshfs
Hallo,
das klingt für viele jetzt erstmal total schwer. Es ist überhaupt nicht schwer.
Nutzt das Tool gcore und folgendes Kommando
gcore -o /tmp/dump 12375 (PID ID)
Dann schreibt er den Core Dump. Schaut das auch genug Platz da ist, den soviel Speicher wie der Prozess im RAM belegt wird auch in etwa auf der Platte benötigt.
Man nehme das Paket xrdp unter Debian und schon geht es per RDP Client auf den Rechner
Wollte gerade mal wissen, was den Xubuntu gerade verwendet.
sudo blkid -o list -w /dev/null
device fs_type label mount point UUID
——————————————————————————-
/dev/sda1 ntfs System-reserviert (not mounted) 86BC23BCBC23A621
/dev/sda2 ntfs /media/moep/96C82613C825F1E3 96C82613C825F1E3
/dev/sda5 swap 5e999311-4755-4e4a-abad-baec83c614c9
/dev/sda6 ext4 / d1fe1a90-ca86-4180-8759-e00a0f5cb89f