similar to: Dieing?

Here is the log over a 12 hour period: pid 91923 (pop3), uid 25039: exited on signal 6 pid 98265 (pop3), uid 25039: exited on signal 6 pid 95547 (pop3), uid 25039: exited on signal 6 pid 235 (pop3), uid 25039: exited on signal 6 pid 239 (pop3), uid 25039: exited on signal 6 pid 318 (pop3), uid 25039: exited on signal 6 pid 386 (pop3), uid 25039: exited on signal 6 pid 415 (pop3), uid 25039:

Is there some automated system to import windows accounts into a samba or a samba ldap situation? I've got a few hundred users on an NT domain, and I'd like to migrate them sometime before the last piece of hardware supported by NT4 rusts. Right now several linux based samba servers are doing all of the heavy lifting (shared files printers etc), but they are all looking at the domain

On Wed, Feb 4, 2015 at 4:55 PM, Warren Young <wyml at etr-usa.com> wrote: >>> >> There have been remotely exploitable vulnerabilities where an arbitrary file could be read > > CVEs, please? > > I?m aware of vulnerabilities that allow a remote read of arbitrary files that are readable by the exploited process?s user, but for such an exploit to work on /etc/shadow,

I''m having a hell of a time trying to get my site stable with lighttpd/fcgi. Here''s a sample of the fcgi error log: 2005-04-06 09:29:03: (mod_fastcgi.c.2782) response not sent, request sent: 1167 connection-fd: 26 fcgi-fd: 28 2005-04-06 09:29:03: (mod_fastcgi.c.1921) unexpected end-of-file (perhaps the fastcgi process died): pid: 25117 fcgi-fd: 31 remote-fd: 29 2005-04-06

Hi all, 1.0-test76 is crashing about every two weeks. Got this in the log file: pid 76217 (dovecot-auth), uid 0: exited on signal 6 (core dumped) pid 61724 (dovecot-auth), uid 0: exited on signal 6 (core dumped) pid 52961 (dovecot-auth), uid 0: exited on signal 6 (core dumped) pid 81257 (dovecot-auth), uid 0: exited on signal 6 (core dumped) Also a bunch of these around the same time...

Hi One of the two mongrel processes has died in the middle of the night four times in the past 9 days, and I need help debugging this. Each time the symptoms are the same: * Each time I can restart the process via cap -a restart_app. * Before the restart, there is nothing unusual in production.log or mongrel.log. * During the restart, about 100 repetitions of an error message are generated in

We recently began seeing server crashes in our cluster related to "pop3-login", which is causing "oom-killer" to be invoked. The server only recovers after a reboot. From dovecot.conf: login_process_per_connection = yes login_processes_count = 16 login_max_processes_count = 256 (Should we try switching processes_per_connection to no?) From dovecot.log: dovecot: Apr 17

Hi list, In our platform we have a lot of machines in which the system is a single disk image loaded on RAM from PXE. The problem is quite simple : if I install puppetd on the image, I will end up using the same certificate for 100 different servers with different names (the hostname is setup at boot time from dhcp) and I guess the puppetmaster won''t allow that. In other words : what

Hi Simon, thanks for your quick reply. 1) ... so you can reproduce this? 2) Do you know a way how this can be 'foreseen'? We allocate larger matrices in the copula package depending on the user's input dimension. It would be good to tell her/him "Your dimension is quite large. Be aware of killers in your neighborhood"... before the killer attacks. Thanks & cheers,

Hi all, I originally posted this on postfix's mailing list but then realized that this COULD be a pop3 server problem since that downloads and deletes mail. This has only been happening since I upgraded from .99 to 1.0-7 ... Our users have been reporting double messages in their inbox, as well as emails that they deleted a long time ago reappearing. The only thing in my maillog is a

Hi all, Just watching for my first time the 'oom-killer' call in a CentOS 4.2 workstation. System was running normally but with high load of nice process, iow, rosetta and seti, others appart, nautilus, etc... i realized that after a night of standby running normally, the next moorning after few manual operations from X-session in local console, it started a massive swapping, this time

On Tue, Aug 06, 2019 at 01:54:56AM +0000, Grant Street wrote: > Try checking your /var/log/messages for OOM killer log lines. If your machine is running low on memory the oom killer will start killing high memory usage programs. > > Grant we have watched top while it runs and there's no evidence of a memory shortage. > ________________________________________ > From: CentOS

Excessive virtio_balloon inflation can cause invocation of OOM-killer, when Linux is under severe memory pressure. Various mechanisms are responsible for correct virtio_balloon memory management. Nevertheless it is often the case that these control tools does not have enough time to react on fast changing memory load. As a result OS runs out of memory and invokes OOM-killer. The balancing of

Excessive virtio_balloon inflation can cause invocation of OOM-killer, when Linux is under severe memory pressure. Various mechanisms are responsible for correct virtio_balloon memory management. Nevertheless it is often the case that these control tools does not have enough time to react on fast changing memory load. As a result OS runs out of memory and invokes OOM-killer. The balancing of

> Can you elaborate on "leads to R being killed"? You should tell to the killer not to do it again :). Hi Simon! Sure, but who do you tell it if you don't know the killer? This is all the killer left me with, the 'crime scene' if you like :-) > m <- matrix(0, 90000, 100000) Killed: 9 My colleague Wayne Oldford also tried it on his Mac machine and apparently the

Excessive virtio_balloon inflation can cause invocation of OOM-killer, when Linux is under severe memory pressure. Various mechanisms are responsible for correct virtio_balloon memory management. Nevertheless it is often the case that these control tools does not have enough time to react on fast changing memory load. As a result OS runs out of memory and invokes OOM-killer. The balancing of

Excessive virtio_balloon inflation can cause invocation of OOM-killer, when Linux is under severe memory pressure. Various mechanisms are responsible for correct virtio_balloon memory management. Nevertheless it is often the case that these control tools does not have enough time to react on fast changing memory load. As a result OS runs out of memory and invokes OOM-killer. The balancing of

Hi all, I really don't know where to go from here. I've traced and pasted, but never heard responses.... I'm getting the following (see bottom of this email) in a single day of dmesg....most of the time the error message in the log file is something like: Oct 5 09:21:43 mail1 dovecot: imap(*****): file mbox-save.c: line 280 (mbox_save_init_file): assertion failed:

Under both XEN 3.0.4 (2.6.16.33) and XEN 3.1 (2.6.18), I can make the OOM killer appear in dom0 of my server by doing heavy I/O from within a VM. If I start 5 VMs on the same server, each VM doing constant I/O over its boot disk (read/write a 2GB file), after about 30 minutes the OOM killer appears in dom0 and starts killing processes. This was observed using 256MB in dom0. If I bump the memory in

On 7/27/2018 11:50 AM, Warren Young wrote: > On Jul 27, 2018, at 9:10 AM, Bowie Bailey <Bowie_Bailey at BUC.com> wrote: >> I have a CentOS 7 server that is running out of memory > How do you know that? Give a specific symptom. This was brought to my attention because one program was killed by the kernel to free memory and another program failed because it was unable to allocate