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
|Anonymous | Login||2020-12-02 12:19 UTC|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002550||Endian Firewall||Other Scripts||public||2009-12-16 14:10||2010-11-22 12:06|
|Priority||high||Severity||minor||Reproducibility||have not tried|
|Target Version||2.3.1||Fixed in Version||2.3.1|
|Summary||0002550: Message on the gui for a new kernel installed|
|Description||I've noticed that with the latest updates although a new kernel has been installed the user is not warned via gui that the system must be rebooted.|
I remember it happened with 2.2
This has not been implemented within dashboard!
Dashboard should also display such a message (like the old main.cgi did), if /var/tmp/oldkernel does exist.
Please discuss with christian for scheduling and GUI positioning
i think it's more or less important. Otherwise people do not reboot after 2.3 updates and that causes some iptables things misbehave
migration will reboot automatically
If you don't reboot ipsec stop working because of a missing module:
FATAL: Could not load /lib/modules/184.108.40.206-72.e18/modules.dep No such file or directory
I think this issue is also related to the kernel upgrade:
df: cannot read table of mounted filesystems: No such file or directory
It happened on two systems and after the reboot it was resolved.
df does not work anymore because the /etc/mtab link to /proc/mounts will be removed with the upgrade. the boot process creates a correct mtab file, so after reboot this is fixed.
it should not affect the kernel check script /usr/local/bin/checkkernel.sh, which understands if there was a kernel upgrade and creates a flag file in /var/tmp/oldkernel, if a reboot is necessary.
however, within the dashboard it's not implemented anymore to react upon that flag-file and display the boot message, so that's to fix whether upgrade does work or not.
|Feb 5 10:10:20 efw-1259685155 ipsec_setup: FATAL: Could not load /lib/modules/220.127.116.11-72.e18/modules.dep: No such file or directory|
|well ok.. this happens because a kernel upgrade need a reboot.|
|now dashboard shows kernel version and instead of the version a "reboot required" message, if /var/tmp/oldkernel exists|
|2009-12-16 14:10||luca-endian||New Issue|
|2009-12-19 04:11||peter-endian||Note Added: 0003609|
|2009-12-19 04:11||peter-endian||Assigned To||=> simon-endian|
|2009-12-19 04:11||peter-endian||Status||new => confirmed|
|2009-12-19 04:11||peter-endian||Target Version||=> 2.3.1|
|2009-12-19 04:13||peter-endian||Note Added: 0003610|
|2010-01-25 08:47||luca-endian||Tag Attached: purple|
|2010-01-25 08:48||luca-endian||Note Added: 0003697|
|2010-01-29 10:26||luca-endian||Note Added: 0003723|
|2010-02-01 16:51||peter-endian||Note Added: 0003728|
|2010-02-08 10:05||luca-endian||Note Added: 0003749|
|2010-02-08 15:40||luca-endian||Relationship added||parent of 0002660|
|2010-02-08 15:48||peter-endian||Note Added: 0003754|
|2010-02-10 10:38||luca-endian||Priority||normal => high|
|2010-02-15 04:06||simon-endian||Note Added: 0003778|
|2010-02-15 04:06||simon-endian||Status||confirmed => resolved|
|2010-02-15 04:06||simon-endian||Fixed in Version||=> 2.3.1|
|2010-02-15 04:06||simon-endian||Resolution||open => fixed|
|2010-11-22 12:06||peter-endian||Status||resolved => closed|
|2010-12-06 08:32||luca-endian||Relationship added||related to 0003355|
|Copyright © 2000 - 2012 MantisBT Group|