Author: Emerson .

sendmail – Warning: RunAsUser for MSP ignored, check group ids

Every time that I sent an email with an user, the system was displaying the message that could not chdir to the mail directory. I solved following the steps below:

user@linux:~ $ mail blackhole@domain.com
Subject: Test
Sending email to test
.
Cc:
user@linux:~ $ WARNING: RunAsUser for MSP ignored, check group ids (egid=503, want=51)
can not chdir(/var/spool/clientmqueue/): Permission denied
Program mode requires special privileges, e.g., root or TrustedUser.

The group ID 503 was from the user that was logged in and sending the mail. The problem in this system was that it needed setgid set in the sendmail binary file.

root@linux:~ # ls -l /usr/sbin/sendmail.sendmail
-rwxrwxrwx  1 root smmsp 757168 Apr 15  2008 /usr/sbin/sendmail.sendmail

root@anotherlinuxhost:~ # ls -l /usr/sbin/sendmail.sendmail
-rwxr-sr-x  1 root smmsp 757168 Apr 15  2008 /usr/sbin/sendmail.sendmail

root@linux:~ # chmod 2755 /usr/sbin/sendmail.sendmail
root@linux:~ # ls -l /usr/sbin/sendmail.sendmail
-rwxr-sr-x  1 root smmsp 757168 Apr 15  2008 /usr/sbin/sendmail.sendmail

Restarted sendmail and no error message is shown when sending a message.

root@linux:~ # service sendmail restart
Shutting down sm-client:                                   [  OK  ]
Shutting down sendmail:                                    [  OK  ]
Starting sendmail:                                         [  OK  ]
Starting sm-client:                                        [  OK  ]

user@linux:~ $ mail blackhole@domain.com
Subject: Test
Sending email to test
.
Cc:
user@linux:~ $

SteelSeries Siberia USB Soundcard on Windows 7

I bought a SteelSeries 5Hv2 USB on ProGaming Computer. It’s a nice headset and comes with a USB soundcard similar to the SteelSeries Siberia USB soundcard.

According to the website, it had drivers for Windows XP and Windows Vista but no  support for Windows 7. I solved this problem by installing a beta driver available at the SteelSeries blog. Other people reported success right-clicking the driver installer and selecting to execute in Windows Vista combatibility mode.

Now you just need to download the official Windows 7 drivers at the manufacturer’s website.

Sun System Management Services – Error: Exclusive session is in use, disconnecting.

You need to connect to a System Controller (SC) to manage a domain in a Sun Fire E12K, E15K, E20K or E25K. It has the System Management Services (SMS) software that allows you to control the domains.

To view the console, you use /opt/SUNWSMS/bin/console -d <domain letter or domain name> but I was having the error message “Exclusive session is in use, disconnecting”.

sms-svc@sc0:/ $ console -d domain06
Trying to connect…
Connected to Domain Server.

Exclusive session is in use, disconnecting.

I asked to a friend why I was having this problem and he said that I needed to kill the other session.

sms-svc@sc0:/ $ w
9:24am  up 76 day(s),  3:53,  2 users,  load average: 0.91, 2.04, 1.52
User     tty           login@  idle   JCPU   PCPU  what
root     pts/1         9:08am     9                console -d domain06
root     pts/2         9:19am                      w

I found out which PID is running the console, then killed it.

sms-svc@sc0:/ $ ps -ef | grep consol
root  3127     1  0   Sep 19 console  0:00 /usr/lib/saf/ttymon -g -h -p sc0-01-vix console login:  -T sun -d /dev/console
sms-svc 11229 11182  0 09:24:18 pts/2    0:00 grep consol
sms-svc  5492 5398  0 09:09:23 pts/1    0:00 console -d domain06

sms-svc@sc0:/ $ kill 5492

Worked as expected:

sms-svc@sc0:/ $ /opt/SUNWSMS/bin/console -d domain06
Trying to connect…
Connected to Domain Server.
Your console is in exclusive mode now.

Informix Dynamic Server – Logical log files are almost full – backup is needed

Yesterday we had a problem with an Informix Dynamic Server that wasn’t going to Online Mode. The problem was that the Logical log was full and it hang the Informix Dynamic Server

root@hp-ux:/ # tail -f /usr/informix/onlinep.log

Sun Nov 22 10:48:32 2009

10:48:32  Event alarms enabled.  ALARMPROG = ‘/usr/informix/etc/log_full.sh’
10:48:33  Booting Language <c> from module <>
10:48:33  Loading Module <CNULL>
10:48:33  Booting Language <builtin> from module <>
10:48:33  Loading Module <BUILTINNULL>
10:48:38  Informix Dynamic Server 2000 Version 9.21.FC5     Software Serial Number
10:48:38  Informix Dynamic Server 2000 Initialized — Shared Memory Initialized.

10:48:38  Physical Recovery Started at Page(4:21673).
10:48:38  Physical Recovery Complete: 0 Pages Examined 0 Pages Restored.

10:48:38  Logical Recovery Started.
10:48:38  10 recovery worker threads will be started.
10:48:41  Logical Recovery Complete.
0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks

10:48:42  Logical log files are almost full – backup is needed.
10:48:42  Dataskip is now OFF for all dbspaces
10:48:42  Checkpoint Completed:  duration was 0 seconds.
10:48:42  Checkpoint loguniq 5951, logpos 0x18018

10:48:42  Dropping temporary TBLspace 100120, recovering 8 pages.

The problem was solved when someone ran ontape -c and it backed up the log to the tape.

Cray Upgrades “Kraken” Supercomputer with Six-Core AMD Opteron Processors

The third Supercomputer according to the Top 500 List is getting a CPU upgrade by Cray. The AMD Quad-Core processors are being replaced by Six-Core processors without having to replace any board.

AIX Volume Group can’t properly display the Logical Volume Type

Listing the logical volumes inside the volume group. AIX can’t determine the LV type.

root@aix:/ # lsvg -l oravg
oravg:
LV NAME             TYPE       LPs   PPs   PVs  LV STATE      MOUNT POINT
oravg_lg            ??? 1     1     1    closed/syncd  N/A
ora_lv              ??? 1064  1064  2    closed/syncd  N/A

To solve this problem we’ll export then reimport the VG. But first we’ll need to deactivate it.

root@aix:/ # varyoffvg oravg

And we need at least one disk that is part of the volume group because it has the information needed to import.

root@aix:/ # lspv | grep oravg
hdisk251 00c5f1d097cc8a6e                   oravg
hdisk221 00c5f1d0a7bffede                    oravg

Now we run exportvg and the server will no longer know it once had the volume group.

root@aix:/ # exportvg oravg

Let’s list all the volume groups the server is aware that exists.

root@aix:/ # lsvg
rootvg
datavg
cache01vg
cache02vg

Only the rootvg is currently imported and active.

root@aix:/ # lsvg -o
rootvg

Let’s reimport the volume group. We need to declare one of the disks we listed before to reimport the volume group.

root@aix:/ # importvg -y oravg hdisk251
oravg

Next, we activate the volume group

root@aix:/ # varyonvg oravg

Listing the Volume Group. Volume Group TYPE listed.

root@aix:/ # lsvg -l oravg
oravg:
LV NAME             TYPE       LPs   PPs   PVs  LV STATE      MOUNT POINT
oravg_lg            jfs2log    1     1     1    closed/syncd  N/A
ora_lv              jfs2       1064  1064  2    closed/syncd  /u01

Check OBP variables without rebooting Solaris or going to the ok prompt

To check the OBP variables in your Solaris SPARC server and leaving Solaris up and running, you’ll need to use the eeprom command

root@solaris:/ # eeprom
asr-policy=normal
test-args: data not available.
diag-passes=1
local-mac-address?=true
fcode-debug?=false
scsi-initiator-id=7
oem-logo: data not available.
oem-logo?=false
oem-banner: data not available.
oem-banner?=false
ansi-terminal?=true
screen-#columns=80
screen-#rows=34
ttyb-rts-dtr-off=false
ttyb-ignore-cd=true
ttya-rts-dtr-off=false
ttya-ignore-cd=true
ttyb-mode=9600,8,n,1,-
ttya-mode=9600,8,n,1,-
output-device=ttya
input-device=ttya
auto-boot-on-error?=true
error-reset-recovery=sync
load-base=16384
auto-boot?=true
network-boot-arguments: data not available.
boot-command=boot
diag-file: data not available.
diag-device=disk0:a
boot-file: data not available.
boot-device=vx-rootdisk vx-rootmirr
use-nvramrc?=false
nvramrc=devalias vx-rootdisk /pci@1c,600000/scsi@2/disk@0,0:a
devalias vx-rootmirr /pci@1c,600000/scsi@2/disk@3,0:a
security-mode=none
security-password: data not available.
security-#badlogins=0
verbosity=normal
diag-trigger=error-reset power-on-reset
service-mode?=false
diag-script=normal
diag-level=max
diag-switch?=false

Xlib: PuTTY X11 proxy: wrong authentication protocol attempted

I had this weird error when trying to start an X11 application.

oracle@dbserver:~ $ xclock
xlib: connection to “localhost:12.0” refused by server
Xlib: PuTTY X11 proxy: wrong authentication protocol attempted
Error: Can’t open display: localhost:12.0

Next you try the steps described here to transfer the authorization to the other account. But if you follow the steps and it simply doesnt work, check the filesystem where the home directory is.

oracle@dbserver:~ $ df -h .
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/rootvg-homelv
9.9G  9.4G  128K 100% /home

In this particular machine, I was having the authentication protocol error because the OS couldn’t update the .Xauthority file in the home directory.

Volume inside a Disk Group in Veritas Volume Manager is in NEEDSYNC state

Whenever you see a volume inside a disk group with the NEEDSYNC state, you simply run vxvol -g <disk group> resync <volume> to change the status back to ACTIVE.

root@solaris:/ # vxprint -htg softwaredg
DG NAME         NCONFIG      NLOG     MINORS   GROUP-ID
DT NAME         STATE        DM_CNT   SPARE_CNT         APPVOL_CNT
DM NAME         DEVICE       TYPE     PRIVLEN  PUBLEN   STATE
RV NAME         RLINK_CNT    KSTATE   STATE    PRIMARY  DATAVOLS  SRL
RL NAME         RVG          KSTATE   STATE    REM_HOST REM_DG    REM_RLNK
CO NAME         CACHEVOL     KSTATE   STATE
VT NAME         NVOLUME      KSTATE   STATE
V  NAME         RVG/VSET/CO  KSTATE   STATE    LENGTH   READPOL   PREFPLEX UTYPE
PL NAME         VOLUME       KSTATE   STATE    LENGTH   LAYOUT    NCOL/WID MODE
SD NAME         PLEX         DISK     DISKOFFS LENGTH   [COL/]OFF DEVICE   MODE
SV NAME         PLEX         VOLNAME  NVOLLAYR LENGTH   [COL/]OFF AM/NM    MODE
SC NAME         PLEX         CACHE    DISKOFFS LENGTH   [COL/]OFF DEVICE   MODE
DC NAME         PARENTVOL    LOGVOL
SP NAME         SNAPVOL      DCO

dg softwaredg   default      default  38000    1185222274.13.solaris

dm softwaredg01 c0t9d0s2     auto     20095    286657920 –
dm softwaredg02 c1t11d0s2    auto     20095    286657920 –

v  app.software –            ENABLED  NEEDSYNC 14680064 SELECT    –        fsgen
pl app.software-01 app.software ENABLED ACTIVE 14680064 CONCAT    –        RW
sd softwaredg01-01 app.software-01 softwaredg01 0 14680064 0      c0t9d0   ENA
pl app.software-02 app.software ENABLED ACTIVE 14680064 CONCAT    –        RW
sd softwaredg02-01 app.software-02 softwaredg02 0 14680064 0      c1t11d0  ENA

v  ctm.oracatrman –          ENABLED  NEEDSYNC 2097152  SELECT    –        fsgen
pl ctm.oracatrman-01 ctm.oracatrman ENABLED ACTIVE 2097152 CONCAT –        RW
sd softwaredg01-02 ctm.oracatrman-01 softwaredg01 14680064 2097152 0 c0t9d0 ENA
pl ctm.oracatrman-02 ctm.oracatrman ENABLED ACTIVE 2097152 CONCAT –        RW
sd softwaredg02-04 ctm.oracatrman-02 softwaredg02 27262976 2097152 0 c1t11d0 ENA

v  dat.audit    –            ENABLED  NEEDSYNC 4194304  SELECT    –        fsgen
pl dat.audit-01 dat.audit    ENABLED  ACTIVE   4194304  CONCAT    –        RW
sd softwaredg01-03 dat.audit-01 softwaredg01 16777216 4194304 0   c0t9d0   ENA
pl dat.audit-02 dat.audit    ENABLED  ACTIVE   4194304  CONCAT    –        RW
sd softwaredg02-03 dat.audit-02 softwaredg02 23068672 4194304 0   c1t11d0  ENA

v  dat.users    –            ENABLED  NEEDSYNC 8388608  SELECT    –        fsgen
pl dat.users-01 dat.users    ENABLED  ACTIVE   8388608  CONCAT    –        RW
sd softwaredg01-04 dat.users-01 softwaredg01 20971520 8388608 0   c0t9d0   ENA
pl dat.users-02 dat.users    ENABLED  ACTIVE   8388608  CONCAT    –        RW
sd softwaredg02-02 dat.users-02 softwaredg02 14680064 8388608 0   c1t11d0  ENA

v  vol01        –            ENABLED  ACTIVE   10240000 SELECT    –        fsgen
pl vol01-01     vol01        ENABLED  ACTIVE   10240000 CONCAT    –        RW
sd softwaredg01-05 vol01-01  softwaredg01 29360128 10240000 0     c0t9d0   ENA
pl vol01-02     vol01        ENABLED  ACTIVE   10240000 CONCAT    –        RW
sd softwaredg02-05 vol01-02  softwaredg02 29360128 10240000 0     c1t11d0  ENA

root@solaris:/ # vxvol -g softwaredg resync dat.audit

Street Fighter IV – Can’t connect to Live: Error 0x80151911

I bought Street Fighter IV and when you start the game it asks for you to create or use an existing profile.

Any Game for Windows Live will enable you to create a profile that have all your games and you can show to other people what you have been playing. For example, see Microsoft Xbox Live Director of Programming Larry Hryb gamertag Major Nelson.

You enter your an email address and the password and it will download your profile to your computer but in my case it said “Can’t connect to Live – Error 0x80151911”

I read that the culprit was the MTU parameter set on your network. It can be set in any part of your network like your router or your Windows computer.

You need to set the MTU size to at least 1400 to make it download the profile. See your router documentation on how to change this parameter.

On a Windows computer you need to open regedit.exe and then search for the entries called MTU in HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Tcpip/Interfaces and select each interface (a random string of numbers). Right click the parameter MTU and choose decimal then type 1492 or 1500. Now you should be able to download your profile.