http://forums.novell.com/ en Sun, 22 Nov 2009 07:38:45 GMT vBulletin 60 http://forums.novell.com/images/ca_serenity/misc/rss.jpg http://forums.novell.com/ http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393533-how-install-php-oci8-11gr1-x-rpm-sles-11-a.html Sat, 21 Nov 2009 21:20:54 GMT Hi all,

I am like to install an oracle product called "Real User Experience Insight" on a SLES 11 server. I am running into a problem as I tried to install the php-oci8-11GR1-5.1.6-20.el5_2.1.x86_64.rpm package because of missing dependencies.

error: Failed dependencies:
php.common >= 5.1.6 is nedded by php-oci8-11gR1-5.1.6-20.el5_2.1.x86_64
libaio >= 0.3.106 is needed by php-oci8-11gR1-5.1.6-20.el5_2.1.x86_64

How can I solve the dependencies? Any feedback is appreiciate. Thanks in advance.

Regards
Maik ]]> SLES: Configure-Administer msandmann http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393533-how-install-php-oci8-11gr1-x-rpm-sles-11-a.html http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393476-access-privileges-disk-group-members.html Fri, 20 Nov 2009 18:23:21 GMT Does anybody know which access privileges does a user that belongs to "disk" UNIX group have? Is there any security issue concerned?

In principle, members of such group have access to 'disk' information, raw devices, etc., but where all these privileges specified?

Thanks for any help. ]]> SLES: Configure-Administer rsarmiento http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393476-access-privileges-disk-group-members.html http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393369-configuring-mono-extension-2-0-2-4-a.html Fri, 20 Nov 2009 10:41:53 GMT Hi Experts, I recently am trying out SUSE Enterprise 11 after my tryout of OpenSUSE 11.1 and 11.2. I installed SUSE Enterprise 11 successfully... Hi Experts,

I recently am trying out SUSE Enterprise 11 after my tryout of OpenSUSE 11.1 and 11.2.

I installed SUSE Enterprise 11 successfully (no errors or smoke).
I downloaded and added the add-on Mono Extension and followed the steps listed here: Installation Instructions

However, I'm at a problem... the mono running still shows it being 2.0 when doing "mono --version" from the terminal.

I have confirmed through Yast2 that mono-add-on (2.4) is indeed installed.... so is mono 2.0.

Doing the logical thing, I removed mono 2.0 and then mono stopped working completely... even though it still showed installed in Yats2 Software Manager.

I should mention I have yet to receive an activation code for Mono Extension, however I do have it for SUSE Enterprise and have registered it successfully. Is Mono 2.4 locked until the activation code arrives in my mail box? (It's been 36 hours since I put the request through Novell website...)

I did receive the email saying "Added to subscription SUSE Linux Enterprise Mono Extension.".. but no activation code.

Thoughts?

Cheers. ]]> SLES: Configure-Administer utnsteve http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393369-configuring-mono-extension-2-0-2-4-a.html http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393358-some-trivial-preparation-questions-about-drbd.html Fri, 20 Nov 2009 06:35:39 GMT two questions before going to implement DRBD for the oracle db filesystems replication 1, what happens if the Primary and Slave communication is... two questions before going to implement DRBD for the oracle db filesystems replication

1, what happens if the Primary and Slave communication is not possible for 3 or 4 hours, does the Primary Server re-replicate all the changes/updates happend when the network was down ?

2, for testing .. is it possible to change the status of Primary to Secondary and vice verca
?

last but not least please suggest a step-by-step manual/configuration guide for DRBD(withou HA, as we are not configuring HA, only data replication)

Regards ]]> SLES: Configure-Administer needee http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393358-some-trivial-preparation-questions-about-drbd.html http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393350-unable-connect-server-using-ssh-outside-home-netw.html Fri, 20 Nov 2009 02:52:35 GMT hi, I am using ssh to connect my suse linux enterprise server.I am able to connect if i am in the home networ but if i try to connect from outside... hi,

I am using ssh to connect my suse linux enterprise server.I am able to connect if i am in the home networ but if i try to connect from outside home network i am getting the following errors.

Network:connection timeout
Network:connection refused.

I already forwarded port 22 in my router.I have been trying to resolve this issue from past 2 day,but no success.Can any one please help how to resolve this issue.

/etc/ssh # ps -ef | grep sshd
root 4009 1 0 16:45 ? 00:00:00 /usr/sbin/sshd -o PidFile=/var/run/sshd.init.pid


Here is my sshd_config and ssh_config Files.

:/etc/ssh # cat sshd_config
# $OpenBSD: sshd_config,v 1.80 2008/07/02 02:24:18 djm Exp $

# This is the sshd server system-wide configuration file. See
# sshd_config(5) for more information.

# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented. Uncommented options change a
# default value.

Port 22
#AddressFamily any
ListenAddress 192.168.2.102
#ListenAddress ::

# Disable legacy (protocol version 1) support in the server for new
# installations. In future the default will change to require explicit
# activation of protocol 1
Protocol 2

# HostKey for protocol version 1
#HostKey /etc/ssh/ssh_host_key
# HostKeys for protocol version 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key

# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 1024

# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
#LogLevel INFO

# Authentication:

LoginGraceTime 600
PermitRootLogin no
StrictModes yes
#MaxAuthTries 6
#MaxSessions 10

#RSAAuthentication yes
#PubkeyAuthentication yes
#AuthorizedKeysFile .ssh/authorized_keys

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
RhostsRSAAuthentication no
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# To disable tunneled clear text passwords, change to no here!
PasswordAuthentication yes
PermitEmptyPasswords no

# Change to no to disable s/key passwords
#ChallengeResponseAuthentication yes

# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

# Set this to 'yes' to enable support for the deprecated 'gssapi' authentication
# mechanism to OpenSSH 3.8p1. The newer 'gssapi-with-mic' mechanism is included
# in this release. The use of 'gssapi' is deprecated due to the presence of
# potential man-in-the-middle attacks, which 'gssapi-with-mic' is not susceptible to.
#GSSAPIEnableMITMAttack no


# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication. Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM yes

#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
X11Forwarding no
#X11DisplayOffset 10
#X11UseLocalhost yes
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
#UsePrivilegeSeparation yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS yes
#PidFile /var/run/sshd.pid
#MaxStartups 10
#PermitTunnel no
#ChrootDirectory none

# no default banner path
#Banner none

# override default of no subsystems
Subsystem sftp /usr/lib64/ssh/sftp-server

# This enables accepting locale enviroment variables LC_* LANG, see sshd_config(5).
AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES
AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
AcceptEnv LC_IDENTIFICATION LC_ALL
AllowTcpForwarding yes
Compression yes
MaxAuthTries 6
PermitRootLogin no
PrintMotd yes
PubkeyAuthentication yes
RSAAuthentication no

# Example of overriding settings on a per-user basis
#Match User anoncvs
# X11Forwarding no
# AllowTcpForwarding no
# ForceCommand cvs server


/etc/ssh # cat ssh_config
# $OpenBSD: ssh_config,v 1.23 2007/06/08 04:40:40 pvalchev Exp $

# This is the ssh client system-wide configuration file. See
# ssh_config(5) for more information. This file provides defaults for
# users, and the values can be changed in per-user configuration files
# or on the command line.

# Configuration data is parsed as follows:
# 1. command line options
# 2. user-specific file
# 3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.

# Site-wide defaults for some commonly used options. For a comprehensive
# list of available options, their meanings and defaults, please see the
# ssh_config(5) man page.

Host *
# ForwardAgent no
# ForwardX11 no

# If you do not trust your remote host (or its administrator), you
# should not forward X11 connections to your local X11-display for
# security reasons: Someone stealing the authentification data on the
# remote side (the "spoofed" X-server by the remote sshd) can read your
# keystrokes as you type, just like any other X11 client could do.
# Set this to "no" here for global effect or in your own ~/.ssh/config
# file if you want to have the remote X11 authentification data to
# expire after two minutes after remote login.
ForwardX11Trusted yes

# RhostsRSAAuthentication no
# RSAAuthentication yes
PasswordAuthentication yes
# HostbasedAuthentication no
# GSSAPIAuthentication no
# GSSAPIDelegateCredentials no
# BatchMode no
# CheckHostIP yes
# AddressFamily any
ConnectTimeout 200
# StrictHostKeyChecking ask
# IdentityFile ~/.ssh/identity
# IdentityFile ~/.ssh/id_rsa
# IdentityFile ~/.ssh/id_dsa
Port 22
Protocol 2
# Cipher 3des
# Ciphers aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc
# MACs hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160
# EscapeChar ~
# Tunnel no
# TunnelDevice any:any
# PermitLocalCommand no
# GSSAPIAuthentication no
# GSSAPIDelegateCredentials no

# Set this to 'yes' to enable support for the deprecated 'gssapi' authentication
# mechanism to OpenSSH 3.8p1. The newer 'gssapi-with-mic' mechanism is included
# in this release. The use of 'gssapi' is deprecated due to the presence of
# potential man-in-the-middle attacks, which 'gssapi-with-mic' is not susceptible to.
# GSSAPIEnableMITMAttack no

# This enables sending locale enviroment variables LC_* LANG, see ssh_config(5).
SendEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES
SendEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
SendEnv LC_IDENTIFICATION LC_ALL ]]> SLES: Configure-Administer ukatru http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393350-unable-connect-server-using-ssh-outside-home-netw.html http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393346-smt-run-smt-job-manually.html Thu, 19 Nov 2009 23:46:52 GMT Is there a possiblilty to run smt-jobs manually? for example if i want to force the clients to install the updates? Why is the client not beeing... Is there a possiblilty to run smt-jobs manually? for example if i want to force the clients to install the updates?

Why is the client not beeing updated after the first connect to the smt server automatically? ]]> SLES: Configure-Administer domb http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393346-smt-run-smt-job-manually.html http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393336-change-permissions-proc-sys-fs-aio-nr-file.html Thu, 19 Nov 2009 21:56:09 GMT Hi,

I am running SLES 11.0 and Oracle.

I need to change the value of fs.aio-nr

I can't change the value using sysctl, chmod, etc., as the /proc/sys/fs/aio-nr file is read only and owned by root. I can't make any changes to the file even though I am logged in as root. I get a "permission denied" message when I attempt to write to the file or change permissions.

-r--r--r-- 1 root root 0 Nov 19 16:10 aio-nr

How do I change the permission of this file so I can update the parameter value?

Thanks in advance!

Greg
Elcom ]]> SLES: Configure-Administer gbennett-elcom http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393336-change-permissions-proc-sys-fs-aio-nr-file.html http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393307-how-unload-owcimomd-sles.html Thu, 19 Nov 2009 17:44:01 GMT Very new to Linux and have a very basic question. Having a problem trying to config CIFS and one of the forums said to unload owcimomd and then make... Very new to Linux and have a very basic question. Having a problem trying to config CIFS and one of the forums said to unload owcimomd and then make some changes to a file and reload it, problem is I dont know how to unload in linux, no systme prompt like in plain OES - Im running SLES 10sp2 with OESsp1. How do I do this?

thanks in advance! ]]> SLES: Configure-Administer rodriguezh http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393307-how-unload-owcimomd-sles.html http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393294-squidguard.html Thu, 19 Nov 2009 15:53:57 GMT Hi, I'm searching a RPM-package for quidguard for my SLES11-64 bit version, but I can't found anyone.

I tried to compile a version 1.4 from squidguard.org, but this give me the error message: The Berkley DB library version 2.6.4 or newer is required.

I have also downloaded v 4.8.24 and compiled it, but again the error message above. I also renamed the install directory to /usr/local/BerkeleyDB.

Can someone help me to get a running version of squidquard? ]]> SLES: Configure-Administer markusherbert http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393294-squidguard.html http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393151-how-move-quorum-partition.html Wed, 18 Nov 2009 16:20:28 GMT Hi to all;

I've two node SLES in a cluster configuration.
Now i need to change the datastore where is placed the quorum configuration.
I've checked from iManager, but i cannot found where move quorum partition...

can you help me?

thank you in advance... ]]> SLES: Configure-Administer bluedive http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393151-how-move-quorum-partition.html http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393150-disk-space-mystery.html Wed, 18 Nov 2009 16:00:55 GMT Please help. I have two servers configured basically the same but one is now reporting "0" space left on the / logical volume. All my real data resides on a separate disk and volume called /data. What could possibly using the space in /dev/mapper/VG-root_lv? The other server is only using 16% of the 4 gigs allocated to the / logical volume.


Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/VG-root_lv
4128448 4128092 0 100% /
udev 2022004 164 2021840 1% /dev
/dev/sda3 202225 14406 177377 8% /boot
/dev/mapper/VG-home_lv
7224824 147424 6710400 3% /home
/dev/mapper/VG-opt_lv
3096336 570068 2368984 20% /opt
/dev/mapper/VG-srv_lv
3096336 1112168 1826884 38% /srv
/dev/mapper/VG-tmp_lv
3096336 70244 2868808 3% /tmp
/dev/mapper/VG-usr_lv
7224824 1564820 5293004 23% /usr
/dev/mapper/VG-var_lv
3096336 456336 2482716 16% /var
/dev/mapper/data-lv_data
488310212 368541604 119768608 76% /data ]]> SLES: Configure-Administer tnjpatton http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393150-disk-space-mystery.html http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393146-sles-server-having-application-sap-slow-hangs.html Wed, 18 Nov 2009 15:41:29 GMT My SLES Server has SAP installed on it. I have found that the server frequently hangs (freezes) and when it is working it is very slow. What can be... My SLES Server has SAP installed on it. I have found that the server frequently hangs (freezes) and when it is working it is very slow. What can be the cause of this? ]]> SLES: Configure-Administer gakiimurerwa http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393146-sles-server-having-application-sap-slow-hangs.html http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393143-how-do-you-handle-sles-updates.html Wed, 18 Nov 2009 15:29:17 GMT As my org continues to move away from NetWare, we're using more and more SLES servers. Some have OES installed, some do not. Right now, I vnc into each server and manually run online update on each server for patching.

How do you handle doing updates on your SLES servers? Do you update one machine at a time, or do you have a tool that manages the patching? ]]> SLES: Configure-Administer imc http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393143-how-do-you-handle-sles-updates.html http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393123-what-pm-profiler.html Wed, 18 Nov 2009 12:26:53 GMT Hi i'm new to Linux.

I have a SLES 11 from Novell.
And the Server shuts down at 00:00 ...
it is triggered by pm-profiler.
What is pm-profiler ?!

Does anybody know ? ]]> SLES: Configure-Administer mrbiomathe http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393123-what-pm-profiler.html http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393104-setting-up-disaster-recovery-scenario-sles-10-zseries.html Wed, 18 Nov 2009 06:45:15 GMT hi, i am having a hard time setting up a disaster recovery scenario for a sles 10 running on an ibm zseries lpar (ifl). the back end disk... hi,

i am having a hard time setting up a disaster recovery scenario for a sles 10 running on an ibm zseries lpar (ifl).

the back end disk replicates its contents to another site. the idea is that in the event of a disaster, the "replica" copy will be booted on another site.

the problem that i facing is that sles 10 uses the dasd units and later on assigns a major/minor number with dasdxxx.

originally, in the runing site, the os knows that (e.g.) dasda corresponds to a unit 0x186c. on the replicated end, the unit 0x186c will already be different (e.g.) 0x2589. to add to the complexity, there are cases where this unit will be given a new device name such as dasdm.

i've tried using udev, but the system didn't even boot at all. any other ideas, recommnedations, solutions?

given the scenario above, how will the replicated copy be booted to the other system?

thanks,
leonard ]]> SLES: Configure-Administer lnbnatera http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/393104-setting-up-disaster-recovery-scenario-sles-10-zseries.html