Studio 10 dbx dumps core with access checking on

I have an application that causes Studio 10 dbx to dump core on start with access checking turned on. It will run OK under Studio 9 dbx, but tends to kill dbx if I attempt to follow the stack when a violation is found.
For some odd reason, 'suppress rui' does not work with it as well.
What information can I provide to help identify this bug? I expect the application and its build environment are too big to send in.
Cheers,
Ian

x86/AMD64 doesn't do access checking, or does it now?
Anyway, here is the pstack:
Cheers, Ian.
core '/tmp/core' of 12721: /opt/studio10/SUNWspro/bin/../prod/bin/sparcv9/dbx sm70/icp/test/sparc
ffffffff7e6a39c0 _kill (ffffffff7e7b0f88, 31b1, 2002, 100532d9d, 100532000, 100532) + 8
00000001000bbaa4 ???????? (10062e, 100400, b, 100400, 100633000, 10053f5e0)
ffffffff7e6a2dfc sigacthandler (b, ffffffff7fff8850, ffffffff7fff8570, b, 3d, 3d000000) + 2c
--- called from signal handler with signal 11 (SIGSEGV) ---
000000010025881c __1cHTypetabHGetType6Mii_pnEType__ (ffffffff7fffe738, 100999670, 100999680, 0, 0, ffffffff7
fffb892) + c
000000010029a01c __1cFStabsQmake_tactarglist6MpcrnHSymlist_pnHObjfile_ibb_2_ (ffffffff7fffe738, 7c, 1, 10099
9670, 0, 0) + 104
000000010029ae90 __1cFStabsZcafe_parse_templ_fun_inst6MpnHObjfile_pnDFun_pc5b_4_ (ffffffff7fffe738, 10099967
0, 1009ba7d0, 1, ffffffff7d340fc2, ffffffff7fffb884) + 24c
0000000100286c60 __1cFStabsIFuncDecl6MpnHObjfile_pnDFun_pcb_4_ (ffffffff7fffe738, 100999670, 1009ba990, 5f,
4c, 1009ba990) + ec
0000000100282828 __1cFStabsSNPatchProcessDebug6MpnHObjfile_pnEstab_pcIIbb_I_ (ffffffff7fffe738, 100999670, f
fffffff7d349e14, ffffffff7d31df38, ffffffff7d34f364, ffffffff7fffe66c) + 1d8
000000010024b478 ???????? (10076b050, 49e14, 0, de6, 0, 1)
000000010024b8d8 ???????? (100999670, ffffffffffffffff, 103955440, 102eb6730, 1, 1)
000000010024b6a8 __1cNReadLazyStabs6FpnHObjfile_bb_v_ (100999670, 10053f000, 1, 1, 10053f5e0, 100400) + e4
00000001001dbae8 __1cGRtcFunTlocate_npatch_sites6M_v_ (103933330, 7, e, 80, 84, 103933330) + 80
00000001001db888 __1cGRtcFunSlocate_patch_sites6ML_i_ (103933330, 51eb8400, ed11ad88, 100999a60, 81c7e008, 1
) + 784
00000001001d6544 __1cKRtcLoadObjRrtc_process_check6Mb_v_ (103933330, 100400, 100983860, 1009c4e70, 100983870
, ffffffffffffffff) + 6fc
00000001001c714c __1cGRtcMgrPrtc_new_process6M_v_ (102c1ae30, 10065a400, 0, 0, 1, 10056fe74) + 80c
00000001001c590c __1cGRtcMgrTtry_rtc_new_process6M_b_ (10065a400, 1005d4d05, 0, 10056f000, 10056f, 10076ac30
) + c
00000001001c5544 ???????? (1, 1029df5a9, 10053f5e0, 10065a400, 5, 1002452c8)
00000001000c7984 __1cSActionList_execute6FpnEList4nGAction___pnEProc_pnHHandler_pnJEventInst_nHLevel_e__v_ (
102d13780, 102cb0340, 102d1e1c0, 102ab71d0, 1, 10053b) + 64
0000000100166a4c __1cHHandlerSdecision_procedure6MpnEProc__v_ (102d1e1c0, 102cb0340, 100558, 100400, 1005585
bc, 102ab71d0) + 158
00000001001bfccc __1cKRecognizerHtrigger6MpnEProc__v_ (102d1e1c0, 102cb0340, 100400, 100581000, 100581ea8, 1
0056c18d) + e8
00000001001c0240 __1cKRecognizerIdispatch6FpnGTarget_pnEProc__v_ (10053f5e0, 102cb0340, 100400, 1, 0, 10064e
370) + 58
00000001001b0c44 __1cEProcNvcpu_dispatch6MpnEVCpu__b_ (102cb0340, 100766070, 1005468d0, 1002182a0, 100769888
, 100645d30) + 384
00000001001b0de8 __1cEProcQpervcpu_dispatch6MpnEVCpu__v_ (102cb0340, 10057c3d0, 102d3bc60, 10057c450, 10057c
3d0, 100569599) + 14c
00000001001b15d4 __1cEProcQgeneric_dispatch6MpnEVCpu__b_ (102cb0340, 10057c458, 100569, 100581000, 10056972b
, 100581) + 1a8
00000001001b1d4c __1cEProcCgo6MpnEVCpu_nGProcGo_b_v_ (102cb0340, 100569, 102be9050, cc4, 100581fe8, 1) + 52c
000000010017ca14 __1cGdo_run6FpnGInterp_bnHLevel_e__i_ (100400, 100568000, 100400, 10053f5e0, 100400, 100400
) + 328
00000001002bbba0 ???????? (1005983f7, 102ab8230, 10065b8d8, 0, 10066f510, 102b487e0)
00000001002ba890 __1cNpdksh_execute6FpnGInterp_pnCop_i_i_ (10065b890, 102c81dc0, 0, 10065b890, 102bcf5a0, 10
3539140) + 1c0
00000001002a710c __1cLpdksh_shell6FpnGInterp_pnGSource__i_ (10065b890, 102cf6280, 100400, 100596d79, 100596d
80, 1000bb4b0) + 4c0
00000001000bfa5c __1cNmain_cmd_loop6FpnGInterp__v_ (10065b890, 100400, 100533d18, 100614178, 100581f10, 1005
33) + a8
00000001000c0a8c main (100400, 100532, 100533d18, 10065b890, 10053f5e0, 1) + b8c
00000001000b409c _start (0, 0, 0, 0, 0, 0) + 17c                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

Similar Messages

  • Dbx error with access checking after attaching

    I used dbx - <pid> to attach to a process that had LD_PRELOAD /opt/SUNWspro/lib/librtc.so in its environment. I had previously used the same setup to enable leaks/memuse checking. When I tried to enable access checking I got the following error:
    (dbx 5) check -all
    access checking - ON
    memuse checking - ON
    RTC: Enabling Error Checking...
    RTC: access error limit reached -- disabling access checking
    RTC: Running program...
    Setup is Sol8 Forte 6U2. Any thoughts?

    Thanks. Meanwhile I've found another problem of course. I'm again trying to get access/leaks checking working in my process. This time, the process was started from within dbx, no attaching, but the process died with a SEGV in __rtc_trap_handler:
    detected a multithreaded program
    access checking - ON
    memuse checking - ON
    Running: sogo
    (process id 2972)
    RTC: Enabling Error Checking...
    RTC: Running program...
    stopped in main at line 98 in file "sogo.cpp"
    98 return ::sogo::main(argc, argv, arge);
    dbx: warning: can't find symbolic information for thrown type
    t@3 (l@3) signal SEGV (no mapping at the fault address) in __rtc_trap_handler at 0xfe9610d8
    0xfe9610d8: __rtc_trap_handler+0x0058: ld [%l5], %l0
    dbx: warning: invalid frame pointer
    (dbx 1) where
    current thread: t@3
    [1] setup_context(0xfdf90600, 0xf8ffbfa0, 0xf3514738, 0xf8f00000, 0xfc000, 0xfb7fbbd0), at 0xf35146d8
    [2] thrpcreate(0xfdf90200, 0x0, 0xfdf90600, 0x0, 0x41, 0x0), at 0xf3508fc4
    [3] thrcreate(0x0, 0x0, 0xe0900d54, 0x0, 0x41, 0x0), at 0xf3509208
    [4] thr_create(0x0, 0x0, 0xe0900d54, 0x0, 0x41, 0x0), at 0xfe947738
    [5] door_create_server(0x0, 0xffffffff, 0x2, 0x1, 0xfb7fbf18, 0x3), at 0xe0900da8
    [6] __door_return(0x25d700, 0x0, 0x0, 0x0, 0xfb7fbfa0, 0x4), at 0xf9999264
    (dbx 2)
    the actuall invocation of dbx looked like (from a script):
    dbx -C -q -c \
    "check -all -frames 16; \
    ignore SIGQUIT ; \
    dbxenv run_autostart on ; \
    runargs $* ; \
    step ; \
    cont" \
    sogo &
    Does the RTC library not play nicely with doors? Setup is still sol8/6U2.
    Thanks.

  • BDB dumps core after adding approx 19MB of data

    Hi,
    BDB core dumps after adding about 19MB of data & killing and restarting it several times.
    Stack trace :
    #0 0xc00000000033cad0:0 in kill+0x30 () from /usr/lib/hpux64/libc.so.1
    (gdb) bt
    #0 0xc00000000033cad0:0 in kill+0x30 () from /usr/lib/hpux64/libc.so.1
    #1 0xc000000000260cf0:0 in raise+0x30 () from /usr/lib/hpux64/libc.so.1
    #2 0xc0000000002fe710:0 in abort+0x190 () from /usr/lib/hpux64/libc.so.1
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile db_err.o.
    If NOT specified will behave as a non -g compiled binary.
    warning: No unwind information found.
    Skipping this library /integhome/jobin/B063_runEnv/add-ons/lib/libicudata.sl.34.
    #3 0xc000000022ec2340:0 in __db_assert+0xc0 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile db_meta.o.
    If NOT specified will behave as a non -g compiled binary.
    #4 0xc000000022ed2870:0 in __db_new+0x780 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile bt_split.o.
    If NOT specified will behave as a non -g compiled binary.
    #5 0xc000000022ded690:0 in __bam_root+0xb0 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    #6 0xc000000022ded2d0:0 in __bam_split+0x1e0 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile bt_cursor.o.
    If NOT specified will behave as a non -g compiled binary.
    #7 0xc000000022dc83f0:0 in __bam_c_put+0x360 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile db_cam.o.
    If NOT specified will behave as a non -g compiled binary.
    #8 0xc000000022eb8c10:0 in __db_c_put+0x740 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile db_am.o.
    If NOT specified will behave as a non -g compiled binary.
    #9 0xc000000022ea4100:0 in __db_put+0x4c0 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so---Type <return> to continue, or q <return> to quit---
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile db_iface.o.
    If NOT specified will behave as a non -g compiled binary.
    #10 0xc000000022eca7a0:0 in __db_put_pp+0x240 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile cxx_db.o.
    If NOT specified will behave as a non -g compiled binary.
    #11 0xc000000022d92c90:0 in Db::put(DbTxn*,Dbt*,Dbt*,unsigned int)+0x120 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    What is the behaviour of BDB if its killed & restarted when a bdb transaction is in progress?
    anybody has an idea as to why BDB dumps core in above scenario?
    Regards
    Sandhya

    Hi Bogdan,
    As suggested by you i am using the below flags to open an enviornment.
    DB_RECOVER |DB_CREATE | DB_INIT_LOG | DB_INIT_MPOOL | DB_INIT_TXN|DB_THREAD
    DB_INIT_LOCK is not used because at our application level we are maintaining a lock to guard against multiple simultaneous access.
    The foll msg is output on the console & the dumps core with same stack trace as posted before.
    __db_assert: "last == pgno" failed: file "../dist/../db/db_meta.c", line 163
    I ran db_verify, db_stat, db_recover tools on the DB & thier results are as below.
    db_verify <dbfile>
    db_verify: Page 4965: partially zeroed page
    db_verify: ./configserviceDB: DB_VERIFY_BAD: Database verification failed
    db_recover -v
    Finding last valid log LSN: file: 1 offset 42872
    Recovery starting from [1][42200]
    Recovery complete at Sat Jul 28 17:40:36 2007
    Maximum transaction ID 8000000b Recovery checkpoint [1][42964]
    db_stat -d <dbfile>
    53162 Btree magic number
    9 Btree version number
    Big-endian Byte order
    Flags
    2 Minimum keys per-page
    8192 Underlying database page size
    1 Number of levels in the tree
    60 Number of unique keys in the tree
    60 Number of data items in the tree
    0 Number of tree internal pages
    0 Number of bytes free in tree internal pages (0% ff)
    1 Number of tree leaf pages
    62 Number of bytes free in tree leaf pages (99% ff)
    0 Number of tree duplicate pages
    0 Number of bytes free in tree duplicate pages (0% ff)
    0 Number of tree overflow pages
    0 Number of bytes free in tree overflow pages (0% ff)
    0 Number of empty pages
    0 Number of pages on the free list
    db_stat -E <dbfile>
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Default database environment information:
    4.3.28 Environment version
    0x120897 Magic number
    0 Panic value
    2 References
    0 The number of region locks that required waiting (0%)
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Per region database environment information:
    Mpool Region:
    2 Region ID
    -1 Segment ID
    1MB 264KB Size
    0 The number of region locks that required waiting (0%)
    Log Region:
    3 Region ID
    -1 Segment ID
    1MB 64KB Size
    0 The number of region locks that required waiting (0%)
    Transaction Region:
    4 Region ID
    -1 Segment ID
    16KB Size
    0 The number of region locks that required waiting (0%)
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    DB_ENV handle information:
    Set Errfile
    db_stat Errpfx
    !Set Errcall
    !Set Feedback
    !Set Panic
    !Set Malloc
    !Set Realloc
    !Set Free
    Verbose flags
    !Set App private
    !Set App dispatch
    !Set Home
    !Set Log dir
    /integhome/jobin/B064_July2/runEnv/temp Tmp dir
    !Set Data dir
    0660 Mode
    DB_INIT_LOG, DB_INIT_MPOOL, DB_INIT_TXN, DB_USE_ENVIRON Open flags
    !Set Lockfhp
    Set Rec tab
    187 Rec tab slots
    !Set RPC client
    0 RPC client ID
    0 DB ref count
    -1 Shared mem key
    400 test-and-set spin configuration
    !Set DB handle mutex
    !Set api1 internal
    !Set api2 internal
    !Set password
    !Set crypto handle
    !Set MT mutex
    DB_ENV_LOG_AUTOREMOVE, DB_ENV_OPEN_CALLED Flags
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Default logging region information:
    0x40988 Log magic number
    10 Log version number
    1MB Log record cache size
    0660 Log file mode
    1Mb Current log file size
    632B Log bytes written
    632B Log bytes written since last checkpoint
    1 Total log file writes
    0 Total log file write due to overflow
    1 Total log file flushes
    1 Current log file number
    42872 Current log file offset
    1 On-disk log file number
    42872 On-disk log file offset
    1 Maximum commits in a log flush
    1 Minimum commits in a log flush
    1MB 64KB Log region size
    0 The number of region locks that required waiting (0%)
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Log REGINFO information:
    Log Region type
    3 Region ID
    __db.003 Region name
    0xc00000000b774000 Original region address
    0xc00000000b774000 Region address
    0xc00000000b883dd0 Region primary address
    0 Region maximum allocation
    0 Region allocated
    REGION_JOIN_OK Region flags
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    DB_LOG handle information:
    !Set DB_LOG handle mutex
    0 Log file name
    !Set Log file handle
    Flags
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    LOG handle information:
    0 file name list mutex (0%)
    0x40988 persist.magic
    10 persist.version
    0 persist.log_size
    0660 persist.mode
    1/42872 current file offset LSN
    1/42872 first buffer byte LSN
    0 current buffer offset
    42872 current file write offset
    68 length of last record
    0 log flush in progress
    0 Log flush mutex (0%)
    1/42872 last sync LSN
    1/41475 cached checkpoint LSN
    1MB log buffer size
    1MB log file size
    1MB next log file size
    0 transactions waiting to commit
    1/0 LSN of first commit
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    LOG FNAME list:
    0 File name mutex (0%)
    1 Fid max
    ID Name Type Pgno Txnid DBP-info
    0 configserviceDB btree 0 0 No DBP 0 0 0
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Default cache region information:
    1MB 262KB 960B Total cache size
    1 Number of caches
    1MB 264KB Pool individual cache size
    0 Maximum memory-mapped file size
    0 Maximum open file descriptors
    0 Maximum sequential buffer writes
    0 Sleep after writing maximum sequential buffers
    0 Requested pages mapped into the process' address space
    43312 Requested pages found in the cache (89%)
    4968 Requested pages not found in the cache
    640 Pages created in the cache
    4965 Pages read into the cache
    621 Pages written from the cache to the backing file
    4818 Clean pages forced from the cache
    621 Dirty pages forced from the cache
    0 Dirty pages written by trickle-sync thread
    166 Current total page count
    146 Current clean page count
    20 Current dirty page count
    131 Number of hash buckets used for page location
    53888 Total number of times hash chains searched for a page
    4 The longest hash chain searched for a page
    92783 Total number of hash buckets examined for page location
    0 The number of hash bucket locks that required waiting (0%)
    0 The maximum number of times any hash bucket lock was waited for
    0 The number of region locks that required waiting (0%)
    5615 The number of page allocations
    10931 The number of hash buckets examined during allocations
    22 The maximum number of hash buckets examined for an allocation
    5439 The number of pages examined during allocations
    11 The max number of pages examined for an allocation
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Pool File: temporary
    1024 Page size
    0 Requested pages mapped into the process' address space
    43245 Requested pages found in the cache (99%)
    1 Requested pages not found in the cache
    635 Pages created in the cache
    0 Pages read into the cache
    617 Pages written from the cache to the backing file
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Pool File: configserviceDB
    8192 Page size
    0 Requested pages mapped into the process' address space
    65 Requested pages found in the cache (1%)
    4965 Requested pages not found in the cache
    1 Pages created in the cache
    4965 Pages read into the cache
    0 Pages written from the cache to the backing file
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Mpool REGINFO information:
    Mpool Region type
    2 Region ID
    __db.002 Region name
    0xc00000000b632000 Original region address
    0xc00000000b632000 Region address
    0xc00000000b773f08 Region primary address
    0 Region maximum allocation
    0 Region allocated
    REGION_JOIN_OK Region flags
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    MPOOL structure:
    0/0 Maximum checkpoint LSN
    131 Hash table entries
    64 Hash table last-checked
    48905 Hash table LRU count
    48914 Put counter
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    DB_MPOOL handle information:
    !Set DB_MPOOL handle mutex
    1 Underlying cache regions
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    DB_MPOOLFILE structures:
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    MPOOLFILE structures:
    File #1: temporary
    0 Mutex (0%)
    0 Reference count
    18 Block count
    634 Last page number
    0 Original last page number
    0 Maximum page number
    0 Type
    0 Priority
    0 Page's LSN offset
    32 Page's clear length
    0 0 0 0 0 0 0 8 0 0 0 0 0 0 0 f8 0 0 0 0 ID
    deadfile, file written Flags
    File #2: configserviceDB
    0 Mutex (0%)
    1 Reference count
    148 Block count
    4965 Last page number
    4964 Original last page number
    0 Maximum page number
    0 Type
    0 Priority
    0 Page's LSN offset
    32 Page's clear length
    0 0 b6 59 40 1 0 2 39 ac 13 6f 0 a df 18 0 0 0 0 ID
    file written Flags
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Cache #1:
    BH hash table (131 hash slots)
    bucket #: priority, mutex
    pageno, file, ref, LSN, mutex, address, priority, flags
    bucket 0: 47385, 0/0%:
    4813, #2, 0, 0/1, 0/0%, 0x04acf0, 47385
    4944, #2, 0, 0/0, 0/0%, 0x020c18, 48692

  • Studio12/dbx: access checking broken for setlocate() call in "de" locale

    It seems that access checking crashes the dbx target
    when it is running in the "de" locale and a call to setlocale()
    is used.
    % dbx -V
    Sun Dbx Debugger 7.6 SunOS_i386 2007/05/03
    (running on opensolaris x86 / build 68)
    % locale
    LANG=de_DE.ISO8859-1
    LC_CTYPE=de_DE.ISO8859-1
    LC_NUMERIC=de_DE.ISO8859-1
    LC_TIME=de_DE.ISO8859-1
    LC_COLLATE=de_DE.ISO8859-1
    LC_MONETARY=de_DE.ISO8859-1
    LC_MESSAGES=de_DE.ISO8859-1
    LC_ALL=de_DE.ISO8859-1
    % cat hello.c
    #include <stdio.h>
    #include <stdlib.h>
    #include <locale.h>
    void
    func(void)
    int i;
    printf("hello, world!\n%d\n", i);
    int
    main(int argc, char **argv)
    char x[32768];
    long *p = malloc(32768);
    int i;
    long s;
    setlocale(LC_ALL, "");
    for (i = 0; i < 32768 / sizeof(long); i++)
    s += p;
    printf("%ld\n", s);
    func();
    exit(1);
    % cc -g -o hello hello.c
    % bcheck -access hello
    Reading hello
    Reading ld.so.1
    Reading rtcapihook.so
    Reading libc.so.1
    Reading libdl.so.1
    Reading rtcaudit.so
    Reading libmapmalloc.so.1
    Reading libgen.so.1
    Reading libm.so.2
    Reading rtcboot.so
    Reading librtc.so
    access checking - ON
    Running: hello
    (process id 1662)
    RTC: Enabling Error Checking...
    RTC: Running program...
    Reading disasm.so
    Reading de_DE.ISO8859-1.so.3
    terminating signal 11 SIGSEGV
    % dbx -C hello
    Reading hello
    Reading ld.so.1
    Reading rtcapihook.so
    Reading libc.so.1
    Reading libdl.so.1
    Reading rtcaudit.so
    Reading libmapmalloc.so.1
    Reading libgen.so.1
    Reading libm.so.2
    Reading rtcboot.so
    Reading librtc.so
    (dbx) check -all
    access checking - ON
    memuse checking - ON
    (dbx) run
    Running: hello
    (process id 1668)
    RTC: Enabling Error Checking...
    RTC: Running program...
    Reading disasm.so
    Reading de_DE.ISO8859-1.so.3
    terminating signal 11 SIGSEGV
    (dbx) where
    dbx: program is not active
    There's a new core dump in the current
    directory:
    % pstack /tmp/core
    core '/tmp/core' of 1952: /tmp/hello
    ee188106 clearinternal_mbstate (803ed8c, 803ec28, ee1c0837, 803ed8c, ee1f5000, f) + 21
    ee1c067f __charmap_init (803ed8c, ee1f5000, f, 10, 803ef38, ee1bca1f) + 27
    ee1c0837 __locale_init (803ed8c) + 27
    ee1bca1f setlocale (6, 8050b74, 0, 0, 8060d48, 0) + 9ff
    08050a9a main (1, 8046f8c, 8046f94, ee1fa540, 8046f80, 805095f) + 2a
    080509bd _start   (1, 8047134, 0, 804713f, 804715a, 80471b8) + 7d
    % pflags /tmp/core
    core '/tmp/core' of 1952: /tmp/hello
    data model = _ILP32  flags = RLC|BPTADJ|MSACCT|MSFORK
    flttrace = 0x00000004
    sigtrace = 0xfffffeff 0xffffffff
    HUP|INT|QUIT|ILL|TRAP|ABRT|EMT|FPE|BUS|SEGV|SYS|PIPE|ALRM|TERM|USR1|USR2|CLD|PWR|WINCH|URG|POLL|STOP|TSTP|CONT|TTIN|TTOU|VTALRM|PROF|XCPU|XFSZ|WAITING|LWP|FREEZE|THAW|CANCEL|LOST|XRES|JVM1|JVM2|RTMIN|RTMIN+1|RTMIN+2|RTMIN+3|RTMAX-3|RTMAX-2|RTMAX-1|RTMAX
    entryset = 0x00000403 0x04000000 0x00000000 0x00400000
    0x80004000 0x00000000 0x00000000 0x00000000
    exitset = 0x00000002 0x00000000 0x00000000 0x00400000
    0x40004000 0x00000000 0x00000000 0x00000000
    /1: flags = 0
    sigmask = 0xfffffeff,0x0000ffff cursig = SIGSEGV
    Workaround: run access checking in the "C" locale.

    The cause might be the same - nested signals. Dbx
    replaces memory access instructions with an
    instruction that generates SIGSEGV; when it happens,
    signal handler installed by dbx is invoked and it
    performs all necessary checks. If the application
    tries to install its own handler for SIGSEGV, it
    might fail, thus the "Terminating signal 11"
    message.I'm not sure I understand this. My sample programs do
    not install SIGSEGV handlers.
    But I can imagine that the issue is that dbx rtc is trying
    to use setlocale(), nl_langinfo(), getexecname() while
    running in the SIGSEGV handler, checking the memory
    access (maybe because rtc has found some problem
    and is trying to report it), and now trips over the patched
    memory access instructions in these functions.
    And indeed, using the dbx commands
    (dbx) check -all
    (dbx) rtc skippatch libc.so.1 -f setlocale nl_langinfo getexecname thrkeycreate_once thrkeycreate_once pthread_key_create_once_np pthreadkey_create_once_np
    seems to work around these issues.
    The only possible fix for this is to skip
    instrumentation of functions that can cause nested
    signals; there's built-in command for that in dbx,
    rtc skippatch (type 'help rtc skippatch' in dbx to
    see more info) and there's internal list of such
    functions, which is frequently updated. However, it
    is not always easy to determine which function should
    not be instrumented.
    So if you find more errors like this, please report
    them here.readdir64_r() is the next one:
    % cat readdir.c
    #define POSIXPTHREAD_SEMANTICS 1
    #include <sys/types.h>
    #include <dirent.h>
    int
    main(int argc, char **argv)
    struct dirent dent, *dent_result;
    DIR *dir = opendir("/");
    readdir_r(dir, &dent, &dent_result);
    % cc -g -o readdir readdir.c `getconf LFS_CFLAGS`
    % bcheck -access readdir
    Reading readdir
    Reading ld.so.1
    Reading rtcapihook.so
    Reading libc.so.1
    Reading libdl.so.1
    Reading rtcaudit.so
    Reading libmapmalloc.so.1
    Reading libgen.so.1
    Reading libm.so.2
    Reading rtcboot.so
    Reading librtc.so
    access checking - ON
    Running: readdir
    (process id 4269)
    RTC: Enabling Error Checking...
    RTC: Running program...
    Reading disasm.so
    terminating signal 11 SIGSEGV
    % pstack core
    core 'core' of 4269: /tmp/readdir
    ee166897 readdir64_r (fefa0300, 8046f40, 8046f3c, fefa0300, ee1fcdf0, 133f) + 27
    08050a29 main (1, 8046f88, 8046f90, 8046f7c, 805090f, 8050a60) + 29
    0805096d _start   (1, 8047130, 0, 804713d, 8047158, 80471b6) + 7d                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Application dumps core on solaris with BDB 4.6.21

    Hi,
    my application dumps core on solaris during the appication startup:
    The solaris box detail is :
    SunOS wcturgo3 5.10 Generic_137111-08 sun4v sparc SUNW,Netra-T5220.
    I compiled the BDB with the following configuration:
    ./buildall.sh -p solaris -c cc -x CC -m gmake
    the core file loks like :
    fdc28c68 __db_pthread_mutex_init (50878, 0, 13, 0, ffbfca18, 0) + 88
    fdca3bec __mutex_open (50878, 271638, 2058000, fdd47d1c, 271490, 0) + 224
    fdce56ec __env_open (50878, 0, 880081, 8a0081, 0, 0) + 3bc
    fdc206f4 int DbEnv::open(const char*,unsigned,int) (502f0, 0, 880081, 0, 502f0, fdce50c4) + 5c
    fcb12824 void DbXml::Manager::initTempDbEnv(DbEnv*) (502d8, 503e0, 0, 15540, fe03c9f8, aa878) + 144
    fcb11ea0 DbXml::Manager::Manager #Nvariant 1(unsigned) (502d8, 0, fe2ae760, 15540, fe03c9f8, 502d8) + 430
    fcb059ec DbXml::XmlManager::XmlManager #Nvariant 1() (fe3697ec, fcdef0c0, fcdee994, 40, 13080, 0) + 24
    fe234d68 NemiConfigToolInit::NemiConfigToolInit #Nvariant 1() (fe3697d4, 0, 0, 0, 0, fe36957c) + 60
    fe2ae760 ???????? (0, 0, 0, 0, 0, 0)
    fe2aeb04 ???????? (0, fc665440, aca5c, fe0272cc, fc665400, fe369544)
    fe2f77d0 _init    (ff3f40fc, ff3f5a70, 2b3f4, 0, ff3f4910, 821) + f8
    ff3c5280 call_init (60c10081, 1, ff2f0788, fe2f76d8, ff3f4910, ffdfffff) + 16c
    ff3c47e8 setup (200000, 2801, 602, ff3f40fc, 60c10001, 446) + 1568
    ff3d35cc _setup   (10034, ffffffff, 0, ff3b0000, ffffffff, ffffffff) + 40c
    ff3b8480 rtboot (0, 0, 0, 0, 0, 0) + 88
    00000000 ???????? (0, 0, 0, 0, 0, 0)
    i tried using dbxml build with this BDB. i was able to execute one or two commands without the dbxml dumping core.
    But my application dumps core during startup as sigbus (memory alignment issue).
    I googled and found that people have faced problems of sigbus on solaris. when i checked with solaris, it seems that if the solaris box has 137111-0 to 137111-08 will face core dumps due to memory alignment issue which they say is because the application has misaligned mutex.
    please suggest what should i do .
    a)apply the sloaris kernel patch to temporary solution(as they claim the patch for thsi problem will give temporary solution .)
    b) i have to compile the BDB with different options.

    Hello,
    You need to apply the patch below on top of Berkeley
    DB 4.6.21:
    *** dbinc/mutex_int.h     Tue Jul 01 15:03:43 2008 +1000
    --- dbinc/mutex_int.h     Tue Jul 01 16:11:06 2008 +1000
    *** 616,621 ****
    --- 616,623 ----
    #ifdef HAVE_MUTEX_SPARC_GCC_ASSEMBLY
    typedef unsigned char tsl_t;
    +
    + #define     MUTEX_ALIGN     8
    #ifdef LOAD_ACTUAL_MUTEX_CODE
    This corrects a Solaris-only alignment problem.
    Thanks,
    Sandra

  • Oracle Accessibility Checker with JDeveloper

    HI All,
    At http://www.oracle.com/accessibility/index.html, there is a statement related to the accessibility issue with JDeveloper: "Oracle Accessibility Checker (TM) coming in 2005 as plugin to JDeveloper 10.1.3".
    Does anyone know if it is true that this "Oracle Accessibility Checker" is available for JDeveloper 10.1.3??
    Or does anyone has any information on how to carry out an accessibility test on a JDeveloper application?
    Please help! I need these information ASAP!
    Thank you in advance for any suggestion, advice, or inforamtion.
    Qian

    Forms,
    I don't really have a demo per se, but it's not so hard.
    For example, say http://foo:7777/reports/whatever?param=foo&param2=bar is the URL. Simply put an af:goLink on your page and set its target to http://foo:7777/reports/whatever?param=#{an_el_expression_that_evaluates_to_the_parameter_value}&param2=#{ditto}
    Just treat them like a web link.
    john

  • Core (4500x vss) with Access HP switch spanning tree

    Hello Friends,
    i need your support to guide me for this type of topology network in-order to avoid loops...
    like
    2  4500X series switch configure as a VSS working as core switch
    in access layer i have HP switches which are connected with 1G fiber uplinks to each other (cascaded) and back to these Core switch for Vlan forwarding.
    i need help to configure  spanning tree  for such topology and avoid loops.
    Topology is in attached..

    Hi,
    you mean to say, connect each HP switch back to core (VSS) with 2 uplinks and configure as a ether-channel?
    Yes, exactly.
    actually that is  not possible because the lack of fiber cable between the cabinets (core to access) are not much cores.
    How could it not be possible? According to your drawing in your current design ASW-HP1 and ASW-HP3 both connect to the core VSS, core anyway. So it is just a matter of connecting ASW-HP2 to the core.
    Of course you want 2 uplinks from each HP.
    HTH

  • Studio 12 DBX  internal error while memcheck is on.

    bash-3.00$ dbx -xexec32
    For information about new features see `help changes'
    To remove this message, put `dbxenv suppress_startup_message 7.6' in your .dbxrc
    (dbx) -rwxr-xr-x 1 orbit osgrp1 1.2M Dec 26 17:18 <my_processnmae>
    -rwxr-xr-x: not found
    (dbx) dbxenv mt_sync_tracking off
    (dbx) attach 6792 <this is pid>
    Reading <my_processname>
    Reading ld.so.1
    Reading librtc.so
    Reading libmapmalloc.so.1
    Reading libcurses.so.1
    Reading libnsl.so.1
    Reading libsocket.so.1
    Reading libelf.so.1
    Reading libcrypt_i.so.1
    Reading libpthread.so.1
    Reading libdl.so.1
    Reading librt.so.1
    Reading libc.so.1
    Reading libgen.so.1
    Reading libaio.so.1
    Reading libmd5.so.1
    Reading libc_psr.so.1
    Reading library_name**
    Reading library_name**
    Attached to process 6792 with 3 LWPs
    t@1 (l@1) stopped in soaccept at 0xff040314
    0xff040314: soaccept+0x0004: ta %icc,0x00000008
    Current function is Tcp_receive
    284 if ((th_data->sockfd = accept (sockfd, (struct sockaddr *)&clientaddr,&length)) == -1)
    (dbx) check -access
    access checking - ON
    RTC: Enabling Error Checking...
    RTC: Running program...
    (dbx) cont
    RTC: internal RTC error -- disabling Error Checking file: rtc_heap_map.c line: 697
    ^Ct@2 (l@2) signal INT (Interrupt) in ___sigtimedwait at 0xff040220
    0xff040220: ___sigtimedwait+0x0004: ta %icc,0x00000008
    Current function is sig_thr
    1256 sigwait (&glb_sigact, &signal_alr);
    (dbx) version
    Machine hardware: sun4u
    OS version: 5.10
    Processor type: sparc
    Hardware: SUNW,Sun-Fire-280R
    The following components are installed on your system:
    Sun Studio 12
    Sun Studio 12 C Compiler
    Sun Studio 12 C++ Compiler
    Sun Studio 12 Tools.h++ 7.1
    Sun Studio 12 C++ Standard 64-bit Class Library
    Sun Studio 12 Garbage Collector
    Sun Studio 12 Fortran 95
    Sun Studio 12 Debugging Tools (including dbx)
    Sun Studio 12 IDE
    Sun Studio 12 Debugger GUI
    Sun Studio 12 Performance Analyzer (including collect, ...)
    Sun Studio 12 X-Designer
    Sun Studio 12 VIM editor
    Sun Studio 12 XEmacs editor
    Sun Studio 12 Performance Library
    Sun Studio 12 LockLint
    Sun Studio 12 Building Software (including dmake)
    Sun Studio 12 Documentation Set
    Sun Studio 12 /usr symbolic links and GNOME menu item
    version of "/opt/SunStudio12/SUNWspro/bin/../prod/bin/../../bin/cc": Sun C 5.9 SunOS_sparc 2007/05/03
    version of "/opt/SunStudio12/SUNWspro/bin/../prod/bin/../../bin/CC": Sun C++ 5.9 SunOS_sparc 2007/05/03
    version of "/opt/SunStudio12/SUNWspro/bin/../prod/bin/../../bin/f90": Sun Fortran 95 8.3 SunOS_sparc 2007/05/03
    version of "/opt/SunStudio12/SUNWspro/bin/../prod/bin/../../bin/dbx": Sun Dbx Debugger 7.6 SunOS_sparc 2007/05/03
    version of "/opt/SunStudio12/SUNWspro/bin/../prod/bin/../../bin/analyzer": Sun Analyzer 7.6 SunOS_sparc 2007/05/03
    version of "/opt/SunStudio12/SUNWspro/bin/../prod/bin/../../bin/dmake": Sun Distributed Make 7.8 SunOS_sparc 2007/05/03
    any Idea ?
    am i doing something wrong here. ? I want to check memory leak. ?
    -Raxit

    With hope if its bug, below may helpful.
    (dbx) (dbx) (dbx) quit
    detaching from process 6792
    dbx: internal warning: function (__rtc_release_heap_region) called too early (preloading)
    t@3 (l@3) signal SEGV (no mapping at the fault address) in _sleep at 0xff0330f0
    0xff0330f0: _sleep+0x0078:      ldsb     [%o3 - 3005], %o2
    Current function is scansessionisam_thr
    1362 sleep (cfg_sec_shm_scantime); /*SCF no 10750 */
    execution completed, exit code is 4982056
    dbx: internal warning: rtc: _syscall: failed
    dbx: warning: librtc.so and dbx version mismatch; Error checking disabled
    Check your installation of librtc.so.
    dbx: internal warning: rtc: munmap of patch area of segment '/usr/lib/libmapmalloc.so.1' failed
    dbx: internal error: signal SIGSEGV (no mapping at the fault address)
    dbx's coredump will appear in /tmp
    ls -lrAbort (core dumped)
    bash-3.00$ pstack /tmp/core
    core '/tmp/core' of 6794: dbx -xexec32
    ff1c0f90 lwpkill (6, 0, ff1a4a98, ffffffff, ff1e8284, 6) + 8
    ff13ff98 abort (0, 1, 377d74, a83f0, ff1eb298, 0) + 110
    000b5bf8 ???????? (b, 3c4400, 4575a1, 38b1f4, 37eabe, 1)
    ff1bfec8 __sighndlr (b, ffbff408, ffbff150, b59ec, 0, 1) + c
    ff1b4ff4 call_user_handler (b, 0, 8, 0, ff252000, ffbff150) + 3b8
    001aef98 __1cGRtcMgrShandle_proc_detach6M_v_ (47d670, 5dd2a8, 38, 396000, 4c0498, 38) + d8
    0018f850 __1cEProcGdetach6Mbbbb_v_ (4c0468, 467400, 466400, 0, 3ae2ac, 0) + 19c
    000b8c68 ???????? (47e6f8, 0, 0, 0, 0, 1)
    00289d94 __1cMpdksh_c_exit6FpnGInterp_ippcpv_i_ (47e6f8, 0, 876890, 0, 0, 466000) + a8
    0015fbf4 ???????? (47e6f8, 1, 876890, 0, 877b78, 0)
    002857a0 ???????? (47e6f8, 877b78, 877b58, 876890, 0, 467708)
    0028468c __1cNpdksh_execute6FpnGInterp_pnCop_i_i_ (47e6f8, 49bab8, 0, 277c50, 47e6f8, 38b1f4) + 194
    002735e0 __1cLpdksh_shell6FpnGInterp_pnGSource__i_ (47e6f8, 49e098, 465628, 446f54, 3d9625, 3d962c) + 46c
    000b90d4 __1cNmain_cmd_loop6FpnGInterp__v_ (47e6f8, 37f400, 3ca2a4, 446f70, 3ca000, 3ca000) + 88
    000b9e60 main (37e400, 0, 40, 47e6f8, 37f7c8, 1) + 750
    000af268 _start   (0, 0, 0, 0, 0, 0) + 108
    bash-3.00$
    bash-3.00$ dbx /opt/SunStudio12/
    SUNWspro/ uninstall_Sun_Studio_12.class
    bash-3.00$ dbx /opt/SunStudio12/SUNWspro/bin/dbx /tmp/core
    For information about new features see `help changes'
    To remove this message, put `dbxenv suppress_startup_message 7.6' in your .dbxrc
    Reading dbx
    core file header read successfully
    Reading ld.so.1
    Reading libintl.so.1
    Reading libnsl.so.1
    Reading libsocket.so.1
    Reading libdl.so.1
    Reading libgen.so.1
    Reading libw.so.1
    Reading libm.so.1
    Reading libc.so.1
    Reading libc_psr.so.1
    Reading libcpc.so.1
    Reading libpctx.so.1
    Reading libnvpair.so.1
    Reading libdevinfo.so.1
    Reading libproc.so.1
    Reading librtld_db.so.1
    Reading libelf.so.1
    Reading libctf.so.1
    program terminated by signal ABRT (Abort)
    0xff1c0f90: __lwp_kill+0x0008: bcc,a,pt %icc,__lwp_kill+0x18 ! 0xff1c0fa0
    (dbx) threads
    dbx: thread related commands not available
    (dbx) where
    =>[1] __lwp_kill(0x0, 0x6, 0x0, 0x6, 0xfc00, 0x0), at 0xff1c0f90
    [2] raise(0x6, 0x0, 0xff1a4a98, 0xffffffff, 0xff1e8284, 0x6), at 0xff15fd78
    [3] abort(0x0, 0x1, 0x377d74, 0xa83f0, 0xff1eb298, 0x0), at 0xff13ff98
    [4] 0xb5bf8(0xb, 0x3c4400, 0x4575a1, 0x38b1f4, 0x37eabe, 0x1), at 0xb5bf8
    [5] __sighndlr(0xb, 0xffbff408, 0xffbff150, 0xb59ec, 0x0, 0x1), at 0xff1bfec8
    ---- called from signal handler with signal 11 (SIGSEGV) ------
    [6] RtcMgr::handle_proc_detach(0x47d670, 0x5dd2a8, 0x38, 0x396000, 0x4c0498, 0x38), at 0x1aef98
    [7] Proc::detach(0x4c0468, 0x467400, 0x466400, 0x0, 0x3ae2ac, 0x0), at 0x18f850
    [8] 0xb8c68(0x47e6f8, 0x0, 0x0, 0x0, 0x0, 0x1), at 0xb8c68
    [9] pdksh_c_exit(0x47e6f8, 0x0, 0x876890, 0x0, 0x0, 0x466000), at 0x289d94
    [10] 0x15fbf4(0x47e6f8, 0x1, 0x876890, 0x0, 0x877b78, 0x0), at 0x15fbf4
    [11] 0x2857a0(0x47e6f8, 0x877b78, 0x877b58, 0x876890, 0x0, 0x467708), at 0x2857a0
    [12] pdksh_execute(0x47e6f8, 0x49bab8, 0x0, 0x277c50, 0x47e6f8, 0x38b1f4), at 0x28468c
    [13] pdksh_shell(0x47e6f8, 0x49e098, 0x465628, 0x446f54, 0x3d9625, 0x3d962c), at 0x2735e0
    [14] main_cmd_loop(0x47e6f8, 0x37f400, 0x3ca2a4, 0x446f70, 0x3ca000, 0x3ca000), at 0xb90d4
    [15] main(0x37e400, 0x0, 0x40, 0x47e6f8, 0x37f7c8, 0x1), at 0xb9e60
    (dbx)
    -Raxit

  • [SOLVED] NetworkManager dumped core

    Symptoms: WiFi randomly drops out.
    More specifically: NetworkManager core dumps and network-manager-applet stops (Gnome 3.8)
    If anyone has suggestions, I'd be grateful. I'm at a loss, other than disabling NetworkManager and enabling netctl. Details follow below.
    Thanks so much!
    uname -r
    3.9.0-2-ARCH
    uname -m
    x86_64
    lspci -v
    Network controller: Intel Corporation Centrino Advanced-N 6205
    rfkill list
    0: tpacpi_bluetooth_sw: Bluetooth
    Soft blocked: no
    Hard blocked: no
    1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
    2: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
    iwconfig
    enp0s25 no wireless extensions.
    wlp3s0 IEEE 802.11abgn ESSID:"The Way 5GHz"
    Mode:Managed Frequency:5.18 GHz Access Point: 00:26:F2:F2:E7:D5
    Bit Rate=65 Mb/s Tx-Power=15 dBm
    Retry long limit:7 RTS thr:off Fragment thr:off
    Power Management:off
    Link Quality=54/70 Signal level=-56 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:230 Invalid misc:113 Missed beacon:0
    lo no wireless extensions.
    journalctl -u NetworkManager --since=today
    -- Reboot --
    May 04 14:04:19 arch systemd[1]: Starting Network Manager...
    May 04 14:04:20 arch NetworkManager[284]: <info> NetworkManager (version 0.9.8.0) is starting...
    May 04 14:04:20 arch NetworkManager[284]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
    May 04 14:04:20 arch NetworkManager[284]: <info> WEXT support is enabled
    May 04 14:04:21 arch NetworkManager[284]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager ma
    May 04 14:04:21 arch NetworkManager[284]: keyfile: parsing Auto The Way 5GHz ...
    May 04 14:04:21 arch NetworkManager[284]: keyfile: read connection 'Auto The Way 5GHz'
    May 04 14:04:21 arch NetworkManager[284]: <info> monitoring kernel firmware directory '/lib/firmware'.
    May 04 14:04:21 arch NetworkManager[284]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/ieee80211/
    May 04 14:04:21 arch NetworkManager[284]: <info> WiFi hardware radio set enabled
    May 04 14:04:21 arch systemd[1]: Started Network Manager.
    May 04 14:04:21 arch NetworkManager[284]: <info> WiFi enabled by radio killswitch; enabled by state file
    May 04 14:04:21 arch NetworkManager[284]: <info> WWAN enabled by radio killswitch; enabled by state file
    May 04 14:04:21 arch NetworkManager[284]: <info> WiMAX enabled by radio killswitch; enabled by state file
    May 04 14:04:21 arch NetworkManager[284]: <info> Networking is enabled by state file
    May 04 14:04:21 arch NetworkManager[284]: <warn> failed to allocate link cache: (-10) Operation not supported
    May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): carrier is OFF
    May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): new Ethernet device (driver: 'e1000e' ifindex: 3)
    May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): exported as /org/freedesktop/NetworkManager/Devices/0
    May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): bringing up device.
    May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): preparing device.
    May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): deactivating device (reason 'managed') [2]
    May 04 14:04:21 arch NetworkManager[284]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:19.0/net/enp0
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): using nl80211 for WiFi device control
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): driver supports Access Point (AP) mode
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 2)
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): exported as /org/freedesktop/NetworkManager/Devices/1
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): bringing up device.
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): preparing device.
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): deactivating device (reason 'managed') [2]
    May 04 14:04:21 arch NetworkManager[284]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
    May 04 14:04:21 arch NetworkManager[284]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
    May 04 14:04:21 arch NetworkManager[284]: <warn> error poking ModemManager: GDBus.Error:org.freedesktop.systemd1.LoadFailed: Unit dbus-org.freedesktop
    May 04 14:04:21 arch NetworkManager[284]: <info> wpa_supplicant started
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0) supports 5 scan SSIDs
    May 04 14:04:21 arch NetworkManager[284]: <warn> Trying to remove a non-existant call id.
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: starting -> ready
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: ready -> disconnected
    May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0) supports 5 scan SSIDs
    May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: disconnected -> inactive
    May 04 14:04:25 arch NetworkManager[284]: <info> Auto-activating connection 'Auto The Way 5GHz'.
    May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) starting connection 'Auto The Way 5GHz'
    May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) scheduled...
    May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) started...
    May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) scheduled...
    May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) complete.
    May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) starting...
    May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): device state change: prepare -> config (reason 'none') [40 50 0]
    May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0/wireless): connection 'Auto The Way 5GHz' has security, and secrets exist. No new
    May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'ssid' value 'The Way 5GHz'
    May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'scan_ssid' value '1'
    May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
    May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'auth_alg' value 'OPEN'
    May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'psk' value '<omitted>'
    May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) complete.
    May 04 14:04:25 arch NetworkManager[284]: <info> Config: set interface ap_scan to 1
    May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: inactive -> scanning
    May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: scanning -> authenticating
    May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: authenticating -> associating
    May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: associating -> associated
    May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: associated -> completed
    May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless netwo
    May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) scheduled.
    May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) started...
    May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): device state change: config -> ip-config (reason 'none') [50 70 0]
    May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
    May 04 14:04:28 arch NetworkManager[284]: <info> dhcpcd started with pid 447
    May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Beginning IP6 addrconf.
    May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) complete.
    May 04 14:04:28 arch dhcpcd[447]: version 5.6.8 starting
    May 04 14:04:28 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
    May 04 14:04:28 arch dhcpcd[447]: [color=#FF0000]wlp3s0: sendmsg: Cannot assign requested address[/color]
    May 04 14:04:28 arch dhcpcd[447]: wlp3s0: rebinding lease of 192.168.10.59
    May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): DHCPv4 state changed nbi -> preinit
    May 04 14:04:28 arch dhcpcd[447]: wlp3s0: acknowledged 192.168.10.59 from 192.168.10.1
    May 04 14:04:28 arch dhcpcd[447]: wlp3s0: checking for 192.168.10.59
    May 04 14:04:32 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
    May 04 14:04:33 arch dhcpcd[447]: wlp3s0: leased 192.168.10.59 for 86400 seconds
    May 04 14:04:33 arch NetworkManager[284]: <info> (wlp3s0): DHCPv4 state changed preinit -> bound
    May 04 14:04:33 arch NetworkManager[284]: <info> address 192.168.10.59
    May 04 14:04:33 arch NetworkManager[284]: <info> prefix 24 (255.255.255.0)
    May 04 14:04:33 arch NetworkManager[284]: <info> gateway 192.168.10.1
    May 04 14:04:33 arch NetworkManager[284]: <info> nameserver '192.168.10.1'
    May 04 14:04:33 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    May 04 14:04:33 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Commit) started...
    May 04 14:04:34 arch NetworkManager[284]: <info> (wlp3s0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
    May 04 14:04:34 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Commit) complete.
    May 04 14:04:34 arch NetworkManager[284]: <info> (wlp3s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
    May 04 14:04:34 arch NetworkManager[284]: <info> Policy set 'Auto The Way 5GHz' (wlp3s0) as default for IPv4 routing and DNS.
    May 04 14:04:34 arch NetworkManager[284]: <info> Writing DNS information to /usr/sbin/resolvconf
    May 04 14:04:34 arch NetworkManager[284]: <info> (wlp3s0): roamed from BSSID 90:27:E4:5E:98:24 (The Way 5GHz) to 00:26:F2:F2:E7:D5 (The Way 5GHz)
    May 04 14:04:34 arch NetworkManager[284]: <info> Activation (wlp3s0) successful, device activated.
    May 04 14:04:36 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
    May 04 14:04:40 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
    May 04 14:04:40 arch dhcpcd[447]: wlp3s0: no IPv6 Routers available
    May 04 21:04:49 arch NetworkManager[284]: <info> (wlp3s0): IP6 addrconf timed out or failed.
    May 04 21:04:49 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    May 04 21:04:49 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv6 Configure Timeout) started...
    May 04 21:04:50 arch systemd[1]: NetworkManager.service: main process exited, code=dumped, status=6/ABRT
    May 04 21:04:50 arch systemd[1]: MESSAGE=Unit NetworkManager.service entered failed state.
    May 04 21:04:50 arch systemd-coredump[1036]: [color=#FF0000]Process 284 (NetworkManager) dumped core.[/color]
    journalctl -u wpa_supplicant --since=today
    -- Reboot --
    May 04 14:04:21 arch systemd[1]: Starting WPA supplicant...
    See dmesg at Pastebin
    [edited May 7, 2013]
    I'm marking this topic SOLVED, though more accurately, I should say that I've worked around the problem.
    I achieved a stable wireless connection by changing APs, which leads me to believe that the underlying problem is upstream. Specifically, the problem is most likely that NetworkManager is not compatible with all APs. In my case, when I connect to a Netgear NDR3700v1 running dd-wrt, NetworkManager and nn-applet crashed randomly and frequently. However, after changing to an Apple Airport AP, I achieved a stable connection without crashes.
    Bottomline: if you experience wireless connection troubles with NetworkManager and nm-applet, the problem may be that NetworkManager is not "compatible" with your AP hardware.
    Last edited by hcra (2013-05-07 20:50:36)

    b1tgl0w wrote:Is it normal for crond to run as the root user?
    Completely normal. I'd be asking the question "was I hacked" if I found cron NOT running as root.
    I'd say your computer just crashed.

  • Mdb dumps core (duh)

    While attempting to resolve a problem with mod_ssl vs. Sun Apache-1.3.27 (SUNWapch{d,r,u} with patch 113246-02), I decided to run apache trough mdb.
    # mdb /usr/apache/bin/httpd
    Loading modules: [ libc.so.1 ]
    :cmdb: fork1 detected: follow (p)arent or (c)hild? c
    mdb: target forked child process 135 (debugger following child)
    Segmentation Fault (core dumped)
    # file core
    core: ELF 32-bit MSB core file SPARC Version 1, from 'mdb'
    # pstack core
    core 'core' of 219: mdb /usr/apache/bin/httpd
    ff30d028 ps_ptread (0, ff3f8000, ffbfe4fc, 2c, 0, 0) + 4
    ff2e15e4 rdevent_getmsg32 (bc1f0, ffbfe5e8, 0, 0, 0, 0) + 24
    ff2e0ba8 rd_event_getmsg (bc1f0, ffbfe5e8, 0, 0, 20, 0) + 14
    0003ce8c pt_rtld_event (a7ad8, fffffff8, 0, 1, 4ca68, 77400) + 14
    00048c88 tgt_continue (77688, ffbfeb44, 7b9f8, 0, 0, 4014bc) + 520
    00048e10 tgt_request_continue (a7ad8, ffbfeb44, 100, 41b04, 0, 0) + 1c
    00024aa4 cmd_cont_common (0, 0, 0, 0, 48fb4, 56930) + 158
    0001f5a8 dcmd_invoke (7c498, 0, 0, 0, 0, 0) + 4c
    0001f78c mdb_call_idcmd (0, 0, 0, 1, 0, 0) + 114
    0001f0ec mdb_call (0, 0, 0, 1, 0, 83850) + 33c
    0004edc0 yyparse (53acc, 77000, 53504, 52d2c, ff676980, 130) + 63c
    0001eb5c mdb_run (0, 34c7c, 0, ffbffee2, 2f757372, 2d000000) + 274
    00035e4c main (0, 0, 77564, 43c00, 34000, 44c00) + 1078
    000189e0 _start   (0, 0, 0, 0, 0, 0) + 108
    Now if my own programs happen to dump core, that's my problem. But if the debugger itself crashes, things start to look a bit bleak indeed.
    The system in question is a SunBlade 2000, Solaris 9 with yesterday's recommended patches applied.
    Any hints?
    Regards, Paul Boven.
    P.S. although this is not a C-compiler issue in itself, I felt that this developer forum was the most appropriate place to post this.

    mdb(1) is an OS command supported with adb for
    debugging calls into the kernel. For better results,
    I recommend that this question be posted to one of
    the Solaris discussion groups. This product is not
    maintained under the Compiler Collection or Sun One
    Studio.

  • How to span vlans across core layer in core/distribution/access campus design?

    Hi,
    I studied Cisco Borderless Campus Design Guide 1.0 (http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Campus/Borderless_Campus_Network_1-0/Borderless_Campus_1-0_Design_Guide.html) last week because we plan to redesign our campus backbone to a three tier Core/Distribution/Access Design.
    Today we use a collapsed backbone where a lot of vlans are spanned across the backbone because they are needed in different buildings.
    Could anybody give me a hint how Cisco recommends to deal with that kind of vlans in the multi-tier design?
    In my eyes between core and distribution layer there is only routing functionality and no l2 transport of vlans.
    So using the same vlan in different buildings seems not to be supported?
    Best Regards,
    Thorsten

    Thorsten
    Just to add to Joseph's post.
    It is quite common for a vlan to be spanned when it doesn't actually need to be ie. the network has evolved that way.
    Most things do not need L2 adjacency, they can happily use L3. Servers sometimes do but in the campus design your servers are usually located in one site so you don't need to extend vlans to other sites in your campus.
    Not suggesting this is the case for you but it may be worth checking whether you really do. (apologies if you already have)
    As Joseph mentioned you really want to avoid it if at all possible ie. ideally all connections to the core switches are L3 ie. no need for vlans at all in the core.
    If you need to extend a few vlans then you can do this but still route for all other vlans ie. you would configure your distribution to core connections as trunks and then allow the vlans you need to extend plus one other vlan, unique per distribution pair, to route all other vlans. So per site your distribution switches route all vlans except the extended vlans and of they need to route to a vlan in another site they use that unique vlan.
    But this is not ideal because you then need to extend certain vlans across the core and because you are using L2 connections STP could come into it although that does depend on your core switch selection eg. 4500/6500 VSS etc. would alleviate this.
    There are ways to extend vlans across a L3 network but the solutions available are very much dependant on the kit you use and their capabilities so if you do need multiple vlans in multiple sites but still want to keep a L3 core you may want to investigate some of those before purchasing kit (unless of course you have already purchased it).
    What you do really depends on just how many vlans you actually need to extend between sites.
    Jon

  • Application dumps core in 64-bit but runs fine in 32-bit

    Hi,
    I have a strange problem in a application supposed to be run in 64-bit mode. The application is a batch process run as a daemon. When it is compiled with 32-bit mode, it seems to be working fine, but when it is compiled with 64-bit mode, it dumps core after 30 min to 1 hr. This is not always predictable. The data where it dumps core is also not predictable. When I analysed the core, it shows the location, in a place where there seems to be no problem. I ran purify to check the memory leaks, and there is no memory leak in the code, except in the Forte STL (string).
    The core dump happens in a place where the message is read from a message queue and is assigned to a string. (i.e. assignment from char array to string). I have made sure that the pointers are not getting deleted twice.
    I am using the following environment
    SunOS archie 5.8 Generic_108528-14 sun4u sparc SUNW,Ultra-60
    Sun WorkShop 6 update 2 Compilers C++
    Sun WorkShop 6 update 2 Standard 64-bit Class Library for C++
    If anybody has any idea about the problem, please reply to this.
    Thanks a lot,
    H.M.Joisa

    Since the Configurator doesn't include a compiler, so the flash panel generated by it doesn't have a native height and width.
    So the height and width you assigned in the Configurator is saved into the .gpc file.
    You observation is very sharp and accurate, when a panel is opened first time in the Photoshop.
    It will show the panel in the default size first, then it will load the height and width you assigned from the .gpc file, and resize it to the size you want.
    And then when you close the panel, it will save the current panel size to a flash player share object.
    The next time when you open the panel, it will load the last time saved size back.

  • Dbx dumps

    Hi,
    I have just installed Sun Studio11 for Solaris 10 x86(version 3/5).
    It works fine.
    BUT :
    After loading simple program (squares for example) using debug option in main menu,
    three debug windows show up and then error message " dbx terminated (connection with dbx failed with wait(2) errors). So it is not "hanging" of dbx reported elsewhere.
    If I start dbx simply in terminal it dumps immediately and produces core.
    Nothing has changed after updating the system using UpdateManager(I did not install 2 compiler patches , because it demanded that I remove compiler product, otherwise I updated all) .
    Andrzej

    core 'core' of 2611:     /opt/SUNWspro/bin/dbx -g sync,stdio -c dbxenv suppress_startup_message
    d2d23ce6 cpc_close (0) + 14
    080f4466 ???????? (0, 1, 186a0, 14, 0, 846d0b8)
    080f4600 ???????? (0, 0, d2d90468, 8046d18, 80f199e, 80f1900)
    080f467b hwcfuncs_open (80f1900, 837689c, 8428a94, 8428a98, 8428a9c) + 23
    080f199e ???????? (6, 846d0b8, 8047184, 8047184, 8202fd6, 8047350)
    080f326c hwc_get_cpc_cpuver (8047350, 804724c, 83884c0, 0, 804717c, 6e6b6e75) + 14
    08202fd6 __1cJColl_Ctrl2t5B6Mi_v_ (846d0b8, 1) + 11e
    08200333 __1cMsp_new_state6FpnGTarget__pnLDbxCollCtrl__ (83884c0) + 27
    080f9b42 main (5, 804724c, 8047264) + 13e
    080f0e0a _start   (5, 80473b8, 80473ce, 80473d1, 80473dc, 80473df) + 7a
    Another observation :
    In the meantime I have made reinstall of the system using upgrade option.
    Reinstall was broken, not all was installed. BUT dbx worked fine !!!!(It was preserved)
    After reinstalling with "INITIAL" option system is OK but dbx dumps as before(I have installed sunstudio of course once again).
    It could suggest some problems with shared libraries.
    Andrzej

  • Cupsd dumped core

    from time to time, starting of cupsd fails here and I have no idea why:
    [root@arch64-1]# systemctl status cups
    cups.service - CUPS Printing Service
    Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled)
    Active: failed (Result: core-dump) since Di 2013-09-03 21:12:38 CEST; 4min 19s ago
    Process: 948 ExecStart=/usr/bin/cupsd -f (code=dumped, signal=ABRT)
    Sep 03 21:12:38 arch64-1.xxx systemd[1]: Starting CUPS Printing Service...
    Sep 03 21:12:38 arch64-1.xxx systemd[1]: Started CUPS Printing Service.
    Sep 03 21:12:38 arch64-1.xxx cupsd[948]: cupsd: simple-watch.c:299: destroy_timeout: Assertion `*_head == _item' failed.
    Sep 03 21:12:38 arch64-1.xxx systemd-coredump[951]: Process 948 (cupsd) dumped core.
    Sep 03 21:12:38 arch64-1.xxx systemd[1]: cups.service: main process exited, code=dumped, status=6/ABRT
    Sep 03 21:12:38 arch64-1.xxx systemd[1]: Unit cups.service entered failed state.
    A restart might work - or not.
    How can I find the reason for this?

    I have not experienced this, but I also don't use the cups.service directly.  Insetad I have it autostarted on access with the cups.socket.  I wonder if starting it only when it is needed will help its success…
    There is also the cups.path, which watches for /var/spool/cups/d* and starts is if there is anything that matches that glob.  But I have never used this, as I noticed that there is the creation of some of these files on my system whether or not I am currently printing.

  • Too  Slow - Domino 6.5.4  with access manager agent 2.2 ?

    I don't know how to tune Domino 6.5.4 with access manager agent 2.2?
    I think AMAgent.properties is not good for SSO.
    Please help me to tune it.
    # $Id: AMAgent.properties,v 1.103 2005/09/19 22:08:34 madan Exp $
    # Copyright ? 2002 Sun Microsystems, Inc. All rights reserved.
    # U.S. Government Rights - Commercial software. Government users are
    # subject to the Sun Microsystems, Inc. standard license agreement and
    # applicable provisions of the FAR and its supplements. Use is subject to
    # license terms. Sun, Sun Microsystems, the Sun logo and Sun ONE are
    # trademarks or registered trademarks of Sun Microsystems, Inc. in the
    # U.S. and other countries.
    # Copyright ? 2002 Sun Microsystems, Inc. Tous droits r&#38303;erv&#38303;.
    # Droits du gouvernement am&#38302;icain, utlisateurs gouvernmentaux - logiciel
    # commercial. Les utilisateurs gouvernmentaux sont soumis au contrat de
    # licence standard de Sun Microsystems, Inc., ainsi qu aux dispositions en
    # vigueur de la FAR [ (Federal Acquisition Regulations) et des suppl&#38297;ents
    # ? celles-ci.
    # Distribu? par des licences qui en restreignent l'utilisation. Sun, Sun
    # Microsystems, le logo Sun et Sun ONE sont des marques de fabrique ou des
    # marques d&#38300;os&#38289;s de Sun Microsystems, Inc. aux Etats-Unis et dans
    # d'autres pays.
    # The syntax of this file is that of a standard Java properties file,
    # see the documentation for the java.util.Properties.load method for a
    # complete description. (CAVEAT: The SDK in the parser does not currently
    # support any backslash escapes except for wrapping long lines.)
    # All property names in this file are case-sensitive.
    # NOTE: The value of a property that is specified multiple times is not
    # defined.
    # WARNING: The contents of this file are classified as an UNSTABLE
    # interface by Sun Microsystems, Inc. As such, they are subject to
    # significant, incompatible changes in any future release of the
    # software.
    # The name of the cookie passed between the Access Manager
    # and the SDK.
    # WARNING: Changing this property without making the corresponding change
    # to the Access Manager will disable the SDK.
    com.sun.am.cookie.name = iPlanetDirectoryPro
    # The URL for the Access Manager Naming service.
    com.sun.am.naming.url = http://sportal.yjy.dqyt.petrochina:80/amserver/namingservice
    # The URL of the login page on the Access Manager.
    com.sun.am.policy.am.login.url = http://sportal.yjy.dqyt.petrochina:80/amserver/UI/Login
    # Name of the file to use for logging messages.
    com.sun.am.policy.agents.config.local.log.file = c:/Sun/Access_Manager/Agents/2.2/debug/C__Lotus_Domino/amAgent
    # This property is used for Log Rotation. The value of the property specifies
    # whether the agent deployed on the server supports the feature of not. If set
    # to false all log messages are written to the same file.
    com.sun.am.policy.agents.config.local.log.rotate = true
    # Name of the Access Manager log file to use for logging messages to
    # Access Manager.
    # Just the name of the file is needed. The directory of the file
    # is determined by settings configured on the Access Manager.
    com.sun.am.policy.agents.config.remote.log = amAuthLog.Dominoad.yjy.dqyt.petrochina.80
    # Set the logging level for the specified logging categories.
    # The format of the values is
    #     <ModuleName>[:<Level>][,<ModuleName>[:<Level>]]*
    # The currently used module names are: AuthService, NamingService,
    # PolicyService, SessionService, PolicyEngine, ServiceEngine,
    # Notification, PolicyAgent, RemoteLog and all.
    # The all module can be used to set the logging level for all currently
    # none logging modules. This will also establish the default level for
    # all subsequently created modules.
    # The meaning of the 'Level' value is described below:
    #     0     Disable logging from specified module*
    #     1     Log error messages
    #     2     Log warning and error messages
    #     3     Log info, warning, and error messages
    #     4     Log debug, info, warning, and error messages
    #     5     Like level 4, but with even more debugging messages
    # 128     log url access to log file on AM server.
    # 256     log url access to log file on local machine.
    # If level is omitted, then the logging module will be created with
    # the default logging level, which is the logging level associated with
    # the 'all' module.
    # for level of 128 and 256, you must also specify a logAccessType.
    # *Even if the level is set to zero, some messages may be produced for
    # a module if they are logged with the special level value of 'always'.
    com.sun.am.log.level =
    # The org, username and password for Agent to login to AM.
    com.sun.am.policy.am.username = UrlAccessAgent
    com.sun.am.policy.am.password = LYnKyOIgdWt404ivWY6HPQ==
    # Name of the directory containing the certificate databases for SSL.
    com.sun.am.sslcert.dir = c:/Sun/Access_Manager/Agents/2.2/domino/cert
    # Set this property if the certificate databases in the directory specified
    # by the previous property have a prefix.
    com.sun.am.certdb.prefix =
    # Should agent trust all server certificates when Access Manager
    # is running SSL?
    # Possible values are true or false.
    com.sun.am.trust_server_certs = true
    # Should the policy SDK use the Access Manager notification
    # mechanism to maintain the consistency of its internal cache? If the value
    # is false, then a polling mechanism is used to maintain cache consistency.
    # Possible values are true or false.
    com.sun.am.notification.enable = true
    # URL to which notification messages should be sent if notification is
    # enabled, see previous property.
    com.sun.am.notification.url = http://Dominoad.yjy.dqyt.petrochina:80/amagent/UpdateAgentCacheServlet?shortcircuit=false
    # This property determines whether URL string case sensitivity is
    # obeyed during policy evaluation
    com.sun.am.policy.am.url_comparison.case_ignore = true
    # This property determines the amount of time (in minutes) an entry
    # remains valid after it has been added to the cache. The default
    # value for this property is 3 minutes.
    com.sun.am.policy.am.polling.interval=3
    # This property allows the user to configure the User Id parameter passed
    # by the session information from the access manager. The value of User
    # Id will be used by the agent to set the value of REMOTE_USER server
    # variable. By default this parameter is set to "UserToken"
    com.sun.am.policy.am.userid.param=UserToken
    # Profile attributes fetch mode
    # String attribute mode to specify if additional user profile attributes should
    # be introduced into the request. Possible values are:
    # NONE - no additional user profile attributes will be introduced.
    # HTTP_HEADER - additional user profile attributes will be introduced into
    # HTTP header.
    # HTTP_COOKIE - additional user profile attributes will be introduced through
    # cookies.
    # If not within these values, it will be considered as NONE.
    com.sun.am.policy.agents.config.profile.attribute.fetch.mode=NONE
    # The user profile attributes to be added to the HTTP header. The
    # specification is of the format ldap_attribute_name|http_header_name[,...].
    # ldap_attribute_name is the attribute in data store to be fetched and
    # http_header_name is the name of the header to which the value needs
    # to be assigned.
    # NOTE: In most cases, in a destination application where a "http_header_name"
    # shows up as a request header, it will be prefixed by HTTP_, and all
    # lower case letters will become upper case, and any - will become _;
    # For example, "common-name" would become "HTTP_COMMON_NAME"
    com.sun.am.policy.agents.config.profile.attribute.map=cn|common-name,ou|organizational-unit,o|organization,mail|email,employeenumber|employee-
    number,c|country
    # Session attributes mode
    # String attribute mode to specify if additional user session attributes should
    # be introduced into the request. Possible values are:
    # NONE - no additional user session attributes will be introduced.
    # HTTP_HEADER - additional user session attributes will be introduced into HTTP header.
    # HTTP_COOKIE - additional user session attributes will be introduced through cookies.
    # If not within these values, it will be considered as NONE.
    com.sun.am.policy.agents.config.session.attribute.fetch.mode=NONE
    # The session attributes to be added to the HTTP header. The specification is
    # of the format session_attribute_name|http_header_name[,...].
    # session_attribute_name is the attribute in session to be fetched and
    # http_header_name is the name of the header to which the value needs to be
    # assigned.
    # NOTE: In most cases, in a destination application where a "http_header_name"
    # shows up as a request header, it will be prefixed by HTTP_, and all
    # lower case letters will become upper case, and any - will become _;
    # For example, "common-name" would become "HTTP_COMMON_NAME"
    com.sun.am.policy.agents.config.session.attribute.map=
    # Response Attribute Fetch Mode
    # String attribute mode to specify if additional user response attributes should
    # be introduced into the request. Possible values are:
    # NONE - no additional user response attributes will be introduced.
    # HTTP_HEADER - additional user response attributes will be introduced into
    # HTTP header.
    # HTTP_COOKIE - additional user response attributes will be introduced through
    # cookies.
    # If not within these values, it will be considered as NONE.
    com.sun.am.policy.agents.config.response.attribute.fetch.mode=NONE
    # The response attributes to be added to the HTTP header. The specification is
    # of the format response_attribute_name|http_header_name[,...].
    # response_attribute_name is the attribute in policy response to be fetched and
    # http_header_name is the name of the header to which the value needs to be
    # assigned.
    # NOTE: In most cases, in a destination application where a "http_header_name"
    # shows up as a request header, it will be prefixed by HTTP_, and all
    # lower case letters will become upper case, and any - will become _;
    # For example, "common-name" would become "HTTP_COMMON_NAME"
    com.sun.am.policy.agents.config.response.attribute.map=
    # The cookie name used in iAS for sticky load balancing
    com.sun.am.policy.am.lb.cookie.name = GX_jst
    # indicate where a load balancer is used for Access Manager
    # services.
    # true | false
    com.sun.am.load_balancer.enable = false
    ####Agent Configuration####
    # this is for product versioning, please do not modify it
    com.sun.am.policy.agents.config.version=2.2
    # Set the url access logging level. the choices are
    # LOG_NONE - do not log user access to url
    # LOG_DENY - log url access that was denied.
    # LOG_ALLOW - log url access that was allowed.
    # LOG_BOTH - log url access that was allowed or denied.
    com.sun.am.policy.agents.config.audit.accesstype = LOG_DENY
    # Agent prefix
    com.sun.am.policy.agents.config.agenturi.prefix = http://Dominoad.yjy.dqyt.petrochina:80/amagent
    # Locale setting.
    com.sun.am.policy.agents.config.locale = en_US
    # The unique identifier for this agent instance.
    com.sun.am.policy.agents.config.instance.name = unused
    # Do SSO only
    # Boolean attribute to indicate whether the agent will just enforce user
    # authentication (SSO) without enforcing policies (authorization)
    com.sun.am.policy.agents.config.do_sso_only = true
    # The URL of the access denied page. If no value is specified, then
    # the agent will return an HTTP status of 403 (Forbidden).
    com.sun.am.policy.agents.config.accessdenied.url =
    # This property indicates if FQDN checking is enabled or not.
    com.sun.am.policy.agents.config.fqdn.check.enable = true
    # Default FQDN is the fully qualified hostname that the users should use
    # in order to access resources on this web server instance. This is a
    # required configuration value without which the Web server may not
    # startup correctly.
    # The primary purpose of specifying this property is to ensure that if
    # the users try to access protected resources on this web server
    # instance without specifying the FQDN in the browser URL, the Agent
    # can take corrective action and redirect the user to the URL that
    # contains the correct FQDN.
    # This property is set during the agent installation and need not be
    # modified unless absolutely necessary to accommodate deployment
    # requirements.
    # WARNING: Invalid value for this property can result in the Web Server
    # becoming unusable or the resources becoming inaccessible.
    # See also: com.sun.am.policy.agents.config.fqdn.check.enable,
    # com.sun.am.policy.agents.config.fqdn.map
    com.sun.am.policy.agents.config.fqdn.default = Dominoad.yjy.dqyt.petrochina
    # The FQDN Map is a simple map that enables the Agent to take corrective
    # action in the case where the users may have typed in an incorrect URL
    # such as by specifying partial hostname or using an IP address to
    # access protected resources. It redirects the browser to the URL
    # with fully qualified domain name so that cookies related to the domain
    # are received by the agents.
    # The format for this property is:
    # com.sun.am.policy.agents.config.fqdn.map = [invalid_hostname|valid_hostname][,...]
    # This property can also be used so that the agents use the name specified
    # in this map instead of the web server's actual name. This can be
    # accomplished by doing the following.
    # Say you want your server to be addressed as xyz.hostname.com whereas the
    # actual name of the server is abc.hostname.com. The browsers only knows
    # xyz.hostname.com and you have specified polices using xyz.hostname.com at
    # the Access Manager policy console, in this file set the mapping as
    # com.sun.am.policy.agents.fqdn.map = valid|xyz.hostname.com
    # Another example is if you have multiple virtual servers say rst.hostname.com,
    # uvw.hostname.com and xyz.hostname.com pointing to the same actual server
    # abc.hostname.com and each of the virtual servers have their own policies
    # defined, then the fqdnMap should be defined as follows:
    # com.sun.am.policy.agents.fqdn.map = valid1|rst.hostname.com,valid2|uvw.hostname.com,valid3|xyz.hostname.com
    # WARNING: Invalid value for this property can result in the Web Server
    # becoming unusable or the resources becoming inaccessible.
    com.sun.am.policy.agents.config.fqdn.map =
    # Cookie Reset
    # This property must be set to true, if this agent needs to
    # reset cookies in the response before redirecting to
    # Access Manager for Authentication.
    # By default this is set to false.
    # Example : com.sun.am.policy.agents.config.cookie.reset.enable=true
    com.sun.am.policy.agents.config.cookie.reset.enable=false
    # This property gives the comma separated list of Cookies, that
    # need to be included in the Redirect Response to Access Manager.
    # This property is used only if the Cookie Reset feature is enabled.
    # The Cookie details need to be specified in the following Format
    # name[=value][;Domain=value]
    # If "Domain" is not specified, then the default agent domain is
    # used to set the Cookie.
    # Example : com.sun.am.policy.agents.config.cookie.reset.list=LtpaToken,
    # token=value;Domain=subdomain.domain.com
    com.sun.am.policy.agents.config.cookie.reset.list=
    # This property gives the space separated list of domains in
    # which cookies have to be set in a CDSSO scenario. This property
    # is used only if CDSSO is enabled.
    # If this property is left blank then the fully qualified cookie
    # domain for the agent server will be used for setting the cookie
    # domain. In such case it is a host cookie instead of a domain cookie.
    # Example : com.sun.am.policy.agents.config.cookie.domain.list=.sun.com .iplanet.com
    com.sun.am.policy.agents.config.cookie.domain.list=
    # user id returned if accessing global allow page and not authenticated
    com.sun.am.policy.agents.config.anonymous_user=anonymous
    # Enable/Disable REMOTE_USER processing for anonymous users
    # true | false
    com.sun.am.policy.agents.config.anonymous_user.enable=false
    # Not enforced list is the list of URLs for which no authentication is
    # required. Wildcards can be used to define a pattern of URLs.
    # The URLs specified may not contain any query parameters.
    # Each service have their own not enforced list. The service name is suffixed
    # after "# com.sun.am.policy.agents.notenforcedList." to specify a list
    # for a particular service. SPACE is the separator between the URL.
    com.sun.am.policy.agents.config.notenforced_list = http://dominoad.yjy.dqyt.petrochina/*.nsf http://dominoad.yjy.dqyt.petrochina/teamroom.nsf/TROutline.gif?
    OpenImageResource http://dominoad.yjy.dqyt.petrochina/icons/*.gif
    # Boolean attribute to indicate whether the above list is a not enforced list
    # or an enforced list; When the value is true, the list means enforced list,
    # or in other words, the whole web site is open/accessible without
    # authentication except for those URLs in the list.
    com.sun.am.policy.agents.config.notenforced_list.invert = false
    # Not enforced client IP address list is a list of client IP addresses.
    # No authentication and authorization are required for the requests coming
    # from these client IP addresses. The IP address must be in the form of
    # eg: 192.168.12.2 1.1.1.1
    com.sun.am.policy.agents.config.notenforced_client_ip_list =
    # Enable POST data preservation; By default it is set to false
    com.sun.am.policy.agents.config.postdata.preserve.enable = false
    # POST data preservation : POST cache entry lifetime in minutes,
    # After the specified interval, the entry will be dropped
    com.sun.am.policy.agents.config.postcache.entry.lifetime = 10
    # Cross-Domain Single Sign On URL
    # Is CDSSO enabled.
    com.sun.am.policy.agents.config.cdsso.enable=false
    # This is the URL the user will be redirected to for authentication
    # in a CDSSO Scenario.
    com.sun.am.policy.agents.config.cdcservlet.url =
    # Enable/Disable client IP address validation. This validate
    # will check if the subsequent browser requests come from the
    # same ip address that the SSO token is initially issued against
    com.sun.am.policy.agents.config.client_ip_validation.enable = false
    # Below properties are used to define cookie prefix and cookie max age
    com.sun.am.policy.agents.config.profile.attribute.cookie.prefix = HTTP_
    com.sun.am.policy.agents.config.profile.attribute.cookie.maxage = 300
    # Logout URL - application's Logout URL.
    # This URL is not enforced by policy.
    # if set, agent will intercept this URL and destroy the user's session,
    # if any. The application's logout URL will be allowed whether or not
    # the session destroy is successful.
    com.sun.am.policy.agents.config.logout.url=
    #http://sportal.yjy.dqyt.petrochina/amserver/UI/Logout
    # Any cookies to be reset upon logout in the same format as cookie_reset_list
    com.sun.am.policy.agents.config.logout.cookie.reset.list =
    # By default, when a policy decision for a resource is needed,
    # agent gets and caches the policy decision of the resource and
    # all resource from the root of the resource down, from the Access Manager.
    # For example, if the resource is http://host/a/b/c, the the root of the
    # resource is http://host/. This is because more resources from the
    # same path are likely to be accessed subsequently.
    # However this may take a long time the first time if there
    # are many many policies defined under the root resource.
    # To have agent get and cache the policy decision for the resource only,
    # set the following property to false.
    com.sun.am.policy.am.fetch_from_root_resource = true
    # Whether to get the client's hostname through DNS reverse lookup for use
    # in policy evaluation.
    # It is true by default, if the property does not exist or if it is
    # any value other than false.
    com.sun.am.policy.agents.config.get_client_host_name = false
    # The following property is to enable native encoding of
    # ldap header attributes forwarded by agents. If set to true
    # agent will encode the ldap header value in the default
    # encoding of OS locale. If set to false ldap header values
    # will be encoded in UTF-8
    com.sun.am.policy.agents.config.convert_mbyte.enable = false
    #When the not enforced list or policy has a wildcard '*' character, agent
    #strips the path info from the request URI and uses the resulting request
    #URI to check against the not enforced list or policy instead of the entire
    #request URI, in order to prevent someone from getting access to any URI by
    #simply appending the matching pattern in the policy or not enforced list.
    #For example, if the not enforced list has the value http://host/*.gif,
    #stripping the path info from the request URI will prevent someone from
    #getting access to http://host/index.html by using the URL http://host/index.html?hack.gif.
    #However when a web server (for exmample apache) is configured to be a reverse
    #proxy server for a J2EE application server, path info is interpreted in a different
    #manner since it maps to a resource on the proxy instead of the app server.
    #This prevents the not enforced list or policy from being applied to part of
    #the URI below the app serverpath if there is a wildcard character. For example,
    #if the not enforced list has value http://host/webapp/servcontext/* and the
    #request URL is http://host/webapp/servcontext/example.jsp the path info
    #is /servcontext/example.jsp and the resulting request URL with path info stripped
    #is http://host/webapp, which will not match the not enforced list. By setting the
    #following property to true, the path info will not be stripped from the request URL
    #even if there is a wild character in the not enforced list or policy.
    #Be aware though that if this is set to true there should be nothing following the
    #wildcard character '*' in the not enforced list or policy, or the
    #security loophole described above may occur.
    com.sun.am.policy.agents.config.ignore_path_info = false
    # Override the request url given by the web server with
    # the protocol, host or port of the agent's uri specified in
    # the com.sun.am.policy.agents.agenturiprefix property.
    # These may be needed if the agent is sitting behind a ssl off-loader,
    # load balancer, or proxy, and either the protocol (HTTP scheme),
    # hostname, or port of the machine in front of agent which users go through
    # is different from the agent's protocol, host or port.
    com.sun.am.policy.agents.config.override_protocol =
    com.sun.am.policy.agents.config.override_host =
    com.sun.am.policy.agents.config.override_port =
    # Override the notification url in the same way as other request urls.
    # Set this to true if any one of the override properties above is true,
    # and if the notification url is coming through the proxy or load balancer
    # in the same way as other request url's.
    com.sun.am.policy.agents.config.override_notification.url =
    # The following property defines how long to wait in attempting
    # to connect to an Access Manager AUTH server.
    # The default value is 2 seconds. This value needs to be increased
    # when receiving the error "unable to find active Access Manager Auth server"
    com.sun.am.policy.agents.config.connection_timeout =
    # Time in milliseconds the agent will wait to receive the
    # response from Access Manager. After the timeout, the connection
    # will be drop.
    # A value of 0 means that the agent will wait until receiving the response.
    # WARNING: Invalid value for this property can result in
    # the resources becoming inaccessible.
    com.sun.am.receive_timeout = 0
    # The three following properties are for IIS6 agent only.
    # The two first properties allow to set a username and password that will be
    # used by the authentication filter to pass the Windows challenge when the Basic
    # Authentication option is selected in Microsoft IIS 6.0. The authentication
    # filter is named amiis6auth.dll and is located in
    # Agent_installation_directory/iis6/bin. It must be installed manually on
    # the web site ("ISAPI Filters" tab in the properties of the web site).
    # It must also be uninstalled manually when unintalling the agent.
    # The last property defines the full path for the authentication filter log file.
    com.sun.am.policy.agents.config.iis6.basicAuthentication.username =
    com.sun.am.policy.agents.config.iis6.basicAuthentication.password =
    com.sun.am.policy.agents.config.iis6.basicAuthentication.logFile = c:/Sun/Access_Manager/Agents/2.2/debug/C__Lotus_Domino/amAuthFilter

    Hi,
    I installed opensso (so Sun Java(TM) System Access Manager 7.5) and the agent for Domino 6.5.4 and I have the message in logs "amAgent"
    2007-07-11 18:40:16.119 Error 1708:3dbcf768 PolicyAgent: render_response(): Entered.
    I have the box to identify but it doesnot connect me on my opensso server.
    It still identify with Domino's server
    Thanks for your response
    Thomas

Maybe you are looking for