syslogd 1.3 dumps core, what's wrong ?

syslogd 1.3 dumps core, what's wrong ?

Post by Kari Kivent » Tue, 10 Dec 1996 04:00:00



"Out of the box" Slackware 3.1 (Sep 96) kernel 2.0.0 installation,
(upgraded with XF86 3.2 for MGA)
syslogd ver 1.3: when started from rc.S, waits about ten seconds; creates
process for a few seconds (as seen from top), then quits and dumps core.
When started manually in debug mode (command syslogd -d),
gives immediately "Segmentation fault. Core dumped."

Size of syslogd is **500, when installation CD lists **776.
Installed binary from syslogd.tgz anew, same size (**500), same result.
Compiled it from source, same size (**500), same result.

Everything else (of what I have tested) seems to work OK (Netscape 3.0,
JDK102, NCSA httpd 1.5.2a, ...)

klogd seems to work, when started manually with given target file.

Anybody seen this before ?

-Kari-

 
 
 

syslogd 1.3 dumps core, what's wrong ?

Post by Marshall E. Gigue » Tue, 10 Dec 1996 04:00:00


   "Out of the box" Slackware 3.1 (Sep 96) kernel 2.0.0 installation,
   (upgraded with XF86 3.2 for MGA)
   syslogd ver 1.3: when started from rc.S, waits about ten seconds; creates
   process for a few seconds (as seen from top), then quits and dumps core.
   When started manually in debug mode (command syslogd -d),
   gives immediately "Segmentation fault. Core dumped."

   Size of syslogd is **500, when installation CD lists **776.
   Installed binary from syslogd.tgz anew, same size (**500), same result.
   Compiled it from source, same size (**500), same result.

   Everything else (of what I have tested) seems to work OK (Netscape 3.0,
   JDK102, NCSA httpd 1.5.2a, ...)

   klogd seems to work, when started manually with given target file.

   Anybody seen this before ?

   -Kari-

I had the same problem with Slackware.  For some reasone syslogd 1.3
is very particular about the domain name.  You need to do two things:

1. be sure your "domainname" is set at boot time.  Look in /etc/rc.d/rc.M.
Add a line like:

        /bin/domainname `cut -f2,3,4 -d. /etc/HOSTNAME`

2. In your /etc/hosts file be sure you host is defined somewhere, e.g.

        127.0.0.1       localhost       my.host.domain

I know this isn't quite nice, but it works for me and syslogd should
stop crashing and littering the place with core files.

regards,
-Marsh
--
Marshall E. Giguere                     508.448.3188 voice
Data EXchange Associates, Inc.          508.448.3216 FAX
509 Longley Road                        
Groton,  MA  01450                      www.dexa.com/~dexa

 
 
 

syslogd 1.3 dumps core, what's wrong ?

Post by darre » Fri, 13 Dec 1996 04:00:00


You might also like to replace the4 standard syslogd with a thing called
syslog-fifo, which is available on sunsite in system/Daemons...

I've just installed it and it seems to work, whereas the other changes
people have suggested here made no difference at all for me...

cheers




>    "Out of the box" Slackware 3.1 (Sep 96) kernel 2.0.0 installation,
>    (upgraded with XF86 3.2 for MGA)
>    syslogd ver 1.3: when started from rc.S, waits about ten seconds; creates
>    process for a few seconds (as seen from top), then quits and dumps core.
>    When started manually in debug mode (command syslogd -d),
>    gives immediately "Segmentation fault. Core dumped."

>    Size of syslogd is **500, when installation CD lists **776.
>    Installed binary from syslogd.tgz anew, same size (**500), same result.
>    Compiled it from source, same size (**500), same result.

>    Everything else (of what I have tested) seems to work OK (Netscape 3.0,
>    JDK102, NCSA httpd 1.5.2a, ...)

>    klogd seems to work, when started manually with given target file.

>    Anybody seen this before ?

>    -Kari-

> I had the same problem with Slackware.  For some reasone syslogd 1.3
> is very particular about the domain name.  You need to do two things:

> 1. be sure your "domainname" is set at boot time.  Look in /etc/rc.d/rc.M.
> Add a line like:

>    /bin/domainname `cut -f2,3,4 -d. /etc/HOSTNAME`

> 2. In your /etc/hosts file be sure you host is defined somewhere, e.g.

>    127.0.0.1       localhost       my.host.domain

> I know this isn't quite nice, but it works for me and syslogd should
> stop crashing and littering the place with core files.

> regards,
> -Marsh
> --
> Marshall E. Giguere                        508.448.3188 voice
> Data EXchange Associates, Inc.             508.448.3216 FAX
> 509 Longley Road                  
> Groton,  MA  01450                 www.dexa.com/~dexa

 
 
 

1. CDE 1.3: Hangs/Core Dumps for automounted logins: What am I doing wrong?

Problem:
CDE hangs / dumps core when I login in with my automounted account.  I
setup a non-automounted test account and it works fine.
The workstation is an Ultra 10 running Solaris 7 with the latest Rec/Sec
Patch Cluster.  What am I doing wrong?

/var/adm/messages:
Sep  7 20:16:34 pittysing /usr/dt/bin/ttsession[977]: Could not find
mount point for /etc/tt/types.xdr
Sep  7 20:16:34 pittysing dtwm[980]: libtt[980]: libtt:
startup_ttsession("ttsession -s -d :0.0") failed with code -1, see
syslog

/etc/auto_master:
/net            -hosts          -nosuid,nobrowse
/home           auto_home       -nobrowse
/xfn            -xfn

/etc/auto_home:
*       pittysing:/export/home/&

/etc/dfs/dfstab:
/usr/sbin/share -F nfs -o rw=pittysing -d "home dirs"  /export/home
/usr/sbin/share -F nfs -o ro -d "CD-ROM"  /cdrom/cdrom0

Thanks,
Carl

2. "su" not working correctly

3. Slackware '96 - Syslogd won't run, craps out with a core dump...

4. A little bit of anti-spam fun

5. jdk1.1.3 and RH5 == core dump ?

6. two ethernet cards in one box - naming

7. DP2 Java 1.3 makes core dump

8. Wireless router w/PPPoE - How To - Please Help

9. apache 1.1.1 + ssl 1.3 -> core dump???

10. Mozilla compiled with NetBSD 1.3, core dumped

11. dump core or not dump core

12. core dumps core dumps everywhere...

13. Syslogd dumps core