Peter Pap's Technowiki - User contributions [en]

MediaWiki:Sidebar

2025-06-27T03:13:48Z

Ppapa:

Rancher Login Page Blank

2025-06-27T03:11:13Z

Ppapa:

So, the Rancher login page is loading blank. You log into one of the Rancher nodes and see this:

# kubectl get node
E0627 01:17:45.898377 2181261 memcache.go:265] couldn't get current server API group list: an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding
E0627 01:17:45.899229 2181261 memcache.go:265] couldn't get current server API group list: an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding
E0627 01:17:45.901039 2181261 memcache.go:265] couldn't get current server API group list: an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding
E0627 01:17:45.901660 2181261 memcache.go:265] couldn't get current server API group list: an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding
E0627 01:17:45.903403 2181261 memcache.go:265] couldn't get current server API group list: an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding
Error from server (InternalError): an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding

You run the following command:

# openssl s_client -connect 127.0.0.1:443 -showcerts </dev/null | openssl x509 -noout -text
Can't use SSL_get_servername
depth=0 O = Acme Co, CN = Kubernetes Ingress Controller Fake Certificate
verify error:num=18:self-signed certificate
verify return:1
depth=0 O = Acme Co, CN = Kubernetes Ingress Controller Fake Certificate
verify error:num=10:certificate has expired
notAfter=Jun 26 01:04:33 2025 GMT
verify return:1
depth=0 O = Acme Co, CN = Kubernetes Ingress Controller Fake Certificate
notAfter=Jun 26 01:04:33 2025 GMT
verify return:1
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
82:a2:22:9a:7f:ff:06:e3:cd:4e:1f:23:a6:16:fc:05
Signature Algorithm: sha256WithRSAEncryption
Issuer: O = Acme Co, CN = Kubernetes Ingress Controller Fake Certificate
Validity
Not Before: Jun 26 01:04:33 2024 GMT
'''Not After : Jun 26 01:04:33 2025 GMT'''

Look for the "'''Not After'''" field. If it's in the past, then your "'''Kubernetes Ingress Controller Fake Certificate'''" has expired! This certificate is used for inter Rancher node communication. To make it renew, reboot the node. Wait for it to come back up, then reboot the next node etc. Rancher should be back.

Rancher Login Page Blank

2025-06-27T03:10:50Z

Ppapa:

So, the Rancher login page is loading blank. You log into one of the Rancher nodes and see this:

# kubectl get node
E0627 01:17:45.898377 2181261 memcache.go:265] couldn't get current server API group list: an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding
E0627 01:17:45.899229 2181261 memcache.go:265] couldn't get current server API group list: an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding
E0627 01:17:45.901039 2181261 memcache.go:265] couldn't get current server API group list: an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding
E0627 01:17:45.901660 2181261 memcache.go:265] couldn't get current server API group list: an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding
E0627 01:17:45.903403 2181261 memcache.go:265] couldn't get current server API group list: an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding
Error from server (InternalError): an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding

You run the following command:

# openssl s_client -connect 127.0.0.1:443 -showcerts </dev/null | openssl x509 -noout -text
Can't use SSL_get_servername
depth=0 O = Acme Co, CN = Kubernetes Ingress Controller Fake Certificate
verify error:num=18:self-signed certificate
verify return:1
depth=0 O = Acme Co, CN = Kubernetes Ingress Controller Fake Certificate
verify error:num=10:certificate has expired
notAfter=Jun 26 01:04:33 2025 GMT
verify return:1
depth=0 O = Acme Co, CN = Kubernetes Ingress Controller Fake Certificate
notAfter=Jun 26 01:04:33 2025 GMT
verify return:1
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
82:a2:22:9a:7f:ff:06:e3:cd:4e:1f:23:a6:16:fc:05
Signature Algorithm: sha256WithRSAEncryption
Issuer: O = Acme Co, CN = Kubernetes Ingress Controller Fake Certificate
Validity
Not Before: Jun 26 01:04:33 2024 GMT
'''Not After : Jun 26 01:04:33 2025 GMT'''

Look for the "Not After" field. If it's in the past, then your "Kubernetes Ingress Controller Fake Certificate" has expired! This certificate is used for inter Rancher node communication. To make it renew, reboot the node. Wait for it to come back up, then reboot the next node etc. Rancher should be back.

Rancher Login Page Blank

2025-06-27T03:09:16Z

Ppapa: Created page with "So, the Rancher login page is loading blank. You log into one of the Rancher nodes and see this: # kubectl get node E0627 01:17:45.898377 2181261 memcache.go:265] couldn'..."

So, the Rancher login page is loading blank. You log into one of the Rancher nodes and see this:

# kubectl get node
E0627 01:17:45.898377 2181261 memcache.go:265] couldn't get current server API group list: an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding
E0627 01:17:45.899229 2181261 memcache.go:265] couldn't get current server API group list: an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding
E0627 01:17:45.901039 2181261 memcache.go:265] couldn't get current server API group list: an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding
E0627 01:17:45.901660 2181261 memcache.go:265] couldn't get current server API group list: an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding
E0627 01:17:45.903403 2181261 memcache.go:265] couldn't get current server API group list: an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding
Error from server (InternalError): an error on the server ("dial tcp 10.43.0.1:443: connect: connection refused") has prevented the request from succeeding

You run the following command:

# openssl s_client -connect 127.0.0.1:443 -showcerts </dev/null | openssl x509 -noout -text
Can't use SSL_get_servername
depth=0 O = Acme Co, CN = Kubernetes Ingress Controller Fake Certificate
verify error:num=18:self-signed certificate
verify return:1
depth=0 O = Acme Co, CN = Kubernetes Ingress Controller Fake Certificate
verify error:num=10:certificate has expired
notAfter=Jun 26 01:04:33 2025 GMT
verify return:1
depth=0 O = Acme Co, CN = Kubernetes Ingress Controller Fake Certificate
notAfter=Jun 26 01:04:33 2025 GMT
verify return:1
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
82:a2:22:9a:7f:ff:06:e3:cd:4e:1f:23:a6:16:fc:05
Signature Algorithm: sha256WithRSAEncryption
Issuer: O = Acme Co, CN = Kubernetes Ingress Controller Fake Certificate
Validity
Not Before: Jun 26 01:04:33 2024 GMT
'''Not After : Jun 26 01:04:33 2025 GMT'''

The last line above tells you that "Kubernetes Ingress Controller Fake Certificate" has expired! To make it renew, reboot the node. Wait for it to come back up, then reboot the next node etc.

Rancher

2025-06-27T03:04:42Z

Ppapa: Created page with "<ul> <li>Rancher Login Page Blank</li> </UL>"

<ul>
<li>[[Rancher Login Page Blank]]</li>
</UL>

Kubernetes

2025-06-27T03:03:45Z

Ppapa: Created page with "<ul> <li>Rancher</li> </UL>"

<ul>
<li>[[Rancher]]</li>
</UL>

Main Page

2025-06-27T03:03:00Z

Ppapa:

Welcome to Peter Papagiannopoulos' Technowiki. This page is basically a brain dump of lots of different things I have done and learnt over a period of 18 years as a sys admin. You'll find simple commands that I have found useful over the years, but that I quite often forget. You'll find complete how-to's on things as varied as setting up Cisco wireless access points, to configuring a Solaris Jumpstart server. The idea for this site was a place for me to store my documentation in an easily accessible format, but also a place for people to find things that aren't always that easy to find. If you're reading this, I hope it's been of some use to you as well!

----

<ul>
<li>[[Solaris]]</li>
<li>[[CentOS/Redhat]]</li>
<li>[[Ubuntu]]</li>
<li>[[Windows]]</li>
<li>[[Apple/Mac OS]]</li>
<li>[[Cisco]]</li>
<li>[[NetApp]]</li>
<li>[[Oracle]]</li>
<li>[[General Unix]]</li>
<li>[[Nagios]]</li>
<li>[[VMware]]</li>
<li>[[Veritas]]</li>
<li>[[Avocent]]</li>
<li>[[Dell]]</li>
<li>[[OpenSSL]]</li>
<li>[[Kubernetes]]</li>
</UL>

MediaWiki:Sidebar

2024-02-12T04:44:24Z

Ppapa:

Verify that a private key matches a certificate

2024-02-12T04:42:38Z

Ppapa:

To verify that an RSA private key matches the RSA public key in a certificate you need to i) verify the consistency of the private key and ii) compare the modulus of the public key in the certificate against the modulus of the private key.

To verify the consistency of the RSA private key and to view its modulus:
openssl rsa -modulus -noout -in ''my.key'' | openssl md5

openssl rsa -check -noout -in ''my.key''
RSA Key is ok
If it doesn't say 'RSA key ok', it isn't OK!"

To view the modulus of the RSA public key in a certificate:
openssl x509 -modulus -noout -in ''my.crt'' | openssl md5

If the first commands shows any errors, or if the modulus of the public key in the certificate and the modulus of the private key do not exactly match, then you're not using the correct private key. You can either create a brand new key and CSR and contact support, or you can do a search for any other private keys on the system and see if they match.

Verify that a private key matches a certificate

2024-02-12T04:42:26Z

Ppapa:

Verify that a private key matches a certificate

2024-02-12T04:41:41Z

Ppapa: Created page with "To verify that an RSA private key matches the RSA public key in a certificate you need to i) verify the consistency of the private key and ii) compare the modulus of the publi..."

To verify that an RSA private key matches the RSA public key in a certificate you need to i) verify the consistency of the private key and ii) compare the modulus of the public key in the certificate against the modulus of the private key.

To verify the consistency of the RSA private key and to view its modulus:
openssl rsa -modulus -noout -in myserver.key | openssl md5

openssl rsa -check -noout -in myserver.key
RSA Key is ok
If it doesn't say 'RSA key ok', it isn't OK!"

To view the modulus of the RSA public key in a certificate:
openssl x509 -modulus -noout -in myserver.crt | openssl md5

If the first commands shows any errors, or if the modulus of the public key in the certificate and the modulus of the private key do not exactly match, then you're not using the correct private key. You can either create a brand new key and CSR and contact support, or you can do a search for any other private keys on the system and see if they match.

OpenSSL

2024-02-12T04:40:29Z

Ppapa:

<ul>
<li>[[Verify that a private key matches a certificate]]</li>
</ul>

OpenSSL

2024-02-12T04:40:20Z

Ppapa: Created page with "ul> <li>Verify that a private key matches a certificate</li> </ul>"

ul>
<li>[[Verify that a private key matches a certificate]]</li>
</ul>

Main Page

2024-02-12T04:39:13Z

Ppapa:

Increasing disk space on a VM using Logical Volumes

2022-05-26T03:09:24Z

Ppapa:

So you have a CentOS VM that uses logical volumes and it's running out of space on a given filesystem. You can increase the disk space as described [https://kb.vmware.com/s/article/1006371 here]. Slight adjustments below:

1. Power off the virtual machine.

2. Edit the virtual machine settings and extend the virtual disk size.

3. Power on the virtual machine.

4. Identify the device name, which is by default /dev/sda, and confirm the new size by running the command:

# fdisk -l

5. Create a new primary partition:

# fdisk /dev/sda (depending the results of the step 4)

Press '''p''' to print the partition table to identify the number of partitions. By default, there are 2: sda1 and sda2.

Press '''n''' to create a new primary partition.

Press '''p''' for primary.

Press '''3''' for the partition number, depending on the output of the partition table print.

Press Enter two times.

Press '''t''' to change the system's partition ID.

Press '''3''' to select the newly creation partition.

Type '''8e''' to change the Hex Code of the partition for Linux LVM.

Press '''w''' to write the changes to the partition table.

6. Restart the virtual machine.

7. Run this command to convert the new partition to a physical volume:

'''Note:''' The number for the sda can change depending on system setup. Use the sda number that was created in step 5.

# pvcreate /dev/sda3

8. Run this command to extend the physical volume:

# vgextend VolGroup00 /dev/sda3

'''Note:''' To determine which volume group to extend, use the command vgdisplay.

9. Run this command to verify how many physical extents are available to the Volume Group:

# vgdisplay VolGroup00 | grep "Free"

10. Run the following command to extend the Logical Volume:

# lvextend -L+#G /dev/VolGroup00/LogVol00

Where # is the number of Free space in GB available as per the previous command. Use the full number output from Step 10 including any decimals.

'''Note:''' To determine which logical volume to extend, use the command lvdisplay.

11. Run the following command to expand the ext3 filesystem online, inside of the Logical Volume:

# resize2fs /dev/VolGroup00/LogVol00

YUM and RPM

2022-03-23T00:19:17Z

Ppapa:

YUM (Yellowdog Updater, Modified) has become the defacto standard for managing packages on CentOS, RedHat and Fedora. The benefits are obvious in that if you go to install a package, it will tell if there are any other required packages and will offer you the option of installing them. You can still use RPM (RedHat Package Manager), but of course then you're on your own when it comes to downloading and installing other required packages. Here are some useful YUM and RPM commands.

== YUM ==

=== List all available packages for Installation ===

This command:

yum -y list

will give you the complete list of packages that can be downloaded and installed with the yum command. Very useful for searching with 'grep'.

=== Show which user has performed yum tasks in the past ===

yum history

=== Show the yum history of a given package ===

yum history info ''package_name''

This will show every time the ''package_name'' in a yum action, i.e. when it was installed, updated, erased etc, and during which yum Transactions it occurred. VERY HANDY when trying to figure out who installed what and when!

== RPM ==

=== Using RPM to see if a package is installed ===

rpm -qa package_name

Email alerts failing to send from Dell iDRAC v9

2021-12-10T00:38:40Z

Ppapa:

If you have a Dell server with an iDRAC9, release 4.x, you'll no doubt no longer be receiving email from it. The reason for this is:

''After iDRAC is upgraded to version 4.00.00.00, you may stop receiving encrypted email alerts from iDRAC, if the external email server does not support encryption. iDRAC firmware version 4.00.00.00 introduces a user-selectable encryption option and the default protocol is StartTLS.''

The tell-tale sign of this is when you see the following message in your mail server logs:

Dec 10 00:33:28 mailhost01 sendmail[22446]: 1BA0XSsj022446: idrac.mydomain.com [192.168.2.2] did not issue MAIL/EXPN/VRFY/ETRN during connection to Daemon0

To start receiving email messages again, disable the email encryption by using the following RACADM command:

racadm set idrac.RemoteHosts.ConnectionEncryption None

As of iDRAC9 release 5.x, you can change this from the GUI:

- iDRAC Settings
-> Settings
- SMTP (Email) Server Settings
-> Connection Encryption : '''None'''

Veritas

2021-09-05T23:29:32Z

Ppapa:

<ul>
<li>[[Installing NetBackup on Linux]]</li>
<li>[[Manually expiring images from disk in NetBackup]]</li>
<li>[[Netbackup – Increase Number of Days in Activity Monitor Job History]]</li>
<li>[[Overriding the Symantec IPS on a NetBackup Appliance]]</li>
<li>[[Configure NetBackup client based encryption]]</li>
<li>[[All compatible drive paths are down but media is available]]</li>
</UL>

Show files for a given tablespace

2021-03-11T00:43:54Z

Ppapa:

set linesize 160
set wrap off
column name format a20
column filename format a50

select ts.name, df.name as FILENAME
from V_$TABLESPACE ts, V_$DATAFILE df
where df.TS# = ts.TS#
order by ts.name , df.name;

Show files for a given tablespace

2021-03-11T00:43:43Z

Ppapa:

Show files for a given tablespace

2021-03-11T00:43:25Z

Ppapa: Created page with "set linesize 160 set wrap off column name format a20 column filename format a50 select ts.name, df.name as FILENAME from V_$TABLESPACE ts, V_$DATAFILE df where df.TS# = ts.TS..."

Database

2021-03-11T00:39:11Z

Ppapa:

<ul>
<li>[[Basic Administrative SQL commands]]</li>
<li>[[Get NLS info for your DB]]</li>
<li>[[Determine User Session Privs]]</li>
<li>[[Check backup status of a Database]]</li>
<li>[[Check the percentage free space on autoextend tabelspaces]]</li>
<li>[[Show files for a given tablespace]]</li>
</ul>

MediaWiki:Sidebar

2020-10-08T06:10:10Z

Ppapa:

Email alerts failing to send from Dell iDRAC v9

2020-10-08T05:35:13Z

Ppapa:

If you have a Dell server with a version 9 iDRAC, release 4.x, you'll no doubt no longer be receiving email from it. The reason for this is:

''After iDRAC is upgraded to version 4.00.00.00, you may stop receiving encrypted email alerts from iDRAC, if the external email server does not support encryption. iDRAC firmware version 4.00.00.00 introduces a user-selectable encryption option and the default protocol is StartTLS.''

To start receiving email messages again, disable the email encryption by using the following RACADM command:

racadm set idrac.RemoteHosts.ConnectionEncryption None

Email alerts failing to send from Dell iDRAC v9

2020-10-08T05:35:01Z

Ppapa: Created page with "If you have a Dell server with a version 9 iDRAC, release 4.x, you'll no doubt no longer be receiving email from it. The reason for this is: ''After iDRAC is upgraded to ver..."

Dell

2020-10-08T05:33:05Z

Ppapa:

<ul>
<li>[[Email alerts failing to send from Dell iDRAC v9]]</li>
</UL>

Dell

2020-10-08T05:31:29Z

Ppapa: Created page with "<ul> <li>Email alerts failing to send from Dell iDrac v9</li> </UL>"

<ul>
<li>[[Email alerts failing to send from Dell iDrac v9]]</li>
</UL>

Main Page

2020-10-08T05:30:40Z

Ppapa:

Changing sendmail connect domain macro, Dj, in sendmail.mc

2020-10-02T01:30:46Z

Ppapa:

Generally, hacking your sendmail.cf is a very bad idea! Any changes you want to make should be done in the sendmail.mc file and then the sendmail.cf file built from it. This example is where your mail relay has an internal hostname (eg. internal01.mail.servers.net) but, when it connects to the outside world, you want it to use a different name, eg. relay.myorg.com. Often this is where you have multiple internal mail servers, but they share a common external IP. To change this setting:

1. Edit sendmail.mc and add/change this line:

define(`confDOMAIN_NAME', `relay.myorg.com')dnl

Obviously, change the value to whatever it is that you need for your org.

2. Rebuild sendmail.cf for your platform. It's different on Solaris and Linux, so do what works for you.

3. Restart sendmail.

Changing sendmail connect domain macro, Dj, in sendmail.mc

2020-10-02T01:17:59Z

Ppapa: Created page with "Generally, hacking your sendmail.cf is a very bad idea! Any changes you want to make should be done in the sendmail.mc file and then the sendmail.cf file built from it. This e..."

Generally, hacking your sendmail.cf is a very bad idea! Any changes you want to make should be done in the sendmail.mc file and then the sendmail.cf file built from it. This example is where your mail relay has an internal hostname (eg. internal01.mail.servers.net) but, when it connects to the outside world, you want it to use a different name, eg. relay.myorg.com. oftne this is where you have multiple internal mail servers, but they share a common external IP. To change this setting:

1. Edit sendmail.mc and add/change this line:

define(`confDOMAIN_NAME', `relay.myorg.com')dnl

Obviously, change the value to whatever it is that you need for your org.

2. Rebuild sendmail.cf for your platform. It's different on Solaris and Linux, so do what works for you.

3. Restart sendmail.

General Unix

2020-10-02T01:11:53Z

Ppapa:

<ul>
<li>[[X11 weirdness]]</li>
<li>[[sed commands]]</li>
<li>[[Testing SMTP host with telnet]]</li>
<li>[[Merge AVI files]]</li>
<li>[[Convert MKV to MP4]]</li>
<li>[[Extracting the Private Key from a Java Keystore]]</li>
<li>[[Changing sendmail connect domain macro, Dj, in sendmail.mc]]</li>
</ul>

Increasing disk space on a VM using Logical Volumes

2020-10-01T02:27:22Z

Ppapa:

So you have a CentOS VM that uses logical volumes and it's running out of space on a given filesystem. You can increase the disk space as described [https://kb.vmware.com/s/article/1006371 here]. Slight adjustments below:

1. Power off the virtual machine.

2. Edit the virtual machine settings and extend the virtual disk size.

3. Power on the virtual machine.

4. Identify the device name, which is by default /dev/sda, and confirm the new size by running the command:

# fdisk -l

5. Create a new primary partition:

# fdisk /dev/sda (depending the results of the step 4)

Press p to print the partition table to identify the number of partitions. By default, there are 2: sda1 and sda2.

Press n to create a new primary partition.

Press p for primary.

Press 3 for the partition number, depending on the output of the partition table print.

Press Enter two times.

Press t to change the system's partition ID.

Press 3 to select the newly creation partition.

Type 8e to change the Hex Code of the partition for Linux LVM.

Press w to write the changes to the partition table.

6. Restart the virtual machine.

7. Run this command to convert the new partition to a physical volume:

'''Note:''' The number for the sda can change depending on system setup. Use the sda number that was created in step 5.

# pvcreate /dev/sda3

8. Run this command to extend the physical volume:

# vgextend VolGroup00 /dev/sda3

'''Note:''' To determine which volume group to extend, use the command vgdisplay.

9. Run this command to verify how many physical extents are available to the Volume Group:

# vgdisplay VolGroup00 | grep "Free"

10. Run the following command to extend the Logical Volume:

# lvextend -L+#G /dev/VolGroup00/LogVol00

Where # is the number of Free space in GB available as per the previous command. Use the full number output from Step 10 including any decimals.

'''Note:''' To determine which logical volume to extend, use the command lvdisplay.

11. Run the following command to expand the ext3 filesystem online, inside of the Logical Volume:

# resize2fs /dev/VolGroup00/LogVol00

Increasing disk space on a VM using Logical Volumes

2020-10-01T01:28:57Z

Ppapa: Created page with " So you have a CentOS VM that uses logical volumes and it's running out of space on a given filesystem. You can increase the disk space as described [https://kb.vmware.com/s/a..."

So you have a CentOS VM that uses logical volumes and it's running out of space on a given filesystem. You can increase the disk space as described [https://kb.vmware.com/s/article/1006371 here]. Slight adjustments below:

1. Power off the virtual machine.

2. Edit the virtual machine settings and extend the virtual disk size.

3. Power on the virtual machine.

4. Identify the device name, which is by default /dev/sda, and confirm the new size by running the command:

# fdisk -l

5. Create a new primary partition:

# fdisk /dev/sda (depending the results of the step 4)

Press p to print the partition table to identify the number of partitions. By default, there are 2: sda1 and sda2.
Press n to create a new primary partition.
Press p for primary.
Press 3 for the partition number, depending on the output of the partition table print.
Press Enter two times.
Press t to change the system's partition ID.
Press 3 to select the newly creation partition.
Type 8e to change the Hex Code of the partition for Linux LVM.
Press w to write the changes to the partition table.

6. Restart the virtual machine.

# fdisk -l

7. Run this command to convert the new partition to a physical volume:

'''Note:''' The number for the sda can change depending on system setup. Use the sda number that was created in step 5.

# pvcreate /dev/sda3

8. Run this command to extend the physical volume:

# vgextend VolGroup00 /dev/sda3

'''Note:''' To determine which volume group to extend, use the command vgdisplay.

9. Run this command to verify how many physical extents are available to the Volume Group:

# vgdisplay VolGroup00 | grep "Free"

10. Run the following command to extend the Logical Volume:

# lvextend -L+#G /dev/VolGroup00/LogVol00

Where # is the number of Free space in GB available as per the previous command. Use the full number output from Step 10 including any decimals.

'''Note:''' To determine which logical volume to extend, use the command lvdisplay.

11. Run the following command to expand the ext3 filesystem online, inside of the Logical Volume:

# resize2fs /dev/VolGroup00/LogVol00

CentOS/Redhat

2020-10-01T01:28:51Z

Ppapa:

<ul>
<li>[[CentOS/RedHat Networking]]</li>
<li>[[Enabling Serial Console Output]]</li>
<li>[[YUM and RPM]]</li>
<li>[[Kickstart]]</li>
<li>[[Installing CentOS/RedHat on disks larger than 2Tb]]</li>
<li>[[Mirroring Disks#CentOS/RedHat|Mirroring Disks]]</li>
<li>[[Replacing a failed disk in a software mirror#CentOS/RedHat|Replacing a failed disk in a software mirror]]</li>
<li>[[Creating a CentOS mirror site]]</li>
<li>[[Password Expire]]</li>
<li>[[Enforcing Password Complexity on CentOS/RedHat]]</li>
<li>[[Adding a Disk and Extending a Logical Volume]]</li>
<li>[[Enabling a service]]</li>
<li>[[Increasing disk space on a VM using Logical Volumes]]</li>
</ul>

CentOS/Redhat

2020-10-01T00:56:54Z

Ppapa:

Change Password Policy Settings

2020-08-18T02:20:45Z

Ppapa:

Surprising well documented [https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/how-to-configure-security-policy-settings here].

Configure NTP on Windows 2012 server

2020-07-16T02:27:46Z

Ppapa:

So you want your Windows server to get it's time from you local NTP server. Here's how to configure it:

1. Fire up Windows PowerShell as Administrator

2. Set the NTP servers:

w32tm /config /manualpeerlist:"0.pool.ntp.org 1.pool.ntp.org" /syncfromflags:MANUAL

Obviously, replace the pool servers above with your internal NTP server hostnames or IP's.

3. Restart the Windows time service:

Stop-Service w32time
Start-Service w32time

You can check what you've done with:

w32tm /query /configuration
w32tm /query /status

Overriding the Symantec IPS on a NetBackup Appliance

2019-09-03T03:57:40Z

Ppapa:

NetBackup appliances are basically SUSE Linux boxes with Symantec's own interface over the top. They are designed to be a black box appliance that just works and therefore, Symantec try to keep you out of the base OS so you don't break it. However, there are instances where you might like to be able to access the base OS. In order to do so, you need to bypass the Symantec Intrusion Security Policy (IPS...no I don't know why that accronym doesn't match the name). If you're an experienced Unix/Linux admin, this is safe to do and the instructions here are taken from Symantec's own NetBackup 52xx Appliance Security Guide.

1. Log on to the NetBackup Appliance Shell Menu as an Administrator.

2. Run the Support > Maintenance command.

3. To enter your Maintenance account, run the following command, and provide the password when you receive a prompt.

4. In the Maintenance mode, type the following command to override the Symantec Intrusion Security Policy:

/opt/Symantec/sdcssagent/IPS/sisipsoverride.sh

The appliance displays the following message:

Symantec Critical Protection Policy Override
Agent Version: 5.2.9 (build 739)
Current Policy: NetBackup Appliance Prevention Policy, r19
Policy Prevention: Enabled
Policy Override: Allowed
Override State: Not overridden
To override the policy and disable protection,
enter your login password.
Password:

5. Enter your maintenance password.

The appliance then displays the following options:

Choose the type of override that you wish to perform:
1. Override Prevention except for Self Protection
2. Override Prevention Completely
Choice?

6. Enter 1 to override prevention except for self protection.

Note: Symantec recommends that you use Option 1. Selecting Option 1 allows modification only to the NetBackup Appliance Shell Menu and NOT to the SCSP Agent.

The appliance displays the following options:

Choose the amount of time after which to automatically re-enable:
1. 15 minutes
2. 30 minutes
3. 1 hour
4. 2 hours
5. 4 hours
6. 8 hours
7. never

7. Enter the appropriate number from 1 to 7 based on the time required to debug the Symantec support case.

The appliance displays the following message:

Enter a comment. Press Enter to continue.
Disabling the security policy for
debugging a Symantec
support case no - XYZ

8. Enter a relevant comment as to why the override is required.

The appliance overrides the policy and displays the following message:

Please wait while the policy is being overridden.
........
The policy was successfully overridden.

9. Run the elevate command to become root.

maintenance - !> '''elevate'''

You should now have access to the root account.

Configure NetBackup client based encryption

2019-04-29T00:14:20Z

Ppapa: Created page with "Documented quite well [https://www.veritas.com/support/en_US/article.100021401 here]"

Documented quite well [https://www.veritas.com/support/en_US/article.100021401 here]

Veritas

2019-04-29T00:13:47Z

Ppapa:

Veritas

2019-04-29T00:13:33Z

Ppapa:

MediaWiki:Sidebar

2019-04-29T00:12:36Z

Ppapa:

Veritas

2019-04-29T00:09:57Z

Ppapa: Created page with "<ul> <li>Installing NetBackup on Linux</li> <li>Manually expiring images from disk in NetBackup</li> <li>Netbackup – Increase Number of Days in Activity Monitor Jo..."

Main Page

2019-04-29T00:09:48Z

Ppapa:

Replacing a failed disk in a ZFS/ZPOOL raid array

2019-02-27T01:37:20Z

Ppapa:

This has been used on a SPARC S7-2, but should be relevant to most modern sparc based servers:

1. Identify the failed disk in the zpool array:

# '''zpool status'''
pool: rpool
state: DEGRADED

config:

NAME STATE READ WRITE CKSUM
rpool DEGRADED 0 0 0
mirror-0 DEGRADED 0 0 0
c0t5000CCA02F613ACCd0 ONLINE 0 0 0
'''c0t5000CCA02D0F6C44d0''' UNAVAIL 0 0 0

2. Find the device path for the drive you want to remove:

# '''diskinfo D:devchassis-path'''
D:devchassis-path c:occupant-compdev
---------------------------------- ---------------------
/dev/chassis/SYS/HDD0/disk c0t5000CCA02F613ACCd0
/dev/chassis/SYS/HDD1/disk '''c0t5000CCA02D0F6C44d0'''
/dev/chassis/SYS/HDD2 -
/dev/chassis/SYS/HDD3 -
/dev/chassis/SYS/HDD4 -
/dev/chassis/SYS/HDD5 -
/dev/chassis/SYS/HDD6 -
/dev/chassis/SYS/HDD7 -
/dev/chassis/SYS/MB/EUSB_DISK/disk c1t0d0

3. Check the drive's status:

# '''cfgadm -al'''
Ap_Id Type Receptacle Occupant Condition
/SYS/DBP/NVME0 unknown empty unconfigured unknown
/SYS/DBP/NVME1 unknown empty unconfigured unknown
/SYS/DBP/NVME2 unknown empty unconfigured unknown
/SYS/DBP/NVME3 unknown empty unconfigured unknown
c3 scsi-sas connected configured unknown
c3::w5000cca02f613acd,0 disk-path connected configured unknown
c4 scsi-sas connected configured unknown
'''c4::w5000CCA02D0F6C45,0 disk-path connected configured unknown'''
usb0/1 usb-storage connected configured ok
usb0/2 usb-hub connected configured ok

'''NOTICE''' the slight mismatch between the output of the last two commands.

4. Unconfigure the drive:

# '''cfgadm -c unconfigure c4::w5000CCA02D0F6C45,0'''

and check that it worked:

# '''cfgadm -al'''
Ap_Id Type Receptacle Occupant Condition
/SYS/DBP/NVME0 unknown empty unconfigured unknown
/SYS/DBP/NVME1 unknown empty unconfigured unknown
/SYS/DBP/NVME2 unknown empty unconfigured unknown
/SYS/DBP/NVME3 unknown empty unconfigured unknown
c3 scsi-sas connected configured unknown
c3::w5000cca02f613acd,0 disk-path connected configured unknown
c4 scsi-sas connected configured unknown
c4::w5000CCA02D0F6C45,0 disk-path connected '''unconfigured''' unknown

5. Turn on the Ok to Remove indicator for that drive:

# '''fmadm set-indicator /dev/chassis/SYS/HDD1/disk ok2rm on'''

and check that it worked:

# '''fmadm get-indicator /dev/chassis/SYS/HDD1/disk ok2rm'''
The indicator (ok2rm) is set to on.

6. Remove the failed drive and replace with the new one.

7. The new drive should be configured automatically, but check it anyway:

# '''cfgadm -al'''
Ap_Id Type Receptacle Occupant Condition
/SYS/DBP/NVME0 unknown empty unconfigured unknown
/SYS/DBP/NVME1 unknown empty unconfigured unknown
/SYS/DBP/NVME2 unknown empty unconfigured unknown
/SYS/DBP/NVME3 unknown empty unconfigured unknown
c3 scsi-sas connected configured unknown
c3::w5000cca02f613acd,0 disk-path connected configured unknown
c4 scsi-sas connected configured unknown
c4::w5000cca07d293ca1,0 disk-path connected '''configured''' unknown
usb0/1 usb-storage connected configured ok
usb0/2 usb-hub connected configured ok

If not, configure with:

# '''cfgadm -c unconfigure c4::w5000cca07d293ca1,0'''

8. Get the name od the new drive from the format command:

# '''format'''
Searching for disks...done

AVAILABLE DISK SELECTIONS:
0. c0t5000CCA02F613ACCd0 <HGST-H101860SFSUN600G-A990-558.91GB>
/scsi_vhci/disk@g5000cca02f613acc
/dev/chassis/SYS/HDD0/disk
1. '''c0t5000CCA07D293CA0d0''' <HGST-H101860SFSUN600G-A990-558.91GB>
/scsi_vhci/disk@g5000cca07d293ca0
/dev/chassis/SYS/HDD1/disk
2. c1t0d0 <VT-eUSB-7722-1.91GB>
/pci@300/pci@1/pci@0/pci@2/usb@0/storage@1/disk@0,0
/dev/chassis/SYS/MB/EUSB_DISK/disk
Specify disk (enter its number):

9. Replace the failed disk with the new disk in the zpool:

# '''zpool replace rpool c0t5000CCA02D0F6C44d0 c0t5000CCA07D293CA0d0'''

10. Check the progress with:

# '''zpool status'''
pool: rpool
state: ONLINE
scan: resilvered 75.8G in 8m24s with 0 errors on Wed Feb 27 11:39:38 2019

config:

NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
c0t5000CCA02F613ACCd0 ONLINE 0 0 0
c0t5000CCA07D293CA0d0 ONLINE 0 0 0

errors: No known data errors

11. Once the zpool is happy again, install the boot block on the new disk:

# '''installboot -f -F zfs /usr/platform/`uname -i`/lib/fs/zfs/bootblk /dev/rdsk/c0t5000CCA07D293CA0d0s0'''

Replacing a failed disk in a ZFS/ZPOOL raid array

2019-02-27T01:36:21Z

Ppapa:

This has been used on a SPARC S7-2, but should be relevant to most modern sparc based servers:

1. Identify the failed disk in the zpool array:

# '''zpool status'''
pool: rpool
state: DEGRADED

config:

NAME STATE READ WRITE CKSUM
rpool DEGRADED 0 0 0
mirror-0 DEGRADED 0 0 0
c0t5000CCA02F613ACCd0 ONLINE 0 0 0
'''c0t5000CCA02D0F6C44d0''' UNAVAIL 0 0 0

2. Find the device path for the drive you want to remove:

# '''diskinfo D:devchassis-path'''
D:devchassis-path c:occupant-compdev
---------------------------------- ---------------------
/dev/chassis/SYS/HDD0/disk c0t5000CCA02F613ACCd0
/dev/chassis/SYS/HDD1/disk '''c0t5000CCA02D0F6C44d0'''
/dev/chassis/SYS/HDD2 -
/dev/chassis/SYS/HDD3 -
/dev/chassis/SYS/HDD4 -
/dev/chassis/SYS/HDD5 -
/dev/chassis/SYS/HDD6 -
/dev/chassis/SYS/HDD7 -
/dev/chassis/SYS/MB/EUSB_DISK/disk c1t0d0

3. Check the drive's status:

# '''cfgadm -al'''
Ap_Id Type Receptacle Occupant Condition
/SYS/DBP/NVME0 unknown empty unconfigured unknown
/SYS/DBP/NVME1 unknown empty unconfigured unknown
/SYS/DBP/NVME2 unknown empty unconfigured unknown
/SYS/DBP/NVME3 unknown empty unconfigured unknown
c3 scsi-sas connected configured unknown
c3::w5000cca02f613acd,0 disk-path connected configured unknown
c4 scsi-sas connected configured unknown
'''c4::w5000CCA02D0F6C45,0 disk-path connected configured unknown'''
usb0/1 usb-storage connected configured ok
usb0/2 usb-hub connected configured ok

'''NOTICE''' the slight mismatch between the output of the last two commands.

4. Unconfigure the drive:

# '''cfgadm -c unconfigure c4::w5000CCA02D0F6C45,0'''

and check that it worked:

# '''cfgadm -al'''
Ap_Id Type Receptacle Occupant Condition
/SYS/DBP/NVME0 unknown empty unconfigured unknown
/SYS/DBP/NVME1 unknown empty unconfigured unknown
/SYS/DBP/NVME2 unknown empty unconfigured unknown
/SYS/DBP/NVME3 unknown empty unconfigured unknown
c3 scsi-sas connected configured unknown
c3::w5000cca02f613acd,0 disk-path connected configured unknown
c4 scsi-sas connected configured unknown
c4::w5000CCA02D0F6C45,0 disk-path connected '''unconfigured''' unknown

5. Turn on the Ok to Remove indicator for that drive:

# '''fmadm set-indicator /dev/chassis/SYS/HDD1/disk ok2rm on'''

and check that it worked:

# '''fmadm get-indicator /dev/chassis/SYS/HDD1/disk ok2rm'''
The indicator (ok2rm) is set to on.

6. Remove the failed drive and replace with the new one.

7. The new drive should be configured automatically, but check it anyway:

# '''cfgadm -al'''
Ap_Id Type Receptacle Occupant Condition
/SYS/DBP/NVME0 unknown empty unconfigured unknown
/SYS/DBP/NVME1 unknown empty unconfigured unknown
/SYS/DBP/NVME2 unknown empty unconfigured unknown
/SYS/DBP/NVME3 unknown empty unconfigured unknown
c3 scsi-sas connected configured unknown
c3::w5000cca02f613acd,0 disk-path connected configured unknown
c4 scsi-sas connected configured unknown
c4::w5000cca07d293ca1,0 disk-path connected '''configured''' unknown
usb0/1 usb-storage connected configured ok
usb0/2 usb-hub connected configured ok

If not, configure with:

# '''cfgadm -c unconfigure c4::w5000cca07d293ca1,0'''

8. Get the name od the new drive from the format command:

# '''format'''
Searching for disks...done

AVAILABLE DISK SELECTIONS:
0. c0t5000CCA02F613ACCd0 <HGST-H101860SFSUN600G-A990-558.91GB>
/scsi_vhci/disk@g5000cca02f613acc
/dev/chassis/SYS/HDD0/disk
1. '''c0t5000CCA07D293CA0d0''' <HGST-H101860SFSUN600G-A990-558.91GB>
/scsi_vhci/disk@g5000cca07d293ca0
/dev/chassis/SYS/HDD1/disk
2. c1t0d0 <VT-eUSB-7722-1.91GB>
/pci@300/pci@1/pci@0/pci@2/usb@0/storage@1/disk@0,0
/dev/chassis/SYS/MB/EUSB_DISK/disk
Specify disk (enter its number):

9. Replace the failed disk with the new disk in the zpool:

# '''zpool replace rpool c0t5000CCA02D0F6C44d0 c0t5000CCA07D293CA0d0'''

10. Check the progress with:

# '''zpool status'''

11. Once the zpool is happy again, install the boot block on the new disk:

# '''installboot -f -F zfs /usr/platform/`uname -i`/lib/fs/zfs/bootblk /dev/rdsk/c0t5000CCA07D293CA0d0s0'''

Replacing a failed disk in a ZFS/ZPOOL raid array

2019-02-27T01:20:47Z

Ppapa: Created page with "This has been used on a SPARC S7-2, but should be relevant to most modern sparc based servers: 1. Identify the failed disk in the zpool array: # zpool status pool: rpo..."

This has been used on a SPARC S7-2, but should be relevant to most modern sparc based servers:

1. Identify the failed disk in the zpool array:

# zpool status
pool: rpool
state: DEGRADED

config:

NAME STATE READ WRITE CKSUM
rpool DEGRADED 0 0 0
mirror-0 DEGRADED 0 0 0
c0t5000CCA02F613ACCd0 ONLINE 0 0 0
'''c0t5000CCA02D0F6C44d0''' UNAVAIL 0 0 0

2. Find the device path for the drive you want to remove:

# diskinfo D:devchassis-path
D:devchassis-path c:occupant-compdev
---------------------------------- ---------------------
/dev/chassis/SYS/HDD0/disk c0t5000CCA02F613ACCd0
/dev/chassis/SYS/HDD1/disk '''c0t5000CCA02D0F6C44d0'''
/dev/chassis/SYS/HDD2 -
/dev/chassis/SYS/HDD3 -
/dev/chassis/SYS/HDD4 -
/dev/chassis/SYS/HDD5 -
/dev/chassis/SYS/HDD6 -
/dev/chassis/SYS/HDD7 -
/dev/chassis/SYS/MB/EUSB_DISK/disk c1t0d0

Solaris

2019-02-27T01:13:10Z

Ppapa:

<ul>
<li>[[Jumpstart]]</li>
<li>[[Useful Commands]]</li>
<li>[[Building Custom Packages]]</li>
<li>[[Removing Solaris Packages Non-Interactively]]</li>
<li>[[NFS]]</li>
<li>[[Solaris Networking]]</li>
<li>[[Advanced Lights Out Management (ALOM)]]</li>
<li>[[Mirroring Disks]]</li>
<li>[[Create an NFS share with Solaris]]</li>
<li>[[Replacing a failed disk in a software mirror]]</li>
<li>[[Replacing a failed disk in a ZFS/ZPOOL raid array]]</li>
<li>[[Patching with Live Upgrade]]</li>
<li>[[Manipulating swap space on a running Solaris system]]</li>
<li>[[Navigating My Oracle Support]]</li>
<li>[[Oracle/Sun Hardware]]</li>
<li>[[ZFS]]</li>
<li>[[Virtualisation]]</li>
<li>[[Enforce Password Complexity on Solaris]]</li>
<li>[[ERROR: /packages/ufs-file-system: Last Trap: Division by Zero]]</li>
<li>[[Configure sendmail masquerading]]</li>
<li>[[Slow SSH Connection]]</li>
<li>[[Solaris 11: Useful commands]]</li>
</ul>

Solaris 11: Useful commands

2018-09-27T03:27:49Z

Ppapa: /* Determining Oracle Solaris 11 OS Package Update Version */

== Determining Oracle Solaris 11 OS Package Update Version ==

To determine the package version of the Oracle Solaris 11 OS installed on your system:

pkg info kernel

== Check Available Versions ==

If you want to update your operating system release, check the available versions of the pkg:/entire incorporation package:

pkg list -af entire

Solaris 11: Useful commands

2018-09-27T03:26:22Z

Ppapa: Created page with " == Determining Oracle Solaris 11 OS Package Update Version == pkg info kernel == Check Available Versions == If you want to update your operating system release, check..."

== Determining Oracle Solaris 11 OS Package Update Version ==

pkg info kernel

== Check Available Versions ==

If you want to update your operating system release, check the available versions of the pkg:/entire incorporation package:

pkg list -af entire