similar to: xen save/restore causes cron to hang

Displaying 20 results from an estimated 30000 matches similar to: "xen save/restore causes cron to hang"

2008 Nov 12
0
xen save/restore causes cron to hang
Joe Pruett wrote: > i haven't found anything online to talk about this, so maybe i've got > something odd going on here. i have my xen set up to save/restore on dom0 > reboot. almost everything works fine, but cron on the guest os'es > (everything is centos 5 x86_64) stop processing jobs. i'm guessing it is > missing an alarm or something like that. anyone
2002 Jul 05
1
Why can't I save/restore block devices?
Hello everybody, I'd like to save/restore some partitions on my harddrive via rsync. (They happen to contain other os'es, so I can't safely mount the partitions read/write). So, I'd like to do something like rsync /dev/hda1 server::images/part_1.image -c -z -B65536 -S but: - "skipping non-regular file part_1" is misleading. Not the destination is not a file, the
2003 Apr 20
0
4400+ cron processes causes server crash ...
Evening all ... One of my servers just crashed with the "pmap_new_proc: u_map allocation failed" ... Looking at a ps of the vmcore file, I find: neptune# awk '{print $11}' /tmp/ps.crash | sort | uniq -c 1 (Xvfb) 1 (aac0aif) 1 (adjkerntz) 1 (analog) 1 (bufdaemon) 4412 (cron) 8 (csh) 84 (ctl_cyrusdb) 3 (ctl_deliver) 1 (emacs) 1 (find) 1
2002 Nov 15
0
[Bug 125] with BSM auditing, cron editing thru ssh session causes cron jobs to fail
http://bugzilla.mindrot.org/show_bug.cgi?id=125 ------- Additional Comments From Brian.King at xwave.com 2002-11-16 07:20 ------- One of the suggested work-a-rounds was to set "UseLogin yes" in sshd_config. This does not work 100% of the time. SSH clients used in non-interactive modes still exhibit the problem. e.g.: ssh {hostname} "crontab -l >crontmp ; crontab
2008 Sep 16
5
i didn't see the 4.7 announcement
i (and others) have missed messages on centos-devel as well. did other people not see the 4.7 announcement message? i'm wondering if the centos list server is having some kind of issue.
2003 Jan 03
1
[Bug 125] with BSM auditing, cron editing thru ssh session causes cron jobs to fail
http://bugzilla.mindrot.org/show_bug.cgi?id=125 ------- Additional Comments From jrj at purdue.edu 2003-01-04 06:29 ------- The following attachment updates the suggested patch to 3.5p1. The attachment is a gzip'd tar file. Once you download it, ungzip it and then untar it into a temp directory (or use the 'z' option of GNU tar). Then look at the README for more information.
2002 Jul 14
3
[Bug 125] with BSM auditing, cron editing thru ssh session causes cron jobs to fail
http://bugzilla.mindrot.org/show_bug.cgi?id=125 ------- Additional Comments From jrj at purdue.edu 2002-07-14 13:31 ------- Created an attachment (id=131) Update of bug #2 patch to 3.4p1 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
2003 Mar 25
0
[Bug 125] with BSM auditing, cron editing thru ssh session causes cron jobs to fail
http://bugzilla.mindrot.org/show_bug.cgi?id=125 dleach at securenet.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dleach at securenet.com.au ------- You are receiving this mail because: ------- You are the assignee for the bug, or are
2003 Jul 09
1
[Bug 125] with BSM auditing, cron editing thru ssh session causes cron jobs to fail
http://bugzilla.mindrot.org/show_bug.cgi?id=125 ------- Additional Comments From jrj at purdue.edu 2003-07-10 08:23 ------- Created an attachment (id=355) --> (http://bugzilla.mindrot.org/attachment.cgi?id=355&action=view) Gzip'd tar file with 3.6p1 (and later) patch This version of the patch applies against 3.6p1 (and later). In addition to being an update to a new release,
2003 Nov 15
0
[Bug 125] with BSM auditing, cron editing thru ssh session causes cron jobs to fail
http://bugzilla.mindrot.org/show_bug.cgi?id=125 jrj at purdue.edu changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #438 is|0 |1 obsolete| | ------- Additional Comments From jrj at purdue.edu 2003-11-15 16:00 ------- Created an
2004 Mar 03
2
[Bug 125] with BSM auditing, cron editing thru ssh session causes cron jobs to fail
http://bugzilla.mindrot.org/show_bug.cgi?id=125 jrj at purdue.edu changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #500 is|0 |1 obsolete| | ------- Additional Comments From jrj at purdue.edu 2004-03-04 10:33 ------- Created an
2004 May 31
1
[Bug 125] with BSM auditing, cron editing thru ssh session causes cron jobs to fail
http://bugzilla.mindrot.org/show_bug.cgi?id=125 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #619 is|0 |1 obsolete| | ------- Additional Comments From dtucker at zip.com.au 2004-05-31 23:25 -------
2003 Sep 19
3
[Bug 125] with BSM auditing, cron editing thru ssh session causes cron jobs to fail
http://bugzilla.mindrot.org/show_bug.cgi?id=125 jrj at purdue.edu changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #192 is|0 |1 obsolete| | Attachment #355 is|0 |1 obsolete|
2005 Jan 14
3
Bug#290511: logcheck: syslogd restart in cron.daily/sysklogd causes a log message
Package: logcheck Version: 1.2.32 Severity: wishlist /etc/cron.daily/sysklogd restarts syslogd at the end of the script. This causes a daily log message, currently missed by logcheck: Jan 14 06:55:22 pyloric syslogd 1.4.1#16: restart (remote reception). I'm currently using this regex in ignore.server.d/local-syslogd: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ syslogd 1\.4\.1#16: restart \(remote
2004 Apr 14
8
[Bug 125] with BSM auditing, cron editing thru ssh session causes cron jobs to fail
http://bugzilla.mindrot.org/show_bug.cgi?id=125 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |enhancement ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
2018 May 24
0
Winbindd (tdb_chainlock_with_timeout_internal: alarm (40) timed out for key)
On Thu, 24 May 2018 09:32:56 -0300 Carlos via samba <samba at lists.samba.org> wrote: > Hi! > > I have 3 server: > > S.O. -  Debina 8 > > Winbind Version : 2:4.2.10+dfsg-0+deb8u3 > > Member Domain > > Samba Server : Ubuntu 14.04 with Samba 4.7.7 , are 18 Dcs > > --------------------- > > > In day 21/05 , the 3 server have same problema
2007 Sep 24
0
Spur error with Siemens Hi Path
Hi, I have an IBM server running latest asterisk 1.4.x connected to a Siemens hi-path user a TE120P single-span. Approx every 8 hours (although not every 8 hours and sometimes 2 in a row) at exactly the same time I see the following errors Does anyone have any suggestions / ideas ? Thanks Ruairi Sep 24 11:56:30 asterisk01 -- MARK -- Sep 24 11:59:02 asterisk01 ntpd[3615]: synchronized to
2013 Nov 18
2
[PATCH] al175: updated driver, please restore it
On Tue, Jan 27, 2009 at 04:39:13PM +0100, Arnaud Quette wrote: > Hi Kirill, > > 2009/1/27 Kirill Smelkov <kirr at mns.spb.ru> > > > On Tue, Jan 13, 2009 at 05:58:23PM +0300, Kirill Smelkov wrote: > > > Arjen, Arnaud, > > > first of all, I'm sorry for my late reply. > > > > > > If it's not too late, here is updated al175: >
2018 Dec 19
0
Winbindd (tdb_chainlock_with_timeout_internal: alarm (40) timed out for key)
Hey, But What's the reason of this error? On 05/25/2018 04:58 AM, Carlos via samba wrote: > Hi! > > Thanks  for answer! > > In future my plan is update, but this momento is no possible.. :-| > > But, same error, in same time, in 3 server, is very strange.... > > Regards; > > > On 24-05-2018 15:38, Rowland Penny via samba wrote: >> On Thu, 24 May
2008 Feb 24
1
beta4: outgoing call causes Red Alarm on TDM400P
Calling out on PSTN over a TDM400P seems to generate a Red Alarm - whatever that is. I have another extension on the PSTN, and I can dial out over that. zttool shows no alarms. asterisk*CLI> zap show status Description Alarms IRQ bpviol CRC4 Fra Codi Options LBO Wildcard TDM400P REV I Board 1 OK 0 0 0 CAS Unk YEL 0 db