FLEXCUBE 12.0.3 and SLES 11 SP2/SP3

Hello,
Does anybody knows if there are some issues when running FLEXCUBE 12.0.3.0.0 on Linux SLES 11 SP2/SP3 with kernel 3.0.x
There is nothing mentioned in the pre-requisites about kernel version.
https://docs.oracle.com/cd/E53392_01/PDF/Installation/OraclerFLEXCUBE_FCIS_Pre-requisites.pdf
Thank you.

There should not be any problems with monitoring SLES 10 SP4 or SLES 11 SP2/SP3. If you are getting a "platform not supported" error, it may be that the right management packs have not successfully imported. Can you give more details on when
you get the error, and the management pack versions that you have installed?  And what Update Rollup (UR) for OpsMgr do you have installed?  The latest is UR4, and the Linux/UNIX management packs for UR4 are here: 
http://www.microsoft.com/en-hk/download/details.aspx?id=29696 .  Be sure to download the version for "R2".
Michael Kelley, Lead Program Manager, Open Source Technology Center

Similar Messages

  • Vibe and SLES 11 SP3?

    Is anyone using vibe 3.4 on SLES 11 SP3 and know if it is a supported platform? We are currently running vibe 3.4 on SLES 11 SP2 and are looking to upgrade the O/S. The documentation says the latest support pack, but I'm not sure if vibe 3.4 or sp3 for SLES came out first?
    Thank you for your help.
    Tom

    TSchmauch,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Visit http://support.novell.com and search the knowledgebase and/or check all
    the other self support options and support programs available.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.novell.com)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://forums.novell.com/faq.php
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://forums.novell.com/

  • Unable to monitor SLES 10 SP4,SLES 11 SP3 and SLES 11 SP2 via SCOM 2012 R2

    Hi ,
    I am unable to get SLES 10 SP4, SLES 11 SP3 and  SLES 11 SP2 under SCOM 2012 R2 monitoring. The PAM ,glibc and openssl are at the right versions.
    Per the documentation SCOM MP for unix/Linux provides monitoring of SUSE Linux Enterprise
    Server 9, SUSE Linux Enterprise Server 10 SP1, and SUSE Linux Enterprise Server 11 operating systems. Does this mean it cannot monitor SP2, SP3 and SP4 for the same Operating systems?
    Plat form not supported is the error which I get.
    Thank you much,

    There should not be any problems with monitoring SLES 10 SP4 or SLES 11 SP2/SP3. If you are getting a "platform not supported" error, it may be that the right management packs have not successfully imported. Can you give more details on when
    you get the error, and the management pack versions that you have installed?  And what Update Rollup (UR) for OpsMgr do you have installed?  The latest is UR4, and the Linux/UNIX management packs for UR4 are here: 
    http://www.microsoft.com/en-hk/download/details.aspx?id=29696 .  Be sure to download the version for "R2".
    Michael Kelley, Lead Program Manager, Open Source Technology Center

  • SLES 10 SP3 Crash and reboot

    I'm using SLES 10 SP3 for all my transaction servers and database servers. This Morning (7.40 West Indonesian Time) I found my database server just restarted (from /var/log/messages).
    I'm confused, because kernel crash message in /var/log/messages related to NFS and Samba.
    Here is sample of my syslog message :
    Oct 22 07:07:11 cygnus kernel: CIFS VFS: server not responding
    Oct 22 07:07:11 cygnus kernel: CIFS VFS: No response for cmd 50 mid 47258
    Oct 22 07:07:11 cygnus kernel: CIFS VFS: server not responding
    Oct 22 07:07:11 cygnus kernel: CIFS VFS: server not responding
    Oct 22 07:07:11 cygnus kernel: CIFS VFS: Send error in SETFSUnixInfo = -11
    Oct 22 07:07:11 cygnus kernel: CIFS VFS: No response for cmd 50 mid 47259
    Oct 22 07:07:11 cygnus kernel: CIFS VFS: Send error in SETFSUnixInfo = -11
    Oct 22 07:07:11 cygnus kernel: CIFS VFS: No response for cmd 50 mid 47260
    Oct 22 07:07:11 cygnus kernel: CIFS VFS: Send error in SETFSUnixInfo = -11
    Oct 22 07:07:11 cygnus kernel: CIFS VFS: No response for cmd 50 mid 47257
    Oct 22 07:07:11 cygnus kernel: CIFS VFS: Send error in SETFSUnixInfo = -11
    Oct 22 07:07:12 cygnus kernel: martian source 255.255.255.255 from 10.100.249.2, on dev vlan50
    Oct 22 07:07:12 cygnus kernel: ll header: ff:ff:ff:ff:ff:ff:00:0c:42:ea:50:a2:08:00
    Oct 22 07:07:15 cygnus kernel: CIFS VFS: No response for cmd 162 mid 47256
    Oct 22 07:07:15 cygnus kernel: scheduling while atomic: cmahostd/0xffff8001/5937
    Oct 22 07:07:15 cygnus kernel:
    Oct 22 07:07:15 cygnus kernel: Call Trace: <ffffffff802eea75>{__sched_text_start+125}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884c6dad>{:cifs:wait_for_response+182} <ffffffff8014892e>{autoremove_wake_function+0}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884c76a9>{:cifs:SendReceive2+1237} <ffffffff884cd9b2>{:cifs:CIFS_SessSetup+1405}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b923e>{:cifs:cifs_setup_session+300} <ffffffff8013d754>{del_timer_sync+12}
    Oct 22 07:07:15 cygnus kernel: <ffffffff801db45c>{find_nls+41} <ffffffff884aec3e>{:cifs:smb_init+457}
    Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0} <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458} <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884aeca8>{:cifs:smb_init+563} <ffffffff8014892e>{autoremove_wake_function+0}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 } <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0} <ffffffff884aeca8>{:cifs:smb_init+563}
    Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0} <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458} <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884aeca8>{:cifs:smb_init+563} <ffffffff8014892e>{autoremove_wake_function+0}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 } <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0} <ffffffff884aeca8>{:cifs:smb_init+563}
    Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0} <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458} <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884aeca8>{:cifs:smb_init+563} <ffffffff8014892e>{autoremove_wake_function+0}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 } <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0} <ffffffff884aeca8>{:cifs:smb_init+563}
    Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0} <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458} <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884aeca8>{:cifs:smb_init+563} <ffffffff8014892e>{autoremove_wake_function+0}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 } <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0} <ffffffff884aeca8>{:cifs:smb_init+563}
    Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0} <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458} <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884aeca8>{:cifs:smb_init+563} <ffffffff8014892e>{autoremove_wake_function+0}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 } <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0} <ffffffff884aeca8>{:cifs:smb_init+563}
    Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0} <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458} <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884aeca8>{:cifs:smb_init+563} <ffffffff8014892e>{autoremove_wake_function+0}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 } <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0} <ffffffff884aeca8>{:cifs:smb_init+563}
    Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0} <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}<1 >Unable to handle kernel paging request at 00000000bd022aa0 RIP:
    Oct 22 07:07:15 cygnus kernel: <ffffffff8012cb5b>{try_to_wake_up+53}
    Oct 22 07:07:15 cygnus kernel: PGD 0
    Oct 22 07:07:15 cygnus kernel: <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+460} <0>Oops: 0000 [1] SMP
    Oct 22 07:07:15 cygnus kernel:
    Oct 22 07:07:15 cygnus kernel: <0>last sysfs file: /devices/pci0000:00/0000:00:1c.2/0000:04:00.1/irq
    Oct 22 07:07:15 cygnus kernel: CPU 2
    Oct 22 07:07:15 cygnus kernel: <ffffffff884aeca8>{:cifs:smb_init+563}Modules linked in: ipt_MASQUERADE nls_cp850 smbfs<ffffffff8014892e>{autoremove_wake_function+0 } ip6t_REJECT ipt_REJECT ipt_LOG xt_limit xt_state ip6table_mangle
    Oct 22 07:07:15 cygnus kernel: iptable_mangle ip6table_filter ip6_tables binfmt_misc st sr_mod ide_disk ide_cd cdrom joydev xt_tcpudp<ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnix Info+96} ipt_multiport iptable_nat ip_nat ip_conntrack nfnetlink iptable_filter ip_tables x_tables fuse ntfs<ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+45 8} usb_storage ide_core af_packet nls_utf8 cifs
    Oct 22 07:07:15 cygnus kernel: softdog mptctl mptbase sg vboxpci vboxnetadp vboxnetflt hpilo vboxdrv bnx2i scsi_transport_iscsi cnic 8021q<ffffffff884baa90>{:cifs:reset_cifs_unix_caps +460} bonding ipv6 dock button battery ac apparmor loop usbhid uhci_hcd ehci_hcd usbcore bnx2 ext3 jbd scsi_dh_alua scsi_dh_hp_sw scsi_dh_rdac scsi_dh_emc dm_round_robin dm_multipath scsi_dh dm_snapshot edd dm_mod fan thermal processor cciss sd_mod scsi_mod
    Oct 22 07:07:15 cygnus kernel: Pid: 9619, comm: cifsd Tainted: GF U 2.6.16.60-0.54.5-smp #1
    Oct 22 07:07:15 cygnus kernel: RIP: 0010:[<ffffffff8012cb5b>] <ffffffff8012cb5b>{try_to_wake_up+53}
    Oct 22 07:07:15 cygnus kernel: RSP: 0018:ffff810536e7ddd8 EFLAGS: 00010096
    Oct 22 07:07:15 cygnus kernel: RAX: 0000000027986310 RBX: ffffffff8042f700 RCX: 0000000000000092
    Oct 22 07:07:15 cygnus kernel: RDX: 0000000000000000 RSI: 000000000000000f RDI: ffff8108ab48e7d0
    Oct 22 07:07:15 cygnus kernel: RBP: ffff810536e7de58 R08: 0000000000001ae0 R09: 000000000000fa53
    Oct 22 07:07:15 cygnus kernel: R10: 0000000000007d29 R11: ffff81080ac8fdc0 R12: ffff8108ab48e7d0
    Oct 22 07:07:15 cygnus kernel: R13: ffffffff8042f700 R14: 000000000000000f R15: ffff8106759f6000
    Oct 22 07:07:15 cygnus kernel: FS: 0000000000000000(0000) GS:ffff8108ff57eec0(0000) knlGS:0000000000000000
    Oct 22 07:07:15 cygnus kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
    Oct 22 07:07:15 cygnus kernel: CR2: 00000000bd022aa0 CR3: 0000000077d95000 CR4: 00000000000006e0
    Oct 22 07:07:15 cygnus kernel: Process cifsd (pid: 9619, threadinfo ffff810536e7c000, task ffff810138cf5080)
    Oct 22 07:07:15 cygnus kernel: Stack: 00000000000000d0 000000004959e140 0000000000000061 ffffffff80164839
    Oct 22 07:07:15 cygnus kernel: 0000000000000002 000000028012c2eb ffff8106759f613e 0000000000000000
    Oct 22 07:07:15 cygnus kernel: 0000000000000004 0000000000000296
    Oct 22 07:07:15 cygnus kernel: Call Trace: <ffffffff80164839>{mempool_alloc+49}<ffffffff884ae ca8>{:cifs:smb_init+563}
    Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0}<fff fffff884bdaa4>{:cifs:cifs_demultiplex_thread+2137}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
    Oct 22 07:07:15 cygnus kernel: <ffffffff884bd24b>{:cifs:cifs_demultiplex_thread+0 }<ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}
    Oct 22 07:07:15 cygnus kernel: <ffffffff80148525>{keventd_create_kthread+0} <ffffffff801487ed>{kthread+236}<ffffffff884baa90>{ :cifs:reset_cifs_unix_caps+460}
    Oct 22 07:07:15 cygnus kernel: <ffffffff8010bea6>{child_rip+8} <ffffffff80148525>{keventd_create_kthread+0}
    Oct 22 07:07:15 cygnus kernel:
    Oct 22 07:07:15 cygnus kernel: <ffffffff80148701>{kthread+0} <ffffffff8010be9e>{child_rip+0}<ffffffff884aeca8>{ :cifs:smb_init+563}
    Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0}
    Oct 22 07:07:15 cygnus kernel: Code: 48 8b 04 c5 20
    Oct 22 07:07:15 cygnus kernel: 12 3f 80 4c 03 68 08 4c 89 ef e8 54 43 1c 00
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96}< 1>RIP
    Oct 22 07:07:15 cygnus kernel: <ffffffff8012cb5b>{try_to_wake_up+53} RSP <ffff810536e7ddd8>
    Oct 22 07:07:15 cygnus kernel: CR2: 00000000bd022aa0
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0} <ffffffff884aeca8>{:cifs:smb_init+563}
    Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0} <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458} <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884aeca8>{:cifs:smb_init+563} <ffffffff8014892e>{autoremove_wake_function+0}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 } <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0} <ffffffff884aeca8>{:cifs:smb_init+563}
    Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0} <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458} <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884aeca8>{:cifs:smb_init+563} <ffffffff8014892e>{autoremove_wake_function+0}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 } <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0} <ffffffff884aeca8>{:cifs:smb_init+563}
    Oct 22 07:07:15 cygnus kernel: <ffffffff8014892e>{autoremove_wake_function+0} <ffffffff884b02f8>{:cifs:CIFSSMBSetFSUnixInfo+96 }
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b0642>{:cifs:CIFSSMBQFSUnixInfo+458} <ffffffff884baa90>{:cifs:reset_cifs_unix_caps+46 0}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884aeca8>{:cifs:smb_init+563} <ffffffff8014892e>{autoremove_wake_function+0}
    Oct 22 07:07:15 cygnus kernel: <ffffffff884b00eb>{:cifs:CIFSSMBQFSPosixInfo+96} <ffffffff884ae48a>{:cifs:cifs_statfs+155}
    Oct 22 07:07:15 cygnus kernel: <ffffffff80186044>{vfs_statfs+108} <ffffffff801afc98>{compat_sys_statfs+63}
    Oct 22 07:07:15 cygnus kernel: <ffffffff801fbc97>{_atomic_dec_and_lock+51} <ffffffff8019d4cc>{dput+64}
    Oct 22 07:07:15 cygnus kernel: <ffffffff801865ec>{sys_close+143} <ffffffff80122d2c>{sysenter_do_call+27}
    Oct 22 07:07:15 cygnus kernel: <1>Unable to handle kernel paging request at 00000000bd022aa0 RIP:
    Oct 22 07:07:15 cygnus kernel: <ffffffff802ef4c9>{__sched_text_start+2769}
    Oct 22 07:07:15 cygnus kernel: PGD 77268f067 PUD 0
    Oct 22 07:07:15 cygnus kernel: Oops: 0000 [2] SMP
    Oct 22 07:07:15 cygnus kernel: last sysfs file: /devices/pci0000:00/0000:00:1c.2/0000:04:00.1/irq
    Oct 22 07:07:15 cygnus kernel: CPU 6
    Oct 22 07:07:15 cygnus kernel: Modules linked in: ipt_MASQUERADE nls_cp850 smbfs ip6t_REJECT ipt_REJECT ipt_LOG xt_limit xt_state ip6table_mangle iptable_mangle ip6table_filter ip6_tables binfmt_misc st sr_mod ide_disk ide_cd cdrom joydev xt_tcpudp ipt_multiport iptable_nat ip_nat ip_conntrack nfnetlink iptable_filter ip_tables x_tables fuse ntfs usb_storage ide_core af_packet nls_utf8 cifs softdog mptctl mptbase sg vboxpci vboxnetadp vboxnetflt hpilo vboxdrv bnx2i scsi_transport_iscsi cnic 8021q bonding ipv6 dock button battery ac apparmor loop usbhid uhci_hcd ehci_hcd usbcore bnx2 ext3 jbd scsi_dh_alua scsi_dh_hp_sw scsi_dh_rdac scsi_dh_emc dm_round_robin dm_multipath scsi_dh dm_snapshot edd dm_mod fan thermal processor cciss sd_mod scsi_mod
    Oct 22 07:07:15 cygnus kernel: Pid: 5937, comm: cmahostd Tainted: GF U 2.6.16.60-0.54.5-smp #1
    Oct 22 07:07:15 cygnus kernel: RIP: 0010:[<ffffffff802ef4c9>] <ffffffff802ef4c9>{__sched_text_start+2769}
    Oct 22 07:07:15 cygnus kernel: RSP: 0018:ffff8107726ac4d8 EFLAGS: 00210083
    Oct 22 07:07:15 cygnus kernel: RAX: ffff8107726ac000 RBX: ffff8108ab48e7d0 RCX: ffff8108ab48e7d0
    Oct 22 07:07:15 cygnus kernel: RDX: 0000000027986310 RSI: 0000000000000000 RDI: ffff81000107d800
    Oct 22 07:07:15 cygnus kernel: RBP: ffff8107726ac598 R08: ffff8108aebc8000 R09: 0000000000000001
    Oct 22 07:07:15 cygnus kernel: R10: 0000000000200286 R11: 0000000000000000 R12: ffff8108ab48e7d0
    Oct 22 07:07:15 cygnus kernel: R13: 00000000000009c4 R14: ffff8108ab48e808 R15: 0000000000000000
    Oct 22 07:07:15 cygnus kernel: FS: 0000000000000000(0000) GS:ffff8108ff62dbc0(0063) knlGS:00000000f7d838c0
    Oct 22 07:07:15 cygnus kernel: CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b
    Oct 22 07:07:15 cygnus kernel: CR2: 00000000bd022aa0 CR3: 000000077268d000 CR4: 00000000000006e0
    Oct 22 07:40:15 cygnus syslog-ng[5044]: syslog-ng version 1.6.8 starting
    Oct 22 07:40:15 cygnus auditd[5194]: Init complete, auditd 1.2.9 listening for events
    Oct 22 07:40:15 cygnus bnx2i-daemon[5264]: bnx2id daemon started.
    Oct 22 07:40:15 cygnus rcpowersaved: CPU frequency scaling is not supported by your processor.
    Oct 22 07:40:15 cygnus rcpowersaved: enter 'CPUFREQ_ENABLED=no' in /etc/powersave/cpufreq to avoid this warning.
    Oct 22 07:40:15 cygnus rcpowersaved: Cannot load cpufreq governors - No cpufreq driver available
    Oct 22 07:40:16 cygnus sshd[5389]: Server listening on 0.0.0.0 port 22.
    Oct 22 07:40:16 cygnus rcpowersaved: s2ram does not know your machine. See 's2ram -i' for details. (127)
    Oct 22 07:40:16 cygnus rcpowersaved: Use SUSPEND2RAM_FORCE=yes to override this detection.
    Oct 22 07:40:16 cygnus [powersave-set_disk_settings][5454]: WARNING: could not retrieve list of disks from HAL:
    Oct 22 07:40:16 cygnus vcagentd: Type: 4 - Event ID: 1073741884
    Oct 22 07:40:18 cygnus modprobe: FATAL: Error running install command for binfmt_misc
    Oct 22 07:40:18 cygnus ntpd[5527]: ntpd [email protected] Sat Sep 5 11:15:41 UTC 2009 (1)
    Oct 22 07:40:18 cygnus ntpd[5539]: precision = 1.000 usec
    Oct 22 07:40:18 cygnus ntpd[5539]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
    Oct 22 07:40:18 cygnus ntpd[5539]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
    Oct 22 07:40:18 cygnus ntpd[5539]: Listening on interface #1 lo, 127.0.0.1#123 Enabled
    Oct 22 07:40:18 cygnus ntpd[5539]: Listening on interface #2 lo, 127.0.0.2#123 Enabled
    Oct 22 07:40:18 cygnus ntpd[5539]: Listening on interface #3 bond0, 192.168.5.73#123 Disabled
    Oct 22 07:40:18 cygnus ntpd[5539]: Listening on interface #4 vlan40, 192.168.3.2#123 Disabled
    Oct 22 07:40:18 cygnus ntpd[5539]: Listening on interface #5 vlan50, 172.0.0.5#123 Disabled
    Oct 22 07:40:18 cygnus ntpd[5539]: kernel time sync status 0040
    Oct 22 07:40:18 cygnus ntpd[5539]: frequency initialized 12.181 PPM from /var/lib/ntp/drift/ntp.drift
    Oct 22 07:40:18 cygnus /usr/sbin/cron[5564]: (CRON) STARTUP (V5.0)
    Oct 22 07:40:20 cygnus kernel: klogd 1.4.1, log source = /proc/kmsg started.
    Oct 22 07:40:20 cygnus syslog-ng[5044]: Changing permissions on special file /dev/xconsole
    Oct 22 07:40:20 cygnus syslog-ng[5044]: Changing permissions on special file /dev/tty10
    Oct 22 07:40:20 cygnus kernel: JBD: barrier-based sync failed on dm-3 - disabling barriers
    Oct 22 07:40:20 cygnus kernel: AppArmor: AppArmor initialized
    Oct 22 07:40:20 cygnus kernel: audit(1413938407.210:2): info="AppArmor initialized" pid=3465
    Oct 22 07:40:20 cygnus kernel: IA-32 Microcode Update Driver: v1.14 <[email protected]>
    Oct 22 07:40:20 cygnus kernel: ACPI: Power Button (FF) [PWRF]
    Oct 22 07:40:20 cygnus kernel: IA-32 Microcode Update Driver v1.14 unregistered
    Oct 22 07:40:20 cygnus kernel: No dock devices found.
    Oct 22 07:40:20 cygnus kernel: floppy0: no floppy controllers found
    Oct 22 07:40:20 cygnus kernel: Ethernet Channel Bonding Driver: v3.2.5 (March 21, 2008)
    Oct 22 07:40:20 cygnus kernel: bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link failures! see bonding.txt for details.
    Oct 22 07:40:20 cygnus kernel: bonding: bond0: setting mode to active-backup (1).
    Oct 22 07:40:20 cygnus kernel: bonding: bond0: Setting MII monitoring interval to 100.
    Oct 22 07:40:20 cygnus kernel: bnx2: eth0: using MSI
    Oct 22 07:40:20 cygnus kernel: bonding: bond0: enslaving eth0 as a backup interface with a down link.
    Oct 22 07:40:20 cygnus kernel: bnx2: eth2: using MSI
    Oct 22 07:40:20 cygnus kernel: bonding: bond0: enslaving eth2 as a backup interface with a down link.
    Oct 22 07:40:20 cygnus kernel: bonding: bond1 is being created...
    Oct 22 07:40:20 cygnus kernel: bonding: bond1: setting mode to balance-tlb (5).
    Oct 22 07:40:20 cygnus kernel: bonding: bond1: Setting MII monitoring interval to 100.
    Oct 22 07:40:20 cygnus kernel: bnx2: eth1: using MSI
    Oct 22 07:40:20 cygnus kernel: bonding: bond1: enslaving eth1 as an active interface with a down link.
    Oct 22 07:40:20 cygnus kernel: bnx2: eth3: using MSI
    Oct 22 07:40:20 cygnus kernel: bonding: bond1: enslaving eth3 as an active interface with a down link.
    Oct 22 07:40:20 cygnus kernel: 802.1Q VLAN Support v1.8 Ben Greear <[email protected]>
    Oct 22 07:40:20 cygnus kernel: All bugs added by David S. Miller <[email protected]>
    Oct 22 07:40:20 cygnus kernel: vlan40: add 01:00:5e:00:00:01 mcast address to master interface
    Oct 22 07:40:20 cygnus kernel: vlan50: add 01:00:5e:00:00:01 mcast address to master interface
    Oct 22 07:40:20 cygnus kernel: cnic: module not supported by Novell, setting U taint flag.
    Oct 22 07:40:20 cygnus kernel: Broadcom NetXtreme II CNIC Driver cnic v1.9.13b (Dec 16, 2009)
    Oct 22 07:40:20 cygnus kernel: cnic: Added CNIC device: eth0
    Oct 22 07:40:20 cygnus kernel: cnic: Added CNIC device: eth1
    Oct 22 07:40:20 cygnus kernel: cnic: Added CNIC device: eth2
    Oct 22 07:40:20 cygnus kernel: cnic: Added CNIC device: eth3
    Oct 22 07:40:20 cygnus kernel: Loading iSCSI transport class v2.0-724.
    Oct 22 07:40:20 cygnus kernel: bnx2i: module not supported by Novell, setting U taint flag.
    Oct 22 07:40:20 cygnus kernel: bnx2i: no version for "cnic_register_driver" found: kernel tainted.
    Oct 22 07:40:20 cygnus kernel: Broadcom NetXtreme II iSCSI Driver bnx2i v1.8.12g (Apr 12, 2010)
    Oct 22 07:40:20 cygnus kernel: iscsi: registered transport (bcm570x-040001)
    Oct 22 07:40:20 cygnus kernel: bnx2i: netif=eth3, iscsi=bcm570x-040001
    Oct 22 07:40:20 cygnus kernel: bnx2i [04:00.01]: ISCSI_INIT passed
    Oct 22 07:40:20 cygnus kernel: iscsi: registered transport (bcm570x-040000)
    Oct 22 07:40:20 cygnus kernel: bnx2i: netif=eth2, iscsi=bcm570x-040000
    Oct 22 07:40:20 cygnus kernel: bnx2i [04:00.00]: ISCSI_INIT passed
    Oct 22 07:40:20 cygnus kernel: iscsi: registered transport (bcm570x-030001)
    Oct 22 07:40:20 cygnus kernel: bnx2i: netif=eth1, iscsi=bcm570x-030001
    Oct 22 07:40:20 cygnus kernel: bnx2i [03:00.01]: ISCSI_INIT passed
    Oct 22 07:40:20 cygnus kernel: audit(1413938415.718:3): audit_pid=5194 old=0 by auid=4294967295
    Oct 22 07:40:20 cygnus kernel: iscsi: registered transport (bcm570x-030000)
    Oct 22 07:40:20 cygnus kernel: bnx2i: netif=eth0, iscsi=bcm570x-030000
    Oct 22 07:40:20 cygnus kernel: bnx2i [03:00.00]: ISCSI_INIT passed
    Oct 22 07:40:20 cygnus kernel: vboxdrv: module not supported by Novell, setting U taint flag.
    Oct 22 07:40:20 cygnus kernel: vboxdrv: Found 8 processor cores.
    Oct 22 07:40:20 cygnus kernel: VBoxDrv: dbg - g_abExecMemory=ffffffff88256380
    Oct 22 07:40:20 cygnus kernel: vboxdrv: fAsync=0 offMin=0x8f6 offMax=0x10ce8
    Oct 22 07:40:20 cygnus kernel: vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
    Oct 22 07:40:20 cygnus kernel: vboxdrv: Successfully loaded version 4.1.8 (interface 0x00190000).
    Oct 22 07:40:20 cygnus kernel: hpilo: module not supported by Novell, setting U taint flag.
    Oct 22 07:40:20 cygnus kernel: ACPI: PCI Interrupt 0000:02:00.2[B] -> GSI 17 (level, low) -> IRQ 138
    Oct 22 07:40:20 cygnus kernel: PCI: Setting latency timer of device 0000:02:00.2 to 64
    Oct 22 07:40:20 cygnus kernel: vboxnetflt: module not supported by Novell, setting U taint flag.
    Oct 22 07:40:20 cygnus kernel: vboxnetadp: module not supported by Novell, setting U taint flag.
    Oct 22 07:40:20 cygnus kernel: vboxpci: module not supported by Novell, setting U taint flag.
    Oct 22 07:40:20 cygnus kernel: vboxpci: pci-stub module not available, cannot detach PCI devices
    Oct 22 07:40:20 cygnus kernel: vboxpci: IOMMU not found (not compiled)
    Oct 22 07:40:20 cygnus kernel: bnx2: eth3 NIC Copper Link is Up, 1000 Mbps full duplex
    Oct 22 07:40:20 cygnus kernel: bonding: bond1: link status definitely up for interface eth3.
    Oct 22 07:40:20 cygnus kernel: bonding: bond1: making interface eth3 the new active one.
    Oct 22 07:40:20 cygnus kernel: bonding: bond1: first active interface up!
    Oct 22 07:40:27 cygnus kernel: bnx2: eth0 NIC Copper Link is Up, 100 Mbps full duplex
    Oct 22 07:40:27 cygnus kernel: bonding: bond0: link status definitely up for interface eth0.
    Oct 22 07:40:27 cygnus kernel: bonding: bond0: making interface eth0 the new active one.
    Oct 22 07:40:27 cygnus kernel: bonding: bond0: first active interface up!
    Oct 22 07:40:30 cygnus kernel: bnx2: eth1 NIC Copper Link is Up, 100 Mbps full duplex
    Oct 22 07:40:30 cygnus kernel: bonding: bond1: link status definitely up for interface eth1.
    Oct 22 07:40:32 cygnus kernel: bnx2: eth2 NIC Copper Link is Up, 100 Mbps full duplex
    Oct 22 07:40:32 cygnus kernel: bonding: bond0: link status definitely up for interface eth2.
    Oct 22 07:40:32 cygnus kernel: bnx2: eth2 NIC Copper Link is Down
    Oct 22 07:40:32 cygnus kernel: bonding: bond0: link status definitely down for interface eth2, disabling it
    Oct 22 07:40:34 cygnus kernel: bnx2: eth2 NIC Copper Link is Up, 100 Mbps full duplex
    Oct 22 07:40:34 cygnus kernel: bonding: bond0: link status definitely up for interface eth2.
    Oct 22 07:40:35 cygnus kernel: bnx2: eth2 NIC Copper Link is Down
    Oct 22 07:40:35 cygnus kernel: bonding: bond0: link status definitely down for interface eth2, disabling it
    Oct 22 07:40:35 cygnus hpasmlited[5722]: hpDeferSPDThread: Starting thread to collect DIMM SPD Data.
    Oct 22 07:40:36 cygnus kernel: Fusion MPT base driver 3.04.07_suse
    Oct 22 07:40:36 cygnus kernel: Copyright (c) 1999-2008 LSI Corporation
    Oct 22 07:40:36 cygnus kernel: Fusion MPT misc device (ioctl) driver 3.04.07_suse
    Oct 22 07:40:36 cygnus kernel: mptctl: Registered with Fusion MPT base driver
    Oct 22 07:40:36 cygnus kernel: mptctl: /dev/mptctl @ (major,minor=10,220)
    Oct 22 07:40:36 cygnus kernel: bnx2: eth2 NIC Copper Link is Up, 100 Mbps full duplex
    Oct 22 07:40:36 cygnus kernel: bonding: bond0: link status definitely up for interface eth2.
    Oct 22 07:40:37 cygnus kernel: bnx2: eth2 NIC Copper Link is Down
    Oct 22 07:40:37 cygnus kernel: bonding: bond0: link status definitely down for interface eth2, disabling it
    Oct 22 07:40:39 cygnus kernel: bnx2: eth2 NIC Copper Link is Up, 100 Mbps full duplex
    Oct 22 07:40:39 cygnus kernel: bonding: bond0: link status definitely up for interface eth2.
    Oct 22 07:40:39 cygnus kernel: ipmi message handler version 38.2
    Oct 22 07:40:39 cygnus kernel: IPMI Watchdog: driver initialized
    Oct 22 07:40:39 cygnus hpasrd[7367]: Starting with poll 1 and timeout 600.
    Oct 22 07:40:39 cygnus hpasrd[7367]: Setting the watchdog timer.
    Oct 22 07:40:39 cygnus kernel: Software Watchdog Timer: 0.07 initialized. soft_noboot=0 soft_margin=60 sec (nowayout= 0)
    Oct 22 07:40:39 cygnus hpasrd[7367]: Preferred watchdog driver not found.
    Oct 22 07:40:39 cygnus hpasrd[7367]: Found iLO memory at 0xf1ff0000.
    Oct 22 07:40:39 cygnus hpasrd[7367]: Successfully mapped device.
    Oct 22 07:40:39 cygnus kernel: bnx2: eth2 NIC Copper Link is Down
    Oct 22 07:40:39 cygnus kernel: bonding: bond0: link status definitely down for interface eth2, disabling it
    Oct 22 07:40:41 cygnus kernel: bnx2: eth2 NIC Copper Link is Up, 100 Mbps full duplex
    Oct 22 07:40:41 cygnus kernel: bonding: bond0: link status definitely up for interface eth2.
    Oct 22 07:40:42 cygnus kernel: bnx2: eth2 NIC Copper Link is Down
    Oct 22 07:40:42 cygnus kernel: bonding: bond0: link status definitely down for interface eth2, disabling it
    Oct 22 07:40:43 cygnus kernel: bnx2: eth2 NIC Copper Link is Up, 10 Mbps full duplex
    Oct 22 07:40:43 cygnus kernel: bonding: bond0: link status definitely up for interface eth2.
    Please help me to find root cause off this problem. Is there another log that i should be checking?
    Regards

    On 22/10/2014 04:56, syahrianto wrote:
    > I'm using SLES 10 SP3 for all my transaction servers and database
    > servers.
    These forums are for Novell's Open Enterprise Server (OES) product which
    is an add-on for SUSE Linux Enterprise Server.
    If you are using "regular" SLES then you should repost in one of SUSE's
    Forums for SLES @
    https://forums.suse.com/forumdisplay...erprise-Server
    HTH.
    Simon
    Novell Knowledge Partner
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below. Thanks.

  • SLES 11 SP3 and HP B120i/B320i RAID Controller

    I see this document regarding SLES 11 SP3 installation and these controllers: http://www.novell.com/support/kb/doc.php?id=7014431. My question is, I downloaded the drivers, first using the hpvsa.rpm but I have no idea how to install it. The HP document says at the Installation screen, you pick the F6 for drivers and select the device the file is on. However, you can't run an rpm that way. There was also a driver file with the .dd extension but that doesn't work either.
    I was just curious what I may be doing wrong to get the controller recognized by the SLES 11 install so I can actually install it to the RAID array. I'm having a brain cramp.
    Thank you.

    Originally Posted by alcockb
    I see this document regarding SLES 11 SP3 installation and these controllers: http://www.novell.com/support/kb/doc.php?id=7014431. My question is, I downloaded the drivers, first using the hpvsa.rpm but I have no idea how to install it. The HP document says at the Installation screen, you pick the F6 for drivers and select the device the file is on. However, you can't run an rpm that way. There was also a driver file with the .dd extension but that doesn't work either.
    I was just curious what I may be doing wrong to get the controller recognized by the SLES 11 install so I can actually install it to the RAID array. I'm having a brain cramp.
    Thank you.
    Hi,
    switch off "Soft Raid Mode" and switch on "AHCI Mode" for the Controller. If you can install the machine without HP driver use a MD Raid on maschine

  • No patches for SLES 11 SP3?

    I'm working on deploying ZCM 11.2 for all of my linux patching needs, but have run into a stopper. I download my subscriptions and the ZCM server sees that there are patched avalable/needed for SLES 11 SP3, but when I try to cache them, the downloads fail. This is consistent for all SLES 11 SP3 patches - SP2 patches download without any problems. The error I see in the loader-messages.log for an example download (Novell SUSE 2014:8820 autofs recommended update for SLE 11 SP3 x86_64) is as follows...
    DEBUG] [2/3/14 4:47:28 PM] [] [Loader.MandatoryBaselineManager] [26] [] [Exception during Caching:] [] []
    [DEBUG] [2/3/14 4:47:28 PM] [] [Loader.MandatoryBaselineManager] [26] [] [com.lumension.scr.exception.SCRException: Couldnt find rpm files for advisory SUSE-2014:8820
    at com.lumension.scr.pojo.SCPackage.getRPMPackage(SCP ackage.java:314)
    at com.lumension.scr.pojo.SCPackage.getAllPackageFile s(SCPackage.java:418)
    at com.lumension.scr.pojo.SCPackage.download(SCPackag e.java:363)
    at com.patchlink.sapphire.download.SubscriptionDownlo adActionHandler.processAction(SubscriptionDownload ActionHandler.java:464)
    at com.novell.zenworks.loader.modules.queue.runner.Qu eueThreadWorker.processAction(QueueThreadWorker.ja va:212)
    at com.novell.zenworks.loader.modules.queue.runner.Qu eueThreadWorker.run(QueueThreadWorker.java:143)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run Task(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)
    [DEBUG] [2/3/14 4:47:28 PM] [] [Loader.MandatoryBaselineManager] [26] [] [Failed to create patch cache bundle: Novell SUSE 2014:8820 autofs recommended update for SLE 11 SP3 x86_64] [] []
    I can see this particular patch listed on Lumension's site at http://leic.lumension.com/patches/20...013849%7D.html and on Novell's site at http://download.novell.com/Download?...d=6FEGSAdkSPw~
    Why can't my Zen server successfully download this or any other SLES 11 SP3 update?
    Thanks!

    Hi
    I'm getting a similar thing. Windows patches/baselines are working OK. I can update the SLES servers through YAST/online update, but would like to get the patch management for Linux working as well.
    The DAU on the Linux servers is reporting that patches are required and all SLES 11SP3 patches are listed in the "Patch management/patches" screen. But when I go to update the cache or assign a patch to my baseline, a message pops up in the Patch Management/Status Tab as Queued, and then Failed with the error Failed to download one or more packages. I have about 30 Gig free on the server. I have a subscription set up from NCC for SLES11SP3 which returns "Success".
    In the loader-messages.log I have the following snippet.
    [DEBUG] [6/20/14 10:08:57 AM] [] [PatchManagement] [11022] [] [Downloading file from http://novell.cdn.lumension.com/nove...B22C85842.plp] [] []
    [DEBUG] [6/20/14 10:08:57 AM] [] [PatchManagement] [11022] [] [File exists] [] []
    [DEBUG] [6/20/14 10:08:57 AM] [] [PatchManagement] [11022] [] [download success true] [] []
    [INFO] [6/20/14 10:08:57 AM] [] [PatchManagement] [11022] [vendor SUSE release SLES version 11Architecture x86_64] [vendor SUSE release SLES version 11Architecture x86_64] [] []
    [DEBUG] [6/20/14 10:08:57 AM] [] [PatchManagement] [11022] [] [Local File is /opt/novell/zenworks/zpm/repository/SUSE/null/python-pywbem-0.7-6.22.1.x86_64.rpm] [] []
    [DEBUG] [6/20/14 10:08:57 AM] [] [PatchManagement] [11022] [] [Checksum is null] [] []
    [DEBUG] [6/20/14 10:08:57 AM] [] [PatchManagement] [11022] [] [Checksum type is rpm] [] []
    [DEBUG] [6/20/14 10:08:57 AM] [] [Loader.MandatoryBaselineManager] [11022] [] [Exception during Caching:] [] []
    [DEBUG] [6/20/14 10:08:57 AM] [] [Loader.MandatoryBaselineManager] [11022] [] [java.lang.NullPointerException
    at com.lumension.scr.util.Utils.fromHexString(Utils.j ava:934)
    at com.lumension.scr.nca.repl.PrimaryRPMFile.<init>(P rimaryRPMFile.java:75)
    at com.lumension.scr.pojo.SCPackage.getAllPackageFile s(SCPackage.java:598)
    at com.lumension.scr.pojo.SCPackage.download(SCPackag e.java:363)
    at com.patchlink.sapphire.download.SubscriptionDownlo adActionHandler.processAction(SubscriptionDownload ActionHandler.java:464)
    at com.novell.zenworks.loader.modules.queue.runner.Qu eueThreadWorker.processAction(QueueThreadWorker.ja va:212)
    at com.novell.zenworks.loader.modules.queue.runner.Qu eueThreadWorker.run(QueueThreadWorker.java:143)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run Task(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)
    [DEBUG] [6/20/14 10:08:57 AM] [] [Loader.MandatoryBaselineManager] [11022] [] [Failed to create patch cache bundle: Novell SUSE 2014:9343 python-pywbem recommended update for SLE 11 SP3 x86_64] [] []
    The "Exception during Caching" indicates that maybe I've not set something at my end.
    Any thoughts appreciated.
    Cheers

  • Any news about SLES 11 SP3 support ?

    Hi everyone,
    Does someone know when Groupwise mobility will be support on SLES 11 SP3 ?
    SLES 11 SP3 was released 1 July 2013 which mean SLES 11 SP2 will require a long term service pack support contract at the beginning of 2014.
    Novell is pushing customers to upgrade rapidly to be support but this time we are waiting official word on SLES 11 SP3 support to upgrade.
    Thank You
    Martin Dallaire

    It looks like GW Mobility 2.0 is now available and the docs indicate SLES 11 SP2 and SP3 are supported.
    Al
    On 12/5/2013 at 8:36 AM, mdallair mels<[email protected]> wrote:
    Hi everyone,
    Does someone know when Groupwise mobility will be support on SLES 11 SP3
    SLES 11 SP3 was released 1 July 2013 which mean SLES 11 SP2 will require
    a long term service pack support contract at the beginning of 2014.
    Novell is pushing customers to upgrade rapidly to be support but this
    time we are waiting official word on SLES 11 SP3 support to upgrade.
    Thank You
    Martin Dallaire
    mdallair_mels
    mdallair_mels's Profile: https://forums.novell.com/member.php?userid=117659
    View this thread: https://forums.novell.com/showthread.php?t=473191

  • SLES 10 (SP3) on Hyper-V 2012 R2

    I do realize that is unsupported (only SP4 supposedly is)
    But I have SLES 10 (SP3) image that got converted from vSphere
    Once I can boot the IDE disk (by editing menu.lst to /hda1 & uninstall Vmware Tools, I would need to get network connectivity, so logical step would be to use Intergration Services 2.1 (one that supports SLES 10 SP3)
    But it is a no go. On make install during load of vmbus the whole VM just hangs & dies
    http://imageshack.com/a/img545/7339/16u1.jpg
    The initrd never even gets created as it dies & reset is the only option
    If I rem-out vmbus start in Makefile then I can get new kernel installed, but restulting kernel will panic on VM boot
    Anybody has any clever idea how to get it working (if at all possible)
    Seb

    Getting this to work is going to be difficult.  The older LIS 2.1 does not work with Hyper-V 2012 and 2012 R2 due to changes in Hyper-V itself.  But you could probably get SLES 10 SP3 with LIS 2.1 working if you went back to the older Hyper-V
    2008 R2.
    You are correct that the LIS 3.4 package is created only for the Red Hat (and CentOS) distros.  It will not work with SLES releases.
    We've gotten occasional requests to get SLES 10 working on Hyper-V 2012 and 2012 R2, and we're in conversations with SUSE about creating a combination that works.  But we don't have anything to announce about a timeline.  When/if we get something
    working, it will most likely be SLES 10 SP4, since that's the most up-to-date version from the SLES 10 series.
    Michael Kelley, Lead Program Manager, Open Source Technology Center

  • HANA on SLES 11 SP3 for SAP software selection

    Hi,
    We are planning to install HANA SPS8 on a Vitual Machine with SLES 11 SP3 for SAP.
    ABAP 7.4 and HANA on the Same virtual Machine
    During the Installation of SUSE in the software selection screen, we found the options as
    - SAP Netweaver Server Base
    - SAP HANA Server Base
    We would like to know, whether we have to select these options for the SUSE Installation or only
    SAP Application Server Base would be enough.
    Thanks,
    Regards
    Ahmed Mohammed

    Hi,
    Tuxedo 10.0 extended support ends in September of this year.  If you are making the move from 32 bit versions to 64 bit versions you should definitely move to newer versions of Tuxedo.  Tuxedo 12.1.1 has been out nearly three years at this point and is certified for Suse Linux 11 64 bit.  Is there a reason you are staying on such an old version of Tuxedo while upgrading the OS?
    Regards,
    Todd Little
    Oracle Tuxedo Chief Architect
    PS  For more information about support lifetimes, see:  http://www.oracle.com/us/support/library/lifetime-support-middleware-069163.pdf
    Also if you would like to go all the way to Tuxedo 12.1.3, please ask for a certification in My Oracle Support.

  • Windows 2008 R2: SLES 11 Sp3 Guest converted from Vmware OVA to VHD, does not boot on Hyper-V: could not find /dev/sda4

    Hi
    I have a VMWare OVA file with Guest OS as SLES 11 Sp3. I have converted this file from OVA to VHD using Microsoft Virtual Machine Converter Solution accelerator. On first boot of this VHD on Windows Server 2008 R2 - Microsoft Hyper-V I get an error that
    "Waiting for device /dev/sda4 to appear..
    Cannot find /dev/sda4"
    I have not even booted this VM once on Hyper-V, and hence not installed any Linux integration Services yet.
    What could be the possible reason for this failure? Any suggested solution?
    Thanks
    Ashwini

    Easiest way (and also applies to Hyper-V 2012 R2):
    Ok, following properly (originally missed the step to mount the root directory of the converted VM as "/mnt" )
    http://nwrickert2.wordpress.com/2011/10/24/rescuing-susie/
    Then once chrooted
    mkinitrd -d /dev/sda2
    generated initrd from kdump WITH Hyper-V drivers & VM is usable!
    http://forums.opensuse.org/showthread.php/476780-boot-failure-mkinitrd-does-not-understand-that-dev-sda-has-become-dev-sde
    Can't believe that it was so painful to find the right info easily
    Just to finish it off, after converted machine boots fine, there is a small
    matter of removing tools & fixing networking as per links below:
    https://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.upgrade.doc%2FGUID-6F7BE33A-3B8A-4C57-9C35-656CE05BE22D.html
    http://www.vcritical.com/2010/10/getting-eth0-back-in-a-sles-for-vmware-clone/
    All done!!!
    Also (unsupported), but works fine is SLES 11 SP1

  • Error while installing SAP NW04s on SLES SP2

    My set up is SLES SP2 ( x86_64) and i am trying to install NW04S. In Step 5 Unpack SAP Archivies i am stuck with the below mentioned error. It says permission denied. I changed the permissions of the JDBCCONNECT.JAR and the /sapmnt/SID/exe folder to 777 but it does not solve it. Has somebody come accross this before and got it solved. If so please advise what needs to be done.
    syslib::printOSError(const iastring &, int, DWORD, const iastring &, CMessage::eLogMessage) System call failed.
    Error 13 (Permission denied) in execution of system call 'lstat' with parameter (/root/sapdump/BS_2005_SR3_SAP_Installation_Master/IM_LINUX_X86_64/COMMON/INSTALL/JDBCCONNECT.JAR), line (535) in file (syuxcpath.cpp).
    TRACE  2008-07-20 15:19:21.762 [syuxcpath.cpp:536] CSyPath::getOSNodeType(bool false) lstat(/root/sapdump/BS_2005_SR3_SAP_Installation_Master/IM_LINUX_X86_64/COMMON/INSTALL/JDBCCONNECT.JAR) returned an error I cannot interpret. I will return UNKNOWN.
    ERROR 2008-07-20 15:19:21.762 [syuxcfile.cpp:382] CSyFileImpl::  copy(const CSyPath & /usr/sap/LN1/SYS/exe/run/jdbcconnect.jar, ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const 
    FSL-02015 Node /root/sapdump/BS_2005_SR3_SAP_Installation_Master/IM_LINUX_X86_64/COMMON/INSTALL/JDBCCONNECT.JAR does not exist.
    FCO-00011  The step copyScripts with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_Unpack|ind|ind|ind|ind|8|0|copyScripts was executed with status ERROR ( Last error reported by the step :Caught ESyException in Modulecall: ESAPinstException: error text undefined.).
    syslib::printOSError(const iastring &, int, DWORD, const iastring &, CMessage::eLogMessage)
    FSL-00001  System call failed. Error 13 (Permission denied) in execution of system call 'openU' with parameter (/root/sapdump/BS_2005_SR3_SAP_Installation_Master/IM_LINUX_X86_64/COMMON/INSTALL/JDBCCONNECT.JAR, O_RDONLY), line (368) in file (syuxcfile.cpp).

    HI
    CHECK THIS LINK
    SAP_ERP_6.0_SR3_IDES install error -- permissions error between phase 4&5
    DONT INSTALL FROM ROOT

  • SLES 11 SP3 - VSS Problem

    Hi all,
    I've just installed a fresh SLES 11 SP3 vm. Once rebooted, i noticed this error in hyper-v log:
    - Hyper-V Volume Shadow Copy Requestor failed to connecto to virtual machine "nameofvm" because the version does not match the version expected by hyper-v (virtual machine ID xyz..) Framework version: Negotiated (0.0) Expected (3.0)  Message
    version: Negotiated (0.0) Expected (4.0) To fix this problem you must upgrate the integration services. To upgrade connect to the virtual machine and select insert ....
    Now, obviously the installer disc doesn't work and all integration services are embedded in the linux OS. I'm concerning about two major factor: first, how can this problem impact the system once in production? And how can i address (or disable) this integration
    service? 
    Thank you all

    Hi Miralem, I believe there may be one other way to install updates. When you are installing SLES 11 SP3 for the first time, the installation manager GUI asks you if it should apply the updates. You might want to see if that works for you by creating
    a new VM and closely monitoring the installation manager program.
    If the VM is not going offline while taking the snapshot then this may be a false error. However, if the VM is going offline then probably the snapshot infrastructure is having some issues. Please let me know if you see that the VM is going offline while
    taking the snapshot.
    Also notice that backup for Linux VMs is only file-system consistent and it is not application consistent. This implies that db snapshots may not have the same level of application data consistency that you have come to expect through use of VSS on Windows.
    This is because Linux does not have VSS style infrastructure to coordinate with user mode while a snapshot or a backup operation is in progress.
    Please keep me posted on your progress.
    Thanks,
    Abhishek

  • PC-Suite and XP-SP2

    I have a 6310i and XP-SP2
    What PC-suite version do I need? 4.88 (latest version) won't install!
    Thanks in advance,
    Fred

    If its XP SP 2 you should get version 6.81, you will only be able to use if for backup/restore and synchronising.

  • Outlook 2010 and Exchange 2010 SP3

    Hello,
    we are planning to upgrade from Exchange 2010 sp1 to SP3, most of client PCs has Windows XP sp3 and Oultook 2010 with VSTO addins working with mapi properties.
    I need to know if there are any known issues between this client environment and Exchange 2010 SP3 ??
    thanks a lot,
    Mauricio.
    Mauricio

    Windows XP is not supported in any scenario, so yes, I'd call that a known issue.
    Mike Crowley | MVP
    My Blog --
    Planet Technologies

  • Setup Boot Camp and installed XP SP3 now no OS 10.5.8 please help

    I have setup boot camp and installed XP SP3 onto the macbook pro. When i restarted the computer the only operating system is XP. I have held down the options key while restarting only the WINDOWS option is displayed. How can i get the Mac OS back as i have some pretty important document in that section.
    I have a time capsule but i can not restore from the time capsule as it takes a continues to search for the disk image.
    Can i reboot the computer and start again, then carry out a restore from there?
    How do i reboot/format the computer so i can start again?
    I need to get this sorted ASAP as i have to get this information sent away ASAP.
    Cheers

    Have you tried booting from the disk that came with your computer? I'd try that first, and see if you can see your OS X partition in Disk Utility and possibly repair it.
    Good luck!

Maybe you are looking for