Re: what means: sockstat: sysctl(): No such process
On Fri, 8 Sep 2006 09:18:32 -0500 Dan Nelson [EMAIL PROTECTED] wrote: In the last episode (Sep 07), [EMAIL PROTECTED] said: hallo list while running [ $(sockstat | grep -c saslauthd) -gt 90 ] /usr/local/etc/rc.d/saslauthd restart via cron (/etc/crontab, as root) (why i do this is of no importance for this question), i get from time to time - about 3-4 times a day, cronjob runs every 11 minutes - the message: sockstat: sysctl(): No such process i do not understand why i get this only sometimes, and what this exactly means. Sockstat first gets a list of all open sockets, then looks up the command name for each one. If the process has exited before the name is looked up, you get the warning, and sockstat prints ?? as the process name. You can quiet it by redirecting stderr to /dev/null: sockstat 2/dev/null thank you for explanation. i will quieten it by redirecting stderr as you suggested. ¨reinhard -- Algol-60 surely must be regarded as the most important programming language yet developed. -- T. Cheatham ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: openldap-2.3 won't start on a 6.1R system
had the same problem, went away after disabling WITH_SHELL, there also seems to be a related entry in /usr/ports/UPDATING: [..] 20060526: AFFECTS: users of net/openldap23-server AUTHOR: [EMAIL PROTECTED] The setting of SHELL backend has been inverted to off by default, because of the side effect it can cause. ... ... You are advised to do a make config in the net/openldap23-server directory *before* upgrading. [..] lg, ~reinhard Am Mon, 22 May 2006 15:23:53 -0700 (PDT) schrieb Jon Falconer [EMAIL PROTECTED]: Greetings, I had a server running FreeBSD 6.0 Release with openldap 2.3.20 running fine (along with postfix, cyrus-sasl, courier-imap, bdb-4.3, etc.) I needed to move the system to new hardware, so I rebuild it using 6.1 Release. The ports tree has been updated so openldap 2.3.23 is current. After building and installing this port, and copying my config files from my 6.0 system, openldap server will not start. It silently quits with no error or log entries when run using /usr/local/etc/rc.d/slapd start. However typing: /usr/local/libexec/slapd -Tt yields: /libexec/ld-elf.so.1: /usr/local/lib/libldap_r-2.3.so.2: Undefined symbol pthread_getconcurrency My build options for openldap are: %cat /var/db/ports/openldap23/options # This file is auto-generated by 'make config'. # No user-servicable parts inside! # Options for openldap-server-2.3.23 _OPTIONS_READ=openldap-server-2.3.23 WITH_SASL=true WITHOUT_PERL=true WITH_SHELL=true WITHOUT_ODBC=true WITHOUT_SLP=true WITHOUT_SLAPI=true WITH_TCP_WRAPPERS=true WITH_BDB=true WITHOUT_ACCESSLOG=true WITHOUT_AUDITLOG=true WITHOUT_DENYOP=true WITHOUT_DYNGROUP=true WITHOUT_DYNLIST=true WITHOUT_LASTMOD=true WITHOUT_PPOLICY=true WITHOUT_PROXYCACHE=true WITHOUT_REFINT=true WITHOUT_RETCODE=true WITHOUT_RWM=true WITHOUT_SYNCPROV=true WITHOUT_TRANSLUCENT=true WITHOUT_UNIQUE=true WITHOUT_VALSORT=true WITHOUT_ACI=true WITH_DYNAMIC_BACKENDS=true % I don't know if this is a problem with the db43 library or something else. Any pointers are welcome. Thanks, Jon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- reinhard weismann creative media gmbh ditscheinergasse 4/3, a-1030 vienna t: +43 1 7150227 74 f: +43 1 7150227 99 http://www.creative.co.at ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: broken ports
Thank you very much for the info's in the meanwhile, the problem got solved, after upgrading p5-Mail-DomainKeys-0.23 to 0.80 yesterday, p5-Mail-SpamAssassin upgrade also worked. The reason I'm asking is that segmentation faults are often caused by failing hardware (faulty memory chip, overheating CPU etc). In your case, hardware fault is even more likely since you noticed yourself that the port builds successfully on another machine. i don't think so, this problem appeared on two of my machines, both installed with 5.4, but not on another machine with 5.3 regards, reinhard On Thu, 06 Oct 2005 15:12:40 +0300 Toomas Aas [EMAIL PROTECTED] wrote: Reinhard Weismann wrote: does anybody know where to report broken ports, or, where to get information if/why a port currently is broken. From your description I am not at all sure that the port is broken in this case. But since you asked... If you are sure that the port really is broken, you should first see whether somebody has already noted this, by going to http://www.freebsd.org/support/bugreports.html and searching for existing reports on a particular port. You can also look at the archive of freebsd-ports mailing list by going to http://www.freebsd.org/search/search.html#mailinglists FreeBSD has a large and active user community, so real port breakage is usually found very fast and by the time you notice it, it's very likely that the problem has already been found and even fixed. Cvsupping your ports tree and trying to build the port again is often a quick fix to port build problems. If you dont see any existing reports on your problem AND YOU ARE STILL SURE THAT IT IS ACTUALLY A PROBLEM WITH THE PORT then it's time to submit a bug report at http://www.freebsd.org/support/bugreports.html in this case on my 5.4-RELEASE-p6 (i386) installations, the port mail/p5-Mail-SpamAssassin (p5-Mail-SpamAssassin-3.1.0) does not compile, i.e. i get [..] Segmentation fault (core dumped) *** Error code 139 [..] Does this happen only to this port? Can you build other ports successfully? Can you successfully run 'make buildworld'? The reason I'm asking is that segmentation faults are often caused by failing hardware (faulty memory chip, overheating CPU etc). In your case, hardware fault is even more likely since you noticed yourself that the port builds successfully on another machine. -- Toomas Aas -- If you give Congress a chance to vote on both sides of an issue, it will always do it. -- Les Aspin, D., Wisconsin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
broken ports
does anybody know where to report broken ports, or, where to get information if/why a port currently is broken. in this case on my 5.4-RELEASE-p6 (i386) installations, the port mail/p5-Mail-SpamAssassin (p5-Mail-SpamAssassin-3.1.0) does not compile, i.e. i get [..] Segmentation fault (core dumped) *** Error code 139 [..] when doing a `make configure` (regardless of which options are enabled/disabled and which optional modules are installed) on another installation with 5.3, but same perl-version (v5.8.7 built for i386-freebsd-64int) it works. -- Everything is controlled by a small evil group to which, unfortunately, no one we know belongs. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
