PF_LOCAL sockets problem on a md fs

From: Bjoern A. Zeeb (bzeeb-lists_at_lists.zabbadoz.net)
Date: 01/18/04

  • Next message: Alexander Leidinger: "Re: sound/pcm/* bugs" 
    Date: Sun, 18 Jan 2004 09:41:38 +0000 (UTC)
To: FreeBSD current mailing list <current@freebsd.org>

    Hi,

    I am running on a MD
            host# mount
            /dev/md0c on / (ufs, local)
            devfs on /dev (devfs, local)
            procfs on /proc (procfs, local)

    on startup syslogd, postfix, ppp and racoon are started.
    While for postfix the relative sockets show up in filesystem they
    do not (with absolut socket names) for syslogd and ppp (at least
    not for ppp).

    The first time I do a ls -la /var/run; ls -la /var/run/ppp there is
    neither a log socket nor the ppp socket does show up.

    find / -type s will only shows the sockets from postfix while
    netstat -an -f unix whill show them all (this is from ppp and syslogd
    too). according to fstat all the sockets are open too.

    It gets even more confusing:

    logging works at this point for (almost) everything (syslogd logs
    to another host): I get ppp logs, racoon logs and klog info.

    Now I kill ppp and start it again and the ppp local IPC socket also
    shows up in filessystem but ppp no longer logs (mostly because it
    cannot find /var/run/log ?).

    So I restart syslogd and /var/run/log shows up too and somewhen after
    this ppp and racoon do logging and postfix starts to log too.

    At boot startup order is like this:
            syslogd
            postfix
            ppp
            racoon

    I have seen similar problems for weeks but never investigated.

    The machine is a HEAD from about 20040117-0934 UTC.

    Anybody any ideas ? 

    -- 
Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT
56 69 73 69 74				http://www.zabbadoz.net/
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
  • Next message: Alexander Leidinger: "Re: sound/pcm/* bugs"

    Relevant Pages

    • Re: filling up UDP socket buffers like mad
      ... the box starts dropping UDP due to full socket ... 168725 dropped due to full socket buffers ... named and syslogd are in cron to restart every 15 minutes. ...
      (freebsd-questions)
    • syslogd socket (was Re: PING: Igor S. , regarding Kerberos v4.)
      ... a socket and convention requires syslog to use a privileged port. ... syslogd is also "privilege separated" for security. ... To "disable" the feature of creating the socket would require ...
      (comp.unix.bsd.openbsd.misc)
    • Re: linksys logs and snmp
      ... >> snmp logs broadcast from my linksys router. ... just want a small simple daemon doing this little ... ErrCode = SockLoadFuncs ... Say 'SockSocket() failed:' Socket ...
      (comp.os.linux.networking)
    • Problem re-stated
      ... Starting system log daemon: syslogd ... I had checked that 'Unix domain socket' was selected in the kernel config. ...
      (Debian-User)
    • Re: fast reliable IPC
      ... written to the file (socket is not fast enough ?). ... Are you using a queue between the threads? ... logs between the threads. ... install this componnent on every PC I install the logger. ...
      (microsoft.public.dotnet.languages.csharp)