7022110: GW Admin Console Help text for “PO Restore Area” is incorrect

This document (7022110) is provided subject to the disclaimer at the end of this document.

Environment

GroupWise 2014 R2 Support Pack 2

Situation

GW Admin Console Help text for “PO Restore Area” is incorrectfor a Linux POA where it states this today in14.2.2-126868…
——
Path: Specify the path to the restore area folder, from thepoint of view of the POA that must access it.
Linux Path: For GroupWise 8 Mac/Linux client users, specifythe path from the point of view of Mac or Linux workstations.
——

Resolution

it should say this…
——
Path: Specify the path to the restore area folder, from thepoint of view of the POA that must access it.
Linux Path: Specify the full path to the restore area folder,from the point of view of the Linux POA that must access it. The Linux POA does not use the value entered in the “Path:” valueentered above.
——

Cause

This has been reported to engineering

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7021556: Why isn’t DBus restarted after it has been patched ?

This document (7021556) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 12

SUSE Linux Enterprise Desktop 12

Situation

The DBus package is upgraded, but it is still showing the previous version.

Resolution

When a restart of DBus is required, this needs to be achieved by rebooting the machine.

Cause

It is currently not supported to restart the DBus service using Systemd

Status

Reported to Engineering

Additional Information

In certain cases however, restarting the DBus service may work, however since most applications also do not support restarting DBus, this is neither recommended, nor supported.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7022069: ZENworks 2017 Update 1 system update overwrites HealthMetrics.xml

This document (7022069) is provided subject to the disclaimer at the end of this document.

Environment

ZENworks Configuration Management 2017

Situation

After applying ZENworks Configuration Management 2017 Update 1 to primary servers, the file HealthMetrics.xml is overwritten.

Linux: /opt/novell/zenworks/share/tomcat/webapps/zenworks/WEB-INF/conf/HealthMetrics.xml
Windows: %ZENWORKS_HOME%sharetomcatwebappszenworksWEB-INFconfHealthMetrix.xml

Resolution

If HealthMetrics.xml had been modified from defaults prior to the system update, restore the values manually and restart the ZENworks services.

Status

Reported to Engineering

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7021385: YaST clone_system module errors on ntp.conf changes

This document (7021385) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 12 Service Pack 3 (SLES 12 SP3)

Situation

The following lines in /etc/ntp.conf were uncommented:

server 127.127.1.0 # local clock (LCL)

fudge 127.127.1.0 stratum 10 # LCL is unsynchronized

After running yast clone_system, the following error was observed:

Internal error. Please report a bug report with logs.

Run save_y2logs to get complete logs.
Details: Invalid value #<CFA::NtpConf::FudgeRecord:0x00000005a18308 @augeas={:key=>"fudge[]", :value=>#<CFA::AugeasTreeValue:0x000
Caller: /usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:206:in `call_builtin'

The /root/autoinst.xml file does not get created after this error.

The issue cannot be duplicated on SLES12 SP2.

If the following changes are made in /etc/ntp.conf:

server 127.127.1.0 mode 5 prefer

fudge 127.127.1.0 stratum 10

No errors are observed, but /root/autoinst.xml does not get a valid <ntp-client><peers> section.

 <ntp-client>

<ntp_policy>auto</ntp_policy>
<peers config:type="list"/>
<restricts config:type="list"/>
<start_at_boot config:type="boolean">false</start_at_boot>
<start_in_chroot config:type="boolean">false</start_in_chroot>
<sync_interval config:type="integer">5</sync_interval>
<synchronize_time config:type="boolean">false</synchronize_time>
</ntp-client>

Resolution

Reported to Engineering. Contact support for a PTF.

Currently you will need to leave the lines commented out and add the tags manually to the /root/autoinst.xml file.

Cause

The problem occurs in yast2-ntp-client-3.2.14-2.5.11 and earlier versions.

Status

Reported to Engineering

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7018123: Steps to Create a Salt SUSE Manager Client

This document (7018123) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Manager 3 (salt client)

Situation

The SUSE Manager 3 has just been installed. What preparations/steps are needed in order to connect a salt client to SUSE Manager?

Resolution

1. Generate desired activation key.

a. Enter the webUI tool for SUSE Manager.

b. Select the Systems tab at the top of the page.
c. Select the Activation keys tab on the left-hand side of the page.
d. Click the Create Key link in the upper right-hand corner.
i. Description – Enter a description to identify the generated activation key.
ii. Key – Choose either automatic generation by leaving this field blank or enter the key name that is wanted for generation.
iii. Usage – Determine the maximum amount of systems that may be simultaneously registered to the SUSE Manager with this key, or leave blank for unlimited use.
iv. Base Channels – Specify the channels accessible to the client using this key. If a system using this key is not compatible with the selected channel, it will fall back to the default channel. The default channel will automatically assign channels to the client based on installed products.
v. Add-On System Types – Select any additional entitlements for the clients to receive with this key.
vi. Contact Method – Select how clients communicate with the SUSE Manager. (Not applicable to salt clients)
vii. Universal Default – Select whether or not this key should be the primary activation key for this organization.
e. Click Create Activation Key to create the key.
2. Select product(s) to make into channels.
a. Select the Admin tab at the top of the page.
b. Select the SUSE Products sub-tab.
c. Check the boxes of the products you want to be mirrored by the SUSE Manager.
d. Click the Add Products button at the bottom of the page after selecting the desired products to mirror.
e. Wait for mirroring to complete.
3. Create bootstrap repository.
a. Run the following command on the SUSE Manager:
# mgr-create-bootstrap-repo
b. Enter the desired product label.
c. Repeat for all products you need your clients to use.
4. Add the SUSE Manager Tools repository to the client.
a. Run the following command on the client. (The path in the repo will vary slightly based on version and service pack. e.g. below is specific to SLE 11 SP4)
# zypper ar http://<fqdn of SUSE Manager>/pub/repositories/11/4/bootstrap/ spacewalk-tools-repo
5. Refresh the client’s repositories.
a. Run this command on the client:
# zypper ref -s
6. Install all available salt packages on the client.
a. Run this command on the client:
# zypper in salt*
7. Point the client to the SUSE Manager as salt master.
a. Open the /etc/salt/minion file on the client
b. Uncomment (remove # symbol at the beginning of the line) and adjust the following line:
master: <fqdn of suse manager>

8. Create salt grains file telling client which activation key to use.
a. Create /etc/salt/grains file
b. Open /etc/salt/grains file
c. Add the following: (spacing and indentation is important)
susemanager:
activation_key: 1-<key>
9. Restart and enable the salt-minion service.
a. Run matching client version’s commands:
SLE11:
# service salt-minion restart
# chkconfig salt-minion on
SLE12:
# systemctl restart salt-minion.service

# systemctl enable salt-minion.service
10. Onboard the Salt Client from the SUSE Manager
a. Enter the webUI tool for SUSE Manager again.
b. Select the Salt tab at the top of the page
c. Your new machine should be listed as pending. Click accept on the machine you want to accept.
11. Deploy the SUSE Manager certificate to the client
a. Run this command on the SUSE Manager:
For a SLE11 client:
# salt ‘<client minion name>’ state.apply certs.SLES11
For a SLE12 client:
# salt ‘<client minion name>’ state.apply certs
b. At the end of the output from the command above you should see something like this:
Succeeded: 2 (changed=2)
Failed:0
———–
Total states run:2

Additional Information

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7022057: How to enable the iPrint /ipp page with the 3.1 iPrint Appliance

This document (7022057) is provided subject to the disclaimer at the end of this document.

Environment

Micro Focus iPrint Appliance 3.1

Situation

Starting with the iPrint Appliance 3.1, the traditional iPrint /ipp page is no longer available. When going to http://<iPrintServerAddress>/ipp, the iPrint Portal Page is loaded.

Question: How can the iPrint Appliance be configured to load the traditional iPrint /ipp page instead of redirecting to the iPrint Portal page?

Resolution

  • Open a terminal session to the iPrint server (putty or otherwise).
    • sh /opt/novell/iprintmobile/bin/ipp_page_enable_disable.sh –enable
      • Answer y to the Apache restart question.
    • Note: To undo this change, execute this command:
      • sh /opt/novell/iprintmobile/bin/ipp_page_enable_disable.sh –disable

Additional Information

See this video to understand the advantages of the iPrint Portal page.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7010584: How to setup SSL certificate for apache

This document (7010584) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server
Novell Open Enterprise Server
Novell GroupWise

Situation

How to SSLize WebAccess on Linux

How to secure WebAccess using SSL
GroupWise WebAccess shows untrusted certificate after pointing to 3rd party certificate using ConsoleOne for WebAccess Agent

Resolution

  1. (conditional) If not yet configured, Enable the SSL module and set the Apache Server Flags to SSL:
  • From a terminal window: edit file /etc/sysconfig/apache2
  • Verify ssl is found in the list of APACHE_MODULES.

    Note: If it is not, please run the following command, which should enable the ssl module and add it to this list:

    sudo a2enmod ssl
  • From this same file, please find APACHE_SERVER_FLAGS=”” and add SSL in between the quotations.
  • Create a virtual host for ssl by copying from the template:

    cp /etc/apache2/vhosts.d/vhost-ssl.template /etc/apache2/vhosts.d/vhost-ssl.conf

  • Configure Apache to use new certificate files:
    • From a terminal window: cd /etc/apache2/vhosts.d/
    • Edit file vhost-ssl.conf
    • Update paths to the appropriate file(s) as needed:
      • SSLCertificateFile <directory to the cert (*.cert)>
      • SSLCertificateKeyFile <path to the private key (*.key)>
      • SSLCertificateChainFile <path to CA Chain file(s)>
      • SSLCACertificateFile <path to bundles>
    • Save and Close.
    • From a Terminal window: type rcapache2 restart and press Enter.

    Additional Information

    How to setup Apache using a single PEM file, if so desired.

    Replace Step 2 above with the following:

    1. See TID 7013103 – How to create a .pem file for SSL Certificate Installations
    2. Point Apache to the New PEM:
      • From a terminal window: type cd /etc/apache2/vhosts.d/ and press Enter.
      • Edit file vhost-ssl.conf
      • Find and replace with the path to the same file:
        • SSLCertificateFile <path to the server.pem>
        • SSLCertificateChainFile <path to the server.pem>
      • Comment out any other Certificate configuration (pem created above includes them):
        • SSLCertificateKeyFile
        • SSLCACertificateFile
      • Save and Close.
      • From a Terminal window: type rcapache2 restart and press Enter.

    Disclaimer

    This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

    Related:

    7017833: SLES12 SP1 ESXi guest with kernel 3.12.57-60.35-default is crashing with an invalid RIP:

    This document (7017833) is provided subject to the disclaimer at the end of this document.

    Environment

    SUSE Linux Enterprise Server 12 Service Pack 1 (SLES 12 SP1)

    Kernel: 3.12.57-60.35-default or older.

    Situation

    SLES12 SP1 guests running on VMware ESXi 6.0 may crash.

    After a core dump has been saved, the ‘dmesg’ log will show entries like (edited for better readability):

    bad: scheduling from the idle thread!
    
    CPU: 0 PID: 0 Comm: swapper/0 Tainted: G W 3.12.57-60.35-default #1
    Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/21/2015
    0000000000000000 ffffffff815202d0 ffff88083fc11f80 ffff88083fc03c60
    ffffffff8108f997 ffffffff81c11460 ffffffff81523a01 ffffffff81c11460
    ffffffff81c01fd8 ffffffff81c01fd8 ffffffff81c01fd8 ffffffff81c11460
    Call Trace:
    [<ffffffff8100475d>] dump_trace+0x7d/0x2d0
    [<ffffffff81004a44>] show_stack_log_lvl+0x94/0x170
    [<ffffffff81005d01>] show_stack+0x21/0x50
    [<ffffffff815202d0>] dump_stack+0x5d/0x78
    [<ffffffff8108f997>] dequeue_task_idle+0x27/0x30
    [<ffffffff81523a01>] thread_return+0x232/0x4a1
    [<ffffffff81521ed9>] schedule_timeout+0x269/0x300
    [<ffffffff81522c7f>] wait_for_completion+0x9f/0x110
    [<ffffffff8107883b>] wait_rcu_gp+0x4b/0x60
    [<ffffffffa017b715>] vmci_event_unsubscribe+0x75/0xb0 [vmw_vmci]
    [<ffffffffa02c55cd>] vmci_transport_destruct+0x1d/0xe0 [vmw_vsock_vmci_transport]
    [<ffffffffa02db7e3>] vsock_sk_destruct+0x13/0x60 [vsock]
    [<ffffffff8142438a>] __sk_free+0x1a/0x170
    [<ffffffffa02c61f8>] vmci_transport_recv_stream_cb+0x1e8/0x2d0 [vmw_vsock_vmci_transport]
    [<ffffffffa017acda>] vmci_datagram_invoke_guest_handler+0xaa/0xd0 [vmw_vmci]
    [<ffffffffa017bb71>] vmci_dispatch_dgs+0xc1/0x200 [vmw_vmci]
    [<ffffffff8105e03c>] tasklet_action+0x11c/0x130
    [<ffffffff8105e61d>] __do_softirq+0xed/0x280
    [<ffffffff8153009c>] call_softirq+0x1c/0x30
    [<ffffffff810046a5>] do_softirq+0x55/0x90
    [<ffffffff8105e905>] irq_exit+0x95/0xa0
    [<ffffffff8153088e>] do_IRQ+0x4e/0xb0
    [<ffffffff8152686d>] common_interrupt+0x6d/0x6d
    [<ffffffff81042762>] native_safe_halt+0x2/0x10
    [<ffffffff8100b2a9>] default_idle+0x19/0xd0
    [<ffffffff810b1181>] cpu_startup_entry+0xe1/0x2b0
    [<ffffffff81d50ea1>] start_kernel+0x43e/0x449
    [<ffffffff81d506a3>] x86_64_start_kernel+0x10c/0x11b
    BUG: scheduling while atomic: swapper/0/0/0x00000100

    followed by the following stack trace:

     BUG: unable to handle kernel NULL pointer dereference at (null)
    
    IP: [< (null)>] (null)
    PGD b6202067 PUD b6066067 PMD 0
    Oops: 0010 [#1] SMP
    Modules linked in: binfmt_misc nfsv3 nfs_acl nfs lockd sunrpc fscache af_packet iscsi_ibft iscsi_boot_sysfs msr vmw_vsock_vmci_transport vsock coretemp cr
    ct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel(X) aesni_intel aes_x86_64 ppdev lrw gf128mul vmw_balloon glue_helper ablk_helper cryptd pcspkr serio_raw vmxn
    et3 parport_pc parport vmw_vmci shpchp battery processor button ac xfs libcrc32c sr_mod cdrom ata_generic sd_mod ata_piix ahci libahci vmwgfx ttm drm libata vmw_pvscsi dm
    _mod sg scsi_mod autofs4
    Supported: Yes, External
    CPU: 4 PID: 28 Comm: ksoftirqd/4 Tainted: G W X 3.12.49-11-default #1
    Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/21/2015
    task: ffff880813f788c0 ti: ffff880813f7c000 task.ti: ffff880813f7c000
    RIP: 0010:[<0000000000000000>] [< (null)>] (null)
    RSP: 0018:ffff880813f7dcf0 EFLAGS: 00010082
    RAX: 0000000000000000 RBX: ffff880813e3c380 RCX: 000000000000a7f0
    RDX: 0000000000000005 RSI: ffff880813e3c380 RDI: ffff88083fd11f40
    RBP: ffff880813f7dd08 R08: 0000000000000004 R09: 0000000000000004
    R10: 0000000000000550 R11: 0000000000000550 R12: ffff88083fd11f40
    R13: 0000000000000000 R14: 0000000000000046 R15: ffff88083fd11f40
    FS: 0000000000000000(0000) GS:ffff88083fd00000(0000) knlGS:0000000000000000
    CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
    CR2: 0000000000000000 CR3: 00000007fb72f000 CR4: 00000000001407e0
    Stack:
    ffffffff81088de3 ffff880813e3c380 ffff880813e3cde4 ffff880813f7dd58
    ffffffff8108aee2 ffff88083fd0c778 ffff88083fd0c7b8 0000d31500000004
    0000000000000001 0000000000000000 0000000000000000 0000000000000003
    Call Trace:
    Inexact backtrace:
    [<ffffffff81088de3>] ? ttwu_do_activate.constprop.88+0x33/0x70
    [<ffffffff8108aee2>] ? try_to_wake_up+0x1f2/0x2e0
    [<ffffffff8107ba67>] ? __wake_up_common+0x57/0x90
    [<ffffffff81085087>] ? complete+0x37/0x50
    [<ffffffff810ff52a>] ? rcu_process_callbacks+0x1ca/0x530
    [<ffffffff8105e1e5>] ? __do_softirq+0xe5/0x230
    [<ffffffff8105e35d>] ? run_ksoftirqd+0x2d/0x50
    [<ffffffff81082cbc>] ? smpboot_thread_fn+0xfc/0x1a0
    [<ffffffff81082bc0>] ? smpboot_unregister_percpu_thread+0x60/0x60
    [<ffffffff8107ad94>] ? kthread+0xb4/0xc0
    [<ffffffff8107ace0>] ? __kthread_parkme+0x70/0x70
    [<ffffffff8152a518>] ? ret_from_fork+0x58/0x90
    [<ffffffff8107ace0>] ? __kthread_parkme+0x70/0x70
    Code: Bad RIP value.
    RIP [< (null)>] (null)
    RSP <ffff880813f7dcf0>
    CR2: 0000000000000000

    Resolution

    A fix for this bug should be included in kernel 3.12.62-60.62.1

    Disclaimer

    This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

    Related: