Useful Links (All Semesters)
- When updating packages if you abort suddenly, then you might end up with a broken package database. In that case, you can fix a broken yum package system using the following blog post: [ How to fix duplicate packages in yum ].
Good to know and include somewhere (OPS235 future content update).
Current Semester: Winter 2017
- There seems to be a procedure that works if you are booting Centos7 from your removable SATA drive in your labs and it doesn't connect to the Internet...
Note: If you cannot connect, you should see on the top right-hand corner before you login such as: [...]
This means there is no Internet connection.
If that is the case, perform the following steps:- Quickly press the power button (do not hold it down!). This should put it in suspend mode. You can confirm it is in suspend mode if the blue power light is flashing.
- Wait a few seconds, then press the power button again. This will go out of suspend mode. You can confirm is is not in suspend mode if blue power light is solid (not flashing).
- In a few seconds, the symbol on the top right-hand side should appear like: .
This symbol means that you can connect to the Internet.
Fall 2016
- Lab 1: Unusual problem of network not showing up in c7host VM. Happened because I had not enabled a second network adapter in VMware Workstation Pro (use Team as the type).
- Change all VM sizes to be at least 20GB because some (lab 2 VMs) still say 15GB and they cause problems during installation for CentOS 7.2
- Keep consistent lab1 checking scripts for ALL OPS235 instructors (This semester was exception for Mark F., due to caching problem showing older partitions for previous semester).
- I think in future (based on scripting questions I gave on midterm) that we will need to add to the questions section of the labs something to do with shell scripting - even a simple walk-through. This can be incorporated into future quizzes.
- VMware gets odd naming for interfaces, for example ifconfig in VMware on CentOS 7 I get this (among other network setup). The problem is they've switched from the interface naming. There is a workaround in CentOS FAQ: https://wiki.centos.org/FAQ/CentOS7
eno16777736: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 - I noticed that some students have a different volume group name for centos2 than centos_centos2
I suspect it is that students didn't follow instructions when creating the centos2 VM by specifying the correct hostname: centos2
This could be corrected by including centos2 being checked for correct hostname in lab2 checking script, but not time to do that for this semester. - Add youtube video on how LVM works for lab5 notes
- Check learning outcomes and topic outline match for OPS235 course
- For OPS235 Assignment #2, remove references to chkconfig command (deprecated), should use systemctl status service-name
CentOS 7 VM (VMware) Known Issues
HP Z230 machines on campus
- Not getting network interface in CentOS (VMware network configured to using NAT). Solved (sometimes) by adding another network interface and setting that interface to VMnet8
- USB failure from Windows host. Could this be due to bad USB cable, but one student reported Windows on HP Z230 automatically unmounts the USB drive while the VM was running thereby freezing CentOS in VMware
Lab 5 suggestion (received from a student)
Create a virtual disk /dev/vda in centos2 and use that virtual disk (vda) instead of /dev/sda (so use fdisk /dev/vda instead of using fdisk /dev/sda). This makes Lab 5 easier to handle accidental corruption students might make while doing that lab thereby destroying their centos2. This might require Lab 5 checker script to be tweaked to work with /dev/vda.
Lab 7 Issue
Some students could only get their labs to work with the browser after they did this:
iptables -I INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
Assignment 2
chkconfig gives an error message telling students to use:
- systemctl list-dependents httpd
- systemctl list-dependents mysql
Previous Semesters
Summer 2016 (Refer to previous semesters below)=
- No entries
Winter 2016
- N.B. - On "TODO list" - LAB 1 - Picture under part 2 - The picture called "Partition Verification" shows a LVM setup, but the instructions ask specifically for a standard partition setup.
- FIXED BUT REQUIRES VERIFICATION THAT FIX WORKED - LAB 1 - Investigation 3 - Part 2 - Questions 21 - Not important but, report3.bash script uses the command "cat /root/install.log >> installation_report.html", the file /root/install.log does not exist on centos7 install.
- N.B. On List for Murray Saul to work on during non-contact period - "tweak" lab2check2.bash to provide additional checks including xml dumps to home directory for all VMs and reminder from script to back those items to USB key. Also should check if centos2 has / for 8 GB and /home for 2GB. I read somewhere that xfs can mess up with LVM which we talk about in lab5. For next time, I will add in requirement in lab2 signoff that students show for all VMs the /etc/fstab to ensure ext4 fs. Perhaps checking script can be modified next time to check for that... Good idea to expand shell script check for ALL labs. Student would be required to show same information PLUS the results from running the checking shell script.
- N.B. On List for Murray Saul to work on during non-contact period - It would be nice to rearrange the content for lab5 to discuss df -h and space concerns first, then flow into LVM. This would provide a better "flow" to reinforce student understanding. Shell script at end would remain at end to show how to use crontab to automate (flag) space issues.
- N.B. On List for Murray Saul to work on during non-contact period - Good idea to review study questions at end of each lab to see if they are applicable to each lab.
- Would be neat to create prezi slide shows for each lab preparation (for class). This would be in sync with OPS335 course. Online slides can be exported to PDF files as well.
- N.B. On List for Murray Saul to work on during non-contact period - Would be helpful for a script or program to check all links in all OPS235 (OPS335, etc) WIKIs to check for non-working links. This would allow course overseer to run just prior to the start of the semester and be incorporated into the startup checklist.
- N.B. On List for Murray Saul to work on during non-contact period - Some students note different vg name (like centos instead of centos_centos2). Solution is to get students to issue vgs to obtain vg name. Should investigate why this is happening to prevent (eg. shell script check at end of a lab).
- N.B. On List for Murray Saul to work on during non-contact period - Check mailx package when installed (lab5 example) for OPS235 to see why not sending mail to demo that script works for a lower threshold point for file space usage.
- N.B. On List for Murray Saul to work on during non-contact period - Method to better explain in lab7 tunnelling via local ports (eg. show some command of available ports, etc) - example:
sysctl net.ipv4.ip_local_port_range
net.ipv4.ip_local_port_range = 32768 61000
(But where does that fit in with using 20808?)
Summer 2015
- LAB 1 - Installing NON-GUI version of Linux OS: A lot of students ran into the same problem with lab 1, that is they didn't pay close enough attention to the instructions and installed the OS without a GUI. But that is no flaw in your wiki, just the tendency of students to rush through things. I have done my best to enforce that they should read all the instructions carefully BEFORE they start on the labs.
- LAB2 - Backup Script demo: Current VM backup script should also allow for backing up xml configuration files.
- LAB - LVM: Current VM backup script does not factor in virtual hard drive images. May be a good idea to add this to the backup script, so students can be encouraged to run backup scripts.
- The wget http://belmont.senecac.on.ca/centos/7/isos/x86_64/CentOS-7-x86_64-LiveGNOME-1503.iso command is still not working
- When students issue the “service iptables restart” command it returns a message that says the service is dead and not running. Yet, I’ve tested the iptables themselves by adding a few rules and they are certainly still working. I’m really not sure what exactly is going on. Perhaps it’s just a glitch in CentOS7?
- The virtualization software also seems to need a system reboot before the virtual network will come into effect. Simply restarting the virt-manager or the libvirtd service doesn’t seem to do it. So, again, rebooting the system is the way to go to make sure the virtual default NAT network becomes visible for new VMs.
- Some students in lab2 may not be performing the correct steps in creating VMS (image paths and types). A shell script to be run to check this would be useful, but may need release time to create a comprehensive and user-friendly shell script.
Winter 2015
- Winter 2015: OPS235 - Short-term - Older Issues