11-19-2008
The problem right now is that smartmon, pure and simple, isn't working -- it's not getting the data. It won't be able to give you any advance warning should your SATA drives decide to slowly go south on you.
From the sounds of the error, -d won't work for you because your version specifically states it doesn't support -d yet, and neither do your device drivers. A kernel upgrade, then an upgrade to smartmon, is needed to get smartmon back in order as I see it.
10 More Discussions You Might Find Interesting
1. UNIX Desktop Questions & Answers
Hey all,
I'm brand new to Unix/Linux and have a couple of questions. I own a small education/consulting company that has a staff of approx. 50 employees. Most our work is geared towards the office-style environment (i.e. Word, Excel, Powerpoint, etc.). There are also some C and Java programmers... (4 Replies)
Discussion started by: dennie1
4 Replies
2. Solaris
Ladies/Gentlemen,
I am looking for a web-based tool to keep track of my Sun inventory. The following list of fields are fields I would like to store: Root Passwd (needs to be secure) / Hostid / Console Port / IP Address / Platform / Application / Hostname . . . you get the point.
Do any of... (4 Replies)
Discussion started by: pc9456
4 Replies
3. Post Here to Contact Site Administrators and Moderators
Hi,
I am new at this site and at unix. I was reading some answers that the administrators and moderators have posted to others, and sometimes I feel like their a little sarcastic.
I am asking just to be patient to me, I know nothing about unix but I do want to learn, and I think that positive... (7 Replies)
Discussion started by: HN19
7 Replies
4. UNIX for Dummies Questions & Answers
i'm trying to figure out a script that uses sed, and i'm not totally sure if it does what I think it does.
The script...
- takes in 3 inputs, $1, $2 are names. $3 is a file.
- filename is a file.
Here is what I'm trying to figure out:
cat $3 | grep "id17" > var2
sed "s|@@.*||g" var2 >... (1 Reply)
Discussion started by: gammaman
1 Replies
5. UNIX for Dummies Questions & Answers
Hello,
I get the following in one of my error logs:
Device /dev/sda, SATA disks accessed
via libata are not currently supported by smartmontools. When libata is
given an ATA
pass-thru ioctl() then an additional '-d libata' device type will be
added to smartmontools.
---------------
I... (0 Replies)
Discussion started by: mojoman
0 Replies
6. UNIX for Advanced & Expert Users
This perhaps does not belong in ths category; apologies, however, we have a heated debate going and your input will decide the result.
Should UNIX (HP, AIX, etc) be rebooted following a monthly cycle (Every month, or a qtr, etc.). We have some UX admins (grumps) who say they have seen a UX... (6 Replies)
Discussion started by: rsheikh
6 Replies
7. UNIX for Advanced & Expert Users
Hello all,
I want to deny any torrents passing thru linux box that are NOT encrypted. My ISP is doing packet inspection and gives warnings.
I'd like to allow torrents when client sets encryption.
Any thoughts? (5 Replies)
Discussion started by: darkman_hr
5 Replies
8. What is on Your Mind?
Dear Forum staff / Advisors / members ,
I am having something in my mind, about Linux / Unix possible Interview questions collections, I guess if I post them here,which might be useful for our members and for students, and in meantime we can discuss also about those questions, what's your... (4 Replies)
Discussion started by: Akshay Hegde
4 Replies
9. Shell Programming and Scripting
:wall:I've this simple code:
STF=/opt/aaa
cat $STF | nice sort -u > $STF.new && mv $STF.new $STF
Which works until today. What happened is that this script has been corrupted the FS, so I've to use fschk to repair the filesystem.
I presume the move command executed just a little too early... (1 Reply)
Discussion started by: accolito
1 Replies
10. AIX
Why Do We Need Root on the HMC?
In this article in IBMSystems Magazine Rob McNelly asked the question
Why Don't We Have Root on the HMC?
and he goes on to justify why we indeed shouldn't have root - kinda. I think his arguments are not as valid as he perhaps thinks they are and what's more... (11 Replies)
Discussion started by: bakunin
11 Replies
LEARN ABOUT CENTOS
pki-upgrade
pki-upgrade(8) PKI Upgrade Tool pki-upgrade(8)
NAME
pki-upgrade - Tool for upgrading system-wide configuration for Certificate System.
SYNOPSIS
pki-upgrade [OPTIONS]
DESCRIPTION
There are two parts to upgrading Certificate System: upgrading the system configuration files used by both the client and the server pro-
cesses and upgrading the server configuration files.
When upgrading Certificate System, the existing system configuration files (e.g. /etc/pki/pki.conf) may need to be upgraded because the
content may have changed from one version to another. The configuration upgrade is executed automatically during RPM upgrade. However, in
case there is a problem, the process can also be run manually using pki-upgrade.
The system upgrade process is done incrementally using upgrade scriptlets. The upgrade process and scriptlet execution is monitored in
upgrade trackers. A counter shows the latest index number for the most recently executed scriptlet; when all scriptlets have run, the com-
ponent tracker shows the updated version number.
The scriptlets are stored in the upgrade directory:
/usr/share/pki/upgrade/<version>/<index>-<name>
The version is the system version to be upgraded. The index is the script execution order. The name is the scriptlet name.
During upgrade, the scriptlets will back up all changes to the filesystem into the following folder:
/var/log/pki/upgrade/<version>/<index>
The version and index values indicate the scriptlet being executed. A copy of the files and folders that are being modified or removed will
be stored in oldfiles. The names of the newly-added files and folders will be stored in newfiles.
The system upgrade process is tracked using this file:
/etc/pki/pki.version
The file stores the current configuration version and the last successful scriptlet index.
OPTIONS
General options
--silent
Upgrade in silent mode.
--status
Show upgrade status only without performing the upgrade.
--revert
Revert the last version.
-X Show advanced options.
-v, --verbose
Run in verbose mode.
-h, --help
Show this help message.
Advanced options
The advanced options circumvent the normal component tracking process by changing the scriptlet order or changing the tracker information.
WARNING: These options may render the system unusable.
--scriptlet-version <version>
Run scriptlets for a specific version only.
--scriptlet-index <index>
Run a specific scriptlet only.
--remove-tracker
Remove the tracker.
--reset-tracker
Reset the tracker to match the package version.
--set-tracker <version>
Set the tracker to a specific version.
OPERATIONS
Interactive mode
By default, pki-upgrade will run interactively. It will ask for a confirmation before executing each scriptlet.
% pki-upgrade
If there is an error, it will stop and show the error.
Silent mode
The upgrade process can also be done silently without user interaction:
% pki-upgrade --silent
If there is an error, it will stop and show the error.
Checking upgrade status
It is possible to check the status of a running upgrade process.
% pki-upgrade --status
Troubleshooting
If there is an error, rerun the upgrade in verbose mode:
% pki-upgrade --verbose
Check the scriptlet to see which operations are being executed. Once the error is identified and corrected, the upgrade can be resumed by
re-running pki-upgrade.
It is possible to rerun a failed script by itself, specifying the instance and subsystem, version, and scriptlet index:
% pki-upgrade --scriptlet-version 10.0.1 --scriptlet-index 1
Reverting an upgrade
If necessary, the upgrade can be reverted:
% pki-upgrade --revert
Files and folders that were created by the scriptlet will be removed. Files and folders that were modified or removed by the scriptlet will
be restored.
FILES
/usr/sbin/pki-upgrade
AUTHORS
Ade Lee <alee@redhat.com>, Ella Deon Lackey <dlackey@redhat.com>, and Endi Dewata <edewata@redhat.com>. pki-upgrade was written by the
Dogtag project.
COPYRIGHT
Copyright (c) 2013 Red Hat, Inc. This is licensed under the GNU General Public License, version 2 (GPLv2). A copy of this license is avail-
able at http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt.
version 1.0 Jul 22, 2013 pki-upgrade(8)