Hi！I had run a freeswitch for a callcenter ivr service.
During this time, freeswitch crash twice for the similar reasons below:
freeswitch[39310]: segfault at 7f556d514638 ip 00007f55dd909dc6 sp
00007f556d514640 error 6 in libspeexdsp.so.1.5.0[7f55dd8ff000+12000]
Dec 6 17:37:08 calltest kernel: freeswitch[19590]: segfault at
7f96ca9c8b18 ip 00007f96cb3b4dc6 sp 00007f96ca9c8b20 error 6 in
libspeexdsp.so.1.5.0[7f96cb3aa000+12000]
OS version: CentOS release 6.6 (Final)
freeswitch version: FreeSWITCH Version 1.4.19~64bit (64bit)
How can I find out what happen to freeswitch, and fixed the problem?
Thank you for your time.
you need to upgrade FreeSWITCH to the latest version, and open a Jira ticket if the problem persists. You will need to attach as much as possible logs and information to the ticket, so that it's possible to analyze and maybe reproduce.
Also the best would be to migrate to FreeSWITCH version 1.6, as most of development is happening there, and the bugs get fixed faster.
Related
I've upgraded the Windows 10 to 1809 for test purposes and now the SCCM client has the problem that it needs a very long time until it starts and then aborts with the error:
Loading Software Center returned error code 0x80041001 (-2147217407).
Unfortunately I do not really find much under the error message, are there any solutions for that?
If I reset the Windows installation and then install the SCCM client everything works fine again ...
System information:
Version 1810
Console version: 5.1810.1075.2000
Site version: 5.0.8740.1000
Small addendum, after I did the following everything seems to work again:
SCCM Upgrade
SCCM client deinstallation
WMIRepair (Roger Zander)
Reinstall SCCM client
We are observing frequent crashes of our Production JVM which runs webMethods v9.12.
After analyzing the crash dumps, we came to conclusion that the reason could be some of the libraries in Tuxedo 12.1.1.0 Client because the crash dump mentioned that the problematic frame was in libwsc.so.71.
To give a history of the issue, the problem of Crash was existing from long time when we were running older version of webMethods (8.2) on JVM 1.6. When we were installing the same, we observed these frequent crashes with Tuxedo 8.x. So, up on advice from our Tuxedo Server Ops Team, we upgraded the Tuxedo client to 12.1.1.0 which reduced the number of crashes considerably.
However, now after upgrading to version 9.12, we are observing the issue of frequent crashes again.
Before Upgrade:
Java Version: 1.6.0_27
Tuxedo: 12.1.1.0
After Upgrade:
Java Version: 1.8.0_151
Tuxedo: 12.1.1.0
Please find sample crash file here
Appreciate any pointers to resolve these crash issues.
I suggest you to report this issue on https://support.oracle.com/ and try to get some help there. I've reported several Tuxedo issues there myself and got fixes or workarounds.
I think StackOverflow is a bad place for asking such questions about Oracle's proprietary software. Programming, configuration - yes, crashes - no/
After trying to start the run mode, I get a fatal error on the target system :
Init7\IO: Set State TComObj PREOP OP >> AdsWarning: 1861 (0x745, ADS
ERROR: timeout elapsed) Anyone of you know how to fix it??
Is your target system running Windows 10? Has it recently been updated (Windows Update) to version 1803? If so, the problem is because TwinCAT is not compatible with the 1803-version of W10. Beckhoff did release an updated TwinCAT version 3.1.4022.20, but removed it as it caused other problems. They will release a new version in the coming days.
That often occurs when you have EtherCAT bus in the system and there are problems. For example you could have an EtherCAT slave configured and it is not found when trying to start the system. So check you I/O configuration.
Of course, the problem could also be the one that Jakob described.
We ran into intermittent 1861 (0x745) errors with Twincat2 on Win10 version 1809 communicating with a CX8090. We did not see the intermittent 1861 errors on Win10 version 1709.
Based off of Jakob's, answer we tried updating the TcAdsDll.dll and AdsDll.dll from the latest Twincat 2.11 x64 Engineering release install (which was 2305) and it resolved our intermittent 1861 errors.
I'm not sure if anyone else out there still uses Twincat2, but this might help someone else searching for a solution to the 1861 error code.
I have downloaded WSO2 IoT server version 3.0.0, and followed all the instructions to run the product on Windows 10 machine with JDK 1.8 installed. Everything was going fine until I tried to download virtual fire alarm device agent.
Simple, it was not working, and a blank page with no response was all that I have got. Then I tried the same for a Raspberry Pi device, and again the device agent failed to be downloaded. It is interesting that this bug was reported for Alpha and 3.1.0 product versions, so it seemed that the current official version is free from this.
Do you have any explanation of this ill behavior (it doesn't seem to me that anything is missing in the documentation)?
I've found this helpful tutorial on web
http://blog.rayapps.com/2009/09/14/how-to-install-oracle-database-10g-on-mac-os-x-snow-leopard/
I've followed all steps, but, I've a problem with netca run. When I'll start it, crash with this error:
Invalid memory access of location 00000014 eip=11069523
/opt/oracle/product/10.2.0/db_1/jdk/jre/bin/java: line 2: 10323 Bus error /System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home/bin/java -d32 -Xbootclasspath/a:/opt/oracle/product/10.2.0/db_1/jdk/jre/lib/ext:/opt/oracle/product/10.2.0/db_1/jdk/lib/ext $*
and the error message on popup show that the problem is with libnjni10.jnilib plugin. On snow leopard there is only Java 1.6 but I've installed also JDK1.5 and I've changed the symbolic link for 1.4.2 to run the 1.5
Any idea?
thanks a lot!
Andrea
Alex Gorbachev's install guide suggests a couple of different ways of resolving this problem - editing runinstaller or installing JDK 1.4.2. Check it out.
Try Using VMWare
Is this for development purposes? I've been happy with installing Oracle on a VMWare Linux instance. One nice feature is that I can prep my database as I like, take a VMWare snapshot, and roll back to the saved snapshot as necessary.