Enterprise Linux Support

Solution: Booting the AWS public clound instance using another Debian Linux image and mounting the original disk, deleting files and booting the original disk again.

Solution: Stopping the Webserver to prevent further writes to the disk, booting a rescue Linux system, using the command line tool foremost to recover the files from the ext4 file system.

Solution: Reading the log files and based on the information gathered testing the RAM modules using the command line tool memtester to identify a broken RAM module.

Solution: Dmesg messages identify two failing disks in an MDADM RAID 5 array, identifying the disks using the smartctl command line tool, migrating the data just before total failure.

Solution: Logging in over the virtual KVM console, attempting to restore network connectivity reveals malformatted SSH authorized keys configuration file.

Solution: Literally just running apt --fix-broken install. Sometimes all we have to do is "press the CAPS lock key". We did not issue an invoice and asked to call us again next time.

Solution: Identifying DNS resolution problem with the first name server listed in /etc/resolv.conf. DNS server is managed by different department, switching to second DNS server.

Solution: Identified 173 attached client Linux Operating Systems attached to one NFS server. Advised to install and configure CEPH over all Linux servers in the custom data center racks.

Solution: Made Cron job scripts executable using chmod and gave 15 minute introduction into Linux file permission basics. We did not send an invoice.

Solution: Identified port 123 Network Time Protocol (NTP) being blocked by the firewall, which casued the servers time to be incorrect by ~45 minutes. Reconfigured nftables.

Solution: Identified changed password for the sending email account. Configured a OpenSMTPD based mailrelay on the server to queue mails in case of error.