SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264

0002660: Kernel and Modules mismatch - MantisBT
MantisBT - Endian Firewall
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0002660Endian FirewallHardware related (kernel, drivers, hardware)public2010-02-08 15:382010-02-10 13:36
Reporteraender 
Assigned To 
PrioritynormalSeveritycrashReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version2.3 
Target VersionFixed in Version 
Customer Importance
Customer Occurrences
Queue
Summary0002660: Kernel and Modules mismatch
DescriptionI have the latest 2.3 enterprise with all patches installed.

IPSec won´t work correct. Here the logs:

ipsec_setup Starting Openswan IPsec 2.4.15...
System 2010-02-04 21:16:37 ipsec_setup: FATAL: Could not load /lib/modules/2.6.22.19-72.e18/modules.dep No such file or directory
System 2010-02-04 21:16:37 ipsec_setup: FATAL: Could not load /lib/modules/2.6.22.19-72.e18/modules.dep No such file or directory

Looks like IPSec want to start old kernel modules....
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
child of 0002550closed simon-endian Message on the gui for a new kernel installed 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-02-08 15:38aenderNew Issue
2010-02-08 15:40luca-endianRelationship addedchild of 0002550
2010-02-08 15:41luca-endianNote Added: 0003753
2010-02-10 10:38luca-endianStatusnew => confirmed
2010-02-10 13:35aenderNote Added: 0003761
2010-02-10 13:36aenderStatusconfirmed => closed
2010-02-10 13:36aenderResolutionopen => fixed

Notes
(0003753)
luca-endian   
2010-02-08 15:41   
That's because a new kernel has been installed.

You just have to reboot the system.
(0003761)
aender   
2010-02-10 13:35   
Thanks.

A reboot solves the problem.