similar to: Samba aborts with exit code "134"

Displaying 20 results from an estimated 200000 matches similar to: "Samba aborts with exit code "134""

2014 Aug 07
2
Exit status code 134; what is it, in the context of Dovecot Antispam plug-in?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 7 Aug 2014, Ben Johnson wrote: > On 7/29/2014 11:20 AM, Ben Johnson wrote: >> On 7/29/2014 3:13 AM, Steffen Kaiser wrote: >>> On Mon, 28 Jul 2014, Ben Johnson wrote: >>> >>>> I have some debugging output in my pipe script; the output looks >>> >>> How does your script looks like?
2014 Aug 08
1
Backtrace io_add(0x1) called twice fd= (was Exit status code 134; what is it, in the context of Dovecot Antispam plug-in?)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 7 Aug 2014, Ben Johnson wrote: > On 8/7/2014 11:14 AM, Steffen Kaiser wrote: >> one idea: http://www.tldp.org/LDP/abs/html/exitcodes.html >> >> exit code 134 would be in bash's meaning (if this website is >> correct all) some program died off signal 6. This would be Abort in >> Linux. >> >>
2014 Jul 29
0
Exit status code 134; what is it, in the context of Dovecot Antispam plug-in?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 28 Jul 2014, Ben Johnson wrote: > I have some debugging output in my pipe script; the output looks How does your script looks like? > Copying message contents to temporary file for debugging purposes; file > is: /tmp/sendmail-msg-7662.txt > Checking if the command-line input argument string (--spam) contains the > string
2014 Jul 29
3
Exit status code 134; what is it, in the context of Dovecot Antispam plug-in?
Hello! I just migrated from Ubuntu 12.04 LTS to 14.04 LTS and thereby from Dovecot 2.0.19 to 2.2.9. I've been using dovecot-antispam plugin with great success for the past year with 2.0.19, but after this migration, I've been seeing the exit status code 134 in the syslog when attempting to debug the Dovecot Antispam plugin not working after the migration. I have some debugging output in
2009 Jun 29
0
Asterisk ended with exit status 134... Asterisk exited on signal 6.
I was trying to enable CDR in a mysql-database when the following occured : asterisk*CLI> cdr status CDR logging: enabled CDR mode: simple CDR output unanswered calls: yes CDR registered backend: cdr_manager CDR registered backend: cdr-custom asterisk*CLI> exit [Jun 29 21:56:52] Executing last minute cleanups [root at asterisk asterisk]# vi modules.conf [root at asterisk asterisk]# service
2002 Feb 19
1
Samba exit on signal 6
Hi! I use samba with FreeBSD 4.4. And sometimes (when i restart computer) Samba does not start. In error i have error like this server /kernel: pid 228 (nmbd), uid 0: exited on signal 6 (core dumped) Then i have to start manualy, and everything works. And there is one strange thing. Sometimes this machine is not visible from other computers for about max of 1 - 2 minutes. Sometimes less than 1
2018 Feb 28
0
[PATCH] lib: Don't abort if a signal handler calls exit(2) during a guestfs_* function.
$ virt-sparsify input output [ 0.0] Create overlay file in /tmp to protect source disk [ 0.0] Examine source disk ^C guestfs_close: g->lock: Device or resource busy Aborted (core dumped) The reason for this is because virt-sparsify calls exit(2) in the SIGINT signal handler, which causes the close_handles atexit handler to run, which calls guestfs_close. However the same handle is in the
2023 Mar 08
2
[libnbd PATCH v2] lib/errors.c: Fix assert fail in exit path in multi-threaded code
When a highly multi-threaded program such as nbdcopy encounters an error, there is a race condition in the library which can cause an assertion failure and thus a core dump: (1) An error occurs on one of the threads. nbdcopy calls exit(3). (2) In lib/errors.c, the destructor calls pthread_key_delete. (3) Another thread which is still running also encounters an error, and inside libnbd the
2020 Mar 23
0
Samba still DNS Exit Code 23
On 23/03/2020 14:59, mauri via samba wrote: > Meny thanks for our fast answer ! > > root at AD:/source# cat /tmp/samba-debug-info.txt > Collected config --- 2020-03-23-15:57 ----------- > > Hostname: AD > DNS Domain: Caloro.m > FQDN: AD.Caloro.m > ipaddress: 192.168.1.7 > > ----------- > > Kerberos SRV _kerberos._tcp.Caloro.m record verified ok, sample
2013 Sep 15
1
Executing a code until a new user input aborts it (readlines?)
Hi, I know that with readlines you can start executing a code upon user input. What I would like to do is to have the ability to abort a code based on a new user input. E.g. when the user hits enter the code stops running. That is, I would periodically check for a user input and stop the code when the correct input was entered. Below is an example of a function which would run an endless loop
2010 Feb 03
1
ctrl-C aborts R when compiling package code with ICC+openMP
Hi all, I have some C++ code that I call from my package. In my main C++ loop, I check for user interrupts and return to the R shell after ensuring I've deallocated memory appropriately. This works fine when the code is compiled with gcc+openmp and with icc without openmp, but when I compile with icc and use openmp, the entire R session is immediately terminated when I hit ctrl-C. This
2020 Mar 23
0
Samba still DNS Exit Code 23
Your welkom Can you run this : https://raw.githubusercontent.com/thctlo/samba4/master/samba-collect-debug-info.sh Anonimize where needed. That should tell use enough to see whats going on. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > mauri via samba > Verzonden: maandag 23 maart 2020 14:13 > Aan:
2020 Mar 24
7
Samba still DNS Exit Code 23
Yesterday i delete the hole debian machine and rebuild Samba ad-dc Same issu, thanks for any help or update. root at AD:/home/mauri# kinit Administrator Password for Administrator at CALORO.M: kinit: Password incorrect while getting initial credentials root at AD:/source# cat /tmp/samba-debug-info.txt Collected config --- 2020-03-24-12:27 ----------- Hostname: AD DNS Domain: CALORO.M FQDN:
2003 Sep 19
1
[Bug 691] All connections aborts
http://bugzilla.mindrot.org/show_bug.cgi?id=691 Summary: All connections aborts Product: Portable OpenSSH Version: 3.7.1p1 Platform: MIPS OS/Version: IRIX Status: NEW Severity: major Priority: P2 Component: Build system AssignedTo: openssh-bugs at mindrot.org ReportedBy: d.guy at free.fr
2004 May 03
1
Install of 3.1 aborts
Hello everybody, yes I did check the installation medium (dvd), so that's not the problem. My system only contains components which are accepted by the redhat hardware compatibiliy list. But anaconda fails, announcing: You are trying to install on a machne which isn't supported by this release of CentOS-3 The error message stems from this part of anaconda code in packages.py: # this
2019 Jun 08
0
Determining the exit code of an "almost finished" R script
On 08/06/2019 9:55 a.m., Gergely Dar?czi wrote: > On Sat, Jun 8, 2019 at 2:13 PM Duncan Murdoch <murdoch.duncan at gmail.com> wrote: >> >> On 08/06/2019 7:42 a.m., Gergely Dar?czi wrote: >>> Dear All, >>> >>> I'm using "reg.finalizer" in a function that is to be called in R scripts >>> to do some cleanup on success. I have not
2019 Jun 08
2
Determining the exit code of an "almost finished" R script
Dear All, I'm using "reg.finalizer" in a function that is to be called in R scripts to do some cleanup on success. I have not found a way to run the function only if the script run without errors, so when the exit code is expected to be 0. What I've tried is checking "geterrmessage()", but unfortunately it's not perfect: if an error was handled with eg
2002 Feb 04
0
hang on exit
> Woa! > > What's up with this? Why a server-side patch? I thought we'd all > agreed that this needs to be a client-side decision. After all, the > client knows when the session exits and can choose what to do. > It is the server side that is making the (bad -- my opinion) decision about when to disconnect and thus what needs to be tweaked. I've offered an available
2001 Apr 27
0
exit codes of samba tools: not really a bug, but a proposal
Hi there, this is not really a bug report, but on the other hand it may be fixed without too much effort in one of the next minor releases: the 'nmblookup' (and possibly other) tools don't return a non-zero exit code on failure (e.g.: nmblookup exits "$?=0" even when reporting 'name_query failed to find name ...'). For scripting, it'd be good to have a
2020 Mar 23
2
Samba still DNS Exit Code 23
Meny thanks for our fast answer ! root at AD:/source# cat /tmp/samba-debug-info.txt Collected config --- 2020-03-23-15:57 ----------- Hostname: AD DNS Domain: Caloro.m FQDN: AD.Caloro.m ipaddress: 192.168.1.7 ----------- Kerberos SRV _kerberos._tcp.Caloro.m record verified ok, sample output: Server: 192.168.1.9 Address: 192.168.1.9#53 _kerberos._tcp.caloro.m service = 0 0 88