Unable to write in the "logs" directory

1,108 views
Skip to first unread message

kmu...@nmu.edu

unread,
Jun 3, 2021, 9:54:40 AM6/3/21
to SimpleSAMLphp
I am upgrading my SPs and IDPs from 1.18.8 to 1.19.1 

With 1.19.1 I receive the following error on the SP that I upgraded 

SimpleSAML\Error\Error: UNHANDLEDEXCEPTION
Backtrace:
1 www/_include.php:17 (SimpleSAML_exception_handler)
0 [builtin] (N/A)
Caused by: RuntimeException: Unable to write in the "logs" directory (/var/simplesaml/simplesamlphp-1.19.1//log/).
Backtrace:
5 vendor/symfony/http-kernel/Kernel.php:691 (Symfony\Component\HttpKernel\Kernel::buildContainer)
4 vendor/symfony/http-kernel/Kernel.php:595 (Symfony\Component\HttpKernel\Kernel::initializeContainer)
3 vendor/symfony/http-kernel/Kernel.php:136 (Symfony\Component\HttpKernel\Kernel::boot)
2 vendor/symfony/http-kernel/Kernel.php:196 (Symfony\Component\HttpKernel\Kernel::handle)
1 lib/SimpleSAML/Module.php:198 (SimpleSAML\Module::process)
0 www/module.php:10 (N/A)

My config.php contains 

    'loggingdir' => 'log/',
    'logging.handler' => 'syslog',

I've been running with this setup for years and the logs are definetly being handled by the syslog daemon.  

I tried setting the loggindir to an empty string, but I still get an error.  

I can make the log folder writable, but nothing gets written there. 

I'm guessing there is now a check for write access which wasn't there before?

Nicolas Roggli

unread,
May 25, 2022, 8:10:38 AM5/25/22
to SimpleSAMLphp
Got stucked the same...
Put the absolute path and problem is solved

Reply all
Reply to author
Forward
0 new messages