Re: portupgrade causes kernel message: maxproc limit exceeded by uid 0
On 12/05/2010 10:45 AM, Lowell Gilbert wrote: Yuri y...@rawbw.com writes: Beginning at some time less than 1 month ago I started getting such message. Increasing maxproc doesn't help. Current values are like this: kern.maxproc: 6164 kern.maxprocperuid: 5547 What may be causing such condition? limits(1), perhaps? I DoSed a remote box building devel/glib20 too. Just now reproduced it locally. It manifested as a forkbomb somewhere in gnome-libtool while building glib-2.26.1 inside a clean chroot (not a jail). The issue seemed to only manifest within the chroot, regardless of whether the configuration was identical to the host or not. It did not occur when attempting to build on the host machine. Every other package I built worked just fine. I eventually tracked it down to a stray colon at the start of the PATH variable in my chroot build environment: PATH=:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin Thus, it might be a good idea to verify that your build environment variables and config files are sane. == mv -f .deps/gdatetime.Tpo .deps/gdatetime.Po /bin/sh /usr/obj/usr/ports/devel/glib20/work/gnome-libtool --tag=CC --mode=link cc -O2 -pipe -O2 -pipe -march=nocona -fno-strict-aliasing -Wall -L/usr/local/lib -lintl -o strfuncs strfuncs.o ../../glib/libglib-2.0.la -lm mv -f .deps/regex.Tpo .deps/regex.Po /bin/sh /usr/obj/usr/ports/devel/glib20/work/gnome-libtool --tag=CC --mode=link cc -O2 -pipe -O2 -pipe -march=nocona -fno-strict-aliasing -Wall -L/usr/local/lib -lintl -o string string.o ../../glib/libglib-2.0.la -lm printf: Cannot fork: Resource temporarily unavailable printf: Cannot fork: Resource temporarily unavailable printf: Cannot fork: Resource temporarily unavailable printf: Cannot fork: Resource temporarily unavailable printf: Cannot fork: Resource temporarily unavailable /libexec/ld-elf.so.1: Shared object libglib-2.0.so.0 not found, required by printf == -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net cyber...@cyberleo.net Furry Peace! - http://.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade causes kernel message: maxproc limit exceeded by uid 0
Yuri y...@rawbw.com writes: Beginning at some time less than 1 month ago I started getting such message. Increasing maxproc doesn't help. Current values are like this: kern.maxproc: 6164 kern.maxprocperuid: 5547 What may be causing such condition? limits(1), perhaps? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
portupgrade causes kernel message: maxproc limit exceeded by uid 0
Beginning at some time less than 1 month ago I started getting such message. Increasing maxproc doesn't help. Current values are like this: kern.maxproc: 6164 kern.maxprocperuid: 5547 What may be causing such condition? Yuri --- sample log from portupgrade --- mv -f .deps/regex.Tpo .deps/regex.Po /bin/sh /usr/ports/devel/glib20/work/gnome-libtool --tag=CC --mode=link cc -O2 -pipe -fno-strict-aliasing -Wall -L/usr/local/lib -lintl -o markup-escape markup-escape.o ../../glib/libglib-2.0.la mv -f .deps/gdatetime.Tpo .deps/gdatetime.Po /bin/sh /usr/ports/devel/glib20/work/gnome-libtool --tag=CC --mode=link cc -O2 -pipe -fno-strict-aliasing -Wall -L/usr/local/lib -lintl -o markup-subparser markup-subparser.o ../../glib/libglib-2.0.la ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable /printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable cd: can't cd to /snprintf /snprintf /snprintf /snprintf /snprintf /snprintf /snprintf /printf /printf /printf /sprintf GLib-ERROR **: failed to fork test program: Resource temporarily unavailable aborting... GLib-ERROR **: failed to fork test program: Resource temporarily unavailable aborting... cd: can't cd to /snprintf /snprintf /snprintf /snprintf /snprintf /snprintf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Security | Kernel message
A prt of my daily security run: triton.xxx.xxx.xxx kernel log messages: +++ /tmp/security.VnqB8ZT6 2008-10-27 23:53:32.0 +0100 +em0: link state changed to DOWN +em0: link state changed to UP +em0: link state changed to DOWN +em0: link state changed to UP +em0: link state changed to DOWN +em0: link state changed to UP Is there a way of adding the time on every DOWN and UP line? Jos Chrispijn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Security | Kernel message
On Tue, Oct 28, 2008 at 05:26:03PM +0100, Jos Chrispijn wrote: A prt of my daily security run: triton.xxx.xxx.xxx kernel log messages: +++ /tmp/security.VnqB8ZT62008-10-27 23:53:32.0 +0100 +em0: link state changed to DOWN +em0: link state changed to UP +em0: link state changed to DOWN +em0: link state changed to UP +em0: link state changed to DOWN +em0: link state changed to UP Is there a way of adding the time on every DOWN and UP line? No, because the messages are in the kernel log. The kernel itself does not print timestamps, because that's silly. Try doing this: 1) Edit /etc/syslog.conf and enable /var/log/all.log, 2) touch /var/log/all.log 3) chown root:wheel /var/log/all.log 4) chmod 600 /var/log/all.log 5) killall -HUP syslogd Then wait until the next event, and examine /var/log/all.log, which will contain timestamps. Also, are you seeing any watchdog timeout events on em0 as well? If so, please read the Network devices section of my Wiki regarding what this problem could be (specific to certain models of Intel 82573 NIC): http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Security | Kernel message
Jeremy, Uit een eerder bericht (28-10-2008 17:32): No, because the messages are in the kernel log. The kernel itself does not print timestamps, because that's silly. Yes that is .true. Try doing this: Great, will do that! No 'watchdog timeout' events yet :-) thanks for sharing, Jos Chrispijn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Security | Kernel message
On Tuesday 28 October 2008 17:32:36 Jeremy Chadwick wrote: On Tue, Oct 28, 2008 at 05:26:03PM +0100, Jos Chrispijn wrote: A prt of my daily security run: triton.xxx.xxx.xxx kernel log messages: +++ /tmp/security.VnqB8ZT6 2008-10-27 23:53:32.0 +0100 +em0: link state changed to DOWN +em0: link state changed to UP +em0: link state changed to DOWN +em0: link state changed to UP +em0: link state changed to DOWN +em0: link state changed to UP Is there a way of adding the time on every DOWN and UP line? No, because the messages are in the kernel log. The kernel itself does not print timestamps, because that's silly. Try doing this: 1) Edit /etc/syslog.conf and enable /var/log/all.log, Actually, these end up in /var/log/messages in a vanilla system (*.notice). You can modify /etc/periodic/security/700.kernelmsg, by using: fgrep 'kernel: ' /var/log/messages 2/dev/null | where it says: dmesg 2/dev/null Or more prescise: fgrep 'your.host.name kernel: ' /var/log/messages This will give you timestamps with the output. I can't really think of anything that does end up in dmesg and not in /var/log/messages, but I'm sure there are some. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Security / kernel message interpretations please !
I posted about this a few days ago and its appeared again in my security log (the backup routine log appears to be fine) +(sa0:ahc0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 0 0 +(sa0:ahc0:0:6:0): CAM Status: SCSI Status Error +(sa0:ahc0:0:6:0): SCSI Status: Check Condition +(sa0:ahc0:0:6:0): UNIT ATTENTION asc:28,0 +(sa0:ahc0:0:6:0): Not ready to ready change, medium may have changed +(sa0:ahc0:0:6:0): Unretryable error I have googled about and there is some suggestion that a change of tape may cure this ie using DDS4 tapes rather than DDS3 in a DDS4 drive. I also read about Vendor Specific ASCQ but it was beyond me. I am going to leave the same tape in and see if its repeated at tonites backup. If this isnt something serious I will ignore it and go away however I am curious and would really like to know why :) (never stop asking...there are no stupid questions etc) Thanks in advance :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Security / kernel message interpretations please !
In the last episode (May 13), Graham Bentley said: I posted about this a few days ago and its appeared again in my security log (the backup routine log appears to be fine) +(sa0:ahc0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 0 0 +(sa0:ahc0:0:6:0): CAM Status: SCSI Status Error +(sa0:ahc0:0:6:0): SCSI Status: Check Condition +(sa0:ahc0:0:6:0): UNIT ATTENTION asc:28,0 +(sa0:ahc0:0:6:0): Not ready to ready change, medium may have changed +(sa0:ahc0:0:6:0): Unretryable error I have googled about and there is some suggestion that a change of tape may cure this ie using DDS4 tapes rather than DDS3 in a DDS4 drive. I also read about Vendor Specific ASCQ but it was beyond me. I am going to leave the same tape in and see if its repeated at tonites backup. I believe you'll get a UNIT ATTENTION on every media load; it's just how SCSI drivers work. Not sure why it's getting logged to the console, though. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel message = ?
hi, on my freebsd 4.x box I get no matching session as an kernel log. I was wondering what this could mean. thx in advance christian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
PXE booting 5.3-BETA6 kernel message issues
Hello, I did post this to -current a few days ago, but having got no response, perhaps here is a better place for it. I've also noted a few previous attempts to get an answer to this question on freebsd-questions in January and February, but nobody replied. This doesn't seem to be an isolated case.. I've been trying to get 5.3-BETA6 PXE booting; I don't want anything special at the moment, just an NFS mounted root with tools available to perform disaster recovery etc. I've got the kernel transferred via TFTP and an mfsroot. If I use the mfsroot.flp from a release I eventually see sysinstall pop up, so it looks like everything is working, with one exception - the last message I see before sysinstall appears is the acpi.ko loading notification. Where are all the kernel messages going? It makes it quite difficult to construct my own mfsroot that just gives me a prompt when I can't see what's going on :) I've verified that the console is set to vidconsole in the loader; I tried comconsole and attaching a serial console also, same result, no messages. Setting boot_verbose didn't change anything. I'm not sure what else to try. Does anyone have any ideas? Cheers, -- Chris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel message
On Mon, 8 Dec 2003, Michael A. Alestock wrote: What does this message mean??... No debugger in kernel Dec 8 17:40:05 bsd /kernel: No debugger in kernel I hope it isn't anything serious??? I haven't changed or altered anything in a long time. It probably means you accidentally typed the magic debug key combination (usually ctl-alt-esc) at the system console driver but you didn't have options DDB in youer kernel configuration. This is not anything serious. Do man ddb for more information. Dan Strick [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Kernel message
What does this message mean??... No debugger in kernel Dec 8 17:40:05 bsd /kernel: No debugger in kernel I hope it isn't anything serious??? I haven't changed or altered anything in a long time. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel message -- a prank?
with last hour, cvsup current, rebuild everything,... immediately after kernel mount msg for / kernel cranks out msg Be nice to each other, mmmkay? system otherwise fine. Is this a known prank? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: kernel message -- a prank?
[redirected to -current]
On Tuesday, 4 February 2003 at 17:55:42 -0800, [EMAIL PROTECTED] wrote:
with last hour, cvsup current, rebuild everything,... immediately
after kernel mount msg for /
kernel cranks out msg
Be nice to each other, mmmkay?
system otherwise fine. Is this a known prank?
It is now. It's in /sys/kern/init_main.c:
1.112(des 20-Apr-99):
1.224(des 04-Feb-03): printf(Be nice to each other, mmmkay?\n);
1.223(des 04-Feb-03):
1.118(jb 05-May-99): for (path = init_path; *path != '\0'; path =
next) {
But this question should be asked on -current, not -questions.
Greg
--
When replying to this message, please copy the original recipients.
If you don't, I may ignore the reply or reply to the original recipients.
For more information, see http://www.lemis.com/questions.html
See complete headers for address and phone numbers
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
kernel message when sending mail
Each time I send an email using Mutt the following message pops up on the screen: /kernel: Connection attempt to TCP 127.0.0.1:113 from 127.0.0.1:1572 What could be the cause? Using a freshly loaded v4.7 running IPFW with the following in rc.conf firewall_type="open" #wide open when using rc.firewall firewall_script="/etc/rc.firewall" #original and unmodified firewall_enable="NO" #leave firewall with 'pass/block all' line only Also running ipfilter with a ruleset that leaves the firewall wide open. regards from Kjell / LA3SG To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: kernel message when sending mail
On Fri, 31 Jan 2003, Kjell wrote: Each time I send an email using Mutt the following message pops up on the screen: /kernel: Connection attempt to TCP 127.0.0.1:113 from 127.0.0.1:1572 What could be the cause? TCP port 113 is the Auth service. When you send mail, sendmail will attempt to verify the username on the other end of the connection by querying auth. You have auth disabled: if you want to enable it, edit /etc/inetd.conf (the comments in inetd.conf are quite good, but inetd.conf(8) will help too). - Jeff Jirsa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: kernel message
From: adrian kok [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, September 18, 2002 11:55 AM Subject: kernel message Hi all I received the following message from /var/log What is this meaning? Sep 17 12:33:04 mail /kernel: pullup failed i guess your kernel just doesnt work out enough. heh on a more serious note, here is an excerpt from the ipfw man page that may answer your question: There are circumstances where fragmented datagrams are uncondition- ally dropped. TCP packets are dropped if they do not contain at least 20 bytes of TCP header, UDP packets are dropped if they do not contain a full 8 byte UDP header, and ICMP packets are dropped if they do not contain 4 bytes of ICMP header, enough to specify the ICMP type, code, and checksum. These packets are simply logged as ``pullup failed'' since there may not be enough good data in the packet to produce a meaningful log entry. -- dfolkins To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: kernel message
ipfw(8) man page: FINE POINTS · There are circumstances where fragmented datagrams are uncondition ally dropped. TCP packets are dropped if they do not contain at least 20 bytes of TCP header, UDP packets are dropped if they do not contain a full 8 byte UDP header, and ICMP packets are dropped if they do not contain 4 bytes of ICMP header, enough to specify the ICMP type, code, and checksum. These packets are simply logged as ``pullup failed'' since there may not be enough good data in the packet to produce a meaningful log entry. Fragmented packets like that are probably due to broken hardware on your network, although they can be the result of enemy action -CM - Original Message - From: adrian kok [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, September 18, 2002 11:55 AM Subject: kernel message Hi all I received the following message from /var/log What is this meaning? Sep 17 12:33:04 mail /kernel: pullup failed Thank you ___ Do You Yahoo!? Get your free @yahoo.com.hk address at http://mail.english.yahoo.com.hk To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
