Re: imapd cores dump since upgrade to MS7

I can't tell which thread in the first pstack is the one that crashed. 
You should open a support case so we can take a closer look at this.

But thread 23303 in the second pstack looks like bug 6748629, which will 
be fixed in an upcoming patch for 7.0.  If this is happening frequently, 
open a case so we can see about getting you something more quickly.

Kelly

frederic.vandevelde@... wrote:
> Hi,
> 
> We have upgraded to MS 7.x via commpkg upgrade and since then the IMAPD 
> process cores dump from time to time, approximatelly once a week.
> 
> Is there known bugs about IMAPD core dumping in version 7.x ?
> 
> Sun Java(tm) System Messaging Server 7.0-0.04 32bit (built Jun 20 2008)
> libimta.so 7.0-0.04 32bit (built 01:05:03, Jun 20 2008)
> 
> Here is the pstack of the core dumps, we have 2 IMAP processes.
> 
> -----------------  lwp# 1 / thread# 1  --------------------
>  fd54169c __pollsys (49f9a4, 10e, ffbff3c0, 0, 0, fa0) + 8
>  fd4dd150 poll     (49f9a4, 10e, 111e, 10624c00, 5b136e, 16c4db80) + 7c
>  fe647400 GDispCx_DispatchLoop (45e17c, 0, 0, 1, 1, 1) + 358
>  0002c824 imap_main (d45d8, 185, 1, 10b4, fd56ecc0, 9a918) + 203c
>  fe7a9c78 service_start (7f3eb, 7f400, 1, ffbffddc, 2a7e8, 25df0) + 390
>  0002caf4 main     (1, ffbffddc, ffbffde4, 98000, fe370380, fe3703c0) + 4c
>  00021d68 _start   (0, 0, 0, 0, 0, 0) + 108

(unknown)

unsubscribe

Calendar error caldb_pvt_ScanComponents: get: -30988

Good morning,

We regularly have the following error with our calendar:
/var/opt/SUNWics5/logs/admin.log: [01/Oct/2008:06:28:59 +0200] oscar csexport[26956]: General
Error: caldb: caldb_pvt_ScanComponents: get: -30988

As google is not my friend for understanding this error, could you please tell me
what does a get: -30988 on caldb_pvt_ScanComponents mean?

Thanks in advance for your help.
--

-- 
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

      Benoit Schmid              Tel: (++41-22) 379-7209
      UNIGE Postmaster

      University of Geneva - Information Technology Division

_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

Re: Calendar error caldb_pvt_ScanComponents: get: -30988

Benoit Schmid wrote:
> We regularly have the following error with our calendar:
> /var/opt/SUNWics5/logs/admin.log: [01/Oct/2008:06:28:59 +0200] oscar 
> csexport[26956]: General Error: caldb: caldb_pvt_ScanComponents: get: 
> -30988
> 
> As google is not my friend for understanding this error, could you 
> please tell me
> what does a get: -30988 on caldb_pvt_ScanComponents mean?
> 
> Thanks in advance for your help.

This probably won't be that helpful, since I know very little about the 
calendar server, but the number you see is a Berkeley (Sleepycat) DB error 
code being returned when attempting to retrieve a record.

However, the error codes are specific to a particular version of the 
database, so you'd have to know what the Berkerley DB version is to track 
down the exact meaning.

I presume with some Calendar Server version information, someone may be 
able to determine exactly what the version of the database is shipped with 
that particular release, and thus determine what the error code means.

But, as I said that probably won't help you much though. A support case 
would seem to be the best answer.

Cheers
Andrew

Re: imapd cores dump since upgrade to MS7

Re: Calendar error caldb_pvt_ScanComponents: get: -30988

Good morning,

The calendar version is 6.3 Patch: 121657-29.

Sorry for having forgotten that.

Andrew McKeon wrote:
> Benoit Schmid wrote:
>> We regularly have the following error with our calendar:
>> /var/opt/SUNWics5/logs/admin.log: [01/Oct/2008:06:28:59 +0200] oscar 
>> csexport[26956]: General Error: caldb: caldb_pvt_ScanComponents: get: 
>> -30988
>>
>> As google is not my friend for understanding this error, could you 
>> please tell me
>> what does a get: -30988 on caldb_pvt_ScanComponents mean?
>>
>> Thanks in advance for your help.
> 
> 
> This probably won't be that helpful, since I know very little about the 
> calendar server, but the number you see is a Berkeley (Sleepycat) DB 
> error code being returned when attempting to retrieve a record.
> 
> However, the error codes are specific to a particular version of the 
> database, so you'd have to know what the Berkerley DB version is to 
> track down the exact meaning.
> 
> I presume with some Calendar Server version information, someone may be 
> able to determine exactly what the version of the database is shipped 
> with that particular release, and thus determine what the error code means.
> 
> But, as I said that probably won't help you much though. A support case 
> would seem to be the best answer.
> 

Please not that 

> Cheers
> Andrew

--

-- 
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

      Benoit Schmid              Tel: (++41-22) 379-7209
      UNIGE Postmaster

      University of Geneva - Information Technology Division

_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

Daylight Saving Problems

Hi All,

Here is Australia they have decided to change the daylight saving times (yet again!). I have applied the
Solaris patches, updated the Java timezones and fixed the Timezones.ics file in the Calendar server.

However, I am still having problems with recurring events. The current times are correct, and the times
after the change was originally planned are correct, but anything in between is out by one hour.

Has anyone else had this type of problem? 

Sheryl Bruggy 
Systems/Network Administrator 
Southern Cross University 
._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._ 

Re: Convergence and Calendar

Imri,

Last week I got the same problem as you have and found that the user  
was missing some ldap attributes for the calendar.
After I added icscalendar and icssubscribed with the right values  
every went fine.

Can you check wether you have the same issue.

Regards,
Frederic.

On 17 Sep 2008, at 16:46, Imri Zvik wrote:

> On Wednesday 17 September 2008 17:32:27 frederic.vandevelde@...
> wrote:
>> Did you try to activate convergence debug log.
>>
>> iwcadmin -u admin -w password -o log.PROXY_CAL.level -v DEBUG
>
> Yep,
>
> here is the output:
>
>
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,810 - Cal: using proxyauth to  
> login to
> cal service
> AUTH: DEBUG from com.sun.comms.client.web.sso.SSOFilter  Thread
> httpSSLWorkerThread-8080-3 at 17:45:35,811 - SSO is disabled
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,813 - Authenticating
> imriz2@... to cal service using proxyauth username calmaster
> AUTH: DEBUG from
> com.sun.comms.client.web.authorization.CalendarAuthorizationManager   
> Thread
> httpSSLWorkerThread-8080-3 at 17:45:35,815 - The request is  
> anonymous: false
> AUTH: DEBUG from com.sun.comms.client.web.authorization.CalAuthorizationFilter
> Thread httpSSLWorkerThread-8080-3 at 17:45:35,818 - Removing token  
> parameter
> from the Calendar backend service request
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,856 - CAL response Header:   
> Name: Date
> Value: Wed, 17 Sep 2008 14:45:35 GMT
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,858 - CAL response Header:   
> Name:
> Content-type Value: text/xml; charset=UTF-8
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,860 - CAL response Header:   
> Name:
> Content-length Value: 492
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,862 - CAL response Header:   
> Name:
> Last-modified Value: Wed, 17 Sep 2008 14:45:35 GMT
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,863 - CAL response Header:   
> Name:
> Pragma Value: no-cache
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,865 - CAL response Header:   
> Name:
> Expires Value: 0
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,866 - CAL response Header:   
> Name:
> Cache-Control Value: no-cache
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,868 - CAL response Header:   
> Name:
> Connection Value: Keep-Alive
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,875 - Login response: cal_sid  
> is :
> d4fL7dF3yrg
> DEFAULT: DEBUG from
> com.sun.comms.client.web.services.http.HttpServiceConnector  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,877 - HTTPSERVICE: releasing
> Connection
> com 
> .sun.comms.client.web.services.http.HttpServiceConnectionImpl <at> 1e8a18
> DEFAULT: DEBUG from
> com.sun.comms.client.web.services.http.HttpServiceConnector  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,879 - HTTPSERVICE: releasing
> Connection
> com 
> .sun.comms.client.web.services.http.HttpServiceConnectionImpl <at> 1e8a18
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,881 - cal_sid is d4fL7dF3yrg
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-3 at 17:45:35,881 - cal_sid is d4fL7dF3yrg
> DEFAULT: DEBUG from
> com.sun.comms.client.web.services.http.HttpServiceConnectorFactory   
> Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,882 - HTTPSERVICE: returning  
> cached
> Http Connector for  SUN_CAL_SERVICE
> DEFAULT: DEBUG from
> com.sun.comms.client.web.services.http.HttpServiceConnectorFactory   
> Thread
> httpSSLWorkerThread-8080-3 at 17:45:35,884 - HTTPSERVICE: returning  
> cached
> Http Connector for  SUN_CAL_SERVICE
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,886 - CalenderProxy:
> reqURI: /iwc/svc/wcap/list.wcap
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-3 at 17:45:35,887 - CalenderProxy:
> reqURI: /iwc/svc/wcap/list_subscribed.wcap
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,889 - CalenderProxy:
> calCommand: /list.wcap
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-3 at 17:45:35,891 - CalenderProxy:
> calCommand: /list_subscribed.wcap
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,893 - CalenderProxy: svlt
> Path: /svc/wcap
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-3 at 17:45:35,894 - CalenderProxy: svlt
> Path: /svc/wcap
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,896 - WCAP request url
> is: /list.wcap?id=d4fL7dF3yrg&fmt-out=text 
> %2Fjson&token=NFf6rode0Y&dojo.preventCache=1221662742234
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-3 at 17:45:35,898 - WCAP request url
> is: /list_subscribed.wcap?id=d4fL7dF3yrg&fmt-out=text 
> %2Fjson&token=NFf6rode0Y&dojo.preventCache=1221662742234
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,900 -  cal request header  
> name is
> accept
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-3 at 17:45:35,902 -  cal request header  
> name is
> accept
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,903 -  cal request header  
> name is
> accept-language
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-3 at 17:45:35,905 -  cal request header  
> name is
> accept-language
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,907 -  cal request header  
> name is
> referer
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-3 at 17:45:35,908 -  cal request header  
> name is
> referer
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,910 -  cal request header  
> name is
> content-type
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-3 at 17:45:35,912 -  cal request header  
> name is
> content-type
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,913 -  cal request header  
> name is
> ua-cpu
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-3 at 17:45:35,915 -  cal request header  
> name is
> ua-cpu
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,917 -  cal request header  
> name is
> accept-encoding
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-3 at 17:45:35,918 -  cal request header  
> name is
> accept-encoding
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,920 -  cal request header  
> name is
> user-agent
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-3 at 17:45:35,922 -  cal request header  
> name is
> user-agent
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,923 -  cal request header  
> name is host
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-3 at 17:45:35,925 -  cal request header  
> name is host
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,926 -  cal request header  
> name is
> connection
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-3 at 17:45:35,928 -  cal request header  
> name is
> connection
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:35,930 -  cal request header  
> name is
> cookie
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-3 at 17:45:35,932 -  cal request header  
> name is
> cookie
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-3 at 17:45:35,986 - Response code for  
> Calendar
> request: 200
> DEFAULT: DEBUG from
> com.sun.comms.client.web.services.http.HttpServiceConnector  Thread
> httpSSLWorkerThread-8080-3 at 17:45:35,989 - HTTPSERVICE: releasing
> Connection
> com 
> .sun.comms.client.web.services.http.HttpServiceConnectionImpl <at> fc6e58
> PROXY_CAL: DEBUG from
> com.sun.comms.client.web.services.sun.CalendarServiceProxy  Thread
> httpSSLWorkerThread-8080-2 at 17:45:36,011 - Response code for  
> Calendar
> request: 200
> DEFAULT: DEBUG from
> com.sun.comms.client.web.services.http.HttpServiceConnector  Thread
> httpSSLWorkerThread-8080-2 at 17:45:36,015 - HTTPSERVICE: releasing
> Connection
> com 
> .sun.comms.client.web.services.http.HttpServiceConnectionImpl <at> b056fd
>
>>
>> What's the output in the convergence log ?
>>
>> Regards,
>> Frederic.
>>
>> On 17 Sep 2008, at 16:09, Imri Zvik wrote:
>>> Hi,
>>>
>>>
>>> On Monday 15 September 2008 15:13:34
>>>
>>> frederic.vandevelde@... wrote:
>>>>> I couldn't find a list of X-NSCP-WCAP-ERRNO values anywhere, so I
>>>>> have no idea
>>>>> what error 71 & 72 means....
>>>>
>>>> You can find the meaning of error codes here:
>>>> http://docs.sun.com/app/docs/doc/819-4655/6n6pshlfe?l=en&a=view
>>>>
>>>> To use convergence you need to be at the latest patch level of the
>>>> calendar server (121657-29 for solaris sparc)
>>>
>>> I am running this patch level, but still, errors 71 & 72 whenever I
>>> click on
>>> the calander tab...
>>> Nothing at the logs..
>>>
>>> Any ideas?
>>>
>>>> Regards,
>>>> Frederic.
>
>

Re: Daylight Saving Problems

sheryl.bruggy@... wrote:
> Hi All,
>
> Here is Australia they have decided to change the daylight saving times (yet again!). I have applied the
Solaris patches, updated the Java timezones and fixed the Timezones.ics file in the Calendar server.
>
> However, I am still having problems with recurring events. The current times are correct, and the times
after the change was originally planned are correct, but anything in between is out by one hour.
>
> Has anyone else had this type of problem? 
>
>
> Sheryl Bruggy 
> Systems/Network Administrator 
> Southern Cross University 
> ._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._ 
>   
For anyone that wants more info on this stuff, Sun has a website that 
covers this for everything
here : http://www.sun.com/bigadmin/hubs/dst/

-- 
_______________________________________________________________________

Scott Lawson
Systems Architect
Manukau Institute of Technology
Information Communication Technology Services Private Bag 94006 Manukau
City Auckland New Zealand

Phone  : +64 09 968 7611
Fax    : +64 09 968 7641
Mobile : +64 27 568 7611

mailto:scott@...

http://www.manukau.ac.nz

________________________________________________________________________

perl -e 'print
$i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'

________________________________________________________________________ 

convergence customization

Hi,

Did someone managed to customize the title of all pages, the one you  
see in the window name of you browser ?

Using the procedure described at http://wikis.sun.com/display/CommSuite/Changing+Names+and+Labels+in+the+Convergence+UI
I managed to customize labels like the one in example so my i18n setup  
works but using the product_name label doesn't seems to be taken into  
account like in this resources.js file:

{
         product_name:  "Convergence",

         last: ""
}

If I change it directly in the iwc_static/js/iwc/i18n/nls/resources.js  
it works but that's not the way to do it.

Regards,
Frederic.