No, you're good, we saw a strange thing with a system that had 32 and 64 bit java installed. Wanted to make sure that you didn't smack into that.
On Thu, Sep 23, 2010 at 11:05 AM, Matthew Kitchin (public/usenet) < [email protected]> wrote: > I checked java version last night as part of my steps. Everything is good. > > [r...@nshpbx1 sipxpbx]# yum list installed |grep "java" > java-1.6.0-sun.x86_64 1.6.0.19-1.2 > installed > java-1.6.0-sun-devel.x86_64 1.6.0.19-1.2 > installed > java-1.6.0-sun-fonts.x86_64 1.6.0.19-1.2 > installed > > I definitely can't take it down right now. > > On 9/23/2010 9:57 AM, Tony Graziano wrote: > > Hmmm. Check to see if you have both 32 and 64 bit java installed for some > reason... if you do then... > > Don't do anything I suggested yet. > > WARNING: This will seriously impact a running system. I would shut down > sipxecs services before doing this... > > first get rid of it with this: > rpm -e java-1.6.0-sun.i586 java-1.6.0-sun-fonts.i586 > then fix it with this: > yum reinstall java-1.6.0-sun.x86_64 java-1.6.0-sun-fonts.x86_64 > > > On Thu, Sep 23, 2010 at 10:50 AM, Tony Graziano < > [email protected]> wrote: > >> I didn't mean pus the profiles to the phones, i should have been specific >> and said "server" profiles, sorry. >> >> I also prefer to reboot the server between major updates, or when I do an >> OS kernel update (obviously). >> >> Removing the role might delete some data, but my suggestion was "I might >> intend to wipe the ACD config and start over". I would only do that after >> the server profiles had been sent, services shut down and the server >> rebooted. >> >> >> >> On Thu, Sep 23, 2010 at 10:42 AM, Matthew Kitchin (public/usenet) < >> [email protected]> wrote: >> >>> I've attached what seems like a relevant log file. >>> Will removing the ACD role and adding it back delete my ACD queues? I >>> would have to make sure I had them documented very well if so. >>> I didn't think 3.3 would be bad, but I figured I would try what I believe >>> I remembered had been tested the most on 4.2.1. >>> I activated the newer firmwares, push the profilee to my ACD agents >>> phones, and rebooted their phones. They did all pull the new firmware. >>> I have not rebooted the server itself. I can't do that right now. I am >>> running about 30 concurrent calls right now. >>> I pushed all profiles and rebooted after the 4.0.4 to 4.2.1 upgrade. >>> >>> On 9/23/2010 9:30 AM, Tony Graziano wrote: >>> >>> Out of curiosity, because i have seen ACD do strange things, what happens >>> if you remove the ACD configuration altogether and disable the role, then >>> add it back and configure the ACD all over? >>> >>> I recall a few versions back that ACD did some strange things between >>> upgrades and had to be "rebuilt" as it were to overcome it. >>> >>> I don't recall ANYTHING like the error you are seeing though nor do I >>> recall anything that says 3.1.3RevC is "bad' to use in any way. I am >>> assuming you did reboot after the update and send all profiles? >>> >>> On Thu, Sep 23, 2010 at 10:22 AM, Matthew Kitchin (public/usenet) < >>> [email protected]> wrote: >>> >>>> I upgraded from 4.0.4 to 4.2.1 last night. Everything seemed fine. >>>> Obviously I didn't test ACD thoroughly enough. >>>> I'm running CentOS 5.5 64 Bit. Sipxbridge. Verizon VOIP ITSP >>>> Polycom 450 and 550s running 3.1.3 Split. >>>> This morning, the calls bound for the ACD queue would just sit on the >>>> hold music. None of the phones logged in would ever ring. >>>> I tried restarting a few of the services, no help. At one point, >>>> sipxpresence (I'm 95% sure that was the name, it definitely had presence >>>> in the name) was taking 100% of the CPU. It never stop through the GUI. >>>> I had to kill the process. Once it was up and going again, calls were >>>> still stuck in hold. >>>> I remembered reading tha tmost of the testing for 4.2.1 was done with >>>> polycom firmware 3.2.2 (I think). I tired upgrading one of the ACD users >>>> to that firmware. It looked like we had postive results. I upgraded the >>>> other ACD agents phones. A call came through. The caller could hear the >>>> internal ACD agent, but the ACD agent could not hear the caller. Then >>>> everything died again. >>>> >>>> The ACD service keeps failing with the error below (shown in the GUI). I >>>> have restarted it several times, and tried sipxproc --restart >>>> ConfigServer >>>> The ACD service will not stay up. One other service had died. It was one >>>> of the ACD services I beleive , but is has stayed up now. >>>> >>>> Can anyone give me any suggestions? I'm truly desperate. I will start >>>> digging for more info, but I wanted to get this out there now. >>>> >>>> Thanks, >>>> Matthew >>>> >>>> 34370ee000-34370f4000 rw-p 000ee000 fd:00 34448818 >>>> /usr/lib64/libsipXcommserver.so.2.0.0 >>>> 34370f4000-34370fb000 rw-p 34370f4000 00:00 0 >>>> 3437200000-34372a3000 r-xp 00000000 fd:00 34448357 >>>> /usr/lib64/libsipXmedia.so.1.0.0 >>>> 34372a3000-34374a3000 ---p 000a3000 fd:00 34448357 >>>> /usr/lib64/libsipXmedia.so.1.0.0 >>>> 34374a3000-34374ac000 rw-p 000a3000 fd:00 34448357 >>>> /usr/lib64/libsipXmedia.so.1.0.0 >>>> 34374ac000-34374ae000 rw-p 34374ac000 00:00 0 >>>> 3437600000-343773c000 r-xp 00000000 fd:00 34448809 >>>> /usr/lib64/libsipXcall.so.1.0.0 >>>> 343773c000-343793c000 ---p 0013c000 fd:00 34448809 >>>> /usr/lib64/libsipXcall.so.1.0.0 >>>> 343793c000-3437950000 rw-p 0013c000 fd:00 34448809 >>>> /usr/lib64/libsipXcall.so.1.0.0 >>>> 3437a00000-3437a0e000 r-xp 00000000 fd:00 34448358 >>>> /usr/lib64/libsipXmediaProcessing.so.1.0.0 >>>> 3437a0e000-3437c0e000 ---p 0000e000 fd:00 34448358 >>>> /usr/lib64/libsipXmediaProcessing.so.1.0.0 >>>> 3437c0e000-3437c0f000 rw-p 0000e000 fd:00 34448358 >>>> /usr/lib64/libsipXmediaProcessing.so.1.0.0 >>>> 3708200000-370821c000 r-xp 00000000 fd:00 3735556 /lib64/ld-2.5.so >>>> 370841b000-370841c000 r--p 0001b000 fd:00 3735556 /lib64/ld-2.5.so >>>> 370841c000-370841d000 rw-p 0001c000 fd:00 3735556 /lib64/ld-2.5.so >>>> 3708600000-370874e000 r-xp 00000000 fd:00 3735563 /lib64/libc-2.5.so >>>> 370874e000-370894d000 ---p 0014e000 fd:00 3735563 /lib64/libc-2.5.so >>>> 370894d000-3708951000 r--p 0014d000 fd:00 3735563 /lib64/libc-2.5.so >>>> 3708951000-3708952000 rw-p 00151000 fd:00 3735563 /lib64/libc-2.5.so >>>> 3708952000-3708957000 rw-p 3708952000 00:00 0 >>>> 3708a00000-3708a02000 r-xp 00000000 fd:00 3735571 /lib64/libdl-2.5.so >>>> 3708a02000-3708c02000 ---p 00002000 fd:00 3735571 /lib64/libdl-2.5.so >>>> 3708c02000-3708c03000 r--p 00002000 fd:00 3735571 /lib64/libdl-2.5.so >>>> 3708c03000-3708c04000 rw-p 00003000 fd:00 3735571 /lib64/libdl-2.5.so >>>> 3708e00000-3708e82000 r-xp 00000000 fd:00 3735617 /lib64/libm-2.5.so >>>> 3708e82000-3709081000 ---p 00082000 fd:00 3735617 /lib64/libm-2.5.so >>>> 3709081000-3709082000 r--p 00081000 fd:00 3735617 /lib64/libm-2.5.so >>>> 3709082000-3709083000 rw-p 00082000 fd:00 3735617 /lib64/libm-2.5.so >>>> 3709200000-3709216000 r-xp 00000000 fd:00 3735569 /lib64/ >>>> libpthread-2.5.so >>>> 3709216000-3709415000 ---p 00016000 fd:00 3735569 /lib64/ >>>> libpthread-2.5.so >>>> 3709415000-3709416000 r--p 00015000 fd:00 3735569 /lib64/ >>>> libpthread-2.5.so >>>> 3709416000-3709417000 rw-p 00016000 fd:00 3735569 /lib64/ >>>> libpthread-2.5.so >>>> 3709417000-370941b000 rw-p 3709417000 00:00 0 >>>> 3709600000-3709614000 r-xp 00000000 fd:00 34444869 >>>> /usr/lib64/libz.so.1.2.3 >>>> 3709614000-3709813000 ---p 00014000 fd:00 34444869 >>>> /usr/lib64/libz.so.1.2.3 >>>> 3709813000-3709814000 rw-p 00013000 fd:00 34444869 >>>> /usr/lib64/libz.so.1.2.3 >>>> 3709a00000-3709a15000 r-xp 00000000 fd:00 3735591 /lib64/libselinux.so.1 >>>> 3709a15000-3709c15000 ---p 00015000 fd:00 3735591 /lib64/libselinux.so.1 >>>> 3709c15000-3709c17000 rw-p 00015000 fd:00 3735591 /lib64/libselinux.so.1 >>>> 3709c17000-3709c18000 rw-p 3709c17000 00:00 0 >>>> 3709e00000-3709e3b000 r-xp 00000000 fd:00 3735589 /lib64/libsepol.so.1 >>>> 3709e3b000-370a03b000 ---p 0003b000 fd:00 3735589 /lib64/libsepol.so.1 >>>> 370a03b000-370a03c000 rw-p 0003b000 fd:00 3735589 /lib64/libsepol.so.1 >>>> 370a03c000-370a046000 rw-p 370a03c000 00:00 0 >>>> 370a200000-370a2e6000 r-xp 00000000 fd:00 34443406 >>>> /usr/lib64/libstdc++.so.6.0.8 >>>> 370a2e6000-370a4e5000 ---p 000e6000 fd:00 34443406 >>>> /usr/lib64/libstdc++.so.6.0.8 >>>> 370a4e5000-370a4eb000 r--p 000e5000 fd:00 34443406 >>>> /usr/lib64/libstdc++.so.6.0.8 >>>> 370a4eb000-370a4ee000 rw-p 000eb000 fd:00 34443406 >>>> /usr/lib64/libstdc++.so.6.0.8 >>>> 370a4ee000-370a500000 rw-p 370a4ee000 00:00 0 >>>> 370a600000-370a61b000 r-xp 00000000 fd:00 3735614 >>>> /lib64/libpcre.so.0.0.1 >>>> 370a61b000-370a81b000 ---p 0001b000 fd:00 3735614 >>>> /lib64/libpcre.so.0.0.1 >>>> 370a81b000-370a81c000 rw-p 0001b000 fd:00 3735614 >>>> /lib64/libpcre.so.0.0.1 >>>> 370aa00000-370ab2d000 r-xp 00000000 fd:00 3735609 >>>> /lib64/libcrypto.so.0.9.8e >>>> 370ab2d000-370ad2c000 ---p 0012d000 fd:00 3735609 >>>> /lib64/libcrypto.so.0.9.8e >>>> 370ad2c000-370ad4d000 rw-p 0012c000 fd:00 3735609 >>>> /lib64/libcrypto.so.0.9.8e >>>> 370ad4d000-370ad51000 rw-p 370ad4d000 00:00 0 >>>> 370ae00000-370ae02000 r-xp 00000000 fd:00 3735579 /lib64/ >>>> libkeyutils-1.2.so >>>> 370ae02000-370b001000 ---p 00002000 fd:00 3735579 /lib64/ >>>> libkeyutils-1.2.so >>>> 370b001000-370b002000 rw-p 00001000 fd:00 3735579 /lib64/ >>>> libkeyutils-1.2.so >>>> 370b200000-370b211000 r-xp 00000000 fd:00 3735587 /lib64/ >>>> libresolv-2.5.so >>>> 370b211000-370b411000 ---p 00011000 fd:00 3735587 /lib64/ >>>> libresolv-2.5.so >>>> 370b411000-370b412000 r--p 00011000 fd:00 3735587 /lib64/ >>>> libresolv-2.5.so >>>> 370b412000-370b413000 rw-p 00012000 fd:00 3735587 /lib64/ >>>> libresolv-2.5.so >>>> 370b413000-370b415000 rw-p 370b413000 00:00 0 >>>> 370b600000-370b602000 r-xp 00000000 fd:00 3735595 >>>> /lib64/libcom_err.so.2.1 >>>> 370b602000-370b801000 ---p 00002000 fd:00 3735595 >>>> /lib64/libcom_err.so.2.1 >>>> 370b801000-370b802000 rw-p 00001000 fd:00 3735595 >>>> /lib64/libcom_err.so.2.1 >>>> 370ba00000-370ba0d000 r-xp 00000000 fd:00 3735577 >>>> /lib64/libgcc_s-4.1.2-20080825.so.1 >>>> 370ba0d000-370bc0d000 ---p 0000d000 fd:00 3735577 >>>> /lib64/libgcc_s-4.1.2-20080825.so.1 >>>> 370bc0d000-370bc0e000 rw-p 0000d000 fd:00 3735577 >>>> /lib64/libgcc_s-4.1.2-20080825.so.1 >>>> 370c200000-370c224000 r-xp 00000000 fd:00 34448793 >>>> /usr/lib64/libk5crypto.so.3.1 >>>> 370c224000-370c423000 ---p 00024000 fd:00 34448793 >>>> /usr/lib64/libk5crypto.so.3.1 >>>> 370c423000-370c425000 rw-p 00023000 fd:00 34448793 >>>> /usr/lib64/libk5crypto.so.3.1 >>>> 370c600000-370c62c000 r-xp 00000000 fd:00 34448795 >>>> /usr/lib64/libgssapi_krb5.so.2.2 >>>> 370c62c000-370c82c000 ---p 0002c000 fd:00 34448795 >>>> /usr/lib64/libgssapi_krb5.so.2.2 >>>> 370c82c000-370c82e000 rw-p 0002c000 fd:00 34448795 >>>> /usr/lib64/libgssapi_krb5.so.2.2 >>>> 370ca00000-370ca08000 r-xp 00000000 fd:00 34448792 >>>> /usr/lib64/libkrb5support.so.0.1 >>>> 370ca08000-370cc07000 ---p 00008000 fd:00 34448792 >>>> /usr/lib64/libkrb5support.so.0.1 >>>> 370cc07000-370cc08000 rw-p 00007000 fd:00 34448792 >>>> /usr/lib64/libkrb5support.so.0.1 >>>> 370ce00000-370ce46000 r-xp 00000000 fd:00 3735613 >>>> /lib64/libssl.so.0.9.8e >>>> 370ce46000-370d046000 ---p 00046000 fd:00 3735613 >>>> /lib64/libssl.so.0.9.8e >>>> 370d046000-370d04c000 rw-p 00046000 fd:00 3735613 >>>> /lib64/libssl.so.0.9.8e >>>> 370d200000-370d291000 r-xp 00000000 fd:00 34448794 >>>> /usr/lib64/libkrb5.so.3.3 >>>> 370d291000-370d491000 ---p 00091000 fd:00 34448794 >>>> /usr/lib64/libkrb5.so.3.3 >>>> 370d491000-370d495000 rw-p 00091000 fd:00 34448794 >>>> /usr/lib64/libkrb5.so.3.3 >>>> 370e600000-370e65c000 r-xp 00000000 fd:00 34447348 >>>> /usr/lib64/libodbc.so.1.0.0 >>>> 370e65c000-370e85c000 ---p 0005c000 fd:00 34447348 >>>> /usr/lib64/libodbc.so.1.0.0 >>>> 370e85c000-370e864000 rw-p 0005c000 fd:00 34447348 >>>> /usr/lib64/libodbc.so.1.0.0 >>>> 2aaaaaaab000-2aaaaad2a000 rw-p 2aaaaaaab000 00:00 0 >>>> 2aaaaad2a000-2aaaaadab000 rw-s 00000000 00:09 2424836 /SYSV30000363 >>>> (deleted) >>>> 2aaaaadab000-2aaaab5ab000 rw-s 00000000 fd:00 47777386 >>>> /var/sipxdata/tmp/imdb.odb >>>> 2aaaab5b6000-2aaaab5c0000 r-xp 00000000 fd:00 3735578 >>>> /lib64/libnss_files-2.5.so >>>> 2aaaab5c0000-2aaaab7bf000 ---p 0000a000 fd:00 3735578 >>>> /lib64/libnss_files-2.5.so >>>> 2aaaab7bf000-2aaaab7c0000 r--p 00009000 fd:00 3735578 >>>> /lib64/libnss_files-2.5.so >>>> 2aaaab7c0000-2aaaab7c1000 rw-p 0000a000 fd:00 3735578 >>>> /lib64/libnss_files-2.5.so >>>> 2aaaac000000-2aaaac0bb000 rw-p 2aaaac000000 00:00 0 >>>> 2aaaac0bb000-2aaab0000000 ---p 2aaaac0bb000 00:00 0 >>>> 2b9ffd35a000-2b9ffd35b000 rw-p 2b9ffd35a000 00:00 0 >>>> 2b9ffd366000-2b9ffd372000 rw-p 2b9ffd366000 00:00 0 >>>> 7fffe8bae000-7fffe8bc3000 rw-p 7ffffffea000 00:00 0 [stack] >>>> ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0 [vdso] >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> sipx-users mailing list >>>> [email protected] >>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>>> >>> >>> >>> >>> -- >>> ====================== >>> Tony Graziano, Manager >>> Telephone: 434.984.8430 >>> sip: [email protected] >>> Fax: 434.984.8431 >>> >>> Email: [email protected] >>> >>> LAN/Telephony/Security and Control Systems Helpdesk: >>> Telephone: 434.984.8426 >>> sip: [email protected] >>> Fax: 434.984.8427 >>> >>> Helpdesk Contract Customers: >>> http://www.myitdepartment.net/gethelp/ >>> >>> Why do mathematicians always confuse Halloween and Christmas? >>> Because 31 Oct = 25 Dec. >>> >>> >>> _______________________________________________ >>> sipx-users mailing [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> >>> >>> >>> _______________________________________________ >>> sipx-users mailing list >>> [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> >> >> >> >> -- >> ====================== >> Tony Graziano, Manager >> Telephone: 434.984.8430 >> sip: [email protected] >> Fax: 434.984.8431 >> >> Email: [email protected] >> >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> sip: [email protected] >> Fax: 434.984.8427 >> >> Helpdesk Contract Customers: >> http://www.myitdepartment.net/gethelp/ >> >> Why do mathematicians always confuse Halloween and Christmas? >> Because 31 Oct = 25 Dec. >> >> > > > -- > ====================== > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: [email protected] > Fax: 434.984.8431 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > sip: [email protected] > Fax: 434.984.8427 > > Helpdesk Contract Customers: > http://www.myitdepartment.net/gethelp/ > > Why do mathematicians always confuse Halloween and Christmas? > Because 31 Oct = 25 Dec. > > > _______________________________________________ > sipx-users mailing [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
