Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Sep 2004 15:03:18 +0100
From:      Matthew Seaman <m.seaman@infracaninophile.co.uk>
To:        redmyrlin@eml.cc
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Problems with newsyslog
Message-ID:  <20040910140318.GB50475@happy-idiot-talk.infracaninophile.co.uk>
In-Reply-To: <4141AD8F.9080003@eml.cc>
References:  <4141AD8F.9080003@eml.cc>

next in thread | previous in thread | raw e-mail | index | archive | help

--gatW/ieO32f1wygP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Sep 10, 2004 at 02:35:11PM +0100, redmyrlin@eml.cc wrote:
> I have just acquired a new virtual server and have set up newsyslog.conf=
=20
> to mirror that on my old virtual server.  On my old server the logs are=
=20
> rotated and compressed without any problems.  The old server runs=20
> FreeBSD 4.9.
>=20
> The new server runs FreeBSD 4.10, and I'm getting the following errors=20
> reported by Cron
> -------
> newsyslog: can't notify daemon, pid 84000: Operation not permitted
> newsyslog: log /var/log/maillog.0 not compressed because daemon(s) not=20
> notified
> newsyslog: can't notify daemon, pid 43506: Operation not permitted
> newsyslog: log /var/log/ssl_engine_log.0 not compressed because=20
> daemon(s) not notified
> ...
> ------
>=20
> pid 84000 refers to /usr/sbin/syslogd -s
> pid 43506 refers to /usr/local/sbin/httpd -DSSL
>=20
> I cannot see any difference in way I have setup newsyslog and am at a=20
> loss to know how to proceed.
>=20
> Any help would be greatly appreciated.

Usually this error message means that the daemon in question has died
or in some way been restarted so that the PID number that newsyslog
reads out of one of the files under /var/run has become bogus (in this
case. /var/run/sendmail.pid or /var/run/httpd.pid).  However, if
sendmail or apache httpd are running, and you haven't specifically
configured them not to, then they will write their PIDs into those
files.

The other possibility is that you are trying to run newsyslog using a
non-root UID, which means it will not be permitted to send signals to
arbitrary processes, or that the newsyslog process does not have
sufficient privileges to read those PID files.

	Cheers,

	Matthew

--=20
Dr Matthew J Seaman MA, D.Phil.                       26 The Paddocks
                                                      Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey         Marlow
Tel: +44 1628 476614                                  Bucks., SL7 1TH UK

--gatW/ieO32f1wygP
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)

iD8DBQFBQbQmiD657aJF7eIRAq/LAJ4xVDPlkkgpB0mBjZy9nGcseTBEfQCgmi75
nGAZe21WC7ejszJeXw0Oxyo=
=Ivfi
-----END PGP SIGNATURE-----

--gatW/ieO32f1wygP--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040910140318.GB50475>