similar to: Tinc doesn't connect

On Thu, Mar 08, 2001 at 11:51:53AM +0100, Marcel Loesberg wrote: > I'm going to build a VPN and I want to use either Tinc or FreeS/WAN. > I've started building the VPN with FreeS/WAN and I find things are getting > rather complicated. > I looks like Tinc is much easier to configure but in the FAQ and in what I've > seen of the documentation so far there is no mention of

Was running 1.0pre2 just fine, but had to move machines, so I figgured I'd give 1.0pre3 a try. After getting everything to build and figguring out the new config files, here's where I'm stuck. Start the server process (remote machine). Start the client process (local machine). In remote machine, the following shows up in syslog: tinc[2659]: Got SEGV signal In local machine, the

libswfdec/swfdec_as_object.c | 62 +++++++++++++++------- test/trace/Makefile.am | 9 +++ test/trace/addProperty-set-prototypes-5.swf |binary test/trace/addProperty-set-prototypes-5.swf.trace | 4 + test/trace/addProperty-set-prototypes-6.swf |binary test/trace/addProperty-set-prototypes-6.swf.trace | 5 +

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, 4.2 and 4.1 suffers from SEGV during xl network-attach in libxl__device_nic_add. In 4.3-unstable it is fixed by: 5420f2650 libxl: Set vfb and vkb devid if not done so by the caller So either the patch need to be backported to 4.1 and 4.2, or fixed by this one: - ------ libxl: Fix SEGV in network-attach When "device/vif" directory

On Fri, Jun 17, 2011 at 12:04 PM, Renato Golin <rengolin at systemcall.org>wrote: > On 17 June 2011 08:55, Kostya Serebryany <kcc at google.com> wrote: > > I am rather reluctant to add 'generic' code that handles unknown/untested > > platforms because the memory mapping is very platform specific anyway. > > Indeed, but the point of that is more for helping

Hi all, I had an issue this morning with one of my virtual machines. It wouldn't boot (into any runlevel), nor could I chroot into the root partition using a rescue disk. Unfortunately I didn't grab a screenshot, however the error(s) when booting were: /pre-pivot/50selinux-loadpolicy.sh: 14 <other messages> init: readahead main process (425) killed by SEGV signal init:

On 17 June 2011 09:14, Kostya Serebryany <kcc at google.com> wrote: > Maybe the fallback code should just use a function call. Much simpler for > documentation purposes. Sounds good. On 32-bit, the shadow region is: > [0x28000000, 0x3fffffff] HighShadow [0x24000000, 0x27ffffff] ShadowGap [0x20000000, > 0x23ffffff] LowShadow > > This is 0.5G total. So, I mmap all these

2016-09-02 20:40 GMT+02:00 George Joseph <gjoseph at digium.com>: > > > On Fri, Sep 2, 2016 at 9:34 AM, Olivier <oza.4h07 at gmail.com> wrote: > >> Hello, >> >> I had a recent case where Asterisk stopped due to a segfault. >> This reminded me that being sure that whenever such issue occurs, it's >> useful to have a core file or various

On Tue, Sep 6, 2016 at 1:55 AM, Olivier <oza.4h07 at gmail.com> wrote: > Hello, > > After testing "pkill -SEGV -f /usr/sbin/asterisk" on Debian Jessie > platform, I've got several questions : > > > 1. When I issue a "cd /tmp; asterisk -cvvvvvvvvvvvg -U asterisk -G > asterisk" command, and then issue a "pkill -SEGV asterisk" command,

Hello: I have a Windows 2003 Server that is causing rpcclient to SEGV via the following command: $ rpcclient -U Administrator%foobar -c 'netshareenum 502' <server> ... type: 0x6269: SEC_DESC_OWNER_DEFAULTED SEC_DESC_DACL_DEFAULTED SEC_DESC_SACL_DEFAULTED SEC_DESC_DACL_TRUSTED SEC_DESC_SACL_AUTO_INHERIT_REQ SEC_DESC_SACL_PROTECTED SEC_DESC_RM_CONTROL_VALID SACL Segmentation fault

Ok, folks, I brought this up some time ago, and got no replies. We have a good number of systems - > 100 - and we use sssd. On the C 7 boxen, which is most of them, gssproxy *frequently* (like once a day or so) dies with a SEGV. It restarts fine. Dies again eventually. ARE other people seeing this? If so, I guess we get to file a bug report with upstream. Speaking as an old C

Hi all, I am trying to write a D script which would print ustack() for every program in the system receiving SIGSEGV. All the stacks printed in trap()/sigtoproc() context do not have meaningful symbols. The following solves the problem to some degree but I''d much rather have a self-contained D script. dtrace -w -n ''fbt:genunix:sigtoproc:entry/arg2 == 11/ {

Hi experts, The libvirtd can’t start on my server after the server interruption of power supply, the status is below: [root@openstack3 libvirt]# service libvirtd status Redirecting to /bin/systemctl status libvirtd.service libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled) Active: failed (Result: signal) since Tue 2015-03-24

Note that I've set the SA_NODEFER flag for the SEGV handler in the ASan runtime only a couple of days ago. Not sure that could've affected this test though; without that flag the second SEGV would've simply crashed the program. But you can try removing the flag from compiler-rt/trunk/lib/sanitizer_common/sanitizer_posix_libcdep.cc and see if that makes any difference. HTH, Alex On

On Fri, Jun 17, 2011 at 12:42 PM, Renato Golin <rengolin at systemcall.org>wrote: > On 17 June 2011 09:14, Kostya Serebryany <kcc at google.com> wrote: > >> Maybe the fallback code should just use a function call. Much simpler for >> documentation purposes. > > > Sounds good. > I implemented the asm-free way to report warnings as an option to the llvm

Hello, I carefully read [1] which details how backtrace files can be produced. Maybe this seems natural to some, but how can I go one step futher, and check that produced XXX-thread1.txt, XXX-brief.txt, ... files are OK ? In other words, where can I find an example on how to use one of those files and check by myself, that if a system ever fails, I won't have to wait for another failure to

One of my servers has recently started giving an error every time I run "aide --check". I ran it manually twice today with the same results. The second time, I added the -V flag, but that didn't give me anything useful. The system is currently running CentOS 5.3. Nothing on the system has changed recently (that I am aware of). The Aide database hasn't been updated in a few

Hi all, I have been experiencing the failure of the address sanitizer regression tests for a PPC64 target (Power7 machine). My understanding is that most of the failures are related with the fact the stack is not being dumped. I tried to understand what might be wrong and started by looking into the null_deref.cc test as it hangs during the test run. I observe that after the detection of the

Package: xen-utils-4.4 Version: 4.4.1-9 Severity: normal # /usr/lib/xen-4.4/bin/xl create -c /etc/xen/katana Parsing config from /etc/xen/katana libxl: error: libxl_utils.c:217:logrename: failed to rotate logfile - could not rename /var/log/xen/qemu-dm-katana.log.6 to /var/log/xen/qemu-dm-katana.log.7: Permission denied Segmentation fault The above happens repeatably when I run xl on a system

On Mon, Sep 8, 2014 at 7:00 PM, Samuel F Antao <sfantao at us.ibm.com> wrote: > Alexey, Alexander, > > Thanks for the suggestions. I tried removing the flag SA_NODEFER but it > didn't do any good... I have been digging into the problem with the > null_deref test today but I was unable to clearly identify the problem. I > suspect that it was either a bug with the