kdump service loaded<\/strong>
\nThis will indicate Yes if the kdump systemd service is loaded. The service being loaded means that if the system were to freeze during this session, a crash file would be generated. This does not indicate that the system is enabled to automatically start on boot. To see more information, execute the following:<\/p>\nsystemctl status kdump<\/pre>\nkdump service enabled<\/strong>
\nThis will indicate Yes if the kdump systemd service is enabled, meaning it will automatically load on boot. To see more information, execute the following:<\/p>\nsystemctl status kdump<\/pre>\nNumber of recorded system crashes<\/strong>
\n<\/span>This counts the number of directories located in the \/var\/crash directory, which indicates the number of times the system has captured a kernel crash. If the directory doesn’t exist, this value will display 0.<\/p>\nHome and root directories < 80% capacity<\/strong>
\n<\/span>This check parses the df -h command to check the Use% value for -root and -home.
\nThis isn’t a full-proof check – but most customers tend to put specs, cell, data in one of these locations and cyflex resides in ol-root, so this ensures those particular partitions are not nearing capacity.<\/p>\nTo see more details on your disc space, execute<\/p>\n
df -h<\/pre>\nfor a simplified human-readable output, or see the man page for df for more possible arguments.<\/p>\n
If you get “N\/A” for this entry, the parsing didn’t work with your partitioning method. This doesn’t indicate a problem, just use the df -h command to verify your disk capacity.<\/p>\n
rc-local service enabled<\/strong>
\n<\/span>This will indicate Yes if the rc-loal service is enabled, meaning it will automatically load on boot. For more information on the status of your specific rc-local service, execute the following<\/p>\nsystemctl status rc-local<\/pre>\nrc-local is a legacy function still carried over where the commands located in \/etc\/rc.local will be executed when the computer boots. As the header of this file indicates, it is recommended to move away from this and generate standalone systemd services for this functionality. However, it is is still supported at this time (so long as it works…).<\/p>\n
NOTE the service is indeed rc-local and the file is rc_local. This is not a typo.<\/p>\n
rc-local service loaded<\/strong>
\n<\/span>This will indicate Yes if the rc-local service is loaded. This essentially means the rc.local script was executed, either during boot or manually if someone ran<\/p>\nsudo systemctl start rc-local.service<\/pre>\nfrom the command line during troubleshooting.<\/p>\n
rc-local script successfully executed<\/strong>
\n<\/span>This will indicate Yes if the rc-local service has a result of “success”. If you have an error somewhere in your \/etc\/rc.local script, then the service may be successfully executing the script, but the script itself is failing. There are ample reasons it could be failing, such as<\/p>\n-A syntax error in the script itself
\n-You’re executing a command within the script that is failing
\n-A boot order-of-operations issue. This is very common.\u00a0An example of this issue would be trying to set permissions on a serial port, and at the time the script is executed, that serial port hasn’t been created yet. If this occurs, it is recommended you create a dedicated service and ensure it runs later during the boot process. Consult Oracle Linux documentation for instructions for this, or reach out to TRP for assistance.<\/p>\n
A starting point for troubleshooting this would be to execute<\/p>\n
systemctl status rc-local.service<\/pre>\nand see if the output gives any indication of the issue.<\/p>\n
You can also run<\/p>\n
systemctl stop rc-local.service\r\nsystemctl start rc-local.service<\/pre>\nTo restart the service and see if it is successful. If it succeeds from the command line but not during boot, it is most likely a boot order issue.
\nIf restarting still isn’t successful, go through your script line-by-line and investigate why the commands are failing. Depending on the command, you may be able to execute each command (as root) from the command line and investigate which one is failing.<\/p>\n
Additionally, you could disable the service by executing<\/p>\n
systemctl disable rc-local.service\r\nslay_stuff \r\n ** if cyflex is running\r\nsystemctl reboot<\/pre>\nAfter this, copy your rc.local script to \/tmp, make it executable, and add<\/p>\n
set -x<\/pre>\nto the top of the file. Now execute it from the terminal (as root) and investigate why it is failing based on the output you see in the terminal.<\/p>\n
######### CYFLEX SPECIFIC INFORMATION ###############<\/strong><\/span><\/p>\nSRR module loaded<\/span><\/strong>
\nSRR RPM Installed<\/strong>
\n<\/span>SRR is the driver that handles timer events for CyFlex. This must be installed and loaded in order for CyFlex to run.<\/p>\nIf it is not installed, you can execute<\/p>\n
sudo yum install srr-64-devel\r\n<\/pre>\nSVN_SPEC_HOST set<\/strong>
\n<\/span>This will indicate Yes if SVN_SPEC_HOST is found in \/etc\/profile.d\/cyflex.sh
\nThis is only required if you are using SVN to back up your test cells files.<\/p>\n\/cell\/cell_name exists<\/strong>
\n<\/span>This will indicate Yes if this file exists. It does not do any further checks that it is configured correctly.<\/p>\n\/cell\/site_special exists<\/strong>
\n<\/span>This will indicate Yes if this file exists. It does not do any further checks that it is configured correctly.<\/p>\nSITE defined in \/cell\/site_special<\/strong>
\n<\/span>This will indicate Yes if SITE is defined in \/cell\/site_special. It does not verify it is configured correctly.<\/p>\n\/.cellspecs\/<site name>\/<cell name> exists<\/strong>
\n<\/span>This will indicate Yes if this directory exists. If using svn for your test cell backup, this directory is where your backup files will be located and is where the specsbackup script will execute the relevant check out\/in commands for your files.
\nThis is only required if you are using SVN to back up your test cells files.<\/p>\nSVN_SPEC_HOST in .cellspecs\/\/<site name>\/<cell name><\/strong>
\n<\/span>This is only required if you are using SVN to back up your test cells files.<\/p>\nAll \/data\/ subdirs exist<\/strong>
\n<\/span>This verifies all subdirectories of data that are (potentially) required for CyFlex operation have been created.
\nIf this indicates No, you can remedy this by using the mk_data_dirs_tc command. Read the usage page of that command to learn more.<\/p>\nBelow is a list of directories which must exist for this to indicate Yes:<\/p>\n
compressed6
\ncompressed
\nmeters\/occ
\nmeters\/utl
\nmeters\/occ_complete
\ntransfer
\ntransfer\/PAM_datapoint
\ntransfer\/PAM_header
\ntransfer\/PC_format
\ntransfer\/logrPAM_data
\ntransfer\/mua_data
\ntransfer\/mcparts
\nPAMtestids errors
\nmua_data mcparts
\nPC_format
\nPAM_datapoint
\nspc
\nPAM_header
\nturbo
\nfuel_log
\nlogrPAM_header
\nlogrPAM_data
\nfaults
\nutl
\nutl\/complete
\nutl\/ready
\nutl\/hold
\nutl\/ready
\ndlog
\ndlog\/ready
\ndlog\/hold
\ndlog\/complete
\ndlog\/logging
\ndarts_datapoint<\/p>\n
All suid bits set correctly<\/strong>
\n<\/span>Certain cyflex programs need suid bits set a particular way so they can run with root privileges. This should all be handled during the standard CyFlex install. If this script indicates the bits are not set correctly, follow instructions on cyflex.com to reinstall your particular cyflex version.
\nIf that doesn’t correct the issue, contact TRP.<\/p>\nQt 5 Version Installed<\/strong>
\n<\/span>Displays the current version of Qt 5 that is installed.
\nReference cyflex.com documentation for what version is the latest.<\/p>\nCyFlex version installed<\/strong>
\n<\/span>Displays what cyflex version is installed.<\/p>\nCorrect java rpms installed<\/strong>
\n<\/span>For cyflex version 7.0.20 and later you should NOT have cyflex_java rpm installed and you should have the cyflex_sys_log_replicate rpm installed. This line will indicate YES if this is the case and NO if it is not.<\/p>\nCyFlex Error Viewer installed<\/strong>
\n<\/span>This will indicate Yes if the cyflex_error_viewer rpm is installed and No if it is not. This rpm is not required. If you would like to install it, execute the following:<\/p>\nsudo yum install cyflex_error_viewer<\/pre>\nElectronic logbook present<\/strong>
\n<\/span>This will indicate Yes if \/specs\/log\/elogbook.db is present. It does NOT verify that the database is the latest format, but the elb command should automatically make these updates.<\/p>\nNumber of core dumps on this system<\/strong>
\n<\/span>Indicates how many files are located in \/data\/errors with “-core.” in the filename. This should generally correspond to the number of core dumps present on the system.<\/p>\nError database size<\/strong>
\n<\/span>Simple file size of the error database \/data\/errors\/error.db
\nThis will only output if an error database is present on the system, which may not be the case if cyflex has not yet ran or a prior database hasn’t yet been copied over. This is simply displayed for information purposes. There is no hard-set maximum size for an error database, but this can give a quick idea of how many errors are being generated on a particular system.<\/p>\nNumber of CyFlex errors generated in last 24 hrs<\/strong>
\n<\/span>This will display an integer value indicating the number of errors that have been generated on this system in the last 24 hours. It will only be displayed if an error database is present, and if the \/cyflex\/bin\/get_errs command is found (indicating cyflex is installed).
\nThis is simply displayed for information purposes. There is no hard-set number of errors that indicates a problem, but fewer errors is better for overall system performance.<\/p>\nNumber of CyFlex apps running<\/strong>
\n<\/span>This simply counts the output of sin names to give an indication of how many CyFlex apps are running.<\/p>\nCyFlex memory properly allocated<\/strong>
\n<\/span>This will display “Yes” if running “show_mem” does not generate any errors. If you have errors, execute<\/p>\nshow_mem<\/pre>\nto see what values are overrun and correct them by updating sys_start in the go.scp.
\nNOTE that this will report “No” if show_mem is generating an error that you are simply nearing a memory limit, even if you have not exceeded. If this is the case – the best action to take is to increase the memory limit.<\/p>\n
############## HARDWARE\/DRIVER INFORMATION ##############<\/span><\/strong><\/p>\nNVIDIA graphics card installed<\/strong>
\n<\/span>This parses the output of lspci to see if an NVIDIA graphics card is detected in a pci slot.<\/p>\nNVIDIA driver manually installed<\/strong>
\n<\/span>If an NVIDIA graphics card is detected, but the rpm provided by TRP for the NVIDIA driver was not detected, however the nvidia module is loaded, it is assumed that an NVIDIA driver has been manually installed, possibly because the NVIDIA card being used is not supported by any of the rpm’s offered by TRP.
\nThis entry will not be displayed if an NVIDIA graphics card is not detected from the lspci output.<\/p>\nNVIDIA rpm installed<\/strong>
\n<\/span>This indicates if one of the NVIDIA driver rpms provided by TRP has been installed. This entry will not be displayed if an NVIDIA graphics card is not detected from the lspci output.<\/p>\nnouveau graphics driver in use<\/strong>
\n<\/span>The nouveau driver that comes installed with the Oracle OS can be used with NVIDIA graphics cards, although it has found to lead to graphics lockups in many cases and is not recommended. This entry will not be displayed if an NVIDIA graphics card is not detected from the lspci output.<\/p>\nNVIDIA rpm number<\/strong>
\n<\/span>TRP hosts 4 different NVIDIA drivers (all from NVIDIA) on our server. They can be manually installed, or one will automatically be picked during the install process by the post_install script. This check simply shows which driver is installed. This entry will not be displayed if an NVIDIA graphics card is not detected from the lspci output.<\/p>\nIntel i915 module loaded<\/strong>
\n<\/span>This is the driver used by default when you are using onboard intel graphics instead of an NVIDIA card.<\/p>\nDevicemaster driver installed<\/strong>
\n<\/span>This will indicate No if the nslink module is not running. If the module is running, you should see the following entries<\/p>\nnslink service loaded<\/strong>
\nThis will indicate Yes if the nslink systemd service is loaded. This does not indicate that the system is enabled to automatically start on boot. To see more information, execute the following:<\/p>\nsystemctl status nslink<\/pre>\nnslink service enabled<\/strong>
\nThis will indicate Yes if the nslink systemd service is enabled, meaning it will automatically load on boot. To see more information, execute the following:<\/p>\nsystemctl status nslink<\/pre>\nRead\/write permissions correctly set for devicemaster<\/strong>
\n<\/span>When using a comtrol devicemaster TCP to serial hub, the nslink module must be loaded. Checking that the module is loaded comes from parsing the output of lsmod.
\nnslink is managed by systemd. For it to function, the service must be active. For it to function on reboot, the service must be enabled.<\/p>\nTo check the status, run<\/p>\n
systemctl status nslink<\/pre>\nTo start the service,<\/p>\n
systemctl start nslink<\/pre>\nTo ensure it automatically starts on boot,<\/p>\n
systemctl enable nslink<\/pre>\nThere are different means of setting permissions for the serial ports. The tar file used to install the devicemaster drivers will include detailed instructions for setting up and troubleshooting that device.<\/p>\n
Rocketport driver RPM installed<\/strong>
\n<\/span>This will indicate Yes if either the rocketport card or rocketport infinity card is detected in the output of lspci. The rocketpart card is no longer available, but many systems still use them. They plug into the PCI slot of the motherboard. The rocketport infinity card is the successor and plugs into the PCIe slot. These are serial devices.
\nGenerally speaking, the same rocketport infinity driver can be used for any serial rocketport card that installs in the PCI express slot, no matter how many ports it has.<\/p>\nRocketport module loaded<\/strong>
\n<\/span>This will indicate Yes if the rocket module is found to be loaded in the output of lsmod for a rocketport card.<\/p>\nRocketPort Infinity Express RPM installed<\/strong>
\n<\/span>This will indicate Yes if the rp_infinity_express rpm is installed.<\/p>\nRocketPort Infinity Express module installed<\/strong>
\n<\/span>This will indicate Yes if the rp2 module is found to be loaded in the output of lsmod for a rocketport infinity card.<\/p>\nRead\/write permissions correctly set for devicemaster<\/strong>
\n<\/span>This checks that read\/write permissions for the test cell user are currently set.
\nThese permissions are sometimes configured in the rc-local service managed by systemd, the status of which can be seen by checking the output of<\/p>\nsystemctl status rc-local.service<\/pre>\nCounter Timer module loaded<\/strong>
\n<\/span>This will indicate Yes if the tc9513 modules is loaded in the output of lsmod. This module is only required if you’re using MTL IO from the dark ages.<\/p>\nCanFD rpm installed<\/strong>
\n<\/span>This will indicate Yes if the cyflex-canfd rpm is installed. This rpm will download and install the drivers from PEAK.
\nThis rpm can also be installed to install the drivers for a PEAK PCIe CAN card installed on the motherboard, or to utilize the CanFD USB dongle from PEAK.<\/p>\nCAN device present<\/strong>
\n<\/span>This will indicate Yes if the output of<\/p>\nifconfig -a<\/pre>\nindicates a CAN device is present.
\nIt does not validate anything else is properly configured, or that the device has been enabled or configured. For more information on CAN check the usage for<\/p>\n
CanDbc
\nCanFD
\nenable_candbc_nopasswd<\/p>\n
EtherCAT rpm installed<\/strong>
\n<\/span>This will indicate Yes if the cyflex-ethercat rpm is installed. This rpm does not need to be installed if you’re not communicating with any EtherCAT devices.<\/p>\nMAC address for EtherCAT configured<\/strong>
\n<\/span>This will indicate Yes if anything is found to be configured after MASTER0= in \/etc\/sysconfig\/ethercat. It does not verify you’ve correctly put a MAC address in that file.
\nThis will only be displayed if the cyflex-ethercat rpm has been installed.<\/p>\nNumber of EtherCAT MAC addresses configured<\/strong>
\n<\/span>Indicates an integer value of how many MASTERS have been configured in \/etc\/sysconfig\/ethercat. This will only be displayed if the cyflex-ethercat rpm has been installed.<\/p>\nGeneric driver configured for EtherCAT<\/strong>
\n<\/span>Ensures the generic driver has been specified in the bottom of the \/etc\/sysconfig\/ethercat config file. This will only be displayed if the cyflex-ethercat rpm has been installed.<\/p>\n\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":"
The verify_testcell_config.sh script was created to provide a quick means of checking certain system parameters. Although it was primarily developed for developers to quickly\u00a0 assess how a system has been configured, it is a good tool for customers to use after building a new computer. The script does a variety of checks, then outputs information […]<\/p>\n","protected":false},"author":47,"featured_media":0,"parent":1949,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-14640","page","type-page","status-publish","hentry"],"post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/cyflex.com\/index.php\/wp-json\/wp\/v2\/pages\/14640","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cyflex.com\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/cyflex.com\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/cyflex.com\/index.php\/wp-json\/wp\/v2\/users\/47"}],"replies":[{"embeddable":true,"href":"https:\/\/cyflex.com\/index.php\/wp-json\/wp\/v2\/comments?post=14640"}],"version-history":[{"count":0,"href":"https:\/\/cyflex.com\/index.php\/wp-json\/wp\/v2\/pages\/14640\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/cyflex.com\/index.php\/wp-json\/wp\/v2\/pages\/1949"}],"wp:attachment":[{"href":"https:\/\/cyflex.com\/index.php\/wp-json\/wp\/v2\/media?parent=14640"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}