• Linux
  • June 2018
    M T W T F S S
    « May    
     123
    45678910
    11121314151617
    18192021222324
    252627282930  
  • Meta

  • Follow me on Twitter

  • Advertisements

Non-interactive script messages

I’ve got a couple computers that are running most of the time but I don’t actually get on them regularly so I placed a script to run updates  in /etc/cron.weekly. The script creates a log file in my home folder so I can look and see if there were any errors. I noticed the following lines in the log files:

z-update log #1
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:

z-update log #2
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:

The messages appeared following the execution of apt-get dist-upgrade. The updates seemed to have completed without error but these messages merited further investigation. I also noticed the same sort of messages when I watched the progress of updates done with Mint’s Update Manager.

It appears that the command was expecting some king of user interaction even though I’d include the -y and -q flags. My research indicated that setting the DEBIAN_FRONTEND environment variable to “noninteractive” might solve the problem so I changed that line in the script to read:

DEBIAN_FRONTEND=noninteractive apt-get dist-upgrade -yq 2>> $LOGFILE >> $LOGFILE

I checked the log file on one of the computers after the script’s scheduled run this morning and saw that the messages did not appear. Apparently, the fix worked. I can’t say this would work for others. The computers on which the messages appeared are both running Linux Mint 18.3.

Advertisements

A locale fix & an install script

When running updates on my Linux machines, I’d been seeing an error message in the terminal when update-initramfs ran — “Warning: No support for locale: nl_NL.UTF-8” It didn’t seem to be affecting anything but my curiosity about reached its limit and I googled it. The warning message appears because /usr/share/initramfs-tools/hooks/root_locale  is expecting to see individual locale directories in /usr/lib/locale,  but locale-gen is configured to generate an archive file by default.

The solution was simple – just two commands:

sudo locale-gen –purge –no-archive
sudo update-initramfs -u -t

Since I’d been seeing the warning message on all of my Linux systems, I put the commands into a bash script. Easy fix.

When I ran the script on the Latitude E5500, I get an error indicating the drive was full. I’m not sure how I managed to fill it but for all intents and purposes, it was. I had originally set it up with root and home both on a single LVM partition so I figured it was a good time to reinstall Mint on it while dividing the drive into three partitions – root, swap, and home.

Once I got Mint reinstalled, I tested a script I’d put together to install a few utilities, applications, services, and tweaks. Parts of the script worked while other parts of it didn’t so there were some things that I had to individually install. I’m looking at the script and seeing if I can tweak it some and determine why some things didn’t install.

I’m probably going to reload my Dell Latitude E6500 soon which is also set up with an LVM partition. I’m also thinking about reloading my Lenovo M91p desktop. It’s partitioning is a little funky too, essentially a 500GB Windows 10 partition and a Linux partition. I’ve had the system for a little over six months and I’ve never booted into the Windows partition and I don’t think it’s likely that I will. Maybe there’s a way I can move the Windows to another drive. It’s just the installation file. I’ll have to look into that.

Linux Experiments

E-475mEarlier this week I did an OEM installation of Linux Mint 18.3 on my Gateway laptop. I’d seen an EzeeLinux video on how to do it and I wanted to give a try. I had a friend who’d seen me using Mint on my laptop and expressed interest in it and an OEM installation would enable to him to go through the process of setting up his user name, password, and all that

I did the set up much like my own systems, setting up Timeshift, adding the Chromium browser and the Htop utility. I added scripts to the cron.weekly and cron.monthly folders to run get updates and do a little system cleanup.

HP-110-miniIn another experiment, I found my wife’s old HP 110-Mini Netbook and installed Mint 18.3 XFCE on it With an Intel Atom processor and only 1GB of RAM, I wasn’t expecting much. It runs but it’s incredibly slow. I don’t know if bringing it up to 2GB will help much. The netbook originally ran Windows 7 Starter edition. I pulled that hard drive out and replaced it with a different drive just in case the experiment didn’t work out. I’m considering a more lightweight distribution for this device. Maybe Puppy Linux.

Fun with Samba

After replacing my Dell Optioplex 780 with the HP Elite 8300, I wasn’t sure what to do with the Dell. I kind of figured I’d put Linux on it and use it for something. I recently watched an EzeeLinux video on sharing files with Samba. I figured a simple Samba server might be useful for sharing files and making music and videos available across my network.

I installed Linux Mint 18.3 Cinnamon on the Dell and configured it the way I like it. Then I used sftp to copy my entire music library over. I installed and set up Samba, configured it, and set up the shares – a Music share and a Public share. The Public share is a central location for sharing files on the network.

After some tweaking I got it working pretty well on the Dell and the Windows computers. However, I could not see the shares on the other Linux computers. I did an exhaustive search on Google and various Linux forums and found nothing that helped. My smb.conf file seemed to be okay everything was in the same workgroup..

Samba-error

Then I found a suggestion that looked interesting .Someone suggested opening the file manager (nemo, thunar) in a terminal, pointing it to the share – nemo smb://192.168.0.17 . It worked! I had access to the shared folders. On the computers running the Cinnamon desktop, I created a bookmark and on the XCFE desktops, I created a launcher to access the shares. Maybe not the most elegant solution but it works.

When I replied to my comment on the YouTube video I read through the other comments and replies and found that Linux Mint does have problems with smb shares.

How will I use my Samba server? It’s another tool I can use on my network. One of the shares is make my music library available everywhere on the network. The Public share is an alternative to using Dropbox and flash drives. And it was a good learning experience.

Getinfo

Last month I mentioned that I was working on conkyinfo.sh, a script to gather the device information I needed to use in my conky scripts. Now that I’ve found that my old scripts don’t work so well anymore, I’ve adapted a simpler script that shows less information.

But that doesn’t mean that I’ve tossed that script completely aside. Yesterday, I got to thinking about expanding on that script and gathering some basic system information into a text file stored in the home directory. It turned out that I really didn’t use much from the conkyinfo.sh script.

I set up variables to hold the results of dmidecode commands for general information about the system such as manufacturer, product name and version, and system serial number. I started out using dmidecode to get the CPU model and it worked well with the HP laptop I was using when I originally wrote the script.

While testing it on my desktop PC and my other Linux laptops, I noticed that on my Dell laptops, dmidecode returned ‘Not Specified” for the CPU information so I turned to using grep with the lscpu command to give me the information that I needed. I used grep and awk with /proc/meminfo to give me the amount of physical memory in gigabytes.  All this information was redirected into a file.

For information network interfaces and power (batteries), I redirected the output of the ls command on /sys/class/net and /sys/class/power_supply. For hard drive information I redirected the  lsblk output to the file. At the end of the script I ran the cat command on the file to display everything.

getinfo

The only problem I’m having is when I run it on my Lenovo ThinkCentre M91p. The variables containing the output of the dmidecode commands all contain an error message: “Invalid entry length (16). Fixed up to 11.” I’m not sure what’s causing it but from what I’ve read about the error, it may have something to do with using sudo with dmidecode. Some articles talked about the host name being too long but even after shortening the host name, I still got the error and on the other computers have longer host names. I’ve only seen the error when using sudo with dmidecode on the M91p.

Testing on the various machines using ssh and rsync made the process so much easier. With each changed to the script, I had to upload it to each machine and using a script makes that process so much easier when I can upload to all machines with one command.

SyncAll script & SSH

Tux_MonoI’ve been watching the EzeeLinux videos by Joe Collins at EzeeLinux.com and I’ve been learning a lot from them. I recently watched one in which he talked about a SyncAll script he wrote that uses rsync to synchronize a set of folders among all the computers in his home network. It occurred to me that our network environments were very similar so I reached out to him and asked for a copy of the script.

Modifying Joe’s script to fit my network and situation wasn’t all that difficult. One change I made to the script was to set a variable to hold the first three octets of the IP address so that if my networking environment changed for some reason (i.e., a new router) where it changed from 192.168.0.x to 192.168.1.x, I’d only have to make the change once in script.

It was by watching Mr. Desktop & Mr. Server Episode 5 | Linux Networking & Connect2SSH that it all came together for me. That video helped me to get SSH set up on my Linux computers so that the script would work properly. The video also introduced me to SCP (Secure Copy) and SSHFS (SSH File Share) which will prove to be very useful tools.

I’ve assigned static addresses to all of the wired connections, something I’d been thinking about doing for some time. I’ve still got a couple Windows PCs on the network but for now I can deal with them through SMB shares, Dropbox, or Sneaker-Net. If necessary, I could install Linux on the Windows box I just replaced and set up SAMBA on it.

 

Conky Changes

I’ve found that my conky script doesn’t work well with new versions of Conky in the Linux Mint 18.x and Ubuntu 16.04 repositories. My efforts to adapt my script to the newer format were not very successful. I found some newer scripts and settled on a couple of basic and minimalist scripts. For the laptops, I modified the network portion of the scripts with the ‘if-exists’ statements to determine which network interface was being used and display the appropriate information.

I decided to move away from displaying detailed system information, taking a more minimalist approach. Having the information for each CPU core and the graphical display of network activity was nice to have but did I really need it? Maybe but I’m fine without it. I’m sure I’ll add a few things to the display as time goes on.

As I’ve installed the new script on my Linux machines, I’ve copied each .conkyrc file to my Dropbox as a reference and a backup in case I ever reload the operating system.

As for the Conky Configuration page, I’ll keep it up for now but I don’t know how much effort I’ll put into updating it. I really haven’t decided how I want to approach it yet.

%d bloggers like this: