| The error log also stopped working on the 31st - probably because of trying to use an arcane php configuration. Does any of this make sense to you?
[Fri Dec 31 14:37:46.252199 2021] [mpm_prefork:notice] [pid 1833] AH00169: caught SIGTERM, shutting down Failed loading /usr/local/opt/php/lib/php/20210902/opcache.so: dlopen(/usr/local/opt/php/lib/php/20210902/opcache.so, 0x0009): tried: '/usr/local/opt/php/lib/php/20210902/opcache.so' (code signature in <6449B372-19F0-3B12-8B3D-5FF5F56DAEC8> '/usr/local/Cellar/php/8.1.0/lib/php/20210902/opcache.so' not valid for use in process: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.), '/usr/lib/opcache.so' (no such file), '/usr/local/Cellar/php/8.1.0/lib/php/20210902/opcache.so' (code signature in <6449B372-19F0-3B12-8B3D-5FF5F56DAEC8> '/usr/local/Cellar/php/8.1.0/lib/php/20210902/opcache.so' not valid for use in process: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.), '/usr/lib/opcache.so' (no such file) [Fri Dec 31 14:37:46.505444 2021] [mpm_prefork:notice] [pid 1843] AH00163: Apache/2.4.51 (Unix) PHP/8.1.0 configured -- resuming normal operations [Fri Dec 31 14:37:46.505472 2021] [core:notice] [pid 1843] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND' [Fri Dec 31 16:59:13.624383 2021] [mpm_prefork:notice] [pid 1843] AH00169: caught SIGTERM, shutting down
On 1/4/2022 8:37 PM, James Coyle wrote:
I have checked both, but have made no changes to the locations of
either the access log nor the error log:
CustomLog
"/private/var/log/apache2/access_log” common
As per these instructions, I have not
created a Virtual Host container, so ostensibly the log
files should not be elsewhere:
# The location and format of the access
logfile (Common Logfile Format).
# If you do not define any access logfiles
within a <VirtualHost>
# container, they will be logged here.
Contrariwise, if you *do*
# define per-<VirtualHost> access
logfiles, transactions will be
# logged therein and *not* in this file.
Might the change
I added to the DirectoryIndex be culprit? i.e. the
index.php file?
# DirectoryIndex: sets
the file that Apache will serve if a directory
# is requested.
#
<IfModule
dir_module>
DirectoryIndex
index.php index.html
</IfModule>
Thank you
I don't believe DirectoryIndex would be relevant to logging, but
simply what content to provide when presented with a directory
request.
How about your error log? Is it available and does it offer any clue
when you restart Apache?
If you have separate SSL configs do the SSL configs present their
own log configs?
Outside of those thoughts, are the directories listed in the log
configs writable by root assuming root starts Apache?
Jim
On 1/4/2022 8:11 PM, James Coyle wrote:
I recently added PHP
and MySql to my Apache setup, and now notice that the
access and error logs are not working. (The site IS
working)
They both stopped working on the 31st - I don’t know
if that is relevant or not. I have not changed the
location of the logs and I have not added a Virtual
Host.
I’d be grateful if someone could help me rectify this.
Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail:
users-help@xxxxxxxxxxxxxxxx
It would help if you provide some more information such
as relevant Apache log configs such as:
CustomLog
ErrorLog
Search for those settings throughout your Apache config
files.
Perhaps by reviewing those settings the answer will
become apparent.
--
Jim Albert
---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail:
users-help@xxxxxxxxxxxxxxxx
--
Jim Albert
|
